Skip to content

Issues: matrix-org/matrix-spec

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clear current search query, filters, and sorts
78 Open 17 Closed
78 Open 17 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

/_matrix/key/v2/server says it's signed by "the verify keys", but which ones from the list should be used? A-S2S Server-to-Server API (federation) clarification An area where the expected behaviour is understood, but the spec could do with being more explicit good first issue This is a fix that might be an easy place for someone to start for their first contribution
#1726 opened Feb 15, 2024 by turt2live
2
Document minimum HTTP versions for Federation and Client-Server API A-Client-Server Issues affecting the CS API A-S2S Server-to-Server API (federation) improvement An idea/future MSC for the spec
#1666 opened Oct 30, 2023 by turt2live
Move federation traffic from port 8448 to 443 as a default A-S2S Server-to-Server API (federation) feature Suggestion for a significant extension which needs considerable consideration
#1577 opened Jun 16, 2023 by turt2live
2
No explanation for why notary key endpoints return arrays A-S2S Server-to-Server API (federation) clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#1574 opened Jun 14, 2023 by turt2live
2
Server-server authentication doesn't specify what happens when auth fails A-S2S Server-to-Server API (federation) spec-omission implemented but not currently specified
#1570 opened Jun 14, 2023 by turt2live
1
Server discovery step 3 is incredibly long A-S2S Server-to-Server API (federation) clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#1565 opened Jun 12, 2023 by turt2live
join_authorised_via_users_server user must be joined to the room A-Room-spec Something to do with the room version specifications A-S2S Server-to-Server API (federation) spec-omission implemented but not currently specified
#1477 opened Mar 29, 2023 by turt2live
If a server specifies multiple active verify keys, which one(s) are required to sign an object? A-S2S Server-to-Server API (federation) clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#1471 opened Mar 21, 2023 by turt2live
1
/key/v2/query responses do not say that server_keys is a list A-S2S Server-to-Server API (federation) spec-bug Something which is in the spec, but is wrong
#1451 opened Feb 23, 2023 by DMRobertson
1
key/v2/server response contains absolute timestamps, which are vulnerable to clock drift A-S2S Server-to-Server API (federation) spec-bug Something which is in the spec, but is wrong
#1450 opened Feb 23, 2023 by DMRobertson
2
key/v2/server example response isn't signed by any of the example verify_keys A-S2S Server-to-Server API (federation) clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#1448 opened Feb 23, 2023 by DMRobertson
3
What is the state after a rejected state event? A-S2S Server-to-Server API (federation) clarification An area where the expected behaviour is understood, but the spec could do with being more explicit help wanted Interested in contributing to the spec? These would be great additions!
#1373 opened Dec 8, 2022 by DMRobertson
1
Extending homeserver functionality with WASM A-Application-Services Issues affecting the AS API A-S2S Server-to-Server API (federation) feature Suggestion for a significant extension which needs considerable consideration
#1364 opened Nov 28, 2022 by olanod
1
Homeserver signing key grammar is not clear A-S2S Server-to-Server API (federation) clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#1354 opened Nov 21, 2022 by Half-Shot
Including "signatures" into event size calculations can become problematic A-S2S Server-to-Server API (federation) wart A point where the protocol is inconsistent or inelegant
#1311 opened Oct 28, 2022 by ShadowJonathan
1
S-S API does not define User Devices struct. A-S2S Server-to-Server API (federation)
#1300 opened Oct 21, 2022 by DMRobertson
1
Wildcard bans and ban exceptions A-S2S Server-to-Server API (federation) feature Suggestion for a significant extension which needs considerable consideration
#1290 opened Oct 16, 2022 by Mikaela
3
Include guidelines how to backfill with /messages and /context A-S2S Server-to-Server API (federation) clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#1281 opened Oct 12, 2022 by MadLittleMods
Spec timeout threshold values for presence A-Client-Server Issues affecting the CS API A-S2S Server-to-Server API (federation) clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#1279 opened Oct 11, 2022 by MadLittleMods
Anonymous homeservers (Tor/I2P support): Modifying the federation system A-S2S Server-to-Server API (federation) improvement An idea/future MSC for the spec
#1277 opened Oct 7, 2022 by ghost
8
Matrix does not support SVCB DNS records for homeserver discovery A-S2S Server-to-Server API (federation) feature Suggestion for a significant extension which needs considerable consideration
#1220 opened Aug 28, 2022 by lindsayschm
5
Auth rules: behaviour unclear if no power level event is cited as an auth event A-S2S Server-to-Server API (federation) clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#1098 opened May 30, 2022 by DMRobertson
7
Clarify exact rules for encoding federation URLs A-S2S Server-to-Server API (federation) clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#849 opened Jun 18, 2021 by neilalexander
2
We should spec the max size of an EDU over federation A-S2S Server-to-Server API (federation)
#807 opened Apr 14, 2021 by richvdh
11
"state at" is ambiguous A-Client-Server Issues affecting the CS API A-S2S Server-to-Server API (federation) clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#697 opened Sep 28, 2020 by neilalexander
ProTip! Add no:assignee to see everything that’s not assigned.