Driftboard

Building realtime multiplayer for Driftboard (infinite canvas, shapes, sticky notes). I keep going back and forth between CRDTs and operational transform and I'd love real production experience, not blog-post theory. My constraints Offline-first - people sketch on planes and sync later Boards can get big (10k+ elements) Small team, can't babysit a custom OT server forever CRDTs (Yjs) give me offline + conflict-free merges almost for free, but the memory footprint on long-lived boards scares me. OT is leaner on the wire but the server logic is genuinely hard to get right. Specific questions: For those running Yjs in prod - how do you keep the doc from growing unbounded? GC, snapshots, something else? Anyone regret choosing OT and wish they'd gone CRDT (or vice versa)? Not looking for "it depends" - tell me what bit you. 🙏

Tempted to use RSC for the document/comments shell around Driftboard's canvas. The canvas itself is obviously client-side, but everything around it (sidebars, comments, presence) could be server-driven. My worry is latency: every interaction that touches server state pays a round trip, and an editor lives or dies on feeling instant. Do you split "shell = RSC, hot path = client" and keep them strictly separate? How do you avoid waterfalls when the client island needs server data? Is RSC genuinely worth it here, or am I about to spend a month fighting the framework for a worse result than plain client + a good cache?