HNHacker News
TopNewBestAskShowJobs

Arathorn

15,826 karma · joined December 8, 2010

Matrix.org project lead | CEO/CTO [Element](https://element.io)
submissionscomments
Arathorn··on European Commission Trials Matrix to Replace Teams
> It's far from perfect, but using a simple application with no built-in ads, AI, bloat, crap, etc is wonderful.

I think there are three main reasons it's not perfect yet:

1. Building both a decentralised open standard (Matrix) at the same time as a flagship implementation (Element) is playing on hard mode: everything has to be specified under an open governance process (https://spec.matrix.org/proposals) so that the broader ecosystem can benefit from it - while in the early years we could move fast and JFDI, the ecosystem grew much faster than we anticipated and very enthusiastically demanded a better spec process. While Matrix is built extensibly with protocol agility to let you experiment at basically every level of the stack (e.g. right now we're changing the format of user IDs in MSC4243, and the shape of room DAGs in MSC4242) in practice changes take at least ~10x longer to land than in a typical proprietary/centralised product. On the plus side, hopefully the end result ends up being more durable than some proprietary thing, but it's certainly a fun challenge.

2. As Matrix project lead, I took the "Element" use case pretty much for granted from 2019-2022: it felt like Matrix had critical mass and usage was exploding; COVID was highlighting the need for secure comms; it almost felt like we'd done most of the hard bits and finishing building out the app was a given. As a result, I started looking at the N-year horizon instead - spending Element's time working on P2P Matrix (arewep2pyet.com) as a long-term solution to Matrix's metadata footprint and to futureproof Matrix against Chat Control style dystopias... or projects like Third Room (https://thirdroom.io) to try to ensure that spatial collaboration apps didn't get centralised and vendorlocked to Meta, or bluesky on Matrix (https://matrix.org/blog/2020/12/18/introducing-cerulean/, before Jay & Paul got the gig and did atproto).

I maintain that if things had continued on the 2019-2022 trajectory then we would have been able to ship a polished Element and do the various "scifi" long-term projects too. But in practice that didn't happen, and I kinda wish that we'd spent the time focusing on polishing the core Element use case instead. Still, better late than never, in 2023 we did the necessary handbrake turn focusing exclusively on the core Element apps (Element X, Web, Call) and Element Server Suite as an excellent helm-based distro. Hopefully the results speak for themselves now (although Element Web is still being upgraded to use the same engine as Element X).

3. Finally, the thing which went wrong in 2022/2023 was not just the impact of the end of ZIPR, but the horrible realisation that the more successful Matrix got... the more incentive there would be for 3rd parties to commercialise the Apache-licensed code that Element had built (e.g. Synapse) without routing any funds to us as the upstream project. We obviously knew this would happen to some extent - we'd deliberately picked Apache to try to get as much uptake as possible. However, I hadn't realised that the % of projects willing to fund the upstream would reduce as the project got more successful - and the larger the available funds (e.g. governments offering million-dollar deals to deploy Matrix for healthcare, education etc) then you were pretty much guaranteed the % of upstream funding would go to zero.

So, we addressed this in 2023 by having to switch Element's work to AGPL, massively shrinking the company, and then doing an open-core distribution in the form of ESS Pro (https://element.io/server-suite/pro) which puts scalability (but not performance), HA, and enterprise features like antivirus, onboarding/offboarding, audit, border gateways etc behind the paywall. The rule of thumb is that if a feature empowers the end-user it goes FOSS; if it empowers the enterprise over the end-user it goes Pro. Thankfully the model seems to be working - e.g. EC is using ESS for this deployment. There's a lot more gory detail in last year's FOSDEM main-stage talk on this: https://www.youtube.com/watch?v=lkCKhP1jxdk

Eitherway, the good news is that we think we've figured out how to make this work, things are going cautiously well, and these days all of Element is laser-focused on making the Element apps & servers as good as we possibly can - while also continuing to also improve Matrix, both because we believe the world needs Matrix more than ever, and because without Matrix Element is just another boring silo'd chat app.

The bad news is that it took us a while to figure it all out (and there are still some things still to solve - e.g. abuse on the public Matrix network, finishing Hydra (see https://www.youtube.com/watch?v=-Keu8aE8t08), finishing the Element Web rework, and cough custom emoji). I'm hopeful we'll get here in the end :)

Arathorn··on European Commission Trials Matrix to Replace Teams
Element Software SARL and Element Software GmbH however are not. In practice I believe it's Element Software GmbH providing the European Commission deployment of ESS. (Both are owned by the UK topco, but at the current rate we might flip one of them to be the topco instead).
Arathorn··on European Commission Trials Matrix to Replace Teams
If you work with lots of other entities who want full control over their own comms (e.g. other governments, other departments, other EU entities like European Parliament and Council, the UN, NATO, etc) then decentralisation or federation is a big deal.

In the public sector it's basically a requirement: it's bananas if your country's critical infrastructure ends up dependent on some a product effectively controlled by another country (e.g. Teams) - and you obviously want to be able to communicate with other govt entities rather than being stuck in an island.

Then it's a natural extension to the private sector - although for now, it feels more folks are on the "nobody got sacked for using Teams" train.

Arathorn··on European Commission Trials Matrix to Replace Teams
Speaking as the CEO/CTO of Element... the classic Element apps on mobile were buggy, thanks to being a ~10 year old codebase with no shared code between platforms and effectively the 1st generation Matrix client. Which is why we replaced them over the last few years with Element X, with all the heavy lifting shared between iOS & Android via matrix-rust-sdk (effectively a 3rd gen Matrix SDK).

That said, 70% of our users haven't got the memo yet - we'll do a hard-upgrade when the remaining missing features in Element X (Spaces & Threads) are fully out of Labs.

Meanwhile, Element Web is lagging behind Element X - but we're now in the middle of an incremental in-place upgrade (not a big-bang rewrite, thank goodness) to use matrix-rust-sdk - see our talk from FOSDEM last Sunday for the details: https://fosdem.org/2026/schedule/event/DZJVTS-an-element-web...

Arathorn··on European Commission Trials Matrix to Replace Teams
talking about Teams, right? O:-)
Arathorn··on European Commission Trials Matrix to Replace Teams
When did you try it? Both Matrix the protocol and implementations like Element X have improved immeasurably over the last year or so.
Arathorn··on European Commission Trials Matrix to Replace Teams
https://github.com/element-hq/ess-helm (aka ESS Community) is Element’s FOSS distro fwiw.
Arathorn··on European Commission Trials Matrix to Replace Teams
Element’s topco may be UK based for now, but the vast majority of our business and footprint is in the EU - https://element.io/en/about. All but one of our mobile app team is in the EU for instance (and when we started, the UK was too :|)
Arathorn··on European Commission Trials Matrix to Replace Teams
it’s also not decentralised (unless you bridge it to Matrix), nor end-to-end-encrypted. or standards based.
Arathorn··on European Commission Trials Matrix to Replace Teams
Matrix is a decentralised encrypted chat protocol on which you could build something like Zulip, except decentralised and end-to-end encrypted.

Element is the actual app being trialled here, which feels more like Slack and/or Signal than Zulip. The point is that you get something you can selfhost while also interoperating with other deployments… while also encrypting the data end-to-end with Signal protocol.

Arathorn··on France dumps Zoom and Teams as Europe seeks digital autonomy from the US
We’re not trying to obscure anything: we very well know that Tchap’s adoption of Matrix and their current support (Foundation membership, code contributions to Element Web, evangelisation to other countries, etc.) are key to our success, and we are very grateful for it.

We’re just stating facts: DINUM stopped funding upstream development at Element in 2022/2023 when their post-COVID funding evaporated, and this then directly contributed to the licensing changes at Element at the end of 2023 (https://element.io/blog/element-to-adopt-agplv3/) as we tried to figure out a way to survive (which, thankfully, worked).

But we also know that the Tchap team is very budget constrained internally themselves to keep it running, despite the growing criticality and huge visibility of the service, and are trying to find ways to fix the situation at every level.

This is not a challenge limited to France: the question of how to support the upstream when heavily using open source was one of the top topics of last week’s Open Source Week in Brussels, involving folks at every level in European government.

Arathorn··on France dumps Zoom and Teams as Europe seeks digital autonomy from the US
Yup, DINUM does support the Matrix Foundation, which is appreciated in terms of helping keeping Matrix itself alive and independent.

However, this doesn't help support the folks improving & maintaining Element (either its clients or servers), which is the actual upstream product that Tchap is dependent on. Just like donating to the W3C doesn't help improve Firefox, if you were operationally dependent on a Firefox fork.

Arathorn··on France dumps Zoom and Teams as Europe seeks digital autonomy from the US
France was one of the first to already adopt Matrix. However, when they began Visio, Element was embedding Jitsi for VoIP. Meanwhile Element built Element Call, which is somewhat similar to Visio (except E2EE and decentralised thanks to Matrix). Hopefully the two can converge :)
Arathorn··on France dumps Zoom and Teams as Europe seeks digital autonomy from the US
Tchap (the chat part of the suite) is indeed a fork of Element. Unfortunately they haven't funded upstream development for many years (otherwise both Element and Tchap would be much much better!)

Visio (aka meet) began in parallel with Element's work on MatrixRTC and Element Call. Hopefully the two can converge, given they are both built on LiveKit.

Arathorn··on France dumps Zoom and Teams as Europe seeks digital autonomy from the US
The French video conferencing tool is called Visio, and is here: https://github.com/suitenumerique/meet. It uses LiveKit for video, but doesn't yet use Matrix - the hope is to make it speak MatrixRTC so it can interop nicely with Tchap (the French fork of Element).
Arathorn··on Cloudflare claimed they implemented Matrix on Cloudflare workers. They didn't
What on earth are you talking about? They do entirely different things! MLS is an E2EE protocol, whereas Matrix is effectively a conversation-syncing protocol which supports multiple E2EE mechanisms, including MLS.

Source: Guy who started Matrix, was in the room at IETF 101 when MLS was proposed and ratified it for Matrix, and has been working away on the various approaches to use MLS on Matrix.

Arathorn··on Cloudflare claimed they implemented Matrix on Cloudflare workers. They didn't
I’ve posted a comment on this as Matrix at https://matrix.org/blog/2026/01/28/matrix-on-cloudflare-work... fwiw.
Arathorn··on Cloudflare claimed they implemented Matrix on Cloudflare workers. They didn't
what? that's like saying "you should implement TLS instead of HTTP"!

They do entirely different things: MLS is a key agreement protocol, equivalent to the Double Ratchet that Matrix uses for E2EE today. Matrix can use both.

Arathorn··on Cloudflare claimed they implemented Matrix on Cloudflare workers. They didn't
https://github.com/matrix-org/matrix-rust-sdk/blob/main/CONT... is an example of engineering trying to make a comeback, on the Matrix side at least :)
Arathorn··on France Aiming to Replace Zoom, Google Meet, Microsoft Teams, etc.
You can see uptake at https://stats.tchap.incubateur.net/public/dashboard/8c6560e3... - looks pretty mainstream.

Visio could also use Matrix for E2EE & decentralisation by implementing MatrixRTC - we're talking to them about doing so.

Arathorn··on The Internet Doesn't Suck: Blame Big Tech, Not the Internet
> Either the UI/UX sucks, like Matrix

It's ridiculous to say that the UI/UX of a protocol sucks.

Matrix has clients with good UX and ones with less good UX (especially in the past). I would challenge anyone to install Element X and say that it has a bad UI/UX - it's objectively at least as good as WhatsApp/Signal/iMessage. It's probably not as good as Telegram yet (but TG has it easy given it's not E2EE).

Arathorn··on Ask HN: Which Matrix and Mastodon servers are you using and why?
Synapse via ESS Community (https://element.io/server-suite/community), as it just works and is trivial to update, and tracks the best practices from Element in running a deployment with all the Matrix 2.0 stuff (sliding sync, OIDC auth, Element Call) enabled. The Helm charts are literally the same underlying codebase that powers ESS Pro for folks like NATO and the UN; the only difference is that ESS Community doesn't have the horizontal scaling and enterprise-privileging features that ESS Pro has.

The only gotcha is that Synapse is still not very resource efficient, especially for disk space, although work is finally under way to solve that.

(Meanwhile all our customer deployments run Synapse Pro + ESS Pro in order to get the scalability and Rust worker implementations in Syn Pro.)

Arathorn··on Confer – End to end encrypted AI chat
What were meant to be fast-follow fixes to the new left panel after it shipped in September ended up getting starved out by deadlines for paying customers, frustratingly. The work is happening now however.
Arathorn··on Confer – End to end encrypted AI chat
only around 35% of the publicly visible matrix accounts are on matrix.org…
Arathorn··on XMPP and Metadata
Matrix has a pretty comprehensive featureset with clients across a broad range of platforms.

The accusations of it being overengineered come typically due to the Synapse server implementation being slow. This is basically an artefact of Matrix being quite complicated to provide a byzantine fault tolerant decentralised equivalent to WhatsApp or Slack etc - and time has gone into fixing stability and usability rather than performance. Meanwhile performance is getting better, but progress is slow due to tragedy-of-the-commons related funding challenges. We will get there in the end, though.

Arathorn··on XMPP and Metadata
Synapse has improved; Dendrite has stagnated due to lack of funding; meanwhile there are also rust-native homeservers like Conduit which are beta but smaller footprint. The plan on the Element side is to keep optimising Synapse - the main win to be had is https://docs.google.com/presentation/d/1pKtLl4vCV3-8xz8crvxW...
Arathorn··on XMPP and Metadata
it's clean room.
Arathorn··on Gpg.fail
looks like whoever’s run that Element has disabled debug log reporting. not sure i can do much to help here :/
Arathorn··on Gpg.fail
Weird. Encryption these days (in Element Web/Desktop and Element X at least) should be pretty robust - although this whole identity reset thing is a known bug on Element Web/Desktop. You can submit debug logs from Settings: Help & About: Submit Debug Logs, and hopefully that might give a hint on what's going wrong.
Arathorn··on Gpg.fail
bleurgh. that issue is very actively under investigation (modulo xmas). please can you submit debug logs from Element Web referencing that issue.
← PreviousPage 3 of 34Next →