Nothing to add, except that if you are updating multiple sites on a regular basis, check out https://infinitewp.com/. Source: over 1 year ago

If you have lots of sites, and you need a single dashboard giving direct access to all of them, take a look at InfiniteWP or ManageWP. Source: over 2 years ago

Https://infinitewp.com/ have used for several years now. Source: almost 3 years ago

If you are managing multiple unrelated sites check out InfiniteWP. The free base set of tools will let you handle all updates across them quite easily. Source: about 3 years ago

I bought a lifetime license to InfiniteWP maybe 6-7 years ago. https://infinitewp.com/. Source: about 3 years ago

I've seen it come up often in collaborative text editors. Also see: https://github.com/yjs/yjs. - Source: Hacker News / 8 months ago

You are absolutely right that XML is better for document structures. My current theory is that Yjs [0] is the new JSON+XML. It gives you both JSON and XML types in one nested structure, all with conflict free merging via incremental updates. Also, you note the issue with XML and overlapping inline markup. Yjs has an answer for that with its text type, you can apply attributes (for styling or anything else) via... - Source: Hacker News / 10 months ago

Note: https://github.com/yjs/yjs for collaborative "document edition, and user cursors"; has WebRTC, web socket, matrix.org backend. - Source: Hacker News / 10 months ago

CCP needs to revamp proto anyway, due to recent exploits... practically, nothing really prevents 'em from using some sort of CRDT's to make the state of the sig view eventually consistent (yjs lib, if we're speaking frontendian). Source: 11 months ago

Yjs framework: Because it is a CRDT implementation which provides collaborative editing and offline-first capability. Source: 12 months ago