Matrix in the French State What happens when a government adopts open source & open standards for a…

Matrix in the French State What happens when a government adopts open source & open standards for all its internal communication?
by Matthew Hodgson
At: FOSDEM 2019
video.fosdem.org/2019/Janson/...
At the beginning of 2018, the French Government reached out to Matrix.org to discuss the idea of creating an entirely open source, standards-based encrypted messaging app as the official means of instant messaging and VoIP communication across the government; replacing adhoc usage of centralised proprietary services such as Telegram and WhatsApp. As of summer 2018, their app exists (a public fork of Riot.im), and there is now a massive federation of Matrix servers deployed throughout the government serving up to 5.5M users, spanning over 30 clusters, letting each ministry run and admin their own operationally independent deployment. In this talk we'll tell the adventure of rolling out FOSS communications at this scale, and give a tour of the architecture and all the work that's gone into Matrix along the way to reach a 1.0 capable of powering government-grade communication. Matrix is an open source project that defines a protocol for secure, decentralised real-time communication - providing simple HTTP+JSON APIs for sending and receiving instant messages, VoIP calls, file transfers, and any other arbitrary realtime data. In this talk we'll tell the tale of how the French Government has deployed Matrix at massive scale, show off their app and its capabilities, and dive into all the challenges and solutions which came up along the way. Particularly, we'll cover what was needed to finalise Matrix's end-to-end encryption such that it can be turned on by default for all conversations; designing whole new extensions to Matrix to support content-scanning of E2E encrypted attachments, and the pleasures of high-availability clustering and management of Matrix server farms by Ansible.
Meanwhile, Matrix itself is rushing towards a 1.0 release (as of Oct 2018) - defining stable releases of the spec across all API surfaces; defining the long-term open governance process for Matrix; iterating on the room state merge resolution protocol which lies at the core of Matrix's decentralisation; and massive amounts of performance work: reducing disk space by 10x thanks to improved state compression; switching from O(N) to O(1) state resolution via memoization; reducing sync sizes and client RAM by 3-5x via lazy-loading members; saving 2-3x RAM in Synapse by migrating from Python 2 to Python 3 etc. We'll give a tour of Matrix 1.0, and talk about what comes next!
Room: Janson
Scheduled start: 2019-02-02 14:00:00+01

[@MelroyvandenBerg]

Still in 2020 there are still a lot of decrypt errors and problems. In the meanwhile they are adding useless features. Please make Synapse more stable first!!

[@climatechangedoesntbargain9140]

I'd consider Synapse pretty stable

[@xy4489]

How is Telegram "run by Russia"? Didn't the whole team had to flee Russia?

[@MarieAmeliaFreyaAster]

Such wow at 15 mins lul

[@infotruther]

Lol

[@nosimpingnocap]

He said its the same like git, and if you look at the terms they hold and store your messages

[@50_Pence]

Not if you have a home server. You contol it completely

[@wsk5846]

Does french gov involvement possibly point to back doors etc

[@ShiroIsMyName]

Nop, they are so inapt technologically that they wouldn't try, they already have backdoors in SMS, no need to put another one in Matrix when no one is using it

[@50_Pence]

It's all open source

[@leatherhidegaming]

@@ShiroIsMyName SMS doesn't need backdoors. It's plain text fully visible to the provider which the government can access.