Project description
We need a developer to create a document editor embedded in our web application with real-time collaborative editing. The task sounds simple, but doing it right is not easy: two, five or twenty people should open the same document simultaneously and edit it in parallel, never once overwriting each other's edits. When one person types a phrase, all others must see it appear letter by letter in fractions of a second, and each participant's cursor positions must remain correct even when the text around them is constantly changing. We want live cursors and selections, colored by user, a presence panel with a list of who is currently in the document, and a layer of embedded comments where you can highlight a fragment, leave a note and close a discussion thread.
Inside, merging must be conflict-free, so we expect an engine based on CRDT or operational transformations, not a naive 'last write wins' scheme. Simultaneous edits from different clients must converge to exactly the same final state on each machine regardless of packet delivery order and network delays. Offline work is important for us: a user who loses connection should be able to continue editing locally, and their changes should automatically reconcile when connection is restored, without a merge dialog and without losing typed characters. We also need full version history with named snapshots, a visual edit feed, and the ability to restore or compare any previous revision.
Transport should be built on WebSocket with automatic reconnection and backpressure handling, and the entire system must scale across multiple documents and multiple concurrent editors so the server doesn't become a bottleneck. We ask you to treat this as production work: we care about clean APIs, tests around merge logic and clear documentation so our team can maintain the project going forward.
— Live cursors, selections and presence indicator for each user
— CRDT/OT merge engine with convergence guarantee
— Offline editing with automatic reconciliation on reconnection
— Embedded comments, discussion threads and full version history
Inside, merging must be conflict-free, so we expect an engine based on CRDT or operational transformations, not a naive 'last write wins' scheme. Simultaneous edits from different clients must converge to exactly the same final state on each machine regardless of packet delivery order and network delays. Offline work is important for us: a user who loses connection should be able to continue editing locally, and their changes should automatically reconcile when connection is restored, without a merge dialog and without losing typed characters. We also need full version history with named snapshots, a visual edit feed, and the ability to restore or compare any previous revision.
Transport should be built on WebSocket with automatic reconnection and backpressure handling, and the entire system must scale across multiple documents and multiple concurrent editors so the server doesn't become a bottleneck. We ask you to treat this as production work: we care about clean APIs, tests around merge logic and clear documentation so our team can maintain the project going forward.
— Live cursors, selections and presence indicator for each user
— CRDT/OT merge engine with convergence guarantee
— Offline editing with automatic reconciliation on reconnection
— Embedded comments, discussion threads and full version history
Web programming Cash, Bank transfer
