4 ms·

Anyone know of any commenting systems that work on IPFS? In theory how would this work? Could there be some distributed application that stores individual comm

Anyone know of any commenting systems that work on IPFS? In theory how would this work? Could there be some distributed application that stores individual comments on ipfs and serves as some type of routing mechanism or lambda function to aggregate comments into a master thread which can be continuously updated as a static files stored on ipfs?

dane-pgp 5y ago
One of the building blocks for such a system might be something like: https://webmention.io/ https://webmention.io/
- chriswarbo 5y ago
  WebMention requires a server, so it would have all the same problems as other approaches. The fundamental problem is that when a page is created, we don't know what address the comments will get (since it will be based on their content). We can easily look backwards, from a comment to all of the previous thread, e.g.: Page <- 1stComment <- 2ndCommentB <- 3rdComment <- ... The problem is those arrows only point one way; we need to know a name/URL for a comment, rather than the page. To solve this we need a mutable reference, like DNS, IPNS, some third-party service, etc. If we have that, there are lots of things we could use to accumulate and render comments (like WebMention).
  - uncomputation 5y ago
    Say the page is “Hello world!” (CID: `QmXgBq2xJKMqVo8jZdziyudNmnbiwjbpAycy5RbfDBoJRM`), then the comments can “point to” this CID `QmXgB…` and so on. The problem to me is not necessarily the direction of the graph but the existence of this graph at all. IPFS seems to have no method of creating “references” to other hashes, but if it did then I can see comments working unless I’m missing something.
    - chriswarbo 5y ago
      Yes that's exactly the problem: comments can include a reference to the page (via its URL); they can also reference any comments they're replying too (via their URL). Those URLs are the 'arrows' that I drew. > IPFS seems to have no method of creating “references” to other hashes Such references would be arrows pointing the other way.

dane-pgp 5y ago

One of the building blocks for such a system might be something like: https://webmention.io/ https://webmention.io/

chriswarbo 5y ago
WebMention requires a server, so it would have all the same problems as other approaches. The fundamental problem is that when a page is created, we don't know what address the comments will get (since it will be based on their content). We can easily look backwards, from a comment to all of the previous thread, e.g.: Page <- 1stComment <- 2ndCommentB <- 3rdComment <- ... The problem is those arrows only point one way; we need to know a name/URL for a comment, rather than the page. To solve this we need a mutable reference, like DNS, IPNS, some third-party service, etc. If we have that, there are lots of things we could use to accumulate and render comments (like WebMention).
- uncomputation 5y ago
  Say the page is “Hello world!” (CID: `QmXgBq2xJKMqVo8jZdziyudNmnbiwjbpAycy5RbfDBoJRM`), then the comments can “point to” this CID `QmXgB…` and so on. The problem to me is not necessarily the direction of the graph but the existence of this graph at all. IPFS seems to have no method of creating “references” to other hashes, but if it did then I can see comments working unless I’m missing something.
  - chriswarbo 5y ago
    Yes that's exactly the problem: comments can include a reference to the page (via its URL); they can also reference any comments they're replying too (via their URL). Those URLs are the 'arrows' that I drew. > IPFS seems to have no method of creating “references” to other hashes Such references would be arrows pointing the other way.