Thank you for the great work on this project! I have just started digging into the white paper and documentation, and have been learning a lot. The contract delegation mechanism is well designed, the ability to incorporate Activity Streams 2.0 is nice, and I also look forward to seeing how the result of chain selection be.
We at Matters Lab are solving a very similar problem. We have nearly 80k content creators, mostly Chinese speakers, to whom decentralization and censorship-resilience are high priorities. We have been storing content with IPFS in the production environment for 3 years and will move our social and content graph to an Etheruem layer 2 next year, likely Polygon.
Our goal has been to find the simplest way to build a shared social & content graph that actually works while keeping the cost low. This is similar to DSNP, but with a smaller scope: instead of a full-fledged protocol, we are aiming at a data schema that fulfills our current needs and can be iterated on later. Therefore we are only defining a set of on-chain events that signifies updates on the social & content graph, which can be aggregated (and upgraded) by indexers such as The Graph, servers, or frontend clients.
The event spec we are developing looks very similar to the Announcement Types defined in DSNP. So my question is if we only use this subset of DSNP spec, are there any ways for our graph to be interoperable with the graph that DSNP is building?
Or frame it another way: in DSNP’s design, what is the minimal requirement for graph interoperability?
Thank you in advance and congrats again for the great work!