element-hq / element-hq/dendrite

Declare support for Matrix 1.5

Open
#3,223 1 comment 0 reactions 0 assignees View on GitHub
good first issue help wanted spec-compliance
Dominant language
Go
Stars
965
Forks
101
PR merge metrics
No merged PRs in 30d

Description

*This issue was originally created by [**@S7evinK**](https://github.com/S7evinK) at .*

[Complete changelog v1.5](https://github.com/matrix-org/matrix-spec/blob/e40d9ca18676fc774b39f30b44998d7f0118596a/content/changelog/v1.5.md)

### Client-Server API

Backwards Compatible Changes

- [ ] Add `m.reference` relations, as per [MSC3267](https://github.com/matrix-org/matrix-spec-proposals/pull/3267).
- Only missing aggregation, if anything?

Spec Clarifications
(NOTE: non-actionable things removed, as well as things we don't have implemented at all yet, e.g. refresh tokens clarification would be fixed when implementing refresh tokens)

- [x] Define a 400 response from `/_matrix/client/v3/directory/rooms/{roomAlias}`. ([#1286](https://github.com/matrix-org/matrix-spec/issues/1286))
- We already return 400, but not the correct `errcode`

### Application Service API

Spec Clarifications

- [ ] Clarify that application services can only register an interest in local users, as per [MSC3905](https://github.com/matrix-org/matrix-spec-proposals/issues/3905). ([#1305](https://github.com/matrix-org/matrix-spec/issues/1305))
- From the looks of it, we just compile the provided regex, but don't check if the user is local

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the Matrix 1.5 changelog and the linked MSC3267 and MSC3905 proposals. Check the Client-Server room-alias endpoint and application-service user-interest registration, including the noted error-code and local-user validation gaps. Done means the remaining unchecked Matrix 1.5 requirements are implemented and verified against the relevant API behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
api, backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.