Settling the IM war
summary
XMPP already provides an extensible, standards‑based IM stack; HTTP upload adoption is widespread and quick, while OMEMO multi-device encryption proves workable but takes days of volunteer effort to implement and sees only a few paid implementations (Conversations, Gajim plugin, ChatSecure progress). A server feature scanner and public ranked list expose missing extensions and motivates operators to enable them. An independent security audit by Radically Open Security is published, and the claim is made that small direct payments per user would fund full‑time development.
AI-written summary · about
chapters (6)
- 0:00Start
- 11:03MISSING FEATURES?
- 11:14FRAGMENTATION?
- 18:19SLOW STANDARDIZATION?
- 26:34WHY DOESN'T IT GET USED?
- 36:58QUESTIONS?
related talks
55mXMPP 2015 - Challenges of Modern-Day Instant Messaging
42mSecurity of Push Messaging
01h 07mBuilding Rock-Solid Encrypted Applications
47mSecure messaging - how to protect yourself & your company
25mMCMix: Anonymous Messaging via Secure Multiparty Computation
57mBuild your own Secure Messenger
45mHow can applications become more secure, private, and dependable
03mInterview with Anthony, Chris and Xavier