https://web.archive.org/web/20180514151834/http://archagon.net/blog/2018/03/24/data-laced-with-history/
This faggot wanted to implement multiplayer document editing, and he wanted to do it for Apple devices using Apple provided lib, CloudKit. CloudKit is so locked down (wouldn't want you goys running code on Apple servers) and stupid, that the madman decides to figure out how to do the whole thing with purely stupid servers, i.e. acting as dumb transport pipes and nothing more.
This has some very interesting benefits. All the magic happens clientside, meaning this can be used in P2P networks with no single authoritative source of truth at all. He implements an example for a single datatype with a demo app (just editing text) and then expands in the rest of the article on applications and implementations for other more complex datatypes.
What are the ramifications of this type of technology? Collaborative editing is really just a specific example of the general problem this is meant to handle: merging divergent changes to a document. No more worrying about overwrites or data loss with distributed file syncing systems. And I wonder what it could mean for DVCS as well.
Pic related is showing off a simple demo for multiplayer svg editing.