Follow a collaborator's viewport #43
Labels
No labels
area:docs
area:identity
area:ops
area:plugin
area:server
channel:community
channel:direct
channel:owned
channel:press
channel:social
e2ee-constrained
gate:at-ga
gate:pre-ga
marketing
parity
relay:absent
relay:planned
relay:requested
relay:supported
risk:additive
risk:contract
risk:none
usability
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Nectenda/nectenda#43
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Part of #37.
What Relay does
Not shipped. "Collaborative presence — follow-cursor, who's-online across
folders, pull-to-view" sits under Considering on their roadmap (read
21 Sep 2026), which is their least-committed tier.
What we do today
Remote cursors with always-on name labels via
y-codemirror.next(
editor-bridge.ts) and an avatar stack beside the note title(
main.ts:3901 renderPresenceStack, six-seat palette inpresence.ts). Nofollow mode.
What changes
Awareness already carries cursor and selection, and presence is relayed at up to
20 Hz (
AWARENESS_WINDOW_MS = 50). Add viewport to the awareness payload, and aclick on an avatar scrolls to and tracks that person's view.
Worth noting the existing trade in
docs/sync-limitations.md: presence iscoalesced, so following will be smooth rather than frame-exact. That is the right
trade and should stay.
Risk
risk:none. Awareness is relayed, never stored.Verification
Two real Obsidian instances in the multi-vault e2e suite; one follows, the other
scrolls.
Moved to the Vikunja board as NEC-20: https://projectron.nerchure.com/tasks/20