8000 Issues · matrix-org/matrix-spec · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Issues: matrix-org/matrix-spec

Beta
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

1,077 Open 439 Closed
1,077 Open 439 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
Assigned to nobody Loading
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Data type of url field within Application Service registration file is confusing improvement An idea/future MSC for the spec
#2155 opened May 29, 2025 by anoadragon453
1
MSC's should always use their unstable prefix when describing event properties or schema.
#2152 opened May 27, 2025 by Gnuxie
2
Recommend clients avoid including any invitations in the top level of the client. improvement An idea/future MSC for the spec
#2146 opened May 23, 2025 by Gnuxie
Recommend clients avoid notifying for invitations and showing any room information in notifications improvement An idea/future MSC for the spec
#2145 opened May 23, 2025 by Gnuxie
How should m.room.canonical_alias be handled on room upgrade clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#2142 opened May 17, 2025 by olivia-fl
2
Clarify Behavior When Inviting Non-Existent Users clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#2139 opened May 1, 2025 by Jeff92316046
A users own invite event should not be stripped in sync spec-bug Something which is in the spec, but is wrong
#2138 opened Apr 27, 2025 by olivia-fl
Client-side display aliases for rooma/users improvement An idea/future MSC for the spec
#2134 opened Apr 21, 2025 by saihaze
$CHANACS / Assigning power levels to room IDs rather than user IDs improvement An idea/future MSC for the spec
#2129 opened Apr 9, 2025 by Mikaela
What are the set(s) of core-events that are covered by the protocol. clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#2127 opened Mar 31, 2025 by taqtiqa-mark
2
spec idea: roles improvement An idea/future MSC for the spec
#2126 opened Mar 31, 2025 by mageOfstructs
4
Document config.toml moved to config/_default/hugo.toml
#2120 opened Mar 28, 2025 by HarHarLinks
Replace unmaintained klakegg/hugo container with hugomods/hugo
#2119 opened Mar 28, 2025 by HarHarLinks
spaces: Is {"via":[]} considered valid? clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#2118 opened Mar 28, 2025 by VAWVAW
Chosen nickname/alias of a user should be respected (imported) when inviting them to a new space/room improvement An idea/future MSC for the spec
#2117 opened Mar 28, 2025 by heyakyra
DANE support improvement An idea/future MSC for the spec
#2113 opened Mar 26, 2025 by Saiv46
Should ignored users be dropped from m.typing and m.receipt events in sync? clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#2112 opened Mar 23, 2025 by olivia-fl
2
Case insensitive behaviour is defined as server-side implementation detail A-Push clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#2111 opened Mar 21, 2025 by t3chguy
Signed messages in unencrypted rooms improvement An idea/future MSC for the spec
#2103 opened Mar 19, 2025 by Saiv46
850C
GET /initialSync's response mentions a limit parameter which is not documented for the request clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#2099 opened Mar 17, 2025 by zecakeh
room_id should be required in GET /events for peeking spec-bug Something which is in the spec, but is wrong
#2098 opened Mar 17, 2025 by zecakeh
Spec says that room directory is not authed. But in practice, synapse auths it by default. spec-bug Something which is in the spec, but is wrong
#2097 opened Mar 17, 2025 by ara4n
2
Specifying x-addedInMatrixVersion & friends prior to a release
#2096 opened Mar 14, 2025 by Johennes
GET /_matrix/client/v3/directory/room/{roomAlias} is badly designed and leads clients into unsafe behaviour
#2092 opened Mar 8, 2025 by Gnuxie
Unclear IP address syntax requirements clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
#2090 opened Mar 5, 2025 by CobaltCause
8
ProTip! Type g i on any issue or pull request to go back to the issue listing page.
0