Giters
matrix-org
/
matrix-spec
The Matrix protocol specification
Geek Repo:
Geek Repo
Github PK Tool:
Github PK Tool
Stargazers:
158
Watchers:
16
Issues:
1389
Forks:
86
matrix-org/matrix-spec Issues
New transport protocol (sunsetting JSON)
Updated
2 months ago
Comments count
1
Inconsistent `m.call.candidates` candidate definition
Closed
2 months ago
Comments count
1
Conflicting use of PublicRoomsChunk for space hierarchy over federation
Closed
2 months ago
Comments count
3
MSC discussion: Custom emoji/stickers and interactions with authenticated & linked media
Updated
2 months ago
Comments count
4
Batching receipts should be per room/thread, not just per room
Closed
5 months ago
Comments count
4
Threaded receipt EDU shape down /sync makes it impossible to express certain valid receipts
Updated
2 months ago
Comments count
7
`/_matrix/key/v2/server` says it's signed by "the verify keys", but which ones from the list should be used?
Updated
2 months ago
Comments count
1
Ability to mute rooms per device rather than account wide
Updated
2 months ago
Comments count
3
'Third-party Signed' object does not say who the `signatures` are supposed to be from or why they are there
Updated
3 months ago
Re-clarify the auth rules around invite->knock transitions
Updated
3 months ago
Comments count
5
Important/urgent to-device messages (eg room keys) can get blocked behind big queues of less important ones
Updated
3 months ago
Comments count
3
Suggestion: C-S API endpoint to test push notifications
Updated
3 months ago
Comments count
3
NPM publishing for emoji translations still broken
Closed
3 months ago
Remove the navigation bar link to the FAQs
Updated
3 months ago
Suggestion for mandatory message key recovery mechanism
Closed
4 months ago
Comments count
11
Clarify that join events only need to be signed by resident servers if using `join_authorised_via_users_server`
Updated
3 months ago
Comments count
1
Spec gives bad advice on generating transaction IDs
Updated
3 months ago
Comments count
1
Spec incorrectly claims "EDUs do not have a room ID"
Updated
3 months ago
"Archive" of completed rooms such that when a new message is received the room is taken out of the archive
Updated
4 months ago
Comments count
5
Proposal for curated package data
Updated
4 months ago
Federated Invites: It appears that there is no way to retract an invite such that the invitee is made aware of it
Updated
4 months ago
Comments count
1
Ability to move messages to threads
Updated
4 months ago
Should we require disclosure of potential Conflict of Interest on MSCs?
Updated
4 months ago
Comments count
6
Clarification on the /versions C-S Api endpoint and how the versioning works
Updated
4 months ago
Spec says you can't create a thread from a reply, but popular clients and servers say you can
Closed
4 months ago
Comments count
5
Some of the event-schema yaml files dont actually are yaml
Closed
5 months ago
Comments count
2
`is_direct` field on `/createRoom` body does not automatically mark the room as a DM
Updated
5 months ago
Comments count
4
Discussion: tooling for re/viewing, editing, and collaborating on MSCs
Updated
5 months ago
Comments count
3
It's unclear what OpenID standard is actually meant by 'OpenID', if any at all
Updated
5 months ago
Comments count
3
Wanted: documentation regarding user-relevant cryptographic mechanisms
Updated
5 months ago
Spec incorrectly claims that state events are *overwritten*
Updated
5 months ago
Comments count
5
Consider publishing a pre-made Markdown checklist alongside changelog
Updated
5 months ago
Comments count
1
Matrix 1.9
Closed
5 months ago
Comments count
5
Media download endpoints do not describe a 404 response
Closed
5 months ago
Comments count
3
Spec formats items with multiple types as an array
Updated
5 months ago
Comments count
1
Stickers have incomplete / invalid documentation around encryption
Updated
6 months ago
Comments count
6
Look at Nix's RFC process and see if we can use it in our MSC process
Updated
6 months ago
Comments count
1
Comunicate next steps of an MSC better
Updated
6 months ago
Comments count
4
Some issues don't get timely feedback and feel like they are being ignored or not valued
Updated
6 months ago
Document minimum HTTP versions for Federation and Client-Server API
Updated
6 months ago
The `limited` flag in `Timeline` in `/sync` response needs clarification
Updated
6 months ago
virtual/meta rooms
Updated
6 months ago
Richer bot interactions
Updated
6 months ago
Comments count
2
Corporate takeover - Allowing servers to join.
Closed
6 months ago
Comments count
1
OpenAPI for server-server API is not published
Closed
6 months ago
Room-level required opt-in into "new" features
Updated
7 months ago
Comments count
1
Require proof implementations for MSCs to be open source
Updated
7 months ago
Comments count
2
lang field for pushers should probably not be required
Updated
7 months ago
Authorization rules are confusing
Updated
7 months ago
`/context`, `/messages`, and `/sync` state
Closed
7 months ago
Comments count
3
Previous
Next