Change attribution #63
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#63
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. "Change attribution — click a collaborator in the avatar stack
to highlight their text inline" is Active on their roadmap.
What it would take
Yjs already carries a client id per character inside the document, and the
document is what we encrypt — so attribution is decryptable client-side and
needs no server change. What is missing is a stable client-id-to-user mapping
that survives reconnects.
Why it is unscheduled rather than sequenced
It pairs naturally with the version browser, and it is worth less than it looks:
the per-span author data bloats every document, and on a note edited by several
people over months the colouring becomes noise. Worth doing when someone asks for
it, and worth measuring the document-size cost before committing.
Risk
risk:none.Moved to the Vikunja board as NEC-40: https://projectron.nerchure.com/tasks/40