Skip to content

Commit

Permalink
Remove "Posting presence in room" alternative
Browse files Browse the repository at this point in the history
This alternative has a lot of privacy implications and would only further exacerbate the frequent complaint regarding membership updates in the timeline (i.e. "Why are avatar changes always sent to every room individually")
  • Loading branch information
nexy7574 committed Jan 15, 2025
1 parent 3291d20 commit 2e4ba2e
Showing 1 changed file with 0 additions and 4 deletions.
4 changes: 0 additions & 4 deletions proposals/4248-pull-based-presence.md
Original file line number Diff line number Diff line change
Expand Up @@ -168,10 +168,6 @@ respond with [HTTP 413 Payload Too Large](https://developer.mozilla.org/en-US/do
inefficient patterns.
3. **Deprecating presence**: Servers could disable presence entirely. This has already
happened in some deployments but removes a key real-time user activity feature.
4. **Posting presence in rooms**: Embedding presence as timeline events could leverage
existing distribution. However, this would complicate large, high-traffic rooms and let
presence be tracked indefinitely. The added data overhead and privacy impact are worse
than poll-based federation for many use cases.

## Security considerations

Expand Down

0 comments on commit 2e4ba2e

Please sign in to comment.