[jlongster]

What's shutting down is the public syncing server. That server is literally just a message store: it takes CRDT changes and puts them in a big table. And it servers them back out.

Now that the server is public, it's incredibly easy for you to run your own. It's such a simple server (no postgres etc requirement) that this model is actually way better.

[ec109685]

CRDT's and the like seem like the perfect thing to build an app, but you make a good point about it requiring something so custom compared to a thin client that makes web service requests for data on each screen / page view.

[cormacrelf]

> you make a good point about it requiring something so custom

The comment you're replying to didn't say this at all, the developer did. In theory it's also wrong. The server can be application agnostic. It shouldn't care whether the CRDT update is from a budget app or an RSS reader or whatever else, because the sync job for the server is exactly the same. You should also be able to encrypt the content, and therefore set up generic shared CRDT servers instead of requiring people to run their own.

It only requires more work now because nobody has built that yet.