element-hq / element-hq/synapse
Not all presence updates should be sent out over federation immediately.
- Dominant language
- Python
- Stars
- 4.6k
- Forks
- 600
- Avg merge
- 5d 22h
- Merged PRs (30d)
- 51
Description
This issue has been migrated from [#9415](https://github.com/matrix-org/synapse/issues/9415).
---
Similarly to https://github.com/matrix-org/synapse/issues/8955, not all presence updates are urgent and are safe to delay for a short time (e.g. online to idle transitions which are done based on fairly arbitrary timers). By not immediately sending out these updates it allows Synapse to potentially batch up these presence updates with other data that needs to be sent, reducing the number of overall transactions sent.
Contributor guide
Research direction
Start by reviewing the related issue #8955 and the presence federation flow in Synapse. Identify where presence updates are sent immediately and determine how urgent and timer-based updates are distinguished. Done means safe-to-delay updates can be batched with other outbound data while urgent updates retain prompt delivery.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, distributed-systems, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100