yjs VS liveblocks

One idea is just to use fewer random bits in peerIDs. Yjs (https://docs.yjs.dev/) gets away with just 32 random bits. If you compromise and use 64 random bits, then even a very popular doc with 1 million lifetime peerIDs will have a < 10^-7 lifetime probability of collision.

I've seen it come up often in collaborative text editors.

Also see: https://github.com/yjs/yjs

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 arbatary ranges. They can overlap.

Obviously I'm being a little hypabolic suggesting it will replace JSON, the beauty of JSON is is simplicity, but for many systems building on Yjs or similar CRDT based serialisation systems is the future.

https://github.com/yjs/yjs/

Note: https://github.com/yjs/yjs for collaborative "document edition, and user cursors"; has WebRTC, web socket, matrix.org backend

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).

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

No problem. The database CRUD features are just helpers as an abstraction on top of yjs: https://docs.yjs.dev/. Eweser adds schemas in the form of typescript types to make using it simpler, more structured, and interoperability easier.

Absolutely! The real complexity comes from conflict resolution. If someone edits the top, and someone else edits the bottom, which version do you go with? What if they're editing the same area? Entire companies exist to provide elegant solutions to this[0], so it's no simple task.

0: https://liveblocks.io/

I can imagine, browser extensions are a pain in the butt. Are you planning to open source the code? Did you build everything by yourself or on top of https://liveblocks.io/?

For the following example, I want the gradient color to flow from "Hello World" to the "Circle", so they are synchros and match the colors. I created this snippet but I'm having trouble with the rest. https://play.tailwindcss.com/accHTivCcx. Another example would be the https://liveblocks.io/'s title, which flows through the colors in the gradient. How would I achieve this?

Does anyone have any opinions about using Liveblocks for a live collaboration application as opposed to just using Firebase?

liveblocks is great for multiplayer state sync. i was able to make my canvas redux app collaborative in a couple of hours https://liveblocks.io

Very cool use case for CRDTs! I've seen a bunch of different use cases from other products like https://liveblocks.io/ and https://electric-sql.com/. It's interesting how CRDTs are now taking hold so much for all these collaborative syncing scenarios. Wonder what's driving the proliferation now given they've been around for awhile?

Hi Tim,

I'm a bit biased but https://liveblocks.io is great for that :)

If you know how to use React, that's pretty much all you need to know. It also includes some nice hooks to enable things like multiplayer undo/redo and live cursors.

The team even put a couple of interactive blog posts about that that you might find interesting:

True! I would also include https://liveblocks.io to that list of services that help developers make multiplayer experiences.

Interesting to see more players in this space to help more and more developers do this.