matrix-org / matrix-org/matrix-spec
Proposal for curated room updates
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 330
- Forks
- 150
- Avg merge
- 2h 21m
- Merged PRs (30d)
- 3
Description
Problem statement
I am a member of several high traffic rooms in my matrix client. At a network level, high traffic rooms take most data when syncing due to large amounts of events. Secondly, in the client UI, they occupy important "real estate" because they are more likely to have conversations occurring.
I joined a room such as @Ansible Support because I relied on a conversation to solve an issue. After my problem was solved my interest in the chat waned. Ansible Comminity is now a big consumer of my timeliness interest and netowek usage.
I want a way to only sync a ll "curated lists" hourly, daily or weekly.
What does this aim to achieve
- Reduce data load by offering a curated list of messages and threads
- increase community engagement
What is a curated list ?
A bit like when you receive an example of list of activities that happened on a news website or social media. The BBC for example do not include every article they've written in a day. They instead give you 3 most important and popular topics.
In matrix language it would be 3 messages selected by the server, either automatic or manual.
UX advantages
In high-frequency chats, you have a constant stream, and using your time to wade through what is interesting or not might feel exhausting at offset.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named. Start by reviewing the Matrix protocol specification's existing sync behavior and determine how curated messages, server selection, and hourly, daily, or weekly updates would fit. Done requires an agreed, implementable protocol proposal with clear behavior and scope.
Written by the indexing model from the issue text.
Assessment
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100