Let multiple people edit the same map at once, seeing each other's changes live.
Depends on cloud storage (#29) existing first as the shared source of truth. The two will likely share a storage layer, but are tracked separately since collaboration adds real-time sync on top.
Needs a conflict-resolution strategy for concurrent edits (CRDT vs. operational transform) — not decided yet. Given the app's data model (segments, nodes, prefabs, canvas objects), whichever approach is picked needs to merge structural graph edits, not just text.
Open questions: presence/cursors for other users, undo/redo semantics under concurrent edits, offline handling.
Let multiple people edit the same map at once, seeing each other's changes live.
Depends on cloud storage (#29) existing first as the shared source of truth. The two will likely share a storage layer, but are tracked separately since collaboration adds real-time sync on top.
Needs a conflict-resolution strategy for concurrent edits (CRDT vs. operational transform) — not decided yet. Given the app's data model (segments, nodes, prefabs, canvas objects), whichever approach is picked needs to merge structural graph edits, not just text.
Open questions: presence/cursors for other users, undo/redo semantics under concurrent edits, offline handling.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Let multiple people edit the same map at once, seeing each other's changes live.
Depends on cloud storage (#29) existing first as the shared source of truth. The two will likely share a storage layer, but are tracked separately since collaboration adds real-time sync on top.
Needs a conflict-resolution strategy for concurrent edits (CRDT vs. operational transform) — not decided yet. Given the app's data model (segments, nodes, prefabs, canvas objects), whichever approach is picked needs to merge structural graph edits, not just text.
Open questions: presence/cursors for other users, undo/redo semantics under concurrent edits, offline handling.