Andy, I just learned about your Genesis project, and it&#x27;s great to see people pushing towards collaborative DAWs. I&#x27;ve been doing detailed planning for my own vision for a collaborative DAW for years now, though various other projects have kept distracting me from giving it enough coding time to get it off the ground!<p>I&#x27;m curious how you&#x27;re thinking of solving latency &amp; disconnection issues between participants. It looks like you&#x27;re representing things as a sequential list of transactions, and immutable transactions are definitely the starting point for everything I&#x27;ve considered! The question is: what happens if multiple people send each other conflicting transactions at the same time? Google Wave solved this by enforcing a single server-side ordering of all events, and making sure that all transactions would be accepted using Operational Transformation even if they occurred out of order. Without OT, you may have cases where Alice makes a change, only to have it invalidated and essentially erased by Bob&#x27;s change that may have &quot;won&quot; on the server side. And while OT may be largely &quot;solved&quot; for text content, it doesn&#x27;t seem well-studied for music or other timeline-based content.<p>As an alternative, source control manages to get along fine without automated conflict resolution&#x2F;OT, since we&#x27;re willing to dive into merge conflicts and resolve things ourselves. So theoretically, you could create &quot;Git for Music&quot; and drive that from your app. But what&#x27;s the UI equivalent of version control in a DAW? What, exactly, does a &quot;diff&quot; look like in musical notation? And how do you make it unobtrusive to non-coder musicians?<p>All very interesting problems, and it&#x27;s always great to have multiple innovators in this space! Would be happy to connect offline if you&#x27;d like.