CRDTs and Collaborative Playground

Great write-up!<p>&gt; If we extend it further with a fairly simple distributed mutex mechanism, we can now persist and share state across any service which can access the Redis instance!<p>I’m curious to hear more about the approach you took here. Does the first server to open the document hold the mutex, or do servers only hold the mutex when briefly while they persist data?<p>(I’ll also shamelessly plug Y-Sweet, an open source Yjs server with persistence that I contribute to <a href="https:&#x2F;&#x2F;github.com&#x2F;jamsocket&#x2F;y-sweet">https:&#x2F;&#x2F;github.com&#x2F;jamsocket&#x2F;y-sweet</a>)

&gt; Beyond this, if you want to determine causality, e.g. whether events are &quot;causally related&quot; (happened before or after each other) or are &quot;concurrent&quot; (entirely independent of), you can look at Vector Clocks—I won&#x27;t go down that rabbit-hole here, though.<p>If anyone want to go down that rabbit hole: <a href="https:&#x2F;&#x2F;www.exhypothesi.com&#x2F;clocks-and-causality&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.exhypothesi.com&#x2F;clocks-and-causality&#x2F;</a>

I&#x27;ll add Loro[0] to the author&#x27;s list. While I utilise Yjs heavily for another project, Loro is fairly featureful and so I picked it to build a screenplay editor[1], which requires things like Peritext or tree structures. It&#x27;s fairly young, though.<p>I&#x27;ll also commend the author&#x27;s attempt at DIY! Even if your case does not require a custom solution, it&#x27;s healthy to understand how your tools work.<p>[0] <a href="https:&#x2F;&#x2F;loro.dev" rel="nofollow">https:&#x2F;&#x2F;loro.dev</a><p>[1] <a href="https:&#x2F;&#x2F;www.weedonandscott.com&#x2F;tech&#x2F;project-realm" rel="nofollow">https:&#x2F;&#x2F;www.weedonandscott.com&#x2F;tech&#x2F;project-realm</a>