I've been building apps that meet this criteria for several years now. It's nice to see the concept getting some attention here. The only thing I'll point out

I've been building apps that meet this criteria for several years now. It's nice to see the concept getting some attention here. The only thing I'll point out is that CouchDB getting rated "partially meets the idea" seems pretty weak to me. They reference v2.1 but the latest version is 2.3.1 and here's link to the docs on how conflict resolution is dealt with: https://docs.couchdb.org/en/latest/replication/conflicts.html https://docs.couchdb.org/en/latest/replication/conflicts.htm... If finer grained control is needed it would be up to the developer to implement it, and it really shouldn't be difficult to do that. In my case, I use PouchDB to perform a "live sync" with all connected users so they all get the latest updates to a document. If a conflict arises it's easy for any one of the users to fix and push it to everyone connected.