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
50 Open 8 Closed
50 Open 8 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

/logout does not take a request body, which is inconsistent wart A point where the protocol is inconsistent or inelegant
#1845 opened Jun 5, 2024 by reivilibre
1
is_direct field on /createRoom body does not automatically mark the room as a DM wart A point where the protocol is inconsistent or inelegant
#1692 opened Dec 5, 2023 by DMRobertson
4
Stickers have incomplete / invalid documentation around encryption wart A point where the protocol is inconsistent or inelegant
#1667 opened Nov 5, 2023 by jplatte
6
The reason of redactions is in clear-text even for E2EE messages A-E2EE Issues about end-to-end encryption wart A point where the protocol is inconsistent or inelegant
#1608 opened Jul 31, 2023 by davidegirardi
2
RESTful renaming and restructuring wart A point where the protocol is inconsistent or inelegant
#1522 opened May 15, 2023 by OattyGengar
2
Appservice API /_matrix/app/v1/transactions/ should specify maximum transaction sizes A-Application-Services Issues affecting the AS API wart A point where the protocol is inconsistent or inelegant
#1469 opened Mar 21, 2023 by Half-Shot
1
Space rooms silently dropped over federation due to outdated via values. A-Client-Server Issues affecting the CS API wart A point where the protocol is inconsistent or inelegant
#1467 opened Mar 15, 2023 by AndrewRyanChama
1
push_rules vs pushrules A-Push wart A point where the protocol is inconsistent or inelegant
#1434 opened Feb 14, 2023 by richvdh
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
Unexpected powerlevels interactions wart A point where the protocol is inconsistent or inelegant
#1267 opened Oct 4, 2022 by richvdh
The event size limit lives in the Client-Server API docs clarification An area where the expected behaviour is understood, but the spec could do with being more explicit wart A point where the protocol is inconsistent or inelegant
#1208 opened Aug 11, 2022 by anoadragon453
4
POST /_matrix/client/v3/rooms/{roomId}/leave does not cover all possible error situations clarification An area where the expected behaviour is understood, but the spec could do with being more explicit wart A point where the protocol is inconsistent or inelegant
#1181 opened Jul 22, 2022 by Half-Shot
One-time-key upload/claim is racy A-E2EE Issues about end-to-end encryption wart A point where the protocol is inconsistent or inelegant
#1124 opened Jun 14, 2022 by turt2live
4
Widgets exacerbate the lowerCamelCase mixed with snake_case problem A-Widgets anything to do with widgets wart A point where the protocol is inconsistent or inelegant
#689 opened Sep 5, 2020 by turt2live
We should not require pusher URLs to be on a specific path A-Push wart A point where the protocol is inconsistent or inelegant
#677 opened Aug 12, 2020 by richvdh
11
PUT /_matrix/client/r0/rooms/{roomId}/redact/{eventId}/{txnId} makes no sense A-Client-Server Issues affecting the CS API wart A point where the protocol is inconsistent or inelegant
#659 opened Jul 3, 2020 by kegsay
10
Thumbnail method isn't required and has no default A-Client-Server Issues affecting the CS API wart A point where the protocol is inconsistent or inelegant
#656 opened Jun 25, 2020 by Sorunome
8
what is the actual point of per-room pushrules? A-Client-Server Issues affecting the CS API A-Push wart A point where the protocol is inconsistent or inelegant
#651 opened Jun 19, 2020 by richvdh
8
Spec is inconsistent with usage of PDU versus event A-S2S Server-to-Server API (federation) wart A point where the protocol is inconsistent or inelegant
#572 opened Dec 31, 2019 by turt2live
1
Federation request signing is easily broken by proxies wart A point where the protocol is inconsistent or inelegant
#561 opened Nov 15, 2019 by SISheogorath
4
Remove spurious event_id from federation APIs, and convert to POST? A-S2S Server-to-Server API (federation) wart A point where the protocol is inconsistent or inelegant
#555 opened Oct 25, 2019 by richvdh
3
Server access control lists can "ban" users with higher power levels A-Client-Server Issues affecting the CS API wart A point where the protocol is inconsistent or inelegant
#554 opened Oct 21, 2019 by lucavb
redaction algorithm doesn't distinguish between state/non-state events wart A point where the protocol is inconsistent or inelegant
#547 opened Oct 1, 2019 by uhoreg
2
Identity Service API: No way to tell whether to prompt the user for an authentication token wart A point where the protocol is inconsistent or inelegant
#545 opened Sep 23, 2019 by richvdh
It's hard to see how the different 3pid management APIs interact with each other at a glance A-Client-Server Issues affecting the CS API clarification An area where the expected behaviour is understood, but the spec could do with being more explicit wart A point where the protocol is inconsistent or inelegant
#521 opened Aug 6, 2019 by turt2live
ProTip! Follow long discussions with comments:>50.