Declare support for Matrix v1.7

[clokep]

See the changelog (note that I stripped out spec clarifications).

Client-Server API

New Endpoints

• POST /_matrix/client/v1/login/get_token. MSC3882
  • Implement stable support for MSC3882 to allow an existing device/session to generate a login token for use on a new device/session #15388
• POST /_matrix/media/v1/create and PUT /_matrix/media/v3/upload/{serverName}/{mediaId} MSC2246.
  • MSC2246 async uploads #12484 or Asynchronous Uploads #15503

Backwards Compatible Changes

• Changes to the server-side aggregation of m.replace (edit) events, as per MSC3925.
  • Enable MSC3925 by default: stop applying edits. #15193
• Add new push rule conditions: event_property_is and event_property_contains from MSC3758 and MSC3966.
  • Stabilize support for MSC3758: event_property_is push condition #15185 and Stabilize support for MSC3966: event_property_contains push condition #15187
• Add m.annotation relations (reactions), as per MSC2677.
  • This was defacto standard before this spec release, Synapse has support for it.
• Document the m.mentions property; the .m.rule.is_user_mention and .m.rule.is_room_mention push rules; and other behaviour from MSC3952.
  • Stabilize support for MSC3952: Intentional mentions. #15520
• Improve VoIP signaling, as per MSC2746.
  • No server changes needed.
• Update the scope of transaction IDs, as per MSC3970.
  • Stabilize support for MSC3970: updated transaction semantics (scope to device_id) #15629
• Add an ability to redirect downloads, as per MSC3860.
  • Request & follow redirects for /media/v3/download #16701
• Add an ability to use an existing session to log in another, as per MSC3882.
  • Implement stable support for MSC3882 to allow an existing device/session to generate a login token for use on a new device/session #15388

Application Service API

New Endpoints

• POST /_matrix/app/v1/ping and POST /_matrix/client/v1/appservice/{appserviceId}/ping MSC2659.
  • Stabilize MSC2659 support #15528

Backwards Compatible Changes

• Add homeserver->appservice ping mechanism, as per MSC2659.
  • Stabilize MSC2659 support #15528

---

Depends on #15089.

[clokep]

Addition of redirect downloads, as per matrix-org/matrix-spec-proposals#3860.

Note that I think Synapse technically can declare 1.7 without actually doing anything for this, the spec for the /download and /thumbnail endpoints have a new allow_redirect query parameter:

Indicates to the server that it may return a 307 or 308 redirect response that points at the relevant media content. When not explicitly set to true the server must return the media content itself.

Those endpoints should already ignore unknown parameters, so should be compliant.

[tulir]

Note that I think Synapse technically can declare 1.7 without actually doing anything for this

Synapse should implement following redirects when downloading media over federation, but I guess that might not be relevant for declaring support in the C-S API

[clokep]

Note that I think Synapse technically can declare 1.7 without actually doing anything for this

Synapse should implement following redirects when downloading media over federation, but I guess that might not be relevant for declaring support in the C-S API

Yes, that's a good point! 👍 I always forget the S-S & C-S APIs are the same for media. 😢

[clokep]

Note that I think Synapse technically can declare 1.7 without actually doing anything for this

Synapse should implement following redirects when downloading media over federation, but I guess that might not be relevant for declaring support in the C-S API

Yes, that's a good point! 👍 I always forget the S-S & C-S APIs are the same for media. 😢

#16701 should implement following the redirects on the S-S side.