Notifications and mentions #66
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#66
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. "Notifications — mentions and tracked note modifications" sits
under Considering. Their issue #35 asks for an indicator when a file has been
changed by someone else.
What we do today
Nothing beyond the status bar and presence. There is no signal that a note you
are not looking at has changed.
The E2EE shape
A mention is text inside an encrypted document, so the server cannot route
notifications — it cannot see who was mentioned. Two honest options:
notifies locally. Works, needs the client running, no server involvement.
write a mention, and the server fans it out without knowing what it means.
Adds metadata — who mentions whom, and when — which
docs/security-model.mdwould have to disclose.(1) is the one consistent with the position. Note that (2) would weaken a claim
the product leads with, for a convenience feature.
Risk
risk:nonefor option 1.Moved to the Vikunja board as NEC-43: https://projectron.nerchure.com/tasks/43