Unable to decrypt this message
summary
Explains why messages become "unable to decrypt" (UTDs), shows a new test framework complement-crypto that runs home servers in Docker with a man-in-the-middle proxy to inject failures, and reports measurable progress: Element apps see UTDs drop to about 3% web, 4% iOS, 6% Android after five months. Describes concrete failure modes (one‑time key exhaustion, device-list desync, batching/timeouts, federation faults), fixes (Vats + Matrix Rust SDK convergence, server retries, fullback keys) and that the framework already finds real bugs and CVEs.
AI-written summary · about
chapters (8)
- 0:00Introduction to UTDs
- 1:51Why UTDs happen
- 10:57Technical background on UTDs
- 13:03Matrix crypto stack explained
- 22:14Client-side causes of UTDs
- 26:47Testing framework for UTDs
- 30:01Future improvements and thanks
- 30:42Q&A session
