Migrating the gematik TI Messenger spec from Matrix 1.3 to Matrix 1.11
summary
Migrates the TI Messenger spec from Matrix 1.3 → 1.11 by auditing the Matrix changelog, filing clarifying PRs, and adding Tim-specific rules: servers must keep the removed key-ID endpoint, clients must force Authorization header use, the short-lived login-token endpoint is forbidden, and clients may use event replacements only if they show edit history. Threads are disallowed, annotations are limited to one Unicode character, and new room versions 9–11 must be supported while only 9 and 10 may be used for creation.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:07Who is gimatic and TI Messenger
- 5:05Why upgrade from Matrix 1.3 to 1.11
- 8:14Approach to migration process
- 9:38Deprecations and removals in Matrix
- 11:44New endpoints and features
- 13:09Backwards compatible changes
- 16:18New features disguised as compatible
- 19:34Clarifications and spec improvements
- 21:20Summary and future outlook
- 23:25Q&A
related talks
26mTuning Your Chat – Enhancing Matrix with Widgets and Bots
30mThe Challenge of Decentralised Communication
42mDesigning Matrix: A Global Decentralised End-to-End Encrypted..
20mDoctor and Patient in the Fediverse of Madness
15mMongooseIM - Messaging for Mobile
34mPractically-exploitable Cryptographic Vulnerabilities in Matrix
30mMISP 3 - Teaching an Old Dog New Tricks
30mCTI-Transmute: Harmonizing Threat Intelligence in a Multi-Standard Ecosystem