Comments (4)
Jira watchers: @erikjohnston @NegativeMjark @richvdh
from matrix-spec.
For rooms that have a large number of participants split over a small number of servers we can use the existing full mesh protocol by distributing a list of member servers using membership PDUs for a participant on each server to prove that it should be in the list.
For rooms with a large number of participating servers we might need to look at new protocols for distributing the messages without each server needing to know the full list.
from matrix-spec.
Is this bug about alternatives to full-mesh routing, or about reducing the number of state events flying around?
-- @richvdh
from matrix-spec.
full-mesh alternatives seems to be https://github.com/matrix-org/matrix-doc/issues/469, so I assume it's the latter? is this a real problem?
-- @richvdh
from matrix-spec.
Related Issues (20)
- Suggestion: C-S API endpoint to test push notifications HOT 3
- 'Third-party Signed' object does not say who the `signatures` are supposed to be from or why they are there
- Ability to mute rooms per device rather than account wide HOT 3
- `/_matrix/key/v2/server` says it's signed by "the verify keys", but which ones from the list should be used? HOT 1
- Threaded receipt EDU shape down /sync makes it impossible to express certain valid receipts HOT 8
- Conflicting use of PublicRoomsChunk for space hierarchy over federation HOT 3
- New transport protocol (sunsetting JSON) HOT 2
- Inconsistent `m.call.candidates` candidate definition HOT 1
- Matrix 1.10 HOT 6
- As a user or appservice, I want to know if another user has access to a specific event. HOT 2
- SSSS passphrase encoding HOT 1
- Push Notifications: Add Support for: VAPID / WebPush Subscriptions
- `/media/v3/preview_url` response spec should include more properties HOT 6
- Unread notification count remains stagnant when push rules are enabled. HOT 2
- Table of contents: Click to jump to section has regressed
- Test building the historical spec more frequently than release cadence
- Behaviour of `allow_remote` on media endpoints is unclear HOT 1
- Add a version picker UI to the documentation website HOT 2
- "Added in" and "Changed in" attributes should be rendered when attached to requests and responses
- Clarification of invite->knock introduced in 1.10 should be at least a warning on older rendered spec versions HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from matrix-spec.