Declare support for Matrix 1.4

[matrixbot]

This issue was originally created by @S7evinK at https://github.com/matrix-org/dendrite/issues/3222.

Some of these are good first issues

Complete changelog v1.4

Client-Server API

Backwards Compatible Changes

• [x] Add a .m.rule.room.server_acl push rule to match m.room.server_acl events, as per MSC3786.
• [x] Add Cross-Origin-Resource-Policy (CORP) headers to media repository, as per MSC3828.
• [x] Copy a room's type when upgrading it, as per MSC3818.
  • We copy the whole create event and remove unwanted fields
• [ ] Add room_types filter and room_type response to /publicRooms, as per MSC3827.
  • room_types exists, but is unused
• [ ] Add m.replace relations (event edits), as per MSC2676.
  • Looks like we don't have server-side aggregation atm
• [x] Add m.read.private receipts, as per MSC2285.
• [x] Make m.fully_read optional on /read_markers, as per MSC2285.
• [x] Allow m.fully_read markers to be set from /receipts, as per MSC2285.
• [ ] Add threading via m.thread relations, as per MSC3440, MSC3816, MSC3856, and MSC3715.
  • While partly working, there are still missing endpoints, e.g. GET /rooms/{roomId}/threads
• [ ] Add per-thread notifications and read receipts, as per MSC3771 and MSC3773.
• [ ] Add thread_id to the /receipt endpoint, as per MSC3771.

Spec Clarifications (NOTE: Non-actionable things removed)

• [x] Clarify that the "device_id", "user_id" and "access_token" fields are required in the response body of POST /_matrix/client/v3/login.
  • We already return those fields

Server-Server API

Backwards Compatible Changes

• [ ] Add per-thread notifications and read receipts, as per MSC3771 and MSC3773.
  • Missing thread_id in type ReceiptTS struct (which should be renamed, since it's not TS only afterwards)

Application Service API

Breaking Changes

• [ ] Replace homeserver authorization approach with an Authorization header instead of access_token when talking to the application service, as per MSC2832.

[matrixbot]

This comment was originally posted by @slack-coder at https://github.com/matrix-org/dendrite/issues/3222#issuecomment-2009600253.

Heads up, the latest mautrix-whatsapp release (v0.10.6) now expects this version. A workaround is to use version 0.10.5.

2024-03-20T07:10:23-05:00 FTL The homeserver is outdated (supported spec versions are below minimum required by bridge) bridge_requires=v1.4 server_supports=v1.2

[matrixbot]

This comment was originally posted by @Naxora at https://github.com/matrix-org/dendrite/issues/3222#issuecomment-2053596231.

Also mautrix-meta bridge need this version.

2024-04-13T09:57:15Z FTL The homeserver is outdated (supported spec versions are below minimum required by bridge) bridge_requires=v1.4 server_supports=v1.2

[matrixbot]

This comment was originally posted by @fabrixxm at https://github.com/matrix-org/dendrite/issues/3222#issuecomment-2139783688.

Heads up, the latest mautrix-whatsapp release (v0.10.6) now expects this version. A workaround is to use version 0.10.5.

Which unfortunately does not connects to WA anymore...

INF Bridge is using outdated WhatsApp web protocol (2.2353.59, latest is 2.3000.0)

WhatsApp bridge bot Failed to log in: outdated client. The bridge must be updated to continue.

[matrixbot]

This comment was originally posted by @cyberb at https://github.com/matrix-org/dendrite/issues/3222#issuecomment-2284860697.

latest slack bridge error: matrix.slack[3352]: 2024-08-12T20:02:30.864Z FTL The homeserver is outdated (supported spec versions are below minimum required by bridge) bridge_requires=v1.4 server_supports=v1.2 is there any progress on this? or dendrite is slowly dying?

[matrixbot]

This comment was originally posted by @bbortt at https://github.com/matrix-org/dendrite/issues/3222#issuecomment-2397460482.

or dendrite is slowly dying?

seeing as how old this thread is, I suppose: yes.

it's also not an easy task that would allow for first-time contributors to work on, from what I am reading. at least to me this stuff sounds relatively complicated.