research-CRDT

The IPFS folks also have an excellent compilation of resources on CRDTs available here: https://github.com/ipfs/research-CRDT

I found it useful the IPFS research repository in Github [1], there are a lot of resources there including background concepts. [1] https://github.com/ipfs/research-CRDT

CRDTs are quite actively discussed in the IPFS community, in particular here: https://github.com/ipfs/research-CRDT/ (lots of great resources if you're interested in CRDTs) Also check out automerge, a CRDT that aims to be as JSON-like as possible: https://github.com/automerge/automerge Martin Kleppmann (one of the creators of Automerge) has given several great in-depth talks about it, eg. https://www.youtube.com/watch?v=yCcWpzY8dIA

If you just google CRDT right now, you can easily find a bunch of latest works about CRDT, like https://github.com/ipfs/research-CRDT , http://archagon.net/blog/2018/03/24/data-laced-with-history/ and http://y-js.org/#!/examples. One of the conclusion in the paper "So far, CRDT for co-editing has been confined to plain-text editing; it is unknown whether CRDT solutions can be extended for supporting real world co-editors beyond plain-text editing." is definitely not true.

Recently one guy reverse engineered Apple Notes. It is a CRDT. I personally made a CRDT sync for Yandex. There is also list on Github... https://github.com/ipfs/research-CRDT/issues/40

Big fan of IPFS here, but silly question, isn't a status page suppose to have realtime updates of whether a service is online or not? This doesn't seem like a good fit unless you're using some realtime CRDT adapter on top like they list here https://github.com/ipfs/research-CRDT/blob/master/Readme.MD (disclaimer: I'm the author of https://github.com/amark/gun, which is one of the listed options). The StatusPage link is sparse on info, anybody know how it works underneath? Sorry if I'm confused on how status pages are supposed to work, can it really be static if it is supposed to be reporting services uptime liveliness (and thus requires some type of realtime monitoring)??

The next step after DAGs is CRDTs. They have a research page on this: https://github.com/ipfs/research-CRDT One of them is us (https://github.com/amark/gun), David reached out the other week, now we're trying to find time to discuss with Juan how to best integrate.

Hi Mark, Thanks for your interest! Off the CRDT libraries we analysed, Y.js was the one we picked up as it very modular, so that we could create our own connector and database layer. These are all open-source: https://github.com/ipfs-shipyard/y-ipfs-connector and the encryption layer wrapping the database adaptor: https://github.com/pgte/y-indexeddb-encrypted/tree/encrypted About the richtextdetails, the CRDT is based off of Quill.js deltas (https://github.com/quilljs/delta), composed by an array of such operations. Anyway, this is all interim work, and we plan on making this independent of any specific library by implementing a generic CRDT on top of IPFS DAG and Pubsub APIs. If you're interested you can follow / chime in here: https://github.com/ipfs/research-CRDT/issues/11

Hi Mark, Congratz on developing Gun! I've looked at it before and I was super impressed! The decision to use Y.js instead was done due to its modularity. We added IPFS support by simply publishing a connector https://github.com/ipfs-shipyard/y-ipfs-connector which Kevin Jahns later added to the list of connectors - https://github.com/y-js/yjs/issues/77 We have linked Y.js from the page header, if you click the word CRDT it takes you to Y.js directly. Nevertheless, I agree that we need to make it more obvious How we appreciate all the work that Kevin has put into Y.js :) Do not worry, PeerPad nor our CRDT usage is finished, there will be a lot more! (In fact, PeerPad was built with little less than 4 weeks of actual dev time, there is so much more we can do). I'm following up by email, I'm interested in testing Gun as well. Meanwhile, join