Nostr notes by MatrixWire

This Week in Matrix 2026-10-23 🔗Matrix Live S13E14 - Live from ...

2026-10-24T01:18:38Z

This Week in Matrix 2026-10-23

🔗Matrix Live S13E14 - Live from The Matrix Conference Hackathon 2026
🔗Dept of The Matrix Conference 🏛️
Andy announces
A very short This Week in Matrix, because this week, most of the Website & Content Working Group have been at (and involved with running) The Matrix Conference.
We hosted over 340 people across two days of talks and workshops, with three rooms of content streamed and available for interaction via our live Matrix rooms during the event.
If you came to the conference, send us your best blåhaj photos! You'll find us on Matrix and also on Mastodon.
There is more to come, but you can catch up on the talks and content online right now.
🔗That's all I know
See you again soon, and be sure to stop by #twim:matrix.org with your updates!
To learn more about how to prepare an entry for TWIM check out the TWIM guide.

https://matrix.org/blog/2026/10/23/this-week-in-matrix-2026-10-23/

#rss #feeds #linksharing #qwibbit

Operator, I need an exit from Big Tech calls MatrixRTC has landed ...

2026-10-23T01:11:55Z

Operator, I need an exit from Big Tech calls

MatrixRTC has landed and Element Call takes off!
All good things come to those who wait! MatrixRTC is finally here: the world’s first decentralised, end-to-end encrypted (E2EE), multiparty VoIP protocol.
For messaging, decentralisation is a strength. Messages get through even when servers drop offline or networks split, and everything syncs when they reconnect. Voice and video also need low latency, though: a word that arrives two seconds late is no use to anyone.
Decentralised VoIP is hard enough. Making it E2EE, multiparty and scalable has been a long and winding road. For group calling we’ve been through FreeSWITCH, Jitsi, peer-to-peer mesh (Third Room and the original Element Call) and waterfall SFUs. We’ve arrived at MatrixRTC, the hardest and final piece of Matrix 2.0 jigsaw - and now we’re talking!
We have fast, smooth and reliable voice and video, and we’ve built it into the protocol as MatrixRTC. Despite all the complexity underneath, it’s E2EE by default, self-hostable, and easy to deploy and use.
So you can finally hang up on Big Tech calls.
Here’s how it works:
MatrixRTC is an open standard for coordinating multiparty, encrypted VoIP across Matrix.
Each Matrix server can run its own conferencing server (a selective forwarding unit, or SFU).
Your server needs an SFU if you want to start calls.
Users send their audio and video to their own server’s SFU. If it doesn’t have one, they use another participant’s.
Because you don’t need your own SFU to join a call, it’s simpler to roll out across the network.
Calls can also be pinned to a chosen set of SFUs to reduce points of failure, instead of always being spread across every participating server.
Users receive audio and video directly from the SFU where it’s being published.
It supports multiple users per call, and multiple devices per user.
True to the Matrix open standard and the sovereignty it delivers, MatrixRTC isn’t tied to any particular VoIP technology. Element Call currently uses LiveKit, but that choice isn't forced in the protocol: you could use other transports too.
Client C has no local SFU, so it publishes to SFU A. Every client subscribes to every SFU carrying a participant it wants to receive.
MatrixRTC may have been built by Element, but it’s very much an open standard. connect2x has implemented it independently in Tammy, and at the Matrix Conference we’re demoing Element Call and Tammy calling each other: cross-vendor interoperable calling through the Matrix open standard!
Element Call rings the changes
Element Call, the calling function within Element, delivers sovereign, E2EE voice and video, running over a federated network with no single point of failure.
With MatrixRTC finalised, Element Call is getting some big, exciting changes.
At launch, Element Call is the same in ESS Community and ESS Pro. The only difference is that calling supports up to around 50 participants when powered by ESS Community and other Synapse deployments, while ESS Pro’s advanced Synapse Pro architecture takes that to around 200. Over time, ESS Pro will make additional enterprise features available for workplace use (see below).
Element Desktop & Web
We’re merging Element Call directly into Element Desktop & Web, and the standalone single-page app at call.element.io will eventually be retired.
Calls will now be E2EE using your real Matrix identity, not the basic shared-key encryption the standalone app relied on. Link-based calling also comes straight into Element Web, with all-new guest access. You can invite people into your own Matrix deployment, rather than onto a throwaway account on an unfederated homeserver, which makes it ideal for scheduled meetings.
Because Element Call is now built into Element Desktop & Web natively, not loaded as a widget, calls get better performance and security. You can also finally pop calls out into their own windows. On top of that, you can juggle multiple calls, share your screen with audio (on some platforms, at least), and, at last, chat during your calls.
The standalone Element Call app will stay around for a while and can still be used as a widget, but we don’t plan to support it indefinitely.
Element Mobile
We’re replacing Element Call entirely with native MatrixRTC support, which finally brings fully native multiparty voice and video calling to iOS and Android. You no longer have to wait for an embedded web browser to spin up, and calls are no longer limited by what that browser can do.
Audio routing works properly, picture-in-picture is seamless, and accessibility is built in from the start. Calls now look and feel like the rest of the app, with no mismatch between Element Call’s web interface and the native UI. Going native also makes it easy to support the latest hardware features, such as the multiple cameras and screens on the iPhone Duo.
A Rust SDK in every app
Both platforms are converging on matrix-rust-rtc, a new Rust SDK that handles the MatrixRTC lifecycle and signalling as a separate crate, much as matrix-sdk-crypto handles E2EE. Element X already uses the new stack, and Element Web is in the process of switching over from matrix-js-sdk. Keeping all our MatrixRTC signalling logic in one place, with a flagship implementation, will make calls much more reliable, just as matrix-sdk-crypto has done for E2EE.
Features, features, everywhere
This unlocks a wave of new Element Call features, which we’re previewing at the Matrix Conference. They’ll land over the coming weeks and months. The code isn’t released yet, because there’s a lot of it including:
Background replacement
Audio levels
Funky new layouts that let you zoom, drag and drop (everyone loved this from the earliest builds of EC, and it’s back!)
Floor control features that let you configure and moderate who can do what in the room
Flexible layouts
Audio levels and background replacement
Features that empower end users - such as secure voice, video and moderation - are always open source. Features that serve organisations over individual users go into ESS Pro and Element Pro. Here, this means that we’re putting the features which undermine E2EE (by doing server-side actions like recording, transcription, and SIP interoperability) into ESS Pro and Element Pro.
Call recording
Call captions
Call transcriptions
SIP dial-in and calling
So how can I use this?
For personal use and small teams, the obvious option is ESS Community. It’s our official Matrix distribution, is free of charge, and should comfortably support up to around 50 calling participants depending on your exact set up.
If you’re a government or large public sector organisation, get in touch about a fully supported ESS Pro deployment. For all sorts of reasons - not least compliance - these types of organisations really shouldn’t be using community software. Also, please make sure you’re not paying a service provider that is free riding on Matrix.
The future
It’s goodbye to separate Element Call links, and hello to calling built right into the app.
We’re also already exploring alternatives to LiveKit as a MatrixRTC transport. We love LiveKit, but the whole point of Matrix is to be a vendor-neutral open standard, so we take choice seriously.
We’ve been working on an exciting new approach, codenamed cSFU. It uses an entirely new VoIP stack and SFU (not even WebRTC!) to deliver much better performance on poor networks, better scalability, and simpler but stronger encryption. We’ll share more soon. In the meantime, here’s a quick demo of more MatrixRTC interoperability, this time over cSFU between Element Call and DINUM’s Visio.
Will this replace the phone network? Who knows, maybe! It’s an enormous leap forward for both Matrix and Element, and we can’t wait to see where it goes.

https://element.io/blog/operator-i-need-an-exit-from-big-tech-calls/

#elementcall #bigtech #techcalls #sfu #matrix #need #voip #matrixconference

#rss #feeds #linksharing #qwibbit

“Matrix, come here.” The world’s first cross-border ...

2026-10-22T01:38:42Z

“Matrix, come here.” The world’s first cross-border government federation demo

On 10 March 1876, in a Boston laboratory, Alexander Graham Bell spoke into his new instrument: "Mr. Watson, come here, I want to see you." Thomas Watson, in the next room, heard every word. Two people, separated by a wall, had spoken through a wire for the first time, and the world's communications have never been the same.
On 21 October 2026, in a Malmö hotel, we saw a similar breakthrough demonstration. This time, the walls were national borders, and in place of the wire was the Matrix open standard. And instead of Bell and Watson, it was:
PersonOrganisationDemo environment
Mathieu Velten
DINUMthe French government’s digitalisation agency
Tchappart of LaSuite, built on community Synapse
Jeroen Franssen
NATOAllied Command Transformation
FluffyChat and ESS Pro
Fabien Marathée
European Commission
Element and ESS Pro
Kenneth Edwall
FörsäkringskassanSweden’s Social Insurance Agency
SAFOS Chatton ESS Classic
Sven Thomsen
Schleswig-Holstein
Element on ESS Pro
Five public sector organisations, five sovereign run deployments, one conversation, spanning three countries and two international institutions. The live demo was a proof point of what governments can do with the Matrix open standard.
DINUM, NATO and Försäkringskassan each carry their own name and branding, and each is run by its own organisation on its own infrastructure. France develops Tchap in-house from open source code. NATO with NI²CE Messenger (Fluffy Chat in the demo environment), and Försäkringskassan with SAFOS Chat, have built their own versions of the Element app, and the others run Element as it comes. What they share isn't a supplier but a standard, and much of the open source code beneath them started life at Element, the company whose founders created Matrix.
Today, they ran a proof of concept of federation between all of them, in demo environments hosted on the same infrastructure as their actual deployments.
The importance of an open standard
Matrix was conceived as the "missing communications layer of the web." Real-time messaging and VoIP running over a decentralised architecture. As with the original internet, decentralisation makes the network highly resilient. It also lets each party host its own server, which keeps it sovereign. In an era of sharpened geopolitics, that combination of sovereignty and resilience is crucial, and so is the end-to-end encryption Matrix provides.
To each their own stack
Every organisation is running its own stack. Some rely on a vendor, some develop their own solutions. Some are open, and some are locked down. But every one of them can talk to the others.
Deployment
Backend
Network filtering
Enterprise control
DINUM
Developed in-house from community Synapse
IP based
Secure Border Gateway developed in-house
European Commission
ESS Pro
Open
None
NATO
ESS Pro
Open
None
Försäkringskassan
ESS Classic
IP based + geo block
Only accessible to MDM enrolled devices
File transfer blocked
Schleswig-Holstein
ESS Pro
Open
None
One government, many conversations
Government communication is rarely a single organisation talking to itself. A ministry coordinates with its agencies. Agencies work with regional and local authorities. Emergency services, health bodies and the armed forces all need to reach one another, often at short notice. Beyond national borders, the same is true between allies, EU institutions and international partners.
Today the majority of that traffic still runs over vendor-controlled solutions, ‘walled garden’ platforms and consumer-grade apps. When a crisis strikes, people reach for whatever works, rather than whatever is secure, sovereign and accountable.
The answer isn't to put every department, region and country on the same product from the same supplier. That simply swaps many silos for one dependency. Government communication at this scale needs technology that is vendor-agnostic and sovereignty-preserving, so each organisation can choose what suits it and keep control of its own stack, data and infrastructure.
Sweden has already shown what this looks like. In May 2026, Försäkringskassan and Trafikverket federated as a part of Sweden’s dSam initiative. The two agencies use different Matrix-based products from different vendors, and they talk to each other seamlessly. The Malmö demo took the same principle across borders.
cross-border governmentSHNATOSBGDINUMFKECHomeserverSecure Border Gateway
Choice by design: an ecosystem of more than 70 providers
Because Matrix is an open standard, no single company owns or controls it. More than 70 providers now compete across the Matrix ecosystem, offering clients, servers, hosting, integration and support. That gives governments, defence organisations and the public sector a genuine choice between interoperable suppliers, and real protection against vendor lock-in.
If a provider no longer meets an organisation's needs, it can move to another without abandoning its users, its history or its connections to partners. Everyone still speaks the same protocol.
Matrix's open source foundations go one step further. Any organisation can choose to take its deployment in-house, running and maintaining the software itself, whether for reasons of policy, security or cost. That option alone changes the relationship with suppliers: vendors have to keep earning the business, because the customer is never trapped.
200M+
people using Matrix-based communications globally
35+
governments with deployed Matrix-based sovereign systems
40+
competitive vendors in the Matrix ecosystem
30+
service providers and hosters offering Matrix-based solutions
Federation on government terms
Federation doesn't mean open to everyone. For official government communication, Matrix deployments typically run as private, or closed, federations. Only servers that have been explicitly approved can connect, and nothing is exposed to the public Matrix network. France's Tchap, Germany's TI-Messenger initiative all work this way.
When a private federation does open a door to a trusted partner, it can do so with precision. A secure border gateway sits at the edge of a deployment and acts as a checkpoint for federation traffic, enforcing policy on which external servers are allowed to connect.
This gives each organisation layered control:
Who: only named, trusted servers and organisations can federate.
What: policies decide which conversations, content and features can cross the border.
How: messages stay end-to-end encrypted, and each party keeps its own data, logs and audit trail on its own infrastructure.
That's the model the Malmö demo put on show: independently run, sovereign deployments that keep their borders, while choosing exactly who they open them to.
European public sector communications that support Matrix open standard federation

https://element.io/blog/matrix-come-here-the-worlds-first-cross-border-government-federation-demo/

#esspro #matrix #open #element #watson #demo #europeancommission #forsakringskassaness #essclassic #alexandergraham

#rss #feeds #linksharing #qwibbit

Matrix Conference kicks off tomorrow: governments, choice and ...

2026-10-21T01:25:12Z

Matrix Conference kicks off tomorrow: governments, choice and sovereignty

The Matrix Conference gets going in earnest tomorrow in Malmö, and even just a quick glance at the programme says a lot about where Matrix is heading. Governments and public sector organisations from more than 15 countries are taking part, along with intergovernmental organisations (IGOs) including the European Commission, NATO Allied Command Transformation (ACT) and the United Nations International Computing Centre (UNICC).
The truly revealing part being that they aren't coming to learn about the Matrix open standard, but to explain how they are already using it.
Government is building on Matrix, in Europe and beyond
Europe is leading the way. Speakers include:
Sweden: the Swedish Social Insurance Agency (Försäkringskassan) and eSam, Sweden's public-sector collaboration programme
France: Tchap, the French government's messaging service
Germany: FITKO, the Federal IT Cooperation body, gematik, the national digital health agency, and BWI, the IT arm of the German Armed Forces
The Netherlands: the Ministry of the Interior and Kingdom Relations
The EU: the European Commission
The momentum is global too, with delegates attending who run major Matrix deployments for their governments in Brazil, the US and Canada.
The highlight for many will be a world first live demo on Wednesday. Building on Sweden's Matrix-based federation, it shows separate governments and intergovernmental organisations collaborating across borders. Each runs its own infrastructure, and all of them talk to each other. More of that on Wednesday…
No choice, no sovereignty
A 'sovereign' platform from a single vendor just swaps one dependency for another.
Genuine sovereignty means governments being able to choose their tech, and being able to subsequently change that tech with minimal hassle. That is why Matrix exists. As an open standard, its whole purpose is interoperability: any compliant deployment, from any vendor, can talk to any other. Organisations keep control of their own infrastructure without cutting themselves off from everyone else.
So it's great to see so many providers of Matrix-based solutions at the conference this year, including adesso, Arawa, BWI, CompuGroup Medical (CGM), connect2x, Famedly, Labrys, Meedio, Nordeck, RISE, Rocket.Chat and Thales (Ercom). A competitive market is a sign of a healthy standard, and it gives buyers the choice upon which sovereignty depends.
Element and ESS Pro: delivering for governments
Our flagship product, Element Server Suite Pro (ESS Pro), is now used by 10 European governments, as well as Australia, Canada and the US and intergovernmental organisations (IGOs) including the European Commission, NATO Allied Command Transformation (ACT) and the United Nations International Computing Centre (UNICC). Many more governments we work with will move to ESS Pro during 2027. As governments adjust to a changing geopolitical climate, ESS Pro gives them a jump start on sovereign communications.
ESS Pro is driving sovereign innovation in four areas.
Public administration
Matrix is emerging as the communications layer of Europe's sovereign workplace.
France: we work with DINUM on Tchap, its Matrix-based messenger and part of La Suite, which now has around 600,000 registered public servants. Arawa is using ESS Pro, with Adullact and Déclic, to bring a similar model to France's local authorities.
Germany: openDesk and Open Productivity both run ESS Pro, as does FITKO for ZaPuK, its government-to-citizen communications service.
Sweden: we also work closely with Försäkringskassan. It was great to see eSam, Försäkringskassan and Trafikverket demonstrate federation, with solutions from Element and Rocket.Chat working together over Matrix.
Across Europe, governments are building their own sovereign digital workplaces, and they're choosing Matrix to connect them. And they are increasingly realising the value of ESS Pro as a high performance, government-ready platform that delivers compliance (ISO 27001 for IT Grundschutz, ISO 5230, CE+, WCAG 2.1 AA) long-term support versions (LTS), enterprise features, regular updates and continual alignment with each evolution of the Matrix protocol.
Air-gapped deployments
After years of SaaS-first development, many organisations are now upgrading their air-gapped environments in response to geopolitics. Some are replacing end-of-life systems such as Skype for Business and Jabber, while others are migrating for the sovereignty of a Matrix-based solution.
Every ESS Pro release now ships with a dedicated air-gapped bundle, tested in our own automated pipeline. Operators can deploy and update without ever touching the internet, backed by long-term support releases and SLAs. With our partner 4Secure, we're also delivering Cross Domain Gateways that move information between high-side and low-side environments under strict policy control.
Mission Partner Environments
In a Mission Partner Environment (MPE), allies need to share information securely without handing control to any one nation. Matrix fits this perfectly. Each partner runs their own sovereign deployment, from any Matrix vendor, yet they can all still federate with each other.
ESS Pro is used by several armed forces. It sits at the heart of the mission partner environment for Olympus Fires, a joint forces exercise. In ESS Pro, we've added capabilities such as policy enforcement and classification labelling to support MPEs. We partner with specialists including Virtru, Cord3 and Veilant, as well as integrators including IBM SiXworks, Everforth ECS, General Dynamics, Leidos and Raytheon.
TI-Messenger
Germany's TI-Messenger is one of the most ambitious Matrix projects anywhere. It aims for a nationwide federation that will eventually connect the country's 150,000 healthcare organisations and most of its citizens.
T-Systems built Telekom TI-Messenger on ESS Pro for BARMER, one of Germany's largest health insurers. This year CompuGroup Medical, whose certified CGM TI-Messenger serves healthcare providers, also partnered with us to build on ESS Pro.
The next wave is the hardest: hundreds of thousands of pharmacies and local clinics, each needing its own secure server. ESS Pro's multi-tenancy lets providers host up to 50 of them on a single shard, cutting resource use by close to 90%. That makes it cost-effective to bring every corner of German healthcare onto Matrix, and we’re delighted to see T-Systems and CGM create offerings for that marketplace based on ESS Pro.
See you in Malmö
Governments are building on Matrix, a competitive ecosystem is giving them real choice, and ESS Pro is helping achieve sovereignty faster. If you're joining us at the conference, come and find the Element team for a chat, a geek out and a cold beer/hot coffee (*delete as applicable).

https://element.io/blog/matrix-conference-kicks-off-tomorrow-governments-choice-and-sovereignty/

#matrixconference #europeancommission #governments #esspro #commandtransformation #computingcentre #natoallied #internationalcomputing #nationsinternational #unitednations

#rss #feeds #linksharing #qwibbit

This Week in Matrix 2026-10-16 🔗Matrix Live S13E13 - Amandine ...

2026-10-17T01:37:05Z

This Week in Matrix 2026-10-16

🔗Matrix Live S13E13 - Amandine & Matthew brace for the conference
🔗Dept of The Matrix Conference 🏛️
Andy announces
As you can see in Matrix Live this week, we are into the final few days before the Conference!
The event is a team effort, and we're very appreciative of the help of our volunteers (40 of you!). We have a couple of slots (and hoodies!) left if you're willing to help out - just take a look at the volunteer schedule. Maybe there is a free shift during a talk you want to see? How about you help film or record it! If you are willing and able to help out, book a slot!
We are also grateful to our sponsors - their contribution plays a critical role in the Foundation’s ability to run the Conference and progress towards sustainability in general. Thank you!
⚓ Anchor sponsor: Element
🏆 Champion sponsors: Connect2x, Famedly and Rocket.Chat
💪 Sustaining sponsors: DINUM, ERCOM and Nordeck
🍻 Welcome party sponsors: Famedly and CGM
📹 Video sponsor: Element
🚆 Community attendance sponsor: Famedly
📊 Track sponsors: CGM (Healthcare) and Element (Public sector)
💻 Hackathon sponsors: Futurewei and the University of Aalborg
We're looking forward to seeing many of you in Malmö and Copenhagen!
If you're not able to join us in person, we hope you'll be following along online.
See you soon!
Your Events WG
🔗Dept of Social Good 🙆
Amandine says
🇪🇺 Europe is working towards more Digital Sovereignty, and as such taking open source and digital commons at the forefront of regulation and political discourse.
From Tchap in France 🇫🇷 to BundesMessenger and openDesk in Germany 🇩🇪, via BEAM in Belgium 🇧🇪, LuxChat in Luxembourg 🇱🇺, and many more, Matrix underpins government communications across Europe: it makes it an obvious case study of how to scale digital commons. However, despite the popularity of Matrix, only one government agency, France's DINUM, commits to support the open standard they all rely on by being a member.
💡 That gap is exactly one of those the new Digital Commons EDIC (DC-EDIC) could close and with this truly impact Europe’s implementation of digital commons. Drawing on 12 years of building Matrix, we've set out how the DC-EDIC can make the most of its five goals, taking a leaf out of the World Health Organization's book. Our suggestions include:
Build a trusted index of open source projects and vendors
Pool funding across Member States
Fund the guardians of open standards, not just new code
Give policymakers real evidence on costs, privacy and security
… and more!
Europe doesn't lack open source builders. What it needs is a body that does the unglamorous work that keeps everyone's lights on.
Read our recommendations in this blog post.
🔗Dept of Spec 📜
Andrew Morgan (anoa) {he/him} announces
Here's your weekly spec update! The heart of Matrix is the specification - and this is modified by Matrix Spec Change (MSC) proposals. Learn more about how the process works at https://spec.matrix.org/proposals.
🔗MSC Status
New MSCs:
MSC4564: Agent status in room messages
MSC4563: direct_message push rule
MSC4560: Stripped state requests over federation
MSCs in Final Comment Period:
MSC4551: Sliding Sync Extensions: Receipts (merge)
MSC4548: Sliding Sync Extensions: Account data (merge)
MSC4543: Sliding Sync Extensions: End-to-end encryption (merge)
MSC4538: Sliding Sync Extensions: To-Device messages (merge)
MSC4354: Sticky Events (merge)
MSC4196: Voice and video calling application for MatrixRTC (merge)
MSC4195: LiveKit transport for MatrixRTC (merge)
MSC4143: MatrixRTC – Real-time communication over Matrix (merge)
Accepted MSCs:
No MSCs were accepted this week.
Closed MSCs:
MSC4076: Let E2EE clients calculate app badge counts themselves (disable_badge_count)
Ended up becoming a Sygnal config option.
[WIP] MSC3898: Native Matrix VoIP signalling for cascaded foci (SFUs, MCUs...)
Superseded by the MatrixRTC sphere of MSCs (MSC4143)
🔗Spec Updates
There's been a huge push in the last week to get Matrix 2.0 ready. A total of 187 comments across all Matrix 2.0 MSCs in the last week alone! A massive thanks to the authors and all of the reviewers for their work here.
The result is that 8 more Matrix 2.0 MSCs entered FCP this week! Sticky Events has received the most scrutiny, but both it and the implementation are now in a good place in the SCT's eyes.
🟢 MSC4140: Cancellable delayed events — Merged.
🟢 Clarifications for MSC4140: Cancellable delayed events — Merged.
🟢 MSC4354: Sticky Events — Entered FCP on 15 October, up from 2 / 8 approvals. Earlier implementation/testing, expiry and visibility concerns are cleared. Federation catch-up flicker and stale notifications are an explicitly accepted remaining risk, not a solved problem or outstanding blocker. Latest visible follow-up is an RTC example correction.
🟢 MSC4551: Sliding Sync Extensions: Receipts — Entered FCP on 13 October. Replaces the closed MSC3960.
🟢 MSC4538: Sliding Sync Extensions: To-Device messages — Entered FCP on 13 October.
🟢 MSC4543: Sliding Sync Extensions: End-to-end encryption — Entered FCP on 13 October. The token-acceptance feasibility question has been answered.
🟢 MSC4548: Sliding Sync Extensions: Account data — Entered FCP on 13 October. Discussion about implementation coverage for enabling/re-enabling and whether Synapse actually differs from the proposal remains open.
🟢 MSC4143: MatrixRTC – Real-time communication over Matrix — Entered FCP on 15 October. Implementation/migration discussion is now resolved. This week’s slot-ID versus event-ID concern was closed by reverting the proposed slot-event-ID addition. Sticky Events is no longer an outstanding dependency concern.
🟢 MSC4195: LiveKit transport for MatrixRTC — Entered FCP on 15 October. Abuse-mitigation discussion is resolved. A new mandatory-multi-SFU objection was addressed by allowing publishing to a remote SFU.
🟢 MSC4196: Voice and video calling application for MatrixRTC — Entered FCP on 15 October. The server-presets discussion is resolved in favour of client-managed slot creation.
🟡 MSC4480: Sliding Sync Extension: Sticky Events — Now proposed for FCP, 1 / 8 approvals. Blockers remain around room-scope transitions, enable/disable behaviour, long-poll wakeups and lazy-loaded membership for rooms leaving scope. Global pos is now incorporated, but how clients detect backlog exhaustion remains under discussion. Implementation also needs checking by the SCT.
🔴 MSC4075: MatrixRTC invites and notifications — Still in proposal review. Earlier invalid-event and slot-lifecycle questions have been addressed; cross-device ringing is now documented as a limitation, but not fixed. A new potentially blocking session-identity/simultaneous-invite question remains open. Sticky-object validation has an author response awaiting closure, and the PR still carries needs-implementation.
Given the 5-day FCP timer, we should see the majority of these actually become accepted by the conference 🎉 A couple MSCs are still outstanding (SS extension: sticky events and MRTC invites/notifications) but the core of everything is there, and those MSCs won't be left out of the 2.0 release.
For now, we can celebrate how much work has been put in to bring these exciting additions to the spec 🥂
🔗Dept of Servers 🏢
🔗Zendrite (website)
pat-s says
Zendrite, the Dendrite fork written in Go, released v3.5.0.
This release focuses on Element Call and on catching up with the spec.
Element Call
MSC4140 delayed events, which Element Call uses to remove crashed clients from calls, including delayed sticky events.
MSC4354 sticky events in sync v2 and sliding sync, which Element Call's matrix_2_0 MatrixRTC mode needs.
MSC4222 state_after in sync v2.
Optional call guest accounts, so people without a Matrix account can join a call by link without open registration; they can only take part in calls and expire after a configurable lifetime.
An end-to-end deployment guide covering LiveKit, lk-jwt-service, the standalone Element Call app and the Helm chart.
Spec support
/versions now advertises Matrix v1.3 through v1.6, which also unblocks bridges such as mautrix-telegram that refused to start against v1.2.
Jump to date (MSC3030) now asks other servers when local history may hide a closer event.
Custom profile fields (MSC4133), refresh tokens (MSC2918), room type filters for the public room directory (MSC3827), leave reasons (MSC2367), key backup deletion (MSC1219), and the remaining Matrix v1.2 MSCs.
Application services now receive redactions.
Fixes
Sliding sync timelines now apply history visibility, so users can no longer read messages from before they were allowed to see them.
Server ACL globs match against the whole server name.
Redacting v11+ member events keeps third_party_invite.signed.
The built-in NATS server is now 2.15.1, which fixes a broker replica that stopped catching up after rejoining on its old storage; HA deployments running their own brokers should upgrade them to 2.15.1 too, and the HA guide explains how to spot and recover a stuck replica.
Release notes: https://codefloe.com/pat-s/zendrite/releases/tag/v3.5.0
Chat: #dendrite:matrix.org
🔗Tuwunel (website)
Enterprise successor to conduwuit, the high-performance and feature-rich fork of Conduit.
june ✿ 🏳️‍⚧️ (it/she/puppy) announces
Tuwunel 1.9.4 stores media in Google Cloud Storage through asafarian's native media provider. On GCE or GKE, Tuwunel can get credentials from the metadata server instead of an exported key (setup).
With oidc_native_auth enabled, the Native OIDC authorization, account and device-login pages offer a choice of local password or configured SSO providers. tototomate123 built the provider choice at utop-top's request. Account pages gained the choice after utop-top's report that Element X's Manage Account jumped straight to SSO.
arnolicious added controls to limit profile reads to people sharing a room and prevent regular users from setting display names or creating room aliases.
obodnikov added per-account password limits, got JWT B64HMAC working, and ensured JWT login rejects deactivated accounts. The last admin can no longer be deactivated, and removing emergency_password clears the server user's sessions at next startup.
basnijholt fixed thread counts, root bundles and latest replies after redactions. MindRoom Chat kept fetching 13 pages for a thread of roughly 1,000 events because the count still included a redacted reply.
Federated key answers now keep only the answering server's users, and Sliding Sync withholds invited and knocked rooms' timelines.
Startup now repairs the short-id residue behind the repair refusal dogarrowtype reported. mav96 supplied a second log. Uncertain data is preserved.
az4521 fixed URL previews of kkinstagram.com links, and reported the room version 12 create events that caused problems for force-set-room-state-from-server. Thanks to morteng's report, a mistyped !admin users reset-password no longer creates state.
SatvikMishra08 fixed the federate_created_rooms documentation issue edenworky reported. June refreshed dependencies and moved OpenTelemetry to 0.33.
Notes: https://github.com/matrix-construct/tuwunel/blob/f473d9a4a8342514302884041e0ccfea1ad503fc/RELEASE.md
💕 GitHub ✦ Releases ✦ DockerHub ✦ Playbook ✦ Containers ✦ Documentation ✦ Enterprise 🐕️ Tuwunel 💕
🔗Synapse (website)
Synapse is a Matrix homeserver implementation developed by Element.
madlittlemods (Eric Eastwood) says
This week we have a new release, Synapse 1.163.0. To highlight:
We can finally see light at the end of the tunnel with our Matrix v1.17 project. Synapse now advertises support for Matrix v1.14 and v1.15 (#20137, #20286), and Matrix v1.16 and v1.17 will come as part of the next release (already merged). Of course, the spec keeps evolving, so the march isn't over, but we've accomplished the concrete goal we set out for this quarter! 🎉
The experimental MSC4354 Sticky Events implementation got a number of updates to improve robustness. Synapse now catches up remote homeservers with any sticky events they may have missed (#20165), handles sticky events being redacted (#20232), makes sure new joiners know about all sticky events in the room (#20233), and uses sharded tokens to prevent race conditions when using workers (#20186).
Fixed an edge case where the push badge count could undercount. Because it needs specific conditions and because most clients calculate the badge count themselves, this might not be a very commonly visible problem in the wild, but it fixed a Complement test flake that has been plaguing us 🙏 (#20237).
On the Rust side, we reduced contention on the Python GIL (global interpreter lock), and the need to block waiting for it, when handing off data from async Rust to Python (#20252, #20267).
While it's "just" a dependency swap, URL previews now parse HTML with beautifulsoup4 instead of lxml, moving us off libxml2, which is no longer maintained. It's a nice bit of maintenance work that even lets us remove some of our own code, since beautifulsoup4 handles charset detection for us (a rare PR that removes more code than it adds 🔥) (#19301, thanks to @clokep).
Thank you to all our contributors for helping to make Synapse the best it can be. As always, feel free to stop by #synapse:matrix.org to join in on the discussion, and if you encounter a bug, make sure to report it.
🔗Dept of Clients 📱
🔗Vommet (website)
Dark Collective announces
A Discord-like Matrix client that doesn't suck.
Vommet is an LLM-assisted fork of the excellent Commet Matrix client. I run a large Discord community I've been trying to move to Matrix for years, but no matter what client we tried, people kept bouncing off it. Everyone had a missing feature (Telegram sticker packs, screen sharing with audio on Linux, UI friction, etc.) that sent them back to Discord, even as recent policy changes have left many of our members wishing for a real alternative. So I've been working with community members one by one, finding every missing feature, bug or UI wart that makes Matrix hard to use, and fixing it.
Commet doesn't accept LLM contributions, which we respect, so nothing goes upstream. The name is a joke about AI slop and our rapid release cadence. But like the title says, it doesn't suck. Actually, we think it's really, really good.
Voice and calls
Discord-like voice rooms with a "Voice Connected" card, mute and deafen next to your name, and volume sliders
Push to talk, with a key that works while you're in a game (Windows and X11) and a hold-to-talk button on phones
Watch streams like Discord, plus screen sharing with audio: on Linux, pick any app's audio or everything except voice chat apps
Noise suppression in calls (RNNoise or DeepFilterNet3)
Calls in any room or DM, not just voice rooms
Voice chat with your Discord friends using Nether Voice Bridge
Chat
Mass-import your favorite sticker packs from Telegram (and Signal), right in the app, into shareable sticker rooms
Several pictures posted together show up as one Telegram-style mosaic, and you can flip through a room's pictures like a gallery
Send messages while offline, like Telegram: they go out when you're back, even after a restart
Better thread support, with several display modes for thread cards
Voice messages, and (just landed, desktop only so far) on-device transcription like in Telegram
Spoilers on pictures, bridged GIFs that actually play as GIFs, and plain example.com text turned into links like on Telegram
Forwarding, drafts, multi-select, a formatting bar, and Discord-style <t:timestamp> times shown in everyone's own time zone
People and spaces
Explore: browse any homeserver's public room directory, and peek inside a space before you join it
See which spaces and rooms you share with someone on their profile
Block people, with a clear "You blocked" notice in the DM
Get banned from a room and it stays in your list, greyed, with the mod's reason, so you can keep reading until you choose to leave
Banners for spaces and rooms, and better nested subspaces
When joining a space, pick which of its rooms and subspaces you join
Look and feel
Lots of UI improvements (see the screenshots on the website). When in doubt I rip off Discord, the good parts at l

https://matrix.org/blog/2026/10/16/this-week-in-matrix-2026-10-16/

#rss #feeds #linksharing #qwibbit

This Week in Matrix 2026-07-17 🔗Matrix Live S13E02 - Amandine ...

2026-10-15T13:55:47Z

This Week in Matrix 2026-07-17

🔗Matrix Live S13E02 - Amandine talks Foundation Mission & Funding and Matthew talks about P2P
🔗Dept of Spec 📜
uhoreg says
Here's your weekly spec update! The heart of Matrix is the specification - and this is modified by Matrix Spec Change (MSC) proposals. Learn more about how the process works at https://spec.matrix.org/proposals.
🔗MSC Status
New MSCs:
MSC4509: Auto join on accepted knock
MSC4508: Sliding Sync Extension: Typing Notifications
MSC4507: Return additional room state from /_matrix/federation/v1/hierarchy/{roomId}
MSC4506: Push Rules for Knocking
MSC4505: Push Rules for Live Location Sharing
MSC4504: Using a global version number for the entire specification (v2)
MSC4503: External Protocol Handles
MSCs in Final Comment Period:
No MSCs are in FCP.
Accepted MSCs:
MSC3784: Using room type of m.policy for policy rooms
Closed MSCs:
No MSCs were closed/rejected this week.
🔗Dept of Servers 🏢
🔗Tuwunel (website)
Enterprise successor to conduwuit, the high-performance and feature-rich fork of Conduit.
june ✿ 🏳️‍⚧️ (it/she/puppy) announces
Tuwunel 1.8.2 brings richer, more private link previews: preview media now covers video and audio as well as images, relayed through the server so the previewed site sees Tuwunel rather than the person who shared the link. az4521's contribution added the proxying, separate page and media user-agents, and the video previews they had requested.
Packaging expanded on several fronts, all from June: RPM and COPR builds, a SELinux policy module, an apt repository published from CI, and Debian packaging that adopts an existing conduwuit or Conduit database in place.
Appservices now receive more in every transaction: device-list changes and one-time-key counts via MSC3202 and to-device events via MSC4203, both opened by dark-collective. The Synapse-compatible admin API added server-notice, redaction, login-as, federation-destination and media endpoints, and operators can cap forward extremities and list or prune a room's leaves from the admin console.
Federation delivery no longer runs hot against a server that keeps failing: the per-server backoff now reads a server's full failure history rather than one time bucket. Tuwunel also refuses to open over database remnants without a readable manifest, after ItsLiyua reported and diagnosed a wipe-on-open, and native OIDC login completes again after failing mid-redirect.
On spec: v1.18 and v1.19 are declared, basnijholt got MatrixRTC transport discovery working for Element Call without a token, and one-time-key counts match Synapse so a drained client replenishes its keys instead of starving. obodnikov repaired non-unix and macOS builds.
Full release notes: https://github.com/matrix-construct/tuwunel/blob/9099defe5ee340140ca0d56e478751637f34354d/RELEASE.md
💕 GitHub ✦ Releases ✦ DockerHub ✦ Playbook ✦ Containers ✦ Documentation 🐕️ Tuwunel 💕
🔗Synapse (website)
Synapse is a Matrix homeserver implementation developed by Element.
madlittlemods (Eric Eastwood) says
This week we have a new release candidate, Synapse v1.157.0rc1. To highlight:
As part of the 'Synapse rustification' work, we ported the synchronous core of client event serialization to Rust (#19837), and Rust code can now make database calls through the same connection pool as Python (#19878). This unlocks being able to write more endpoints in Rust (/versions is backed by Rust now). To keep all this new async Rust testable, our test utilities now drive the Tokio runtime in Rust just as well as the Twisted reactor in Python (#19871, #19879).
Sliding Sync picked up several database fixes: a deadlock fix (#19826) and new indexes that should smooth out some inconsistent performance (#19912, #19923).
Presence got a few minor performance improvements and tuning options (#19939, #19941, #19942, #19948, #19935) but we still recommend keeping it disabled for any large deployment as the current paradigm doesn't really scale.
The war against test flakes continues. We tracked down and fixed a few more this week (#19890, #19929). Some of this work manifests as fixing flawed tests in other repos (like Complement) but we also merged a fix in our workerized Docker image to prevent nginx from temporarily marking workers as unavailable when a test restarts a server (#19936). See #18537 for a loose list of flakes we experience often.
Support for the deprecated MSC3861 Auth Delegation (experimental_features.msc3861) has been dropped in this version, in favour of the stable Matrix Authentication Service integration. This was deprecated last August but is finally being removed now.
On the experimental side: new support for MSC4446 to allow moving fully read markers backwards (#19663 thanks @SpiritCroc @ Beeper!), and the MSC4140 delayed events implementation now limits the number of delayed events a user can have scheduled at once (#19539).
... and a whole lot more!
Thank you to all our contributors for helping to make Synapse the best it can be. As always, feel free to stop by #synapse:matrix.org to join in on the discussion and if you encounter a bug make sure to report it here.
🔗continuwuity (website)
Continuwuity is a community-driven Matrix homeserver in Rust.
nex [starstruck] reports
Continuwuity v26.6.0 has been released! This major release is packed full to the brim with new features and bug fixes, to the point that it makes you wonder "how much of the codebase can be replaced before it's a new project".
This is a landmark milestone for the project. With over 700 commits since our last feature release, ~65,000 lines of code have been changed across >500 files. In the past year alone, we've changed >180,000 lines of code across >900 files. That's an incredible amount of code to have written since the April of 2025, but we didn't do it alone; 80+ contributors have helped us build this software, and that's not even including the hundreds more that have reported bugs and helped out in our thriving community.
I've been saying for a long time now that there's big things on the horizon - this is the horizon! This huge release includes long awaited and highly demanded features, including (but absolutely not limited to): Native OAuth2 and OIDC support, static musl binaries, room upgrade overhauls, improvements to federation catch-up and state resolution, and many fixes to sync.
But TWIM isn't for changelogs, the release notes are! Go read them!
All Continuwuity deployments are encouraged to upgrade as soon as possible - there are hundreds of internal changes that improve the performance and reliability of the server, not to mention a bunch of new features everyone has been practically begging for in the past 3 months. If you run into any trouble, don't hesitate to reach out!
A keen eye may have also noticed we changed our version scheme! Instead of using "zerover", we're now using "calver", which means our versions are now based on the date in which they enter the release cycle. This should more accurately reflect our development cycle, and allows us to build things even faster than before.
There's still even more to come, so stay tuned (perhaps by joining our announcements room). If you have any questions or concerns, you can reach out in our support room, and even if you don't have a reason to, you should check out the rest of our rooms in our space. The general rooms continue to be more active than your local town square, I bet.
If you like the work we're doing, please consider giving us a star on GitHub: https://github.com/continuwuity/continuwuity. While we don't primarily host there, leaving a star boosts our visibility! Also recommend the project to your friends, if they aren't already using it.
Anyway, enough yammering. I've got more code to write.
➡️ https://continuwuity.org
nex [starstruck] reports
Continuwuity v26.6.2 has been released, which fixes several bugs uncovered shortly after v26.6.0 started being adopted. It is recommended you skip v26.6.0 and upgrade to v26.6.2.
If you find any new bugs, please let us know by opening an issue on our forge. The team is very busy now but we're working as fast as we can to smooth over the teething pains of a major release, and reporting issues will allow us to prioritise work more efficiently. Otherwise, questions and concerns can be raised in #continuwuity:continuwuity.org as usual!
Breaking change notice: some bugs fixed in this version have created an incompatibility with Synapse and as such you will be unable to receive invites from Synapse servers if you update to this version. Do not upgrade if this is something you require, and perhaps subscribe to the relevant issue to be notified when the problem is resolved.
➡️ https://continuwuity.org
🔗Dept of Clients 📱
🔗Tesseract
Marco says
Hello again! 0.8.14 and 0.8.15 went out since the last post!
Due to popular demand (one github issue), Tesseract now supports legacy non-MAS username/password login. Only existing accounts, creating accounts is not supported.
Now you can edit your emoji & sticker packs! During the transition to the stable MSC2545 names, packs will be read from both unstable and stable room state names, and NEW packs will also be saved on both (existing packs will be updated as they are). AND the personal sticker pack is still supported, even if it fell off the spec. So every pack created with other apps should be there! A checkbox in the new advanced settings tab (via the 'advanced' button in the about tab) allows you to only use the stable names, if that's your thing. Choices for everyone :)
Custom emojis now work everywhere, via shortcodes, emoji picker, rendered in the composer and in the timeline.
You can also see all the room media with the new room media gallery available from the room info panel.
Calls are still under a compile flag, but they will probably be enabled by default in the next release. Stay tuned.
Check it out while it's hot!
🔗Harmony
catcraft reports
Hello everyone!
Reset the counter, because another matrix client has been released!
Harmony is different from most other clients in that it supports loading user-provided plugins at runtime.
In fact, the entire client is built on top of this plugin system.
This means that everyone can develop features for it, without needing to maintain a fork and go through the pull request process.
It also allows for a more modular approach to how you use your client (you can turn off support for most features).
Harmony was designed from the start to be easily extensible, so anyone with some JavaScript knowledge can make plugins!
We even have documentation!
Even if you don't plan on developing plugins, Harmony currently supports most features required for daily use, such as
End-to-end encryption and device verification
Spaces (+ nested subspaces)
Attachments
Custom emoji
Reactions
Rich replies
Link previews
and more!
You can find more information and pre-built releases on Codeberg here.
You can also join our matrix rooms using the links below:
Space
General room
Plugin developer room
Announcements
Happy hacking!
🔗Element X iOS (website)
A total rewrite of Element iOS using the Matrix Rust SDK underneath and targeting devices running iOS 17+.
Doug says
This week we made the RC for version 26.07.4, which is available on TestFlight and will land on the App Store on Monday. This release consists of minor changes: calls are always displayed in dark mode and we’ve fixed an issue that could occur when opening rooms whilst your device was offline along with a crash in the Sentry crate that’s bundled within the SDK.
The work on User Status continued this week and is progressing well. We hope to test the new Sliding Sync extension against a live server next week.
Separately we’ve been iterating on our test suite to fix some long-standing issues with flakiness and in the process have added a test parameter that simulates running on a heavily overloaded CI runner (by spawning 20× yes > /dev/null, if you're interested 😄).
🔗Element X Android (website)
Android Matrix messenger application using the Matrix Rust SDK and Jetpack Compose.
Benoit announces
Hey all! 👋 A quick look at what landed in Element X Android this last week.
Content scanner integration — initial support for server-side content/antivirus scanning of media in Element Pro, so attachments can be checked before you view them.
Media & gallery polish — your in-progress caption is now kept when you attach media, and replies to galleries show a handy item-count placeholder in the reply box.
Onboarding refresh — the onboarding screens were reworked to match the latest Figma designs.
Jorge says
Hi everyone, this week is a quiet one, since we've been working mainly on:
Improving accessibility in the app.
Bug fixing, including the issue with access to homeservers in local networks in Android 17 and some live location ones.
UX tweaks in the app and Element Call.
Starting to build a new user status feature.
Building some Element Pro features for parity with the classic Element Android app.
A new v26.07.1 release candidate should be available soon for beta users too with most of these changes.
That's all for now, enjoy the summer, avoid the heat and stay hydrated!
🔗Matrix Federation Stats 📊
Aine [etke.cc] announces
TWIM
collected by MatrixRooms.info - an MRS instance by etke.cc
As of today, 19723 Matrix federateable servers have been discovered by matrixrooms.info, 4155 (21.1%) of them are publishing their rooms directory over federation.
The published directories contain 20416 rooms.
The most popular server software among the online servers is:
synapse: 15508 (78.6%)
continuwuity: 1633 (8.3%)
conduit: 567 (2.9%)
dendrite: 323 (1.6%)
Stats timeline is available on 📊 MatrixRooms.info/stats
🧩 Integrations with apps and servers | 💜 Support the project | 👉 How to add your server | 🙅 How to remove your server
🔗Dept of Ping 🏓
Here we reveal, rank, and applaud the homeservers with the lowest ping, as measured by pingbot, a maubot that you can host on your own server.
Join #ping:maunium.net to experience the fun live, and to find out how to add YOUR server to the game.
RankHostnameMedian MS
1vrkknn.net184
2continuwuity.org185
3sp5mi.eu230
4starseeker.nexus237
5raccoon.cafe264
6zirco.dev269
7nerdhouse.io273
8piros.pitty.hu317
9waywardinn.com335
10awesomesheep48.ca336
🔗That's all I know
See you next week, and be sure to stop by #twim:matrix.org with your updates!
To learn more about how to prepare an entry for TWIM check out the TWIM guide.

https://matrix.org/blog/2026/07/17/this-week-in-matrix-2026-07-17/

This Week in Matrix 2026-07-24 🔗Matrix Live S13E03 – ...

2026-10-15T12:26:58Z

This Week in Matrix 2026-07-24

🔗Matrix Live S13E03 – Homeserver Decentralisation Working Group
🔗Dept of Events and Talks 🗣️
🔗The Matrix Conference
HarHarLinks announces
🔗Last Call for The Matrix Conference Merch Preorders!
Matrix events such as the Conference are always great opportunities to do something special with merch, with exclusive designs never to return! At least for me that's one of the many parts I love about it, right next to the souvenir value of course! For 2026, we decided that last year's white on black edition conference T-shirt and zipper hoodie were plenty stylish, but we wanted more than a re-run. So we decided to expand up everyone's wardrobe opportunities and are going to have black on white (well, reasonably bright grey) this time around! The embroidering will return for the zipper hoodie because we love the quality, feel, and effect, while the T-shirt will be printed. You also might remember the baseball caps we had at FOSDEM earlier this year. Since Conf is going to be in autumn on the verge of the cold season, we are making embroidered beanies in the classic Matrix white on black to keep your ears warm when you go outside to explore Malmö in the evening. Finally we noticed there are still parts of your bodies without Matrix clothing available for them, so I'm really excited to introduce the Matrix socks in Sweden's national colours.
All of this can be preordered before the end of July since we have to make sure we keep to production deadlines. We will do our best to make some of each available for spontaneous decisions on site, but cannot guarantee availability there.
Reserve yours at https://conference.matrix.org/register/!
PS: You will need to make sure your preorder is picked up during the Conference in Malmö, but you can totally order just your merch today if you're not yet sure which ticket you are going to get!
🔗More Volunteering Slots Available
The Matrix Conference is made possible thanks to our awesome sponsors financing it just as well as our awesome volunteer team staffing the welcome desk, operating video equipment, and generally jumping in whenever an extra hand is needed. We have onboarded a lot of volunteers already and our shift booking system was totally booked out while we worked through all these applications from you amazing people, and some have already asked when more will be available. This is (as of writing) the case! If you were waiting for one to free up again, head to our volunteering system and sign up for two shifts to receive a free ticket to the Conference, the limited edition team-only zipper hoodie in special colours, and of course a lot of experience, satisfaction and fun from helping making The Matrix Conference happen!
If you've already signed up a while ago and have received neither an email nor invite on Matrix from us yet, please reach out to us over at #events-wg:matrix.org.
See you soon, your Events WG.
🔗Dept of Working Groups 💪
🔗Homeserver Decentralisation Working Group (website)
The Homeserver Decentralisation Working Group aims to promote decentralisation of the Matrix network by fostering a smoother onboarding experience (to homeservers and clients) on homeservers other than matrix.org, and might propose additional measures in the ecosystem as a whole.
Nicolas Da Mutten announces
I'm happy to report that the Homeserver Decentralisation Working Group graduated from a community group to an official foundation group! Thanks @thedarkwizard:waywardinn.com for sponsoring us and being so proactive! 🎉
Since our last report, we now finalized our policy. While it is finished in its current form, PRs are still welcome, if something needs to be changed. It's not supposed to be set in stone but rather to be a living document.
Going forward we will be focusing on the process of maintaining and automating the future server list and onboarding servers.
🔗Dept of Spec 📜
Andrew Morgan (anoa) {he/him} reports
Here's your weekly spec update! The heart of Matrix is the specification - and this is modified by Matrix Spec Change (MSC) proposals. Learn more about how the process works at https://spec.matrix.org/proposals.
🔗MSC Status
New MSCs:
MSC4518: Registries
MSC4517: Federated thirdparty lookups
MSC4515: RTC Transports discovery for widgets
MSC4514: EDU size limit
MSC4513: Standard HTTP status codes for all endpoints, current and future
MSC4512: Delegating parts of the Client-Server and Server-Server API to application services
MSC4511: Topological query API with sparse fieldsets and Merkleized metadata
MSCs in Final Comment Period:
MSC4319: Room member events for invite and knock rooms in the /sync response (merge)
Accepted MSCs:
No MSCs were accepted this week.
Closed MSCs:
MSC4069: Inhibit profile propagation
Closed in favour of https://github.com/matrix-org/matrix-spec-proposals/pull/4466
MSC3866: M_USER_AWAITING_APPROVAL error code
Closed by the author due to lack of time.
MSC3912: Redaction of related events
Closed by the author due to lack of time.
MSC3026: "busy" presence state
Closed by the author due to lack of time.
MSC3720: Account status
Closed by the author due to lack of time.
MSC2654: Unread counts
Closed by the author due to lack of time.
MSC4146: Shared Message Drafts
Closed by the author in favour of a better, future solution.
🔗Spec Updates
Lots of updates in spec world this week! New MSCs, MSCs being closed in favour of others or due to lack of time. Don't forget that a closed MSC can always be opened under a new MSC # if someone thinks its worth pursuing - the idea isn't dead forever!
MSC4319 entered final comment period this week. It proposes that additional m.room.member events be included when receiving room state during an invite or knock. This allows for clients (and users) to receive information about who invited them (or knocked on the room), when the invite (or knock) occurred etc.
FCP ends in 3 days, so go and check the MSC out for any last minute additions/changes if this is an area you're interested in!
🔗Dept of Clients 📱
🔗Nexus (website)
Matrix client made with Flutter and a Gomuks backend.
QuadRadical (Ping) announces
🔗What's new?
Hello TWIM! You may have been wondering what has been happening with Nexus, as there hasn't been an update in a while. Well, here it is:
Support for OAuth login, and removal of UIAA login
Support for sending media (images, videos, files, etc)
Support for viewing pinned events, thanks to @istalri:federated.nexus for this!
A settings page
Experimental support for MacOS, if you use MacOS please join our support room to help with testing, it's most appreciated!
And a whole lot of bug fixes and smaller features!
🔗Get involved!
If you want to help with development or simply keep up with new features, join our Matrix room at https://matrix.to/#/#nexus:federated.nexus or check out the Git repo at https://nexus.federated.nexus!
🔗Fractal (website)
Matrix messaging app for GNOME written in Rust.
Kévin Commaille says
A regression in Fractal 14 meant that display names could not be changed in account settings anymore for some servers. Fractal 14.1 was just released to address this issue. Thanks to Jack S. for discovering it soon after the 14 release!
This version is available right now on Flathub.
If you want to help us avoid regressions like that in the future, you could use Fractal Nightly. You could even get rid of our remaining bugs yourself!
🔗Element X iOS (website)
A total rewrite of Element iOS using the Matrix Rust SDK underneath and targeting devices running iOS 17+.
Doug says
This week we’ve been hard at work with the 3 next features for the app:
We saw our first data syncing to the app from Synapse for User Status 🎉
We’re adding support for Media Galleries to match Element X Android. Sending is merged and we’re now iterating on the timeline rendering. 🖼️
Work on Message Search has resumed after some team holidays and is looking really good! 🔍
Other than that 26.07.4 landed on the App Store on Monday with all the changes mentioned last week.
🔗Element X Android (website)
Android Matrix messenger application using the Matrix Rust SDK and Jetpack Compose.
Jorge says
This has been a quiet week, mostly focused on continuing the work on WIP features like user status, and fixing bugs and accessibility issues.
Element X Android v26.07.1 has been published and it contains all the changes we told you about in previous TWIM messages.
🔗Dept of SDKs and Frameworks 🧰
🔗matrix-nio
OdoItal reports
matrix-nio 0.26.0
This release swaps the end-to-end encryption backend from libolm to vodozemac, drops end-of-life Python versions, and modernizes the project's tooling.
This is a breaking release. Encryption now runs on vodozemac instead of libolm/python-olm, some encryption defaults have changed, and Python 3.9 and older are no longer supported.
🔗⚠️ Breaking changes
Encryption backend replaced: libolm/python-olm → vodozemac. The e2e extra now depends on vodozemac, and libolm is no longer required as a system dependency.
Store migration is automatic on first load. Stores created with a libolm pickle version older than 4 (roughly, pre-December 2021) can only be migrated if the optional python-olm >= 3.2.7 package is installed at upgrade time — otherwise those pickles cannot be read.
hmac-sha256 is gone for SAS verification. Only hkdf-hmac-sha256 is offered as a message authentication code, so verifying against clients that only support hmac-sha256 is no longer possible.
Account.remove_one_time_keys() has been removed, as it is no longer supported by the underlying library.
Dropped Python 3.8 and 3.9. The minimum supported version is now Python 3.10. Python 3.14 is now supported. Supported: 3.10, 3.11, 3.12, 3.13, 3.14.
🔗Additions
Added unread_thread_notifications to SyncResponse.
🔗Bug fixes
Fixed get_openid_token, which requires an empty JSON body to be sent.
Fixed printing of FileResponse when a download is saved to a file.
🔗Internal / maintenance
Adopted uv for project management, applied pyupgrade and linting, and bumped dependencies.
Unpinned dependencies for more flexible version resolution.
Upgraded the underlying vodozemac to 0.10.0.
🔗vodozemac-python (website)
Python bindings for vodozemac, the implementation of Olm and Megolm in pure Rust.
OdoItal says
vodozemac-python 0.10.0
This release upgrades the underlying vodozemac Rust library to 0.10.0. The Python package version tracks the Rust crate, so this is 0.10.0.
This is a breaking release. The public Python API is nearly unchanged, but several operations that previously always succeeded can now raise an exception, and Python 3.9 is no longer supported.
🔗⚠️ Breaking changes
Some operations are now fallible. As of upstream vodozemac 0.10.0, Diffie-Hellman can reject malicious/low-order keys, which makes the following methods able to raise where they previously always returned a value:
Account.create_outbound_session → may raise SessionCreationException
Session.encrypt → may raise the new OlmEncryptionException
PkEncryption.encrypt → may raise PkDecodeException
Method signatures are unchanged; wrap these calls in error handling if you process untrusted keys.
Stricter Ed25519 signature verification is now mandatory. Non-strict verification has been removed upstream. Signatures that were maliciously crafted and previously accepted may now be rejected.
Dropped Python 3.9. The minimum supported version is now Python 3.10. Python 3.14 is now supported. Supported: 3.10, 3.11, 3.12, 3.13, 3.14.
🔗Additions
New OlmEncryptionException, raised on Olm encryption failures (mirrors the existing OlmDecryptionException).
🔗Internal / maintenance
Upgraded pyo3 0.28 → 0.29 and maturin to 1.14.
Bumped thiserror and refreshed transitive Rust and Python dev dependencies.
Session configuration continues to use protocol version 1 for all Olm/Megolm sessions; this is unchanged from 0.9.
🔗Dept of Ops 🛠
🔗Matrix Connectivity Tester (website)
A web interface to debug and troubleshoot Matrix connectivity issues.
MTRNord (they/them) reports
I just released v0.1.0 (and v0.1.1) of the elixir connectivity tester. This one's a bigger change than the last few: the Rust backend and the separate frontend are now merged into a single Elixir/Phoenix app that ships the web UI, API, alerting, and an OAuth2/OIDC provider together in one deployable unit. Development also moved off GitHub, so the old two-repo setup is gone.
🔗What's Changed
Unified the previously separate backend (Rust) and frontend into one Elixir/Phoenix app. All existing checks (federation, DNS/well-known, TLS, split-brain detection, MatrixRTC, the OAuth2-backed alerts) carried over
New federation checks along the way: an outgoing-federation self-check (does the target server actually reach us back over federation, not just the other way round) (thanks @networkexception:nwex.de for that idea!), dual-stack/protocol asymmetry detection, and signing-key-expiry warnings
Public opt-in statistics page now also breaks down MSC/unstable-feature adoption by server software family and timeframe, not just plain pass/fail counts
Permalinks: freeze and share the exact result (federation check + client-side probe) you saw, instead of asking someone to re-run the check themselves
Export a result as JSON, Markdown, or print/Save-as-PDF
Shields.io-style status badge for READMEs (/api/badge/federation.svg)
Batch endpoint to check several servers in one call
Full OpenAPI spec with an interactive Redoc UI at /api-docs
Uptime percentage (7d/14d/30d) per alert in the alerts overview
Docs search across the built-in /docs pages
Cookieless analytics via self-hosted Plausible (no personal data, no cookies)
Code moved to self-hosted Phorge: https://phorge.mtrnord.blog/source/mcte/repository/main/. The old GitHub repos are no longer where development happens.
Find the deployed version at https://connectivity-tester.mtrnord.blog or, if you're daring, https://stage.connectivity-tester.mtrnord.blog for the staging deployment, which gets changes earlier but at less stability.
If you find issues or want to request features, please direct them at the Phorge repository or the Forum at https://forum.mtrnord.blog/c/matrix-connectivity-tester/5 :)
Weblate has also been updated for this project pivot to elixir. You can find the components over at https://weblate.mtrnord.blog/projects/matrix-connectivity-tester-elixir/
🔗Dept of Interesting Projects 🛰️
nex [starstruck] reports
star rewrote my mxtoken tool so that it doesn't explode if you use a machine other than my own: https://starstruck.systems/mxtoken2. It additionally also properly supports SSO. The legacy mxtoken will continue to show existing sessions prior to the rewrite, but no new sessions can be created through it. Use star's rewrite for that.
I don't think I've announced mxtoken before, so for those who haven't already heard about it, mxtoken is a visual (web) interface that supports various login methods to fetch access tokens, which can safely be re-used in bots, webhooks, curl requests, etc, as they do not set up crypto and are not bound to a browser. It stores all sessions in localstorage, and has a couple management options for refreshing tokens and logging out devices.
🔗Matrix Federation Stats 📊
Aine [etke.cc] says
TWIM
collected by MatrixRooms.info - an MRS instance by etke.cc
As of today, 19800 Matrix federateable servers have been discovered by matrixrooms.info, 4163 (21.0%) of them are publishing their rooms directory over federation.
The published directories contain 20314 rooms.
The most popular server software among the online servers is:
synapse: 15528 (78.4%)
continuwuity: 1669 (8.4%)
conduit: 559 (2.8%)
dendrite: 322 (1.6%)
Stats timeline is available on 📊 MatrixRooms.info/stats
🧩 Integrations with apps and servers | 💜 Support the project | 👉 How to add your server | 🙅 How to remove your server
🔗Dept of Ping 🏓
Here we reveal, rank, and applaud the homeservers with the lowest ping, as measured by pingbot, a maubot that you can host on your own server.
Join #ping:maunium.net to experience the fun live, and to find out how to add YOUR server to the game.
RankHostnameMedian MS
1nerdhouse.io268
2cisnt.uk338.5
3ncat.cafe383
4ellis.link435
5victorewik.es458
6matrix.maciej.cloud469
7feralfox.net559
8blahaj.club881
9b

https://matrix.org/blog/2026/07/24/this-week-in-matrix-2026-07-24/

This Week in Matrix 2026-07-31 🔗Dept of Events and Talks ...

2026-10-15T11:09:29Z

This Week in Matrix 2026-07-31

🔗Dept of Events and Talks 🗣️
🔗Matrix Community Workation Krems 2026
Yan says
In case you haven't spent the last few years asleep under a rock, you've probably come across the Matrix Workations: get-togethers where people who work with, on and for Matrix meet up to work together and side by side (here's what the past ones looked like). The next one is coming up, back at the Schwarzes Rössl in Krems, Austria, from 22 August to 13 September 2026.
It's a workation, not a vacation. You can happily keep doing your day job. There are desks, meeting rooms, workshops and the usual infrastructure. But of course there are also topics and project groups we dig into together, so we've split Krems into three blocks:
Week 1 · Håck ma's (22–30 Aug) ("let's hack" in Austrian slang). Prepping for the Austrian hacker gathering, connecting to the local scene, and exploring hacks from, with and through Matrix. Bring your own Matrix open source project and run a hackathon or bug hunt while you're there.
Week 2 · Public Sector (31 Aug–6 Sep). Matrix in the public sector, including a project retreat for FITKO (in the NEO project a new Matrix-based fabric for citizen-to-authority communication is being laid). Plus the medical sector, education and universities, and public stuff in general. It's getting tight, but ask us anyway, we try to make things possible.
Week 3 · Matrix and beyond (7–13 Sep). Matrix in use cases a bit further from the chat case: Home Assistant and IoT, widgets, or whatever your project happens to be.
Grab a ticket (community prices, early-bird until 31 July) at tickets.matrix-community.events. Coming as a project or a group of four? There's a group discount, just ask us for the voucher. And we're still looking for sponsors: sponsoring keeps the community prices low and makes the whole thing possible, so if you or your org would like to support the Workation, please reach out.
Brought to you by Matrix Community Events. Come say hi in #workation-nation-general:datanauten.de.
🔗Dept of Spec 📜
Andrew Morgan (anoa) {he/him} says
Here's your weekly spec update! The heart of Matrix is the specification - and this is modified by Matrix Spec Change (MSC) proposals. Learn more about how the process works at https://spec.matrix.org/proposals.
🔗MSC Status
New MSCs:
MSC4522: Username colors
MSC4521: Adaptive Set Reconciliation via PinSketch
MSC4519: MatrixRTC Transports Registry
MSCs in Final Comment Period:
MSC4278: Media preview controls (merge)
Accepted MSCs:
MSC4409: Clarify thumbnailing behavior in E2EE
MSC4319: Room member events for invite and knock rooms in the /sync response
Closed MSCs:
No MSCs were closed/rejected this week.
🔗Spec Updates
The spec is ticking along with new MSCs; some getting into FCP and some being accepted. The introduction of a spec registry concept (see MSC4518: Registries and MSC4519: MatrixRTC Transports Registry) is something I've personally found interesting lately. Primarily an event type registry.
Being able to take all the event types of out the (currently very large) Client-Server spec and into a dedicated page, along with the ability for people and organisations to register their own event types is a noble and long-requested effort! MSC4518: Registries specifically goes into detail about how one can propose a registry and the expected behaviour around adding/modifying entries in it.
There's no such MSC for an event registry yet, and I'm cautious about starting one until MSC4518 has some more time in the oven. But it's only a matter of time!
🔗Dept of Servers 🏢
🔗Synapse (website)
Synapse is a Matrix homeserver implementation developed by Element.
madlittlemods (Eric Eastwood) reports
Hi everyone. If you're running Synapse, please note that 11 security vulnerabilities were fixed as part of the v1.157.2 security release.
If you haven't yet updated, please consider doing so soon!
We also have a new release candidate this week, Synapse v1.158.0rc1. To highlight from the changelog:
The default room version is being turned up to 11 🎸🔊1️⃣1️⃣ (#18680 thanks to @ShadowRZ, and @FrenchGithubUser for the underlying test changes necessary)
New MSC2705 animated thumbnailing support (#18831 thanks to @catfromplan9)
Thank you to all our contributors for helping to make Synapse the best it can be. As always, feel free to stop by #synapse:matrix.org to join in on the discussion and if you encounter a bug make sure to report it here.
🔗continuwuity (website)
Continuwuity is a community-driven Matrix homeserver in Rust.
nex (it/she) announces
Continuwuity v26.7.1 has been released!
This update introduces some new features, such as the ability to change where continuwuity sources the connecting IP from (allowing you to use x-forwarded-for again), an admin command to issue permanent access tokens for bots even when the server is in oauth2-only mode, and device authorization grant support was added for non-web clients.
There are also several bugfixes, including a fix for the infamous "room says empty client and must be upgraded from v1 after joining" bug, problems with restricted joins over federation were resolved, new registration admin room alerts were re-introduced after being erroneously dropped, appservice device registration no longer creates orphaned devices, and many fixes related to sync.
You can read the full release notes here: https://forgejo.ellis.link/continuwuation/continuwuity/releases/tag/v26.7.1. We also have deb packages for ARM64 now!
nex (it/she) [starstruck] also says
Continuwuity v26.7.2 has been released!
With new updates come new bugs. New bugs get caught and eventually squashed. In this case, we squashed two regressions introduced around v26.7.1, and fixed a low-severity vulnerability in the sliding sync implementation (particularly relevant to multi-user homeservers). I'd say it's recommended everyone upgrades as soon as possible, but I doubt anyone's hanging around on buggy versions for fun.
You can read the changelog here (it's small, you don't need subway surfers on the side for this one): https://forgejo.ellis.link/continuwuation/continuwuity/releases/tag/v26.7.2
➡️ https://continuwuity.org | #continuwuity:continuwuity.org | #space:continuwuity.org | woof
🔗Dept of Clients 📱
🔗Tesseract (website)
Marco announces
Hello again! 0.8.16 and then 0.8.17 went live, with many many goodies. The most important one is calls being enabled by default (they are still considered experimental, but they are now enabled for anyone that wants to give them a shot).
Among the highlights now you can (finally) create rooms, send your location (with a chat command and proper OS support), quick-reply from notifications, and full app keyboard navigation.
The app visual design got a little refresh, so it should look nicer. Hope you like it!
Feel free to drop by the official room!
🔗Nexus (website)
Matrix client made with Flutter and a Gomuks backend.
QuadRadical (Ping) says
What's new?
Support for encrypted media
Initial support for MacOS - No CI yet, you need to build manually
And some bug fixes, as always :)
Get involved!
If you want to help with development or simply keep up with new features, join our Matrix room at #nexus:federated.nexus or check out the Git repo at https://nexus.federated.nexus!
🔗Element X iOS (website)
A total rewrite of Element iOS using the Matrix Rust SDK underneath and targeting devices running iOS 17+.
Mauro reports
This week on Element X iOS, we wrapped up the media gallery timeline item, so you can now send multiple media files grouped into a single timeline entry. User status is nearly there too, though we're currently waiting on homeserver/Synapse support before it can go further. We've also made solid progress on cross-room search. On top of that, we squashed a good number of bugs and crashes this week, including some particularly nasty ones, which should give app stability a noticeable boost.
🔗Matrix Federation Stats 📊
Aine [etke.cc] says
TWIM
collected by MatrixRooms.info - an MRS instance by etke.cc
As of today, 19935 Matrix federateable servers have been discovered by matrixrooms.info, 4151 (20.8%) of them are publishing their rooms directory over federation.
The published directories contain 20258 rooms.
The most popular server software among the online servers is:
synapse: 15600 (78.3%)
continuwuity: 1707 (8.6%)
conduit: 552 (2.8%)
dendrite: 319 (1.6%)
Stats timeline is available on 📊 MatrixRooms.info/stats
🧩 Integrations with apps and servers | 💜 Support the project | 👉 How to add your server | 🙅 How to remove your server
🔗Dept of Ping 🏓
Here we reveal, rank, and applaud the homeservers with the lowest ping, as measured by pingbot, a maubot that you can host on your own server.
Join #ping:maunium.net to experience the fun live, and to find out how to add YOUR server to the game.
RankHostnameMedian MS
1im.breite.at206.5
2codestorm.net210
3starseeker.nexus225
4continuwuity.org245
5usbpc.xyz246
6cisnt.uk271
7vrkknn.net300.5
8blahaj.club711
9matrix.bochumerjunge.de799.5
10nexussfan.cz1009
🔗That's all I know
See you next week, and be sure to stop by #twim:matrix.org with your updates!
To learn more about how to prepare an entry for TWIM check out the TWIM guide.

https://matrix.org/blog/2026/07/31/this-week-in-matrix-2026-07-31/

This Week in Matrix 2026-08-07 🔗Matrix Live S13E04 - ...

2026-10-15T10:01:47Z

This Week in Matrix 2026-08-07

🔗Matrix Live S13E04 - Continuwuity
🔗Dept of Events and Talks 🗣️
Kegan reports
🔗Local-first Conference
A few weeks ago I was at Local-first Conference in Berlin giving a talk about Local-first Matrix. The video for this is now available. I talk about some of the P2P work we've done recently as well as some Hydra work in the form of the ERA paper. It also bridges the two worlds together, since local-first problems are frequently also Matrix problems, there's a lot we can learn from each other.
HarHarLinks reports
🔗Stammtische (website)
A Stammtisch ("regular's table") is a German meetup format where those with a shared interest meet regularly for discussion, exchange, and socialising.
Find more community organised events at matrix-community.events!
10 August (2nd Monday of every month) 20:00 CEST: #matrix-stammtisch:ccc.ac at CCCAC
11 August (every 4 weeks) 19:00 CEST: #matrix-dortmund:matrix.org at CTDO
12 August (2nd Wednesday of every month) 19:00 CEST: #matrix-stammtisch:koeln.ccc.de at C4
Are you running a Matrix meetup? Add it to the list!
🔗Dept of Spec 📜
TravisR reports
Here's your weekly spec update! The heart of Matrix is the specification - and this is modified by Matrix Spec Change (MSC) proposals. Learn more about how the process works at https://spec.matrix.org/proposals.
🔗MSC Status
New MSCs:
MSC4526: Improve OAuth 2.0 refresh token grant error handling
MSC4525: Paginated Sync
[WIP] MSC4524: Federation Bi-directional Ping
MSCs in Final Comment Period:
No MSCs are in FCP.
Accepted MSCs:
MSC4278: Media preview controls
Closed MSCs:
MSC3961: Sliding Sync Extension: Typing Notifications
Closed in favour of MSC4508
🔗Spec Updates
The SCT is spending most of its time aiming to get Matrix 2.0 across the line ahead of the conference. Watch this space for updates, or follow along in #sct-office:matrix.org.
🔗Dept of Servers 🏢
🔗Tuwunel (website)
Enterprise successor to conduwuit, the high-performance and feature-rich fork of Conduit.
june ✿ 🏳️‍⚧️ (it/she/puppy) reports
Tuwunel 1.8.3 adds QR-code login: Element Web's "Link new device" shows a QR code, Element X scans it, and the phone ends up signed in. MSC4108 carries the handshake; MSC4388 serves alongside, ahead of its clients. Tuwunel's own OIDC server approves the device authorization grant against local accounts, given oidc_native_auth = true (default off), well_known.client and a restart. rjwalters asked for it days later.
Video thumbnails ship gated: media_video_thumbnail_command is empty by default and the containers bundle none. Name one and the thumbnail endpoint serves a frame, not the whole video. az4521 asked, June built it, and lhjt's patch skips generation that only reproduces the source.
journalctl -u tuwunel -p warning returned nothing before: every line arrived as captured output at info priority. byteflavour's native journald logging submits each event at its own severity, and June's layer adds tracing fields under an F_ prefix, so journalctl F_ROOM_ID='!room:example.com' pulls one room out.
lhjt watched one receipt re-emit 2,113 times; his fix makes them monotonic. dasha-uwu reworked the HTTP security headers, unifying the CSPs and splitting out the SSO stylesheet and script so *-src 'self' is satisfiable. obodnikov fixed four non-unix build breakages (#526, #527, #528, #536). utop-top's report traced failing Matrix Authentication Service logins to the default scope; a brand = "MAS" provider now sends openid alone. Xerusion documented Traefik delegation; okias caught a dead docs link.
Upgrading: 1.8.3 refuses -O database_restore_backup= and will not start, so drop it from the launch command. A configured address that cannot bind is now fatal. LDAP login refuses accounts that did not originate in LDAP, locking out a half-finished migration.
Notes: https://github.com/matrix-construct/tuwunel/blob/27140e0a535aa9a8003e3db94f170f4320ad0ff9/RELEASE.md
💕 GitHub ✦ Releases ✦ DockerHub ✦ Playbook ✦ Containers ✦ Documentation ✦ Enterprise 🐕️ Tuwunel 💕
🔗Dept of Clients 📱
🔗Element X iOS (website)
A total rewrite of Element iOS using the Matrix Rust SDK underneath and targeting devices running iOS 17+.
Mauro says
A busy week.
iPad gets a tab rail replacing the top tab bar, giving the split view a less intrusive feel on larger screens.
Work on media galleries completed: gallery items now render in the media browser, the sending limit is up to 60 items, and we did an accessibility pass over the whole flow.
On the calls side you can now see at a glance which room members are in a call, and clear your own call status from Settings.
QR codes for linking a new device now expire correctly rather than hanging around forever.
Plus fixes for the rageshake upload progress bar, for a room list that stopped updating when it wasn't scrollable, stretched avatars in the share sheet, and a rotation bug during calls on Max-sized devices.
Thanks to nankeen, for the community contribution this week.
🔗Dept of Bots 🤖
🔗Reminder Bot
outarde reports
Hello everyone! I'd like to introduce a lightweight Reminder Bot written in Rust for Matrix servers. It sends reminders to users at a specified time.
Why Another Reminder Bot?
When I needed one for my server, none of the existing options worked. Most are outdated: they don't support encryption or modern authentication. In other solutions, reminders are simply an add-on to broader functionality (AI chat, bridges, etc.).
Current State
The bot can:
📆 Recognize dates in messages and send reminders at a specified time.
✅ Verify the bot account and enable backups for full compatibility with encrypted chats.
🔤 Support multiple languages (adding new languages is a top development priority).
Roadmap
The next feature in line is setting a custom time zone for each user. Then I'll add recurring reminders. I'm also considering integrating the bot with self-hosted task managers like Super Productivity or Mindwtr, as they store reminders in a simple .json format.
Links & More About the Project
You can read more about the bot and my journey (I'm not a professional programmer) in this Reddit post. You can also find the setup guide, provide feedback, or report an issue in the GitHub repository.
I hope this bot can make someone's Matrix server more convenient!
🔗Dept of Interesting Projects 🛰️
🔗Venoom
venumonelement announces
Decentralizing social media using Matrix and ATProto
For the past year-ish I have been working on Venoom, a cross-platform social app using Matrix and ATProto. It started as a passion project, trying to recreate a discord-like feel, but is now in a somewhat usable state!
The messaging and server part is built on Matrix. Servers are Matrix Spaces, categories are nested Spaces, and channels are Matrix rooms. It already has encrypted DMs and group chats, roles, custom emotes and reactions, member lists, and MatrixRTC calls with screen sharing. The app is built in Flutter, so it works across mobile and desktop.
Alongside that, I am also working on the social part, where people can share posts and thoughts. That side uses ATProto, although it is still much earlier than the Matrix part.
When you create a Venoom account, you get both a Matrix identity and an ATProto identity. That is the main reason I chose these two protocols. I do not want your account and everything you do to only work inside Venoom. You should be able to use your Matrix identity with other Matrix clients and use your ATProto identity with other apps in that ecosystem.
Basically, I am trying to combine Discord-style servers and messaging with a social feed, while making sure people are never completely locked into Venoom itself. The project is still early, but the Matrix side is now at a point where I would really like some people to test it and tell me what they think.
If you're interested, i will be posting more day to day updates here #venoom:matrix.org
🔗Matrix Federation Stats 📊
collected by MatrixRooms.info - an MRS instance by etke.cc
As of today, 19983 Matrix federateable servers have been discovered by matrixrooms.info, 4145 (20.7%) of them are publishing their rooms directory over federation.
The published directories contain 20273 rooms.
The most popular server software among the online servers is:
synapse: 15597 (78.1%)
continuwuity: 1746 (8.7%)
conduit: 549 (2.7%)
dendrite: 309 (1.5%)
Stats timeline is available on 📊 MatrixRooms.info/stats
🧩 Integrations with apps and servers | 💜 Support the project | 👉 How to add your server | 🙅 How to remove your server
🔗Dept of Ping 🏓
Here we reveal, rank, and applaud the homeservers with the lowest ping, as measured by pingbot, a maubot that you can host on your own server.
Join #ping:maunium.net to experience the fun live, and to find out how to add YOUR server to the game.
RankHostnameMedian MS
1raccoon.cafe191.5
2vrkknn.net199.5
3nerdhouse.io238
4cisnt.uk272
5zirco.dev404
6gingershaped.computer412.5
7victorewik.es430
8bartoostveen.nl467
9thibaultmol.link519
10beeper.com564
🔗That's all I know
See you next week, and be sure to stop by #twim:matrix.org with your updates!
To learn more about how to prepare an entry for TWIM check out the TWIM guide.

https://matrix.org/blog/2026/08/07/this-week-in-matrix-2026-08-07/

This Week in Matrix 2026-08-14 🔗Local-first Matrix 🔗Dept of ...

2026-10-15T08:41:34Z

This Week in Matrix 2026-08-14

🔗Local-first Matrix
🔗Dept of Events and Talks 🗣️
HarHarLinks says
🔗Matrix @ FrOSCon (website)
FrOSCon is the two-day Free and Open Source Software Conference, taking place every year in August at the University of Applied Sciences Bonn-Rhein-Sieg by Bonn, Germany. The Matrix community has long been a part of it, showing off and advertising Matrix as one of the many FLOSS projects. Drop by to say hi at our and the many other exhibitor booths, watch talks across 7 or more rooms in parallel, join one of the many workshops, chat with us, and much more. See you there this weekend!
For more Matrix Community Events, join our chat room #community-events:matrix.org, follow us on the Fediverse @community_events@mastodon.matrix.org, and check our website (we sometimes even update it).
🔗Dept of Spec 📜
TravisR reports
Here's your weekly spec update! The heart of Matrix is the specification - and this is modified by Matrix Spec Change (MSC) proposals. Learn more about how the process works at https://spec.matrix.org/proposals.
🔗MSC Status
New MSCs:
MSC4528: M_INCOMPATIBLE_SERVER error code
MSC4527: State event power levels
MSC4526: Improve OAuth 2.0 refresh token grant error handling
MSCs in Final Comment Period:
No MSCs are in FCP.
Accepted MSCs:
No MSCs were accepted this week.
Closed MSCs:
No MSCs were closed/rejected this week.
🔗Spec Updates
The Spec Core Team (SCT) continues to focus on Matrix 2.0 MSCs with an aim of cutting the release soon. There's not much to report on weekly, but you can follow the SCT's progress in the SCT Office room or on our tracking board.
Other MSCs are still being accepted, though may experience process delays due to priority being given to Matrix 2.0. Let the team know if there's an MSC which could do with review through the SCT Office.
🔗Dept of Servers 🏢
🔗Synapse (website)
Synapse is a Matrix homeserver implementation developed by Element.
madlittlemods (Eric Eastwood) announces
This week we have a new release candidate, Synapse v1.159.0rc1. To highlight:
On the user status front, we landed support for MSC4429: Profile Updates for Legacy Sync (defaults to disabled). To try this out, enable it via include_profile_updates_in_sync in your homeserver config and then use a client which also supports it. You can use the nightly version of Element Web (like https://develop.element.io) with the "User Status" labs flag enabled (visible after you enable "Developer mode" from /devtools). Pro-tip: /status <emoji> <text> ✨. More work to be done on this front like Sliding Sync support and federating all of this goodness.
We shipped some worker replication fixes and robustness tweaks this week (#20085, #20071). This also spawned a few more follow-ups to add some metrics so we can better notice when things are going wrong (will land in the coming weeks).
If you run Synapse against PostgreSQL, we now set idle_in_transaction_session_timeout (30 minutes) on new connections, so a leaked connection can no longer sit there holding locks or blocking vacuum indefinitely (#20077).
On the Matrix v1.16 spec-compliance front, Jason Little from Famedly has been landing fixes (#20021) as we march towards being able to update the default room version to 12.
To make it easier to give us useful info when reporting issues, we have new documentation on how to share a JSON snapshot of your Grafana dashboard (#20048). This is especially helpful when reporting performance problems as we can import the snapshot to dive straight into the Grafana dashboard ourselves to look for clues (way better than static screenshots).
Also for those that use our Debian/Ubuntu packages from packages.matrix.org, we've updated the signing key expiry date. This should be transparent to those that update before the previous version of the key expires (2027-03-15), but please check the relevant section in the upgrade notes.
Thank you to all our contributors for helping to make Synapse the best it can be. As always, feel free to stop by #synapse:matrix.org to join in on the discussion and if you encounter a bug make sure to report it here.
🔗continuwuity (website)
Continuwuity is a community-driven Matrix homeserver in Rust.
nex (it/she) announces
Continuwuity released v26.7.3 earlier this week. It contains two important vulnerability fixes, one of which is of a very high priority for users that have configured SMTP. There are no new features in this update, just the two bug fixes - we urge everyone to update as soon as possible.
However, worry not! I come bearing great news too! We have features in the works! And as a treat for TWIM readers (not really but pretend it is), we've gone ahead and done the unthinkable: published a pre-release! That's right, I'm not telling you to track our main branch for this one (although you have to promise to update your server when the full release is made). If you're eager to get your hands on significantly reduced resource load, faster federation, sticky events, and significant fixes to both legacy and sliding sync, you can deploy the v26.8.0-alpha.1 release! Make sure to report any issues to the issue tracker, and/or seek out support in #continuwuity:continuwuity.org!
➡️ https://continuwuity.org | #continuwuity:continuwuity.org | woof 🐾
🔗Venator (website)
Venator is an independently maintained Matrix homeserver, written from scratch in Go using the mautrix-go SDK.
nex (it/she) says
Venator v0.1.0a3 was just released, containing a healthy balance of bugfixes and new features. There's nothing too exciting in this release (oauth and federation soon I promise), but deployments of older versions may wish to update to take advantage of new security improvements like password peppering, and sweeping reductions in storage usage (with even more to come!).
Using Venator? Let me know in #venator:starstruck.systems, I am continually surprised to find people actually have long-lived deployments of this alpha project.
🔗Dept of Clients 📱
🔗Extera (website)
rustyraven[extera.xyz op] announces
Hi, federation! A lot has happened since our last TWIM post. We've rolled out a wave of updates since version 26.2.0 and we'll cover major things in this post.
Group calls: Added support for LiveKit group calls, should be compatible with Element Call. You can enable this under Calls -> Element Call to join group conversations.
Tailored message layouts: Choose from three different layouts, including a new Discord-inspired "Modern" design, updated bubbles, and the legacy bubbles layout from FluffyChat.
Custom fonts (experimental!): Make the app yours by setting custom fonts for the UI, messages, and code blocks individually. You need to have these fonts in your OS.
Interactive reactions & state events: React, redact, or reply to reactions and state events just like standard Matrix events.
Media spoilers: Media now can be hidden until clicked with content warnings feature (MSC3725).
Quick actions: Double-tap any message to instantly react or reply.
Timezones: Share your local time right in your profile.
User notes: Add notes about users for yourself.
Room server ACLs: Administrators can now manage room server access control lists directly.
Also, we updated the extera.xyz landing website and moved our development from GitHub to a self-hosted Forgejo instance at source.extera.xyz. We made sure that signing up process won't take much time, so you can authenticate using your Matrix account - pick "Matrix" auth method and join a special room or DM our bot.
Community ・ Source code ・ Website ・ Donate
🔗SchildiChat (website)
SchildiChat is a fork of Element for Android and Desktop, that used to focus on UI changes such as message bubbles and a unified chat list, but now also provides some additional tweaks and community-driven features that may not be on the roadmap for the upstream clients.
SpiritCroc reports
You may remember SchildiChat Revenge, my latest desktop client written in Kotlin & Jetpack Compose.
Since the latest release, this 3rd generation SchildiChat now also supports Android!
Initially, porting Revenge to Android was just meant as an experiment for fun, but it worked out way to well to not follow this route further.
It's still missing some important features (such as notifications, integrating with Android share targets, etc.), but I've already switched to using it as my main client on Android.
In case you're curious about what this means for SchildiChat Next, the current Android client based on Element X: it will keep receiving upstream merges and updates for the foreseeable future, but new SchildiChat features are much more likely to happen on Revenge, now that we actually have a shared codebase for both desktop and Android.
If you want to try it out, currently it's only released in my own F-Droid repo (I'll likely also put it into the Play Store at some point).
🔗Element X iOS (website)
A total rewrite of Element iOS using the Matrix Rust SDK underneath and targeting devices running iOS 17+.
Doug announces
This week we pushed the RC for version 26.08.2 to TestFlight, which will land on the App Store on Monday assuming testing goes smoothly. This release has a focus on quality-of-life improvements including a simplified login flow including auto-completion for your previously used homeservers. In addition read receipts should be sent more reliably when resuming the app, we’ve fixed a simulcast issue in Element Call and improved call behaviour during device rotation on Plus/Max sized phones.
In terms of upcoming changes we’ve made a noticeable improvement to launch performance by loading MapLibre only when a map is actually needed, improved the performance of the room list by removing some needless filter operations and fixed the iPad’s tab rail background colour not always being correct.
And the work on user status is nearing completion, with more testing against Synapse’s global profiles sliding sync extension currently underway.
🔗Element X Android (website)
Android Matrix messenger application using the Matrix Rust SDK and Jetpack Compose.
Benoit says
Element X Android v26.08.1 is rolling out on the Play Store 🚀
Highlights of the release:
Push notifications for live location share starts, implementing MSC4505.
Active call participants are now shown in the room's people list.
The emoji picker expands to full height when the keyboard is shown.
A batch of UI and accessibility fixes, including checked/unchecked state announcements for user rows in the invite screen, and the "add reactions" menu in the threads screen.
Since then, develop has been very busy — a huge round of community bugfixes landed, many of them long-standing issues:
Voice messages keep playing when the screen turns off, and messages without a waveform can be seeked.
Enter sends a message when using a physical keyboard (Shift+Enter for a new line).
matrix: URIs in messages are turned into pills, IPv6 URLs are linkified properly, and the server part of a fediverse handle is no longer mistaken for an email address.
Notification fixes: no more duplicated messages in a room notification, no notifications for events sent by another account on the same device, and no notifications for redactions of unknown events.
Videos are never re-encoded at a higher bitrate than the source.
Bug reports no longer fail to send after the app has crashed.
...and much more. Massive thanks to @hayaksi1 for this impressive series of contributions!
Also landed: push notifications for knocks, the global account data API exposed on MatrixClient, and KDoc documentation added across all of the api modules to make the codebase friendlier to newcomers.
Still cooking behind feature flags: user status, and the QR code login / link new device flow (now with proper timeout handling).
🔗Matrix Federation Stats 📊
Aine [etke.cc] reports
collected by MatrixRooms.info - an MRS instance by etke.cc
As of today, 20123 Matrix federateable servers have been discovered by matrixrooms.info, 4160 (20.7%) of them are publishing their rooms directory over federation.
The published directories contain 20397 rooms.
The most popular server software among the online servers is:
synapse: 15707 (78.1%)
continuwuity: 1766 (8.8%)
conduit: 549 (2.7%)
dendrite: 314 (1.6%)
Stats timeline is available on 📊 MatrixRooms.info/stats
🧩 Integrations with apps and servers | 💜 Support the project | 👉 How to add your server | 🙅 How to remove your server
🔗Dept of Ping 🏓
Here we reveal, rank, and applaud the homeservers with the lowest ping, as measured by pingbot, a maubot that you can host on your own server.
Join #ping:maunium.net to experience the fun live, and to find out how to add YOUR server to the game.
RankHostnameMedian MS
1vrkknn.net156.5
2continuwuity.org244
3cisnt.uk268
4vibb.me272
5pro.squarebowl.club285.5
6koenoostveen.nl341
7victorewik.es448.5
8grmml.de571.5
9lennsteenbergen.com627
10agentdid127.com697
🔗That's all I know
See you next week, and be sure to stop by #twim:matrix.org with your updates!
To learn more about how to prepare an entry for TWIM check out the TWIM guide.

https://matrix.org/blog/2026/08/14/this-week-in-matrix-2026-08-14/

Vendors behind openDesk join forces as Open Productivity Six of ...

2026-10-15T07:59:55Z

Vendors behind openDesk join forces as Open Productivity

Six of the vendors behind openDesk, including Element, have formed Open Productivity: a joint venture that brings the sovereign digital workplace to businesses and critical infrastructure operators.
openDesk was created for German public administration. It brings together established open source applications for documents, email, calendars, file sharing, knowledge management and secure real-time communications into a single sovereign workplace suite.
Open Productivity Software GmbH, founded by Collabora Productivity, Element, Nordeck, Open-Xchange, Univention and XWiki, supports the rollout and implementation of openDesk, with the experience of six of its vendors and a network of partners to deploy and run it.
Together with ZenDiS
Open Productivity works in coordination with ZenDiS, the Center for Digital Sovereignty in Public Administration, which leads openDesk. ZenDiS continues to focus on public administration. Open Productivity complements it by giving businesses and organisations a way to work with most of the open source vendors behind openDesk.
We welcome the initiative of several openDesk vendors to support openDesk's path into the enterprise market through Open Productivity. Open Productivity enables the distributors and systems integrators that ZenDiS is now addressing with its new partner program.
Pamela Krosta-Hartl, Managing Director, ZenDiS
Element's part in Open Productivity
Element is a founding shareholder in Open Productivity. We provide openDesk's secure, real-time communications: messaging and calling built on Matrix, the open standard for federated communications.
Federation matters for the organisations Open Productivity serves. Critical infrastructure operators work with suppliers, regulators and partners every day. Matrix lets each of them run its own server and stay in control of its own data, while still communicating securely with the others.
openDesk runs Element Server Suite directly from us as the upstream vendor. That means the same ESS we build and ship ourselves, including hardened Kubernetes deployments, modern OIDC authentication and Element Call. Open Productivity customers get openDesk's communications straight from the people who make it.
openDesk has shown what a sovereign digital workplace looks like in public administration. Open Productivity brings it to businesses and critical infrastructure, with the vendors standing directly behind it. For Element, it means more organisations can communicate securely on Matrix, on their own terms.
Dr. Patrick Alberts, Chief Product Officer, Element, and Managing Director, Element Software GmbH
How Open Productivity supports rollout and operations
Through their partner network, each customer project gets a single point of contact, who handles consulting, migration, integration, deployment and ongoing operations. Customers can run openDesk on their own infrastructure or in the cloud.
Three launch partners bring that capability from day one:
Adfinis, an open source specialist headquartered in Switzerland, integrates and operates open source infrastructure.
The msg group adds industry expertise and systems integration, including experience with critical infrastructure operators.
Smile, a French open source specialist, brings integration experience and a presence in multiple European markets.
About Open Productivity
Open Productivity Software GmbH is a joint venture founded by Collabora Productivity, Element, Nordeck, Open-Xchange, Univention and XWiki. It is led by Managing Director Dr Gerald Pfeifer, formerly CTO for EMEA at SUSE and chair of the openSUSE project from 2019 to 2026.
Businesses need more than strong individual applications. They need to be able to deploy and reliably operate a complete digital workplace.
Dr. Gerald Pfeifer, Managing Director, Open Productivity

https://element.io/blog/vendors-behind-opendesk-join-forces-as-open-productivity/

This Week in Matrix 2026-08-21 🔗Matrix Live S13E05 - Matrix @ ...

2026-10-15T07:44:53Z

This Week in Matrix 2026-08-21

🔗Matrix Live S13E05 - Matrix @ FrOSCon 2026
🔗Dept of Events and Talks 🗣️
HarHarLinks announces
🔗FrOSCon (website)
We had an awesome time representing Matrix at the Free and Open Source Software Conference! The new (as of FOSDEM) Matrix Foundation Events WG™️ Booth Kit was a great help in making our booth look much nicer and more engaging than ever, with 2 Linux laptops, a MacBook, one Android and a postmarketOS phone, various stickers, a standup about the Foundation, etc etc. For more detail, keep an eye out for Matrix Live! Here is a teaser:
HarHarLinks reports
🔗Matrix Community Workation Krems (website)
The workation starts tomorrow! Join the Matrix Community in Krems on the Danube in Austria for up to 3 weeks of hacking and networking in the Matrix community, go on an excursion to the Hack-ma's hacker camp in the next village over, or help the German government in digitising its infrastructure with proper Matrix, proper open source, and proper security and privacy.
Come chat with us #community-events:matrix.org or follow our fedi https://mastodon.matrix.org/@community_events.
PS: anyone going to MRMCD?
andypiper reports
🔗The Matrix Conference Community Hackathon (website)
We're excited to announce that this year's Community Hackathon at The Matrix Conference is in collaboration with Dr. Carla Griggio and the mInt Research Lab on User-centered Messaging Interoperability at the Department of Computer Science, Aalborg University.
On Friday 23rd October, we'll cross the Øresund Bridge to København and spend the afternoon hacking together on a range of Matrix-related projects. We're very grateful to Carla and Aalborg University for their support of this year's Matrix Conference.
We'll be adding more information about the hackathon and logistics (including the straightforward 🇸🇪 🛤️ 🇩🇰 transport options) on the website very soon. Don't worry: we already confirmed that Club Mate is readily available in supermarkets in Copenhagen! 😉
🔗The Matrix Conference schedule (website)
We're starting to send out the first email acceptances to speakers for the Conference! This should happen over the next few days, so prospective speakers, please check the email associated with your talk submission - we need you to click a link to confirm your acceptance. We have a process to get these sent out, so please stand by! We plan to confirm the initial set of content next week, as speakers are able to accept.
🔗Dept of Clients 📱
🔗Harmony (website)
catcraft reports
Hello again everyone!
It's been a bit over a month since our first TWIM entry, and since then, Harmony has had quite a few new features and fixes.
If you missed the previous entry, Harmony is a JavaScript-based, modular, extensible Matrix client with an open plugin system.
Harmony v0.4.0 has just been released, with support for pinned messages, spoiler and mathematical messages, partial power level management, and a few other things.
There has also been a new plugin adding support for MSC4440 biographies.
Since v0.2.0 (the last release posted here), we've also added OAuth/SSO login support, 'jump-to-message' support, and significant performance improvements (particularly for rooms with many members).
You can find the full changelog here.
In my own opinion, since v0.2.0, the experience has gone from 'okay' to 'quite pleasant'!
You can find the latest release on the releases page on Codeberg, and you can also join the Harmony rooms to get announcements and chat about the client:
Space
General room
Plugin developer room
Announcements
Finally, now that the AUR situation has been mostly resolved, packages have been published for Harmony (harmony-im and harmony-im-git).
Happy hacking!
🔗FluffyChat (website)
The cutest instant messenger in the [matrix].
Krille - Christian K. announces
FluffyChat 2.9.0 has been released
After the long waiting for 2.8.0 getting reviewed in the Play Store, we now have already FluffyChat 2.9.0, featuring better notifications on iOS, http3, verification check icon for users, double tap to react and a lot of bug fixes and other improvements.
🔗iOS Notifications
We are still not completely there that we can always display the message content of encrypted messages on iOS. It is still not working when the app is not in foreground duo to the end to end encryption but the app will now display the sender and (if cached) the avatar of the sender so you will know who sent you a message.
In the next release we will aim for displaying the message content for unencrypted rooms and then for encrypted ones. Also other features like message actions will also eventually come to iOS.
🔗http3
By using the flutter packages cronet_http and cupertino_http we now support http3 on iOS and Android. This means FluffyChat will now use the system’s proxy by default and network communication speed should improve.
🔗Double Tap to React
Thanks to AndusDEV we now have double tap to react. This is enabled by default on mobile (can be disabled in the settings if you prefer message selection instead). The default emoji to be sent is of course ❤️ while this can also be configured.
🔗Verification icon
Users you have verified are now marked with a ✅ icon. If you have verified all users in a room, then the whole room is marked as verified. This should give you a better indication, which conversation is extra secure.
🔗Better Android Notifications
On Android notification processing now start a foreground service. This should make push notifications much more reliable when the app has been terminated.
🔗Others
This release does not bring translation updates as there are currently some technical problems on weblate. We are on it. All changeslogs can be found here: https://github.com/krille-chan/fluffychat/blob/main/CHANGELOG.md#v290
🔗Element X iOS (website)
A total rewrite of Element iOS using the Matrix Rust SDK underneath and targeting devices running iOS 17+.
Doug reports
This week we released 26.08.2 to the App Store (with all the changes reported last week) and made an interim RC for 26.08.3 which is a TestFlight-only build to validate some changes to our release workflows.
We continued iterating on User Status, fixing cases where changes weren’t reflected in room member profiles and where your own profile would stop updating if you removed your avatar. The surrounding UI also received tweaks, including a fix for cropped emojis and some refinements to the copy. As part of this the Chats, Search and Spaces screens received a visual tidy-up too. Navigation titles are now more compact, toolbar buttons behave better on iOS 26, and typography is a little more consistent across the app.
Under the hood, Element X should do less unnecessary work during startup, while updates to the Matrix Rust SDK improve profile handling in more homeserver configurations.
We also spent some time optimising our testing setup: flaky tests have been de-flaked, integration tests fail faster, and CI should make better use of cached compilation artefacts.
🔗Dept of VoIP 🤙
Johannes Marbach announces
We've released version 0.6.0 of lk-jwt-service (the LiveKit JWT service).
This release adds support for delegating delayed leave events to the service via the new /delegate_delayed_leave endpoint. This spares clients having to maintain their dead man's switch themselves and improves the mechanism's accuracy. Delegated events can be persisted across service restarts using a new optional storage backend based on Redis.
In a related change, the previously introduced delay_cs_api_url parameter was deprecated on all endpoints. For increased security, the service now ignores this parameter entirely and instead resolves the C-S API location using .well-known discovery. Homeserver admins should make sure to configure .well-known discovery appropriately.
Further noteworthy changes include a new health check endpoint /healthz and improved test coverage.
⚠️ Important: As we continue progressing on MSC4195, the service will undergo further breaking changes. Specifically, the endpoints the service currently provides will be integrated into the Client-Server API to be served by the home server in future. For Synapse, we're planning to run the service as a sidecar application service to which Synapse will proxy incoming requests via MSC4512. Other homeservers can choose to follow this approach if they want to reuse the service implementation.
On a related note, we also have a Rust rewrite in flight (https://github.com/element-hq/lk-jwt-service/pull/197). This won't impact the service's external interface but will change the way the service is built.
🔗Element Call (website)
Native Decentralised End-to-end Encrypted Group Calls in Matrix.
Robin announces
🔗Deprecating .well-known transport discovery
Hi from Element's VoIP team! We just released Element Call 0.24.0, which deprecates the method of discovering MatrixRTC transports that used the homeserver's /.well-known/matrix/client file. This is a PSA for admins and developers that you may need to take some actions to ensure Element Call can still find your LiveKit SFU.
For client developers using Element Call as a widget, make sure that your client supports the new get_rtc_transports action from MSC4515. If desired, you can implement this action in a way that still falls back to .well-known discovery to give your users more time to migrate to the MSC4519 endpoint.
For admins hosting a standalone Element Call instance, make sure that your homeserver supports the GET /_matrix/client/unstable/org.matrix.msc4143/rtc/transports endpoint from MSC4519. (If it doesn't, you could try "implementing" it manually with an unauthenticated reverse proxy entry.) See the updated self-hosting guide. If your server's /.well-known/matrix/client file contained an org.matrix.msc4143.rtc_foci key, you may remove it.
For other homeserver admins, no changes are required at this time because Element Web/Desktop and Element X Android/iOS are all being adapted to keep the .well-known discovery method as a fallback. We still recommend enabling the GET /_matrix/client/unstable/org.matrix.msc4143/rtc/transports endpoint from MSC4519 however to prepare for future changes. See the updated self-hosting guide.
🔗Dept of Ops 🛠
🔗Matrix Connectivity Tester (website)
A web interface to debug and troubleshoot Matrix connectivity issues.
MTRNord (they/them) says
Since the last update, a bunch of federation-check improvements landed to improve edge cases, bugs and also extending the statistics.
🔗What's Changed
Outgoing federation checks can now also probe over a dedicated IPv4-only and IPv6-only address, so you can see whether a server's outgoing federation actually works over each address family individually, not just whichever one its resolver happens to prefer.
The public opt-in Statistics page now also breaks down announced address family (IPv4-only / IPv6-only / dual-stack) and, for dual-stack servers, which family actually connects.
Optional MSC4524 (Federation Bidirectional Ping) support for the outgoing-federation check, as an alternative to the client-API room-alias trick.
Fixed a couple of real, reported false-negatives: a server whose /.well-known/matrix/client redirects elsewhere (client-server side) wasn't followed at all and got silently probed at the wrong base URL, and a well-known response missing CORS headers (including on the redirect itself) was silently treated as "absent" instead of being flagged as its own problem.
Optional (for the operator/hoster) OpenTelemetry tracing support added to allow for better optimizing and debugging of edge cases encountered as bugs.
Cleaned up the OpenAPI spec (interactive docs at /api-docs).
Reworked the way we do alerts instead of having a fixed number of fails before an alert. This reduces flapping spam.
Code lives on self-hosted Phorge: https://phorge.mtrnord.blog/source/mcte/repository/main/.
Find the deployed version at https://connectivity-tester.mtrnord.blog or, if you're daring, https://stage.connectivity-tester.mtrnord.blog for the staging deployment, which gets changes earlier but at less stability.
If you find issues or want to request features, please direct them at the Phorge repository or at the forum at https://forum.mtrnord.blog/c/matrix-connectivity-tester/support/6 :)
Note that I am doing this in my freetime alone so it might take a few days or weeks at times for me to respond. :) I do however try to respond as early as I am able to.
🔗Dept of Videos 📹
andypiper announces
🔗Matrix Live (website)
Matrix Live is our weekly video update that spotlights different aspects of the Matrix ecosystem, from the Foundation's Working Groups, through events, the evolution of the specification, to the many different projects that build on top of the Matrix protocol.
If you'd like to join me (Andy) in a future edition of Matrix Live, get in touch! We're scheduling a number of weeks ahead, and we'd be happy to find time for an upcoming conversation.
🔗Matrix Federation Stats 📊
Aine [etke.cc] says
collected by MatrixRooms.info - an MRS instance by etke.cc
As of today, 20083 Matrix federateable servers have been discovered by matrixrooms.info, 4114 (20.5%) of them are publishing their rooms directory over federation.
The published directories contain 20558 rooms.
The most popular server software among the online servers is:
synapse: 15647 (77.9%)
continuwuity: 1760 (8.8%)
conduit: 548 (2.7%)
dendrite: 305 (1.5%)
Stats timeline is available on 📊 MatrixRooms.info/stats
🧩 Integrations with apps and servers | 💜 Support the project | 👉 How to add your server | 🙅 How to remove your server
🔗Dept of Ping 🏓
Here we reveal, rank, and applaud the homeservers with the lowest ping, as measured by pingbot, a maubot that you can host on your own server.
Join #ping:maunium.net to experience the fun live, and to find out how to add YOUR server to the game.
RankHostnameMedian MS
1continuwuity.org161.5
2vrkknn.net209.5
3raccoon.cafe234
4vibb.me255
5nerdhouse.io256.5
6dykes.ca302
7worldethicaldataforum.org339
8w33b.cloud390.5
9unredacted.org421
10victorewik.es422
🔗That's all I know
See you next week, and be sure to stop by #twim:matrix.org with your updates!
To learn more about how to prepare an entry for TWIM check out the TWIM guide.

https://matrix.org/blog/2026/08/21/this-week-in-matrix-2026-08-21/

This Week in Matrix 2026-08-28 🔗Matrix Live S13E06 - The need ...

2026-10-15T07:27:37Z

This Week in Matrix 2026-08-28

🔗Matrix Live S13E06 - The need for privacy-preserving decentralised reputation
🔗Dept of The Matrix Conference 🏛️
andypiper announces
🔗The Matrix Conference (website)
We've been bowled over by the volume of submissions for this year's conference in Malmö 🇸🇪! We're not quite ready to reveal the complete schedule, but the team has been busy sending out confirmations to speakers. If you submitted to our call for papers, check your email and (most importantly) if your session was accepted please click the required link to confirm your attendance.
You can have a look at an initial set of confirmed talks here. Note that this is not yet the full set of talks, as we're still working with speakers on their proposals. You can expect to hear more over the next couple of weeks.
Look out for talks such as
The Matrix State of the Union
A Vision for a Next-Generation Timeline
Making Custom Profiles in Matrix More Useful
Customize your Matrix Messenger
How Encryption Works in Matrix
Matrix Wrench - a admin tool for operators and community managers
... and many more!
In case you missed it, last week we also announced that the hackathon will be taking place at the neighbouring Aalborg University across the water in Copenhagen 🇩🇰
We're excited about The Matrix Conference 2026, and we think you will be, too! 😎
andypiper says
🔗The Matrix Conference Sticker Swap (website)
Advance notice that we'll have a sticker swap table at The Matrix Conference this year. We want to celebrate, share and spread knowledge of the different community projects that build on Matrix, and what better way to do that than via the medium of stickers 💫 Bring your stickers to share with others, and find out about other projects at the same time.
If you have a project logo to share with the rest of the ecosystem, we'd love to see it on the sticker swap table 🙇🏻 there's also a "booth kit" for The Matrix.org Foundation that pops up at other events throughout the year, and we'll be happy to spread awareness of ecosystem projects via the booth (if there are any stickers left over, that is...). Need help with how to create stickers for your project, or want to send us some to share in case you can't make it to the event? Talk to the Events Working Group #events-wg:matrix.org.
This is also a good time for a reminder to get your ticket for The Matrix Conference 🎟️ (if you haven't done so already). It is shaping up to be an excellent few days of talks, hacking, networking, and celebration.
🔗Dept of Events and Talks 🗣️
HarHarLinks says
🔗Stammtische (website)
A Stammtisch ("regular's table") is a German meetup format where those with a shared interest meet regularly for discussion, exchange, and socialising.
Find more community organised events at matrix-community.events!
2 September (1st Wednesday of every month) 20:00 CEST: Matrix User Meetup Berlin #mumb:c-base.org at c-base
4 September 19:00 CEST: #workation-nation-general:datanauten.de at Schwarzes Rössl - as part of the Matrix Workation
Are you running a Matrix meetup? Add it to the list!
🔗Dept of Built on Matrix 🏗️
Lukas Weller says
🔗Neo Nominated for Open Source Competition
Hello everyone!
We'd like to share an update and some great news that Neo, the pilot project bringing Matrix to German public administration, has been nominated for the Open Source Competition!
Developed by FITKO (Föderale IT-Kooperation) and the team behind it, Neo uses Matrix’s open protocol to enable secure, end-to-end encrypted communication between citizens and authorities. It includes a Matrix-based web client and smartphone app, supports structured workflows like document requests, and integrates with other Matrix solutions.
We feel this is an important step for Matrix adoption in the public sector. If you’re equally excited about Matrix adoption in government IT, it would help us out massively to push Neo to the top. The winner will be announced at SCCON 2026 in October this year.
Vote for Neo at https://open-source-wettbewerb.de/voting/neo/ or spread it on your favorite social network.
You can also find some more info on Neo in the project description or on https://gitlab.opencode.de/fitko/matrix-g2x/.
Thanks for your support!
🔗Dept of Spec 📜
LogN announces
🔗Is presence fixed yet?
No, but we're making progress.
Today, presence is one of Matrix’s least-deployed core features. Even with efforts to improve implementations, almost every major public Matrix deployment disables federated presence, citing privacy and performance concerns.
A group of independent community members, including maintainers of Continuwuity, have been working on a group of proposals to improve the semantics of Matrix presence.
This week we published MSC4532: Revised Social Presence, a proposal to remodel presence information to better support social use cases. This includes proper presence overrides ("appear offline"), and a busy status, alongside potential major performance improvements.
Our first proposal, MSC4495: Selective Presence, is moving along well: we have an unmerged experimental implementation in Continuwuity, now with 3 servers running it!
If you're interested in the work we're doing, take a look at ispresencefixedyet.com or join us at #presence-v2:zirco.dev!
🔗Dept of Clients 📱
🔗Element X Android (website)
Android Matrix messenger application using the Matrix Rust SDK and Jetpack Compose.
Benoit announces
Hey TWIM! Another busy week on Element X Android — 50+ pull requests merged, an internal v26.08.2 release cut, and a remarkable amount of it coming from the community. 🎉
New language: Arabic: Element X Android now ships Arabic translations, synced from Localazy. Many thanks to the translators! (#7461)
Sign-in gets simpler: Choosing where your account lives is now much less fiddly. @jennaharris7 reworked account provider selection so it autocompletes from providers you've used before, accepts a server without typing https://, is case-insensitive, and respects the enterprise allow-list. The text field is also correctly disabled while a sign-in is in flight. (#7394, #7492). Login polish continued around it: the focused field now stays visible above the keyboard (#7455), and stray carriage returns pasted into the login and password fields are stripped out (#7439).
Know why a message failed. Tapping a message that failed to send now opens a dialog explaining the actual reason instead of leaving you guessing. (#7490)
Focused timelines stay focused until the target event has actually been rendered, fixing permalinks that used to drift away mid-pagination. (#7463)
Better looking photos. Image compression has been relaxed so photos and screenshots keep noticeably more detail. (#7451)
Opening an image that hasn't finished uploading now shows the right picture (#7359), and images shared in with a vague mime type keep their transparency (#7452).
Editing a caption now converts markdown to HTML like the composer does (#7441), the send button no longer vanishes when you clear the composer while editing (#7456), and starting a mention refreshes the room member list so recent joiners show up (#7438).
Voice messages keep playing when another app makes a short sound (notification blips no longer kill your playback). (#7454)
Verification unstuck: outgoing session verification no longer hangs when recovery setup is incomplete — thanks @hardcore-sushi! (#7433)
Deep links on cold start: an account provisioning deep link that launches the app from scratch is no longer swallowed. (#7488)
Resuming the app from the recents list no longer re-opens the room you had left (#7436), the app stops waiting forever on a room alias the remote server never resolves (#7446), declining an invite closes the invite screen (#7440), and leaving a room that can't be found shows an error instead of failing silently (#7437).
User IDs containing a slash now open the right profile (#7445).
Switching back to "system" theme after forcing light or dark actually applies the system theme again (#7453).
The sync service no longer restarts while the client is shutting down (#7472), and the applicationName in the User-Agent is normalised — HTTP headers don't allow UTF-8 (#7477).
Call: Picture-in-Picture now reacts to camera orientation changes on the other participant's device, so a remote rotation no longer leaves you with a sideways video (#6951). Element Call embedded also moved to 0.24.0 (#7474).
The notification troubleshooter now explicitly explains a rate-limiting push gateway, instead of reporting a generic failure. (#7448)
A huge shout-out to @hayaksi1, who landed 20 PRs this week alone — timeline, composer, media, notifications, login and release tooling. Thanks also to @jennaharris7, @hardcore-sushi and @bxdxnn for their contributions.
🔗Dept of SDKs and Frameworks 🧰
🔗Trixnity (website)
Multiplatform Kotlin SDK for developing Clients, Bots, Appservices and Servers.
Benedict announces
Just a quick update on Trixnity: The recent 5.8.0 release focuses on refactoring the E2EE and database transaction management to make things a bit cleaner, safer, and easier to test. We also added some media service improvements in 5.7.0, specifically around download size limits and automatic media cleanup.
🔗Dept of Interesting Projects 🛰️
blue @privacyte.ch says
🔗RemoteRails: Matrix & LiveKit Appliance with WG VPN & SSO (website)
The Matrix protocol's versatility for use cases from internal chats to globally federated OTT messaging inspired us to integrate Tuwunel, LiveKit, and Coturn into our self-hosted, zero-knowledge appliance for E2EE chats & calls.
As with the other services (Drive, Office, Mail) in the appliance, the auth and signaling endpoints of Matrix reside on a private VPN subnet managed by Defguard. The Matrix server is accessible only after a user has authenticated with their OIDC SSO credentials and 2FA (TOTP or WebAuthn) to the WireGuard tunnel. By default, the Matrix federation endpoint is also isolated from the web, but this can be relaxed to interoperate with other external homeservers, if desired.
The appliance is engineered for portability, security, and data minimization. We built a set of standardized deployment scripts that install a minimal Debian OS (with no provider telemetry), instantiate the RAID/LVM, and provision the appliance using Debootstrap and Docker Compose. Even when the appliance is hosted in a commercial datacenter, we wanted to achieve an on-premises grade of discretion using LUKS, hardware-based memory encryption (SME/TME), DMA protection, and Secure Boot with UKI. To strip out the dependency on Google Play Services, we also baked in the Ntfy.sh container for self-hosted UnifiedPush notifications on Android.
For a closer look at our defense-in-depth philosophy and threat modelling, check out our Confidential Computing & Security Model writeup.
venumonelement says
🔗Decentralizing social media using ATProto and Matrix (venoom)
Over the past two weeks, I made it possible to use ATProto and Matrix together in one cross-platform app. The goal is to combine an ATProto account and a Matrix account under one identity: ATProto provides profiles and public posts, while Matrix provides encrypted messages and calls.
The accounts are linked by storing the Matrix ID in the ATProto DID document and the ATProto DID in the Matrix extended profile. Venoom checks that both values match and can then show information from both profiles together.
I also connected MAS to an ATProto OAuth broker, so users can access a Matrix account through their ATProto identity or connect a Matrix account they already have.
Next up is refining the app and fixing bugs. I hope to release a test version soon. If you’re interested, you can join the room where I post updates:
https://matrix.to/#/!gxmZLQDhVacrWxzPiM:matrix.org
🔗Matrix Federation Stats 📊
Aine [etke.cc] announces
collected by MatrixRooms.info - an MRS instance by etke.cc
As of today, 20162 Matrix federateable servers have been discovered by matrixrooms.info, 4140 (20.5%) of them are publishing their rooms directory over federation.
The published directories contain 20658 rooms.
The most popular server software among the online servers is:
synapse: 15705 (77.9%)
continuwuity: 1775 (8.8%)
conduit: 533 (2.6%)
dendrite: 307 (1.5%)
Stats timeline is available on 📊 MatrixRooms.info/stats
🧩 Integrations with apps and servers | 💜 Support the project | 👉 How to add your server | 🙅 How to remove your server
🔗Dept of Ping 🏓
Here we reveal, rank, and applaud the homeservers with the lowest ping, as measured by pingbot, a maubot that you can host on your own server.
Join #ping:maunium.net to experience the fun live, and to find out how to add YOUR server to the game.
RankHostnameMedian MS
1vrkknn.net190
2nerdhouse.io236
3victorewik.es321
4zirco.dev365
5ed25519.uk1067.5
6poweron.dk1239
7blahaj.club1268
8matrix.org1711
9matrix.sharks.id.au2177
10tinier.town2599
🔗That's all I know
See you next week, and be sure to stop by #twim:matrix.org with your updates!
To learn more about how to prepare an entry for TWIM check out the TWIM guide.

https://matrix.org/blog/2026/08/28/this-week-in-matrix-2026-08-28/

This Week in Matrix 2026-09-04 🔗Matrix Live S13E07 FITKO Neo / ...

2026-10-15T07:04:30Z

This Week in Matrix 2026-09-04

🔗Matrix Live S13E07 FITKO Neo / Community Workation
🔗Dept of The Matrix Conference 🏛️
🔗The Matrix Conference (website)
andypiper announces
The countdown to The Matrix Conference 2026 is on! We're excited to continue to announce the sessions you can expect to see at the conference, which takes place in Malmö, Sweden 🇸🇪 on 20-22 October, and concludes with a hackathon in Copenhagen, Denmark 🇩🇰 on 23 October.
This week, we thought we'd mention some more talks that have been confirmed for the conference, including:
Bridging private federations across borders
Towards a Post-Quantum Matrix Protocol: A Hybrid Wrapper Adapted to the Brazilian Scenario
When to Change the Locks in Your Matrix
Europe’s tech sovereignty: what’s in it for Matrix?
Hello from the other side: a design workshop to bridge asymmetries between messaging clients
Robrix: a pure Rust multi-platform Matrix client, and a peek at its future
Get your ticket for the conference today!
🔗Dept of Events and Talks 🗣️
🔗Stammtische (website)
HarHarLinks reports
A Stammtisch ("regular's table") is a German meetup format where those with a shared interest meet regularly for discussion, exchange, and socialising.
Find more community organised events at matrix-community.events!
8 September (Tuesday every 4 weeks) 19:00 CEST: #matrix-dortmund:matrix.org at CTDO
9 September (2nd Wednesday of every month) 19:00 CEST: #matrix-stammtisch:koeln.ccc.de at C4
Are you running a Matrix meetup? Add it to the list!
🔗Dept of Servers 🏢
🔗Synapse (website)
Synapse is a Matrix homeserver implementation developed by Element.
madlittlemods (Eric Eastwood) says
This week we have a new release, Synapse 1.160.0. To highlight:
As an update on the user status front, we landed support for MSC4262: Profile Updates for Sliding Sync (#20003) (previously, we only supported legacy sync). It uses the same include_profile_updates_in_sync config option, which still defaults to disabled. There were also a few bugfixes to ensure that sync responses get all of the profile updates (#20135, #20147)
We also sprouted experimental support for MSC4502: 'Targeted and unrestricted room member queries' which gives Application Services (with the appropriate scope in their registration file) a new endpoint to ask whether a given user or server is joined to a room, without being joined themselves (#19974).
A nice bugfix for an edge case where streams (presence, to-device messages, etc.) could stall and prevent new data from being sent to clients (#20090 thanks to @FrenchGithubUser from Famedly)
A few device list performance tweaks which have had a nice impact on matrix.org, which had been struggling to catch-up on a backlog for the past few weeks and has now caught up (#20098, #20120)
WebP images that use transparency are now thumbnailed as PNG rather than JPEG, so your images stay transparent (#20094, thanks to @catfromplan9).
Thank you to all our contributors for helping to make Synapse the best it can be. As always, feel free to stop by #synapse:matrix.org to join in on the discussion and if you encounter a bug make sure to report it.
🔗Dept of Clients 📱
🔗Voyage
nv reports
I'm announcing Voyage, a Matrix client for Android based on Element Classic with a strong focus on modernization. Over the past couple months, development has been underway and the client has now been made available. You can expect several dozen bugfixes or performance improvements, and over a hundred new features, many of which are only seen in cutting edge clients such as Sable or Commet. Mostly everything from SchildiChat Android has been ported over as well.
One of Voyage's main goals is support for older Android versions: the client runs all the way back to Android 4.0. That being said, despite this vastly improved compatibility with older versions of Android, Voyage is by no means dated and feels at home running on the latest Android versions.
Whether you're a fan of Element Classic or not, I highly encourage you to grab the nightly build and try it out, this is only the beginning and testers are much appreciated. There's also a Matrix room (https://matrix.to/#/#voyage:matrix.org) if you'd like to join the conversation, I hope to see you there :-)
🔗Element X iOS (website)
A total rewrite of Element iOS using the Matrix Rust SDK underneath and targeting devices running iOS 17+.
Mauro says
This week on EXI we have worked on a bunch of features that are the result community PRs from Android like
Adding a redaction reason when trying to redacting messages
Started working on multiselecting messages for forwarding/copying purposes
Autoplay consecutive voice messages.
Of course we also took care of various bugfixes and stability improvements
🔗Element X Android (website)
Android Matrix messenger application using the Matrix Rust SDK and Jetpack Compose.
Benoit announces
Element X Android shipped two releases this week, v26.08.3 and v26.08.4, from 60 merged PRs between 21 and 28 August. On features, user status is now on by default (emoji-only in the timeline).
The bugfix run was long: mention suggestions are ranked by match quality, threads survive message deletion, noisy notifications stay noisy behind a PIN code, and downloads no longer break past 32 same-named files. Several empty or confusing states were fixed too — "server unreachable" is now stated explicitly, one-to-one room previews drop the redundant sender name, unknown senders are named from the member list, and stalled verification requests time out. Caption formatting survives edits, database migrations re-run on upgrade, and share mime types are resolved to something concrete.
Under the hood, the Rust SDK moved to 26.08.25 and its git SHA is now logged at startup to speed up triage. Developer options gained a pretty-printed "Push rules" viewer, releases are automated via a new releaseV2.sh, and three large renames landed (*Events → *Event, PreviewParam suffix, Metro binding containers into di). Community contributors carried much of this — hayaksi1 above all, with jennaharris7, bxdxnn and sandhose.
🔗Tammy (website)
Multiplatform messenger built on top of Trixnity Messenger.
Benedict announces
Tammy 16.08.0 has been released! It has been a busy two months of development. Aside from the usual bug fixes, here are the most significant updates:
🔗Streamlined Onboarding
We have completely redesigned the initial account setup process. The new account setup wizard is more concise and intuitive, allowing you to get up and running much faster.
🔗Voice Messaging on Web and iOS
Voice messaging was previously available on Android, but with the addition of Web and iOS support, it is now available across almost all platforms. We have also updated our audio recording engine to be more robust and provide better error feedback during the recording process.
🔗Password Manager Support for Web
If you use Tammy on the Web, you can now use your password manager to securely store and manage your credentials and recovery keys.
🔗Enhanced User Search
Finding people when creating rooms is now much easier. We have introduced a new search API that allows the client to query various search providers. While this may not be highly relevant for a standard Matrix federation, it is incredibly useful in corporate environments. For example, a company can integrate LDAP to include details such as department, location, and availability. We have used this ourselves for our TI-Messenger, where users can search a directory service (VZD) for healthcare practitioners.
🔗Security & Privacy Hardening
This update includes several important security enhancements. We have implemented stricter measures for your local database: if the system detects that the database cannot be decrypted or that secrets have been tampered with, the profile will be automatically deleted to protect your information. Additionally, when you log out of an account, the client now ensures that all local secrets associated with that account are completely wiped from your device.
To help manage your storage, Tammy now prevents large automatic file downloads (such as images in the timeline or avatars) without your explicit permission. The client also checks for available disk space before attempting to download large files. Finally, if you cancel a file upload, the temporary file is now cleared from your local cache.
🔗Major Navigation Refactor
On a more technical note, we have moved to a new navigation framework under the hood. Previously, navigation was largely hardcoded and difficult to extend; this new architecture provides us with full flexibility, making the client much more extensible for future development or community extensions.
🔗Dept of Widgets 🧩
shunmugaraj09876 💀⃤ says
🔗Huddle
Huddle is a new open-source Matrix widget that summarizes each room's
messages from today, running entirely on-device by default — no backend,
nothing leaves your browser unless you explicitly switch a room to cloud
mode. It runs a quantized Gemma model locally via WebGPU (Google's
LiteRT-LM Web runtime), and a Chat tab lets you interact with the chat history. Built on
Nordeck's Matrix Widget Toolkit, Apache-2.0 licensed.
🔗Try it
Source: https://github.com/toshanmugaraj/huddle
Demos:

Early days (v0.1.0) — feedback, issues, and PRs welcome. Contact:
@raj098:matrix.org
🔗Matrix Widget Toolkit (website)
Reusable framework for creating Matrix widgets.
Milton Moura (n.io) announces
We have fresh releases for the Matrix Widget Toolkit!
Two new MSCs found their way into the toolkit, setting up the baseline for our efforts in updating NeoBoard's MatrixRTC implementation to the latest spec proposal.
First up, sticky events (MSC4407, the Widget API side of MSC4354). In @matrix-widget-toolkit/api@5.1.0 you can pass a stickyDurationMs option to sendRoomEvent() and sendDelayedRoomEvent(), and the homeserver will keep delivering that event for as long as you asked for.
Second, RTC transports discovery (MSC4515): widgetApi.getRtcTransports() lets your widget ask the hosting client which realtime transports are available on the homeserver.
Be aware that both proposals are still unstable, so your mileage depends on the client and homeserver playing along. Good news is that @matrix-widget-toolkit/testing@4.1.0 already mocks both, so you can unit test away today.
And finally the boring bits: react@2.1.2 and mui@2.2.2 packages got some maintenance updates. Nothing changed except the dependencies (matrix-widget-api 1.18.0, @reduxjs/toolkit 2.12.0).
Note that widget-server@1.2.3 is rebuilt with the latest nginx:alpine-perl 1.31.4 with all the upstream nginx and Alpine security fixes. Configuration options haven't changed, so it's just an image swap for you.
Full changelogs are on the releases page, and we'd love to hear from you at #nordeck:matrix.org!
🔗Dept of SDKs and Frameworks 🧰
🔗react-native-matrix-crypto
Michel-Marie MAUDET says
Announcing react-native-matrix-crypto v0.3.0: a React Native bridge for Matrix end-to-end encryption, built on matrix-sdk-crypto - the same Rust implementation Element uses behind a small, typed TypeScript surface.
The library deliberately does no networking: there is no login, no /sync, no sending. It hands your application the encrypted events and the list of requests to send, and expects to be told what reached the homeserver. That is the same boundary upstream draws between matrix-sdk-crypto and the full matrix-sdk, kept for the same reason: a crypto engine that also owns transport is far harder to audit and reuse. The published package ships prebuilt binaries for iOS and Android, so no Rust toolchain is required.
Version 0.3.0 adds device verification by scannable code, in all three modes the protocol defines, another user, and your own new login with either device showing. Showing and scanning are announced separately, so a product with a screen but no camera never claims one: that exact claim is what a real Element Web client once acted on, and it is why the switch is two facts and not a boolean. A build that never opts in announces on the wire exactly what every earlier release announced.
What ships with a claim carries its proof: third-party interop against matrix-nio and mautrix-go over real homeservers in both directions, five level-2 proofs, thirteen CI gates each watched rejecting a real violation, and, new in this cycle, the same proofs against Synapse as well as Continuwuity, plus the example app running end to end on an iOS simulator in CI for the first time.
This release is a foundation, not a finish line. The road to 1.0 is tracked in four issues: a real-camera QR proof in CI, multi-participant and federation-neutral coverage, cross-implementation testing (landed with this release), and a stabilised API with published reference documentation.
Built for Twake Workplace but usable by any React Native project.
Repo: https://github.com/linagora/react-native-matrix-crypto
npm: https://www.npmjs.com/package/react-native-matrix-crypto
v1.0 roadmap: https://github.com/linagora/react-native-matrix-crypto/milestone/1
🔗Matrix with Drupal
John says
First video in a series, connecting Drupal to Matrix is live now, up at https://www.freelock.com/blog/john-locke/2026-08/drupal-meets-matrix-part-1-setting-matrix-api .
🔗Drupal Matrix API module
The Matrix API module has been relaying messages from Drupal sites to Matrix rooms for a decade -- now it supports messages from Matrix to Drupal!
🔗Drupal Matrix Recipes
There's now a Drupal "Recipe" in development to make it easy to get started, which is demonstrated in the video in the post. The recipe is at Matrix Recipes, with two working recipes so far - basic installation of the API module and an "ECA" model that sets up the business logic to post new articles to a designated Matrix room, and send replies in a thread to that message back to Drupal as comments.
The other working recipe provides a simple polling mechanism so you can see those comments arrive on the Drupal site.
🔗More coming soon
This is just the start of a full integration we're working on between Drupal and Matrix. Future enhancements include:
Identities - map Matrix user accounts with Drupal user accounts, supporting OIDC from Drupal or a 3rd party IDP
entities - provide more sophisticated mapping between Matrix events and Drupal entities, including spaces, rooms, messages of various kinds on the Matrix side with arbitrary links to Groups, Nodes, comments, and reactions on the Drupal site
application server - manage one (or more) Matrix spaces or rooms from Drupal, with templates for setting room permissions, providing moderation, etc.
widgets - expose arbitrary components from Drupal as widgets inside Matrix rooms
🔗Drupal Groups Initiative
Part of the motivation for this work is a revamping of Drupal's old groups.drupal.org site, which has gotten quite stale and unused over the past decade, while most of the community has moved to Slack as a communication platform. This effort has the goal of providing a superior experience, enticing people to move back to Drupal.org for their collaborative work, while still providing a great chat experience through Matrix and Element.
I'm hoping this is the start of something entirely new - a multi-modal community platform that helps people work together on projects on a fully open platform, with the best of all worlds at their fingertips.
If you have ideas or would like to help, reach out to me at @john:matrix.freelock.com!
🔗Dept of Videos 📹
Matthew announces
The recording of the speedrun recap of the DWebCamp talk on P2P Matrix, Neutrino and Tachyon is now up at
🔗Matrix Federation Stats 📊
Aine [etke.cc] says
collected by MatrixRooms.info - an MRS instance by etke.cc
As of today, 20254 Matrix federateable servers have been discovered by matrixrooms.info, 4148 (20.5%) of them are publishing their rooms directory over federation.
The published directories contain 19970 rooms.
The most popular server software among the online servers is:
synapse: 15733 (77.7%)
continuwuity: 1817 (9.0%)
cond

https://matrix.org/blog/2026/09/04/this-week-in-matrix-2026-09-04/

Organise your chats your way with Sections If your All Chats list ...

2026-10-15T06:54:00Z

Organise your chats your way with Sections

If your All Chats list has grown to the point where finding anything feels like work, you're not alone. A long, flat list of rooms and DMs doesn't scale — the important conversations get buried, the noise is always visible, and keeping on top of it all requires more effort than it should. Introducing sections!
Drag and drop rooms into sections
What's new
Sections lets you create named groups for your rooms to organise them however makes sense for you. You might have a section for a specific project, a team, a client, or just a catch-all for low-traffic chats you want out of the way. The structure is yours to define.
Your existing Favourites, Low Priority, and Chats categories are not going anywhere: they’re now default sections. These replace the old filter buttons — rather than toggling between views, your rooms are grouped in one consistent place.
Sections only appear when they contain rooms in the space you’re browsing, so your list stays clean. You can still find them and add rooms to them via the room context menu.
How it works
To create a section, open the room list menu (+) and select "New section". Give it a name, and it appears in your All Chats list ready to populate.
Creating a new section
Adding a room into a section is as simple as dragging a room and dropping it into a section. If the section doesn’t appear, you can right-click any room and select "Move to Section" — from there you can assign it to any of your sections, default or custom.
Move a room to a section
Sections can be collapsed to hide their contents, which is particularly useful for keeping low-priority groups out of view without losing them entirely. When a section contains unread messages, it tells you.
Sections with unreads
Sections are available now in Element. We'd love to hear how the feature fits into your workflow — and what you'd like to see improved or extended as we continue to develop it.
We don't just ship features and move on. If Sections don’t work for you, help us refine them. Raise a ticket or use the in-app feedback form. To disable it entirely use develop.element.io or Element Nightly, heading to Settings > Preferences and “Disable Sections”.

https://element.io/blog/organise-your-chats-your-way-with-sections/

This Week in Matrix 2026-09-11 🔗Matrix Live - Matrix ...

2026-10-15T06:35:56Z

This Week in Matrix 2026-09-11

🔗Matrix Live - Matrix Conference 2026 Preview
🔗Dept of Editorial 🖋️
andypiper writes
Hello! This Week in Matrix aka TWIM is our weekly update on what is going on in the Matrix ecosystem (the clue is in the title…!)
You can learn more about how we manage submissions to TWIM in the guide. The basic system is that news updates are posted to the Matrix room #thisweekin:matrix.org, and our friendly bot helps us to categorise the entries to output something that is - mostly - ready to publish. After that, we do some light editing, primarily to format things correctly. TWIM production is a collaborative effort, between myself (Andy, on behalf of The Matrix.org Foundation); the Website & Content Working Group; and of course, everyone that shares their news items every week.
Our goal with This Week in Matrix is for it to showcase the progress of Matrix projects, and the vibrancy of our community. We want it to be interesting and fun to read, as well as being informative to folks that don’t have time to follow everything going on across all the different channels.
We know that it can be a bit of work to post something that’s interesting, but it really helps when the news is authentic, novel, or otherwise impactful. A pattern we’ve noticed is that some projects are summarising changelogs, instead of highlighting updates that might be most interesting for people (meaning, people that use the software, developers, spec authors, and more). In other cases, we’ve seen submissions with far less substance - for example, without any code, or without a pointer to a place for readers to ask questions and learn more. We’re excited to see different new apps emerging, but we also want to have a mixture of news, rather than having the same things featured every week.
You can share images with your news submissions, to make them more visually appealing. One of the editors can help with that, so ask us in the TWIM room. If you're posting something about a client app, it helps us if you can describe what the image is demonstrating and what readers might want to be looking for in it.
All of this is to note that we’re adding some editorial curation to TWIM, in order to keep things on track - and yes, that involves some more proactive choices. If projects show up every week, we might choose to reduce the coverage to keep the content fresh. If there is not enough information in a submission, we may hold it back, or ask for it to be rewritten. That said, we're also keen to keep hearing from everyone. Help us keep This Week in Matrix an exciting and interesting read every week 🫶🏻
See you in the This Week in Matrix room!
🔗Dept of The Matrix Conference 🏛️
🔗The Matrix Conference (website)
andypiper announces
The countdown to The Matrix Conference 2026 continues. Watch Matrix Live for a sneak peek, and take a look at the full schedule (and then, get your ticket!)
🔗Dept of Events and Talks 🗣️
🔗Stammtische (website)
HarHarLinks says
A Stammtisch ("regular's table") is a German meetup format where those with a shared interest meet regularly for discussion, exchange, and socialising.
Find more community organised events at matrix-community.events!
14 September (2nd Monday of every month) 20:00 CEST: #matrix-stammtisch:ccc.ac at CCCAC
15 September (3rd Tuesday of every month) 17:30 CEST: #stammtisch-karlsruhe:alsace.hair at Fachschaft ETIT
17 September (3rd Thursday of every month) 19:00 CEST: #matrix-stammtisch:freiburg.social at Blauer Fuchs, see https://blog.freiburg.social/event/matrix-stammtisch-freiburg-6/
19 September 12:30 CEST: #matrix-stammtisch:dresden.network, this time at Datenspuren, see https://dresden.datenpunks.de/events/matrix/2026-09-20-matrix-stammtisch/
Are you running a Matrix meetup? Add it to the list!
🔗Homeserver Deployment 📥️
🔗Element Server Suite (website)
Element Server Suite (ESS) is a backend hosting solution for Matrix-based communications that supports self-hosted and fully managed deployments.
Ben BZ reports
Element Server Suite (ESS) Community 26.9.0 and 26.9.1 have been released.
In addition to including the latest and greatest versions of Synapse, Matrix Authentication Service and Element Web, we have improved our support for delayed events with MatrixRTC, replaced Redis with Valkey and allowed configuration of limits on all ephemeral storage. The Element Admin user interface now includes a screen to manage devices.
Matching 26.9.0 and 26.9.1 releases for ESS Pro include all of the above, along with improvements to URL preview blocking in TI-Messenger and the ability to customize power levels for rooms in Advanced IAM.
🔗Dept of Clients 📱
🔗Koushi (website)
Hiroshi Shinaoka announces
Koushi is a new desktop-first Matrix client built with matrix-rust-sdk and Tauri.
I originally started Koushi for my own research workflow. In particular, I wanted a Matrix client that works well for research and developer communities, with good support for multilingual and CJK text/search, fast navigation, and a desktop-oriented workflow.
The project is still experimental, but I am already using it for my own Matrix communication and continuing to add features based on real usage.
GitHub: https://github.com/shinaoka/koushi-matrix
Matrix room: https://matrix.to/#/#koushi-matrix:matrix.org
🔗Tesseract (website)
Marco reports
Hi, it's been a while!
Four new releases came out since the last TWIM post! Currently at 0.8.21, the most important highlights are:
Bubbles! Tesseract now has multiple message timeline layouts: classic, bubbles, and (of course) an IRC-mode. Yes, I had to. Sue me.
Chat history export: you can export in text / HTML format (with optional media).
Deeper platform integration: recent rooms accessible from the taskbar (windows), full menu bar shortcut coverage / spotlight search (mac), GNOME Shell/KRunner room search.
Room knocking
Video event streaming (don't wait to download the whole media file to start playback)
Low power mode (disable background work when running on battery)
And of course, many many fixes and performance optimizations.
Enjoy!
🔗kazv (website)
kazv is a convergent Matrix client and instant messaging app.
tusooa🏔️ announces
We finally released kazv 0.7.0 . New features include device verification, requesting room keys, importing key backup, SSO and many UI improvements.
Read the full changelog.
🔗FluffyChat (website)
The cutest instant messenger in the [matrix].
Krille - Christian K. announces
🔗Test the new FluffyChat Matrix RTC Calls today!
Yes you have heard right. FluffyChat has now support for end-to-end encrypted Matrix RTC Calls, fully compatible with Element and Cinny. The implementation uses Flutter's LiveKit package and will come with the next release 2.10.0.
If you feel lucky you can already test them out at https://fluffychat.im/nightly.
To have the call button visible your homeserver needs to advertise support for matrix rtc calls in well-known. matrix.org for example does! But if someone on a supported homeserver has created a call you probably can also join even if your homeserver does not yet have support for it.
The implemented features include:
1:1 and group calls
CallKit implementation on Android & iOS (the mobile device will act like being in a native call, Android will also ring when you get called
Raise hand inside of a call
Share your screen (right now only on web and desktop)
Select your audioinput, audiooutput and videoinput
Grid view or focus view depending on the context
If you find (hopefully reproducible) bugs feel free to open issues at https://github.com/krille-chan/fluffychat/issues
🔗Dept of VoIP 🤙
🔗lk-jwt-service (website)
Johannes Marbach reports
lk-jwt-service version 0.7.0 has been released today.
This release brings about a full rewrite of the service in Rust which reduces the service's resource footprint and simplifies future changes. The public interface remains backwards compatible for now so the update should be a drop-in replacement.
In other news, the service now supports running as an application service to serve the new Client-Server and Server-Server endpoints from MSC4195. Note that this setup is still experimental and requires a compatible homeserver (currently only Synapse from develop).
Finally, thanks to GitHub user @benbz, the service now supports loading the Redis password from an independent environment variable and @770grappenmaker fixed a bug that previously rendered the healthcheck endpoint defunct in some situations.
🔗Dept of SDKs and Frameworks 🧰
🔗Ruma (website)
A set of Rust library crates for working with the Matrix protocol. Ruma’s approach to Matrix emphasizes correctness, security, stability and performance.
Kévin Commaille reports
Here comes Ruma 0.17.0, packed with breaking changes to make your life easier (hopefully). Here are the main ones:
Support for Matrix 1.19, including the endpoint to get the rooms in common with another user and stable support for image packs.
The API traits for incoming and outgoing requests or responses were refactored to remove the generics to try to improve compile times of downstream crates. The methods with generics are still available in some cases with new extension traits so you will only need to bring them in scope to avoid making changes to your code.
API crates no longer export anything if neither the client nor server features are enabled, because they are not useful without at least one of these features.
The XMatrix type allowing to construct or parse X-Matrix headers has been refactored to remove a dependency on an external crate.
Identifiers support 2 new internal representations: ThinArc which is cheap to clone like an Arc, but should use less memory and be faster, and SmallVec which allocates sufficiently small strings on the stack rather than on the heap, so it should also be faster but use more memory overall.
Various contributors added unstable support for more MSCs including the not-so-new Configurable per-room message retention periods (MSC1763), and the brand new Membership-based invite blocking (MSC4494) and Selective Presence (MSC4495).
This release was followed by ruma-client 0.20.0 and synapse-admin-api 0.12.0.
We still have a bunch of issues opened and always welcome implementations for ongoing MSCs, so don't hesitate to contribute.
🔗Dept of Ops 🛠
🔗Selfhosting a Matrix Server on a Raspberry Pi 5
andypiper says
I spotted this nice write-up of a personal homeserver migration, with bridges etc.
https://marius.blog/self-hosted-matrix-raspberry-pi/
🔗Dept of Interesting Projects 🛰️
🔗Venoom (website)
venumonelement reports
Venoom is coming along pretty nicely, and I now have test builds available for web, Windows, Android and Linux. macOS and iOS are on the way too.
Venoom is a Bluesky/ATProto and Matrix client in one app. You link your ATProto and Matrix accounts together, which allows for some nice interaction between the two. For example, you can open someone's Matrix profile and see their ATProto posts alongside their Matrix information.
The Matrix side is also getting a lot more fleshed out. Venoom now supports extended profiles with things like banners, bios and avatar decorations, alongside Spaces, rooms, DMs, threads, roles, emotes, voice calls, screen sharing and more.
Everything is still very early and there is plenty left to do, but if you want to mess around with an alpha build you can find them here: https://github.com/drvnm/venoom-releases/releases Web version: https://venoom.net
if you want to follow development, report bugs or just hang out, you can join the Matrix room here: https://matrix.to/#/!gxmZLQDhVacrWxzPiM:matrix.org
Thanks to everyone who has been trying it and giving feedback so far!!
🔗Matrix Federation Stats 📊
Aine [etke.cc] says
collected by MatrixRooms.info - an MRS instance by etke.cc
As of today, 20307 Matrix federateable servers have been discovered by matrixrooms.info, 4141 (20.4%) of them are publishing their rooms directory over federation.
The published directories contain 19552 rooms.
The most popular server software among the online servers is:
synapse: 15763 (77.6%)
continuwuity: 1827 (9.0%)
conduit: 549 (2.7%)
dendrite: 305 (1.5%)
Stats timeline is available on 📊 MatrixRooms.info/stats
🧩 Integrations with apps and servers | 💜 Support the project | 👉 How to add your server | 🙅 How to remove your server
🔗Dept of Ping 🏓
Here we reveal, rank, and applaud the homeservers with the lowest ping, as measured by pingbot, a maubot that you can host on your own server.
Join #ping:maunium.net to experience the fun live, and to find out how to add YOUR server to the game.
RankHostnameMedian MS
1raccoon.cafe178
2codestorm.net188
3vrkknn.net192
4kanp.ai224
5melthecat.dev232.5
6synapse.rntpts.de238.5
7nerdhouse.io251
8zirco.dev255.5
9sspaeth.de308
10avali.zone308
🔗That's all I know
See you next week, and be sure to stop by #twim:matrix.org with your updates!
To learn more about how to prepare an entry for TWIM check out the TWIM guide.

https://matrix.org/blog/2026/09/11/this-week-in-matrix-2026-09-11/

Cyber Resilience Act: What changes this week and how Element is ...

2026-10-15T06:24:11Z

Cyber Resilience Act: What changes this week and how Element is preparing

On 11 September 2026, the first substantive deadline under the Cyber Resilience Act (Regulation (EU) 2024/2847, "the CRA") will come into effect. This Regulation entered into force on 10 December 2024, but it applies in stages, and this week’s date is the second of three stages.
As from 11 September, manufacturers of products with digital elements placed on the EU market become subject to the reporting obligations set out in Article 14. Essentially, an actively exploited vulnerability, or an incident that severely affects the security of a product, now has to be notified to the relevant Computer Security Incident Response Team (CSIRT) and to the European Union Agency for Cybersecurity (ENISA) within a strict timetable:
An early warning, within 24 hours of becoming aware of the incident or actively exploited vulnerability
A more detailed follow-up notification, within 72 hours
A final report once the matter is resolved, within 14 days to 1 month, depending on the type of issue.
This post sets out what this means for Element, why it applies differently depending on which product is involved, and what is still ahead of the CRA’s fuller application in December 2027.
Element as original manufacturer
We have previously discussed the distinction the CRA makes between an open source project without commercial intentions, and the entity that first places a product on the market with commercial intent – the "original manufacturer," in the regulation’s own terminology.
This distinction is key to understanding what kind of compliance support you might expect to receive from Element when it comes to your own CRA obligations. Element develops and stewards open source software including the Community Edition of the Element Server Suite. On the other hand, where Element packages, sells and supports a product commercially, we are the manufacturer of that product, and take on the CRA’s obligations for it directly. This is the case for Element Server Suite Pro (ESS Pro).
As a product placed on the market for commercial purposes, ESS Pro sits inside the CRA’s scope in full; the essential requirements in Annex I once those apply from December 2027, and, from this week, the Article 14 reporting timetable for actively exploited vulnerabilities and severe incidents.
Meeting that timetable depends on having a working path from disclosure to notification; a single point where security disclosures are received, an internal escalation route from that inbox to whoever can assess exploitation and severity quickly enough to meet a 24-hour clock, and a defined interface into the CSIRT and ENISA reporting channels themselves.
As a security minded organisation, these requirements are already largely in line with our existing procedures. Much of the groundwork required for CRA compliance is something we have been working towards for a while, embedding best practice into our organisational modus operandi. This includes, but is not limited to, a maintained Software Bill of Materials for ESS Pro, a record of the components it depends on, and change control over the code that ships in it.
By contrast, Element X and the Community Edition of the Element Server Suite are made available by Element without being placed on the market, and therefore do not come with manufacturer obligations. This is important to consider, and one of the reasons why we do not recommend using ESS Community for professional deployments. We won’t be able to support your organisation’s compliance obligations if you’re not using the Pro products.
What comes next
This week marks an early milestone, but it’s not the end of the journey. The main obligations (i.e. the essential requirements in Annex I, covering secure-by-design development, documented vulnerability assessment processes and conformity assessments) become enforceable in full from 11 December 2027.
On our side the work continues towards our CE marking and evaluating the need for third-party certification. Our recommendation to our customers and partners is very simple. Start engaging with the process now, ensure that any changes required are incremental and embedded with your company’s culture, and find trusted suppliers and partners, such as Element, that can help simplify your journey through this and other regulations.

https://element.io/blog/cyber-resilience-act-what-changes-this-week-and-how-element-is-preparing/

This Week in Matrix 2026-09-18 🔗Matrix Live S13E09 - Hydra ...

2026-10-15T06:12:26Z

This Week in Matrix 2026-09-18

🔗Matrix Live S13E09 - Hydra updates
🔗Dept of The Matrix Conference 🏛️
🔗The Matrix Conference (website)
andypiper announces
This week, we are happy to reveal that the pre-event social 🪩 will be held at Babel Malmö, close to the conference venue, on the evening before the main conference content begins.
Preparations for the event continue. Have a look at the full schedule. We're excited to have some great talks lined up. Just as a taste of what's in there: Community self hosting; Digital Sovereignty; Several government deployments; FluffyChat; Matrix Specification improvements; and so many more.
We don't want you to miss it, so get your ticket now!
🔗Dept of Spec 📜
🔗Is Presence Fixed Yet?
lveneris reports
Still no, but we're evaluating our proposed solutions.
You may have heard the story. Presence has been largely left alone for much of Matrix's life, slipping under the radar through years of updates to the rest of the protocol. It is quite possibly one of few original planks left in our dear Specification of Theseus. This neglect has given rise to a situation where presence is one of Matrix's least-deployed core features. Lately, a group of independent community members, including maintainers of Continuwuity, have been working on a group of proposals to give presence the renovation it sorely needs.
Today, we have a different kind of update to share with you. Instead of announcing a proposal hot off the presses, we're listening in and investigating presence in its natural habitat on the public federation. This noble quest to explore the situation in practice and determine how much our proposals could help led us to capture some three hundred thousand presence updates, in which we found some fascinating twists: servers sending malformed updates; the vast majority of presence updates containing no new presence information at all; and statuses being far less popular on Matrix than we anticipated, even amongst the subset of users sending presence.
Our journey may begin in harsher territory than you think. Can you guess when presence was enabled on this two-user homeserver?
Can you guess when presence was enabled?
We'll let the numbers speak for themselves, though. Read about all this and more in our new post Is presence broken now? on the initiative website ispresencefixedyet.com. If you'd like to come along, or just ask about what we're up to, feel free to join us in #presence-v2:zirco.dev.
🔗Dept of Servers 🏢
🔗Synapse (website)
Synapse is a Matrix homeserver implementation developed by Element.
madlittlemods (Eric Eastwood) says
This week we have a new release, Synapse 1.161.0. To highlight:
We've been driving forward Matrix spec compliance by filling in a bunch of tiny gaps in behavior between Synapse and the Matrix spec that have been preventing us from declaring support for further Matrix versions (#20036, #20101, #20104, #20119, #20169, #20173, #20180, #20192). The "Support for Matrix 1.xx" issues track the broad strokes but there is a stack of tiny gaps we've discovered along the way, which is why we haven't quite declared support for some Matrix versions that look "complete" from the issues alone. Unfortunately, these are only documented internally at the moment but they're practically all underway so things should come together soon.
Event persistence now recovers cleanly from a database interruption. Previously, if the database went away at the wrong moment, the affected room would stop accepting new events until Synapse was restarted (#20148).
We gained experimental support for MSC4512 which allows delegating parts of the Client-Server and Server-Server API to application services (#19972, #19977).
From the community, a couple of fixes when creating a room: First is a fix for the public_chat preset to properly form the power levels for m.call.invite events (#20050, thanks to @itsoyou from Famedly). And the second fixes the m.room.encryption event being duplicated when configuring encryption_enabled_by_default_for_room_type and using initial_state when creating the room (#20106, thanks to @FrenchGithubUser from Famedly).
Thank you to all our contributors for helping to make Synapse the best it can be. As always, feel free to stop by #synapse:matrix.org to join in on the discussion and if you encounter a bug make sure to report it.
🔗Tuwunel (website)
Enterprise successor to conduwuit, the high-performance and feature-rich fork of Conduit.
june ✿ 🏳️‍⚧️ (it/she/puppy) says
Tuwunel 1.9.1 serves animated thumbnails. A thumbnail request with animated=true for an animated GIF, WebP or APNG now returns a looping GIF instead of a frozen first frame. June implemented MSC2705; clients do not send the parameter yet, so the server side arrives first.
Element X for iOS location markers now move as location updates arrive, after utop-top's report. AngelBePro reported Sable space children missing until a reload; subscribed rooms now get their required state without a timeline event. ruka-hamanasu fixed FluffyChat rooms stuck unread after a receipt; basnijholt restored quiet rooms to legacy full-state sync.
June published prebuilt Nix store paths; unattended Nix must trust the cache explicitly. Debian and RPM packages adopt an existing Conduwuit or Conduit database by renaming it into /var/lib/tuwunel. Migrations now report progress every fifteen seconds and stop cleanly at step boundaries.
June also added MSC4155 invitation control by sender (block refuses, ignore hides from sync), the Sliding Sync profiles extension (MSC4262, MSC4426) that Element X requests, with validated status, call and timezone fields, and opt-in auto_accept_invites, raised by sanyamseac.
tototomate123 added url_preview_accept_language for dlrudie's request and summarized query storage sync for justinbrick's report; alemidev asked for url_preview_cache_ttl. basnijholt fixed /messages bounds and a device-key overwrite on read failure; ruka-hamanasu unblocked read markers on backfilled events; obodnikov made both Synapse-compatible deactivation routes (v1, v2) leave their rooms; asmj1108 reported Chrome blocking native OIDC callbacks; tcyrus caught room enable claiming success on an m.federate: false room (MSC4361 remote-invite coverage).
Full notes: https://github.com/matrix-construct/tuwunel/blob/114bc231622299f9a5da7a60f951e2b0e4144b89/RELEASE.md
💕 GitHub ✦ Releases ✦ DockerHub ✦ Playbook ✦ Containers ✦ Documentation ✦ Enterprise 🐕️ Tuwunel 💕
🔗Dept of Clients 📱
🔗Extera (website)
rustyraven[extera.xyz op] announces
We made a lot of changes since last TWIM post which had mentions of Extera. We will cover a few notable changes made since then:
Rich presences. Now they use MSC4544 to show multiple activities, buttons and progress bars.
Added support for HTTP_PROXY environment variable. httpProxy in advanced configuration overrides it.
Polished Livekit calls: added E2EE support (@cherret), redesigned call controls and incoming call popup. Also dropped support for TURN-based calls.
Redesigned reaction popup, where you can see a list of people who sent a certain reaction, and message context menu. Now they use backdrop with blurring and highlighting selected reaction/message.
More customisation options: now you can choose side for message bubbles (one side, adaptive,both sides) and title text in app bar (current account name/app name).
Several bugfixes, including: polls sometimes not showing all votes, "null check on null value" error when forwarding multiple messages.
Matrix space ＊ Source code ＊ Website
rustyraven[extera.xyz op] also says
Extera Rich Presence
Extera has dropped support for MSC4320 in favour of MSC4544, and so does Extera RPC app.
Extera RPC runs independently of Extera, so you can use it alongside any client you like.
Download - Source code
🔗Matrix Federation Stats 📊
Aine [etke.cc] announces
TWIM
collected by MatrixRooms.info - an MRS instance by etke.cc
As of today, 20291 Matrix federateable servers have been discovered by matrixrooms.info, 4129 (20.3%) of them are publishing their rooms directory over federation.
The published directories contain 19680 rooms.
The most popular server software among the online servers is:
synapse: 15749 (77.6%)
continuwuity: 1829 (9.0%)
conduit: 537 (2.6%)
dendrite: 298 (1.5%)
Stats timeline is available on 📊 MatrixRooms.info/stats
🧩 Integrations with apps and servers | 💜 Support the project | 👉 How to add your server | 🙅 How to remove your server
🔗Dept of Ping 🏓
Here we reveal, rank, and applaud the homeservers with the lowest ping, as measured by pingbot, a maubot that you can host on your own server.
Join #ping:maunium.net to experience the fun live, and to find out how to add YOUR server to the game.
RankHostnameMedian MS
1vrkknn.net153
2kanp.ai187
3vibb.me252.5
4dykes.ca255
5zirco.dev259
6jvyden.xyz474
7victorewik.es495.5
8sspaeth.de537
9projxyz.net665
10shadowdrake.org917
🔗That's all I know
See you next week, and be sure to stop by #twim:matrix.org with your updates!
To learn more about how to prepare an entry for TWIM check out the TWIM guide.

https://matrix.org/blog/2026/09/18/this-week-in-matrix-2026-09-18/

This Week in Matrix 2026-09-25 🔗Matrix Live - New Features for ...

2026-10-15T05:57:35Z

This Week in Matrix 2026-09-25

🔗Matrix Live - New Features for FluffyChat
🔗Dept of The Matrix Conference 🏛️
🔗The Matrix Conference (website)
andypiper announces
The Matrix Conference is happening in just a few weeks! (you may have heard about it? 😉)
Join us in Malmö for talks, workshops, and discussions about the future of Matrix. Go to the website for more details, and to get your tickets.
If you have already bought your ticket, these are now available for download or for adding to your digital wallet. Speakers should check their email to find their voucher for a ticket, and follow the instructions in the email to get invited to the speakers' room on Matrix.
The volunteer system has been updated, with some very last volunteer slots available.
We will have a new range of Matrix stickers available! If you have a Matrix-related project, make sure to bring your own stickers for the sticker exchange.
🔗Dept of Spec 📜
Andrew Morgan (anoa) {he/him} announces
Here's your weekly spec update (back from the dead)! The heart of Matrix is the specification - and this is modified by Matrix Spec Change (MSC) proposals. Learn more about how the process works at https://spec.matrix.org/proposals.
🔗MSC Status
New MSCs:
There were no new MSCs this week.
MSCs in Final Comment Period:
MSC4452: Preview URL capabilities API (merge)
MSC4095: Bundled URL previews (merge)
Accepted MSCs:
MSC3959: Sliding Sync Extension: Account Data
Closed MSCs:
No MSCs were closed/rejected this week.
🔗Spec Updates
The Spec Core Team has been focusing intensely on the various Matrix 2.0 MSCs these past few weeks, with the intention to getting them ready before the Matrix conference in October.
The following is a list of the current status of each MSC, courtesy of @Johennes:
Updated MatrixRTC pulse check:
🟢 MSC4140: Cancellable delayed events - Merged
🟡 Clarifications for MSC4140: Cancellable delayed events - Open, review changes requested
🟡 MSC4354: Sticky Events - 2 / 8 checkboxes (unchanged from last week but there was good progress on the discussion threads on the MSC)
🔴 MSC4480: Sliding Sync Extension: Sticky Events - Proposed for FCP readiness as of this week, waiting on initial SCT review
🔴 MSC3960: Sliding Sync Extension: Receipts - Tracking for review
🟡 MSC4538: Sliding Sync Extensions: To-Device messages - Proposed for FCP, currently Ready for FCP ticks
🟡 MSC4543: Sliding Sync Extensions: End-to-end encryption - Proposed for FCP, currently Ready for FCP ticks
🟡 MSC4143: MatrixRTC – Real-time communication over Matrix - 6 / 8 checkboxes (unchanged from last week)
🟡 MSC4195: LiveKit transport for MatrixRTC - 3 / 8 checkboxes (unchanged from last week)
🟡 MSC4196: Voice and video calling application for MatrixRTC - 1 / 8 checkboxes (unchanged from last week)
🔴 MSC4075: MatrixRTC invites and notifications - Proposed for FCP readiness as of this week, waiting on initial SCT review
Regardless, we did have some URL preview improvement MSCs slip through into FCP, which is nice to see.
MSC4095: Bundled URL Previews especially, as it helps reduce the resources needed on the homeserver by either only requiring the sending homeserver to download the linked page, or allowing clients to download the preview instead.
🔗Dept of Trust & Safety ⚖️
Sky reports
Some of you may already know the #cs-auto-open_reg:codestorm.net policy list and some of you may even be using it.
What many of you probably don't know yet is the history behind it.
I wrote a small blog post series where I go trough the initial problem, what I've tried that failed and what eventually ended up working and where we are with it today.
I think its nice to sometimes read a story of something actually working out in the end and I think we already have enough blog posts talking about how hard matrix is to moderate and what all is bad about it so here is my contribution to that with a positive story.
So, I hope you enjoy it and maybe even learn something nerdy and cool while reading it :)
🔗Dept of Servers 🏢
🔗Venator (website)
Venator is an independently maintained Matrix homeserver, written from scratch in Go using the mautrix-go SDK.
nex (it/she) (away -> tbd) announces
Venator v0.1.0a4 was released, bringing exciting new goodies like OAuth2 login support, tangible performance enhancements, a disproportionate number of bug fixes, and I threw in some teasers for early outbound federation support too. Read more about it in the release notes, and/or come discuss the project in #venator:starstruck.systems. Also thanks to everyone who has starred the repository! 🐟️
🔗Dept of Clients 📱
🔗Harmony (website)
catcraft says
Hello everyone!
Harmony v0.6.0 just released, with support for changing room-scoped profiles, server-side search, profile timezones, and improvements to device verification. If you missed the previous entries, Harmony is a JavaScript-based, modular, extensible Matrix client with an open plugin system.
Speaking of plugins, a few more plugins have been released alongside v0.6.0, adding support for setting/displaying user pronouns (MSC4247) and banners (MSC4427). They can be found here. With these, as well as the biographies plugin and builtin timezones plugin, Harmony can now display (and configure) some of the more common profile fields in use today. Hooray!
Since v0.4.0, we've also added support for silent replies, room member management, and stickers. You can find the full changelog for all versions here.
You can find the latest release on the releases page on Codeberg, and you can also join the Harmony rooms to get announcements and chat about the client:
Space
General room
Plugin developer room
Announcements
Happy hacking!
🔗iamb (website)
A terminal-based Matrix client that uses Vim keybindings.
ulyssa reports
iamb v0.0.12 has been cut and released! 🎉
Changes in this release include:
Displaying stickers, image reactions and media captions.
Opening matrix.to links within iamb.
Support for sending traffic through SOCKS5 and HTTPS proxies
Support for custom command aliases, intentional mentions, room knocking, and room upgrades, and updating user profile information.
New config options for specifying encryption indicator location and icons, custom input prompt, when read receipts are updated, default register, and custom cursor shapes.
Improvements to verifications, tracking unread rooms, command completions, and image previews.
Fixes for issues joining rooms, displaying message edits, and other bugs.
Refer to the Github releases page for more information and downloading binaries, and https://iamb.chat for documentation.
🔗Nexus (website)
Matrix client made with Flutter and a Gomuks backend.
QuadRadical (Ping) announces
Hello TWIM! It's been a while since the last update on Nexus, but quite a lot has happened!
iOS support! Nexus can now be built and run on iOS by sideloading an unsigned .ipa. However, there hasn't been too much testing here, so there may be bugs. If you try Nexus on iOS and run into any issues, please let me know in our Matrix room.
MacOS support has come a long way, including proper DMG builds and a number of platform-specific fixes and improvements.
Push notifications! Nexus now has UnifiedPush support on Android and Linux, so it can run fully in the background, and be woken up in the background by your UnifiedPush distributor. FCM is also supported for Android, so you don't need to install a separate UnifiedPush distributor. As part of this update, we also introduced a new Notifications page where you can see all your past notifications.
Push notification support in Nexus is very new, and is quite a complex feature, especially on Linux, and thus comes with some bugs. If you run into anything, please let me know in our Matrix room. Support for picking an UP distributor instead of using the default on your OS is also planned.
A new emoji picker, written from scratch by me. This works far better than the last package we were using, and will enable support for custom emoji at a later stage.
Better rendering of timestamps and state events.
Support for blocking invites and MSC4494.
And, as always, a whole lot of bug fixes 🙂
🔗Initial release progress
I know that in some previous TWIMs I suggested that I would publish a release soon, but since then I decided that I would like Nexus to be in a very good state before an initial release.
There's good news on that front: We are getting close. I've added a milestone on the forge for all the issues that need to be fixed before v1.0.0, though I will likely find some more bugs that need to be squashed.
You can take a look at it here: https://nexus.federated.nexus/milestone/1
🔗Get involved!
If you want to help with development or simply keep up with new features, join our Matrix room at #nexus:federated.nexus or check out the Git repo at https://nexus.federated.nexus.
🔗Element X iOS (website)
A total rewrite of Element iOS using the Matrix Rust SDK underneath and targeting devices running iOS 17+.
Mauro reports
Hi everyone! Here's what the Element X iOS team has been up to this week:
🔗✨ New and improved
Notification counts in the room list: the room list now shows how many notifications you have in each room, and the badge on the app icon uses the same counts, so the two should always match.
Smoother history loading: loading older messages in a room is now more reliable, and this is now on for everyone.
🔗🚧 In progress
Forwarding multiple messages: we made steady progress on letting you select several messages at once and forward them to more than one room in one go.
Native calls: work on the new built-in calling experience continues, and call buttons now also show up on macOS when this experimental feature is turned on.
Multi Account support: preparatory work has started to finally bring one of the most requested features ever.
🔗🐛 Fixes
A round of polish for iOS 27: we fixed the iPad split view layout, some overly bright toolbar elements, and toolbar buttons on macOS.
The side tab bar no longer flickers or disappears when you resize the window.
Fixed a crash caused by some unusual status emojis on user profiles.
🔗Element Web/Desktop (website)
Secure and independent communication, connected via Matrix. Come talk with us in #element-web:matrix.org!
David Langley says
🔗🌴 User Status enabled by default in Element Web
Going on Holidays? Lucky you, let people know with the User Status feature. Use presets like 🌴 Away or set your own custom emoji/message combination. From Tuesday 29th of September this is enabled by default on Element Web. This will only work if User Status is enabled on your homeserver(include_profile_updates_in_sync in homeserver.yaml). It does not yet support federation but that is being worked on.
See MSC4426: Profile Updates, MSC4429: Legacy Sync, and MSC4262: Sliding Sync
🔗📌 Improved timeline scrolling and navigation is coming to Labs
Tired of clicking a matrix.to link only for Element Web to drop you at... well, the wrong message? Good news, we have been hard at work on a new timeline that should land you in the right place.
The new timeline aims to make navigation feel much more reliable, with:
Fewer unexpected jumps while loading messages
More reliable "Jump to bottom" and "Jump to unread" buttons
An unread marker that stays where you expect it to
Improved keyboard navigation, including moving through messages one by one (coming soon).
It is currently experimental and there are some known bugs, so please give it a try and let us know what you find.
It is already available on develop.element.io/desktop nightly, and will be available in the general releases from Tuesday 29 September. Go to All Settings -> Labs -> User interface to enable it.
We would love your feedback and bug reports. Click here to do just that, or find out more about what to expect.
🔗📄 Read PDFs without leaving the conversation
Need to check a PDF while discussing it in a room in Element Web/Desktop? You can now open it in the right panel, so you can read and chat side by side. No more switching back and forth between tabs.
The preview happens entirely in your client, there's no server-side conversion involved.
The PDF reader is currently in Labs 🧪. Try it now on develop.element.io or Element Desktop nightly by enabling Open PDFs in Labs. Or you can enabled it in the general Element Web release from the 29th of September.
🔗Commet (website)
Commet is a client for mobile and desktop with a modern UI and fun features!
airyz reports
The long awaited v0.5 is finally here! By far the biggest highlight of this update, (and the reason it took so long to develop) is adding support for Widgets, which allow you to embed custom tools and games in to your chat rooms. The introduction of the Widgets API opens up many new possibilities to customize your experiences on Matrix, and provides a great foundation for us to build on top of for even more interesting features in the future.
🔗🎮 Widgets
Commet being built in Flutter presented some interesting challenges in developing widgets, since widgets are web apps and thus require a webview to run. While it is possible to embed webviews inside a Flutter app, there were lots of limitations and performance issues with this approach and the quality did not meet our standards. After some experimentation we ended up with a few different implementations of widget runners to try and get the best overall experience for each currently supported platform.
The most interesting implementation was for Android, where we are spawning a new activity with its own webview using Android's split-screen API. This was significantly more performant than embedding the webview in Flutter itself as it completely bypasses the expensive compositing stage, and allows the heavy processing to occur separately with minimal impact on the main Commet instance. This works especially great on tablets in desktop mode (and one user reported it working well in Android based VR headsets!), where the two activities can be manipulated in floating windows. This inspired the implementations for the desktop version of the app as well, where we now have a separate Rust based process acting as the host on Windows, and an implementation utilizing instances of chromium already installed on your system on Linux. We would have liked to use the same Rust process on Linux, but due to limitations of WebKitGTK (lack of WebRTC support) have had to go with chromium for now.
In addition to our support for the Widgets API, we have also been developing some widgets of our own: A collaborative drawing game and a way to watch YouTube videos with your friends. These are both implemented using Element Call in SDK mode for real time communication, and are both in very early alpha!
🔗☎️ Experimental Support for Encrypted Element Call
After a lot of work, we are finally shipping initial support for end to end encryption in our implementation of MatrixRTC / Element Call. It is currently marked as experimental, so it needs to be toggled on before it can be used, and we are looking for user feedback to see where it may need improving.
You can find the release here
🔗Dept of SDKs and Frameworks 🧰
🔗vodozemac-java (website)
Francois Herbreteau announces
vodozemac-java v1.0.0 has been released, a new Java binding for vodozemac, the Rust library used for Matrix cryptographic functionality.
The artifact is available through Maven Central, and the project is hosted here:
🔗 https://github.com/fherbreteau/vodozemac-java
If you’re working on Matrix software in Java, I’d be happy to hear your thoughts!
🔗Matrix Federation Stats 📊
Aine [etke.cc] says
collected by MatrixRooms.info - an MRS instance by etke.cc
As of today, 20298 Matrix federateable servers have been discovered by matrixrooms.info, 4121 (20.3%) of them are publishing their rooms directory over federation.
The published directories contain 19674 rooms.
The most popular server software among the online servers is:
synapse: 15736 (77.5%)
continuwuity: 1846 (9.1%)
conduit: 536 (2.6%)
dendrite: 291 (1.4%)
Stats timeline is available on 📊 MatrixRooms.info/stats
🧩 Integrations with apps and servers | 💜 Support the project | 👉 How to add your server | 🙅 How to remove your server
🔗Dept of Ping 🏓
Here we reveal, rank, and applau

https://matrix.org/blog/2026/09/25/this-week-in-matrix-2026-09-25/

This Week in Matrix 2026-10-02 🔗Matrix Live S13E11 - All ...

2026-10-15T05:09:06Z

This Week in Matrix 2026-10-02

🔗Matrix Live S13E11 - All Things Matrix
🔗Dept of The Matrix Conference 🏛️
🔗The Matrix Conference (website)
HarHarLinks says
It's finally October, the month of The Matrix Conference 2026! Within only 18 days from publishing this blog, the Matrix community and ecosystem meets in Malmö, Sweden for 3 days of conference, followed by another day of hacking and collaborating in Copenhagen, Denmark!
While the Conference is primarily an in-person event #LocalFirst, it will be accompanied with live streams from all 3 conference stages during the 2 main conference days, powered once more by the amazing c3voc! And of course we could not miss our chat rooms to virtually represent the physical stages on Matrix itself, a "General" chat for the hallway track, hackathon, and more. You can now find all of these grouped in this year's Conference space #conference-2026:matrix.org, and also on the Conference website soon. Naturally, the chats are just as practical if you will be attending in person, as we will be posting news and you can get in touch with other attendees, both remote and present! Note that rooms are read-only for now and will become available for chatting closer to the start of the Conference. Speakers and volunteers will also find that the respective private rooms are inside the same space.
Speaking of volunteers: Here's your chance to join the volunteer chat, get a limited Sweden-colored volunteer hoodie, and most importantly help make MatrixConf happen!
We have made some (hopefully final) adjustments so the shifts in our volunteering system match our schedule more precisely, and also added a couple more shifts! If you're interested in participating in one of our workshops, this should be particularly interesting to you!
Finally, our ticket reserves are starting to dwindle, so if you are planning to attend in person, get your ticket!
Until next week with more news,
Your Events WG
🔗Dept of Spec 📜
Andrew Morgan (anoa) {he/him} announces
Here's your weekly spec update! The heart of Matrix is the specification - and this is modified by Matrix Spec Change (MSC) proposals. Learn more about how the process works at https://spec.matrix.org/proposals.
🔗MSC Status
New MSCs:
MSC4553: Forwarded messages
MSC4551: Sliding Sync Extensions: Receipts
MSC4550: Explicit links
MSCs in Final Comment Period:
No MSCs are in FCP.
Accepted MSCs:
MSC4452: Preview URL capabilities API
MSC4095: Bundled URL previews
Closed MSCs:
MSC3960: Sliding Sync Extension: Receipts
Superseded by MSC4551: Sliding Sync Extensions: Receipts
🔗Spec Updates
The SCT is continuing to focus on Matrix 2.0 MSCs in the hope that they may be ready for the Matrix conference this month. Critically, shortcuts are not being taken to get these MSCs over the line. The team is simply focusing their efforts on these MSCs instead of others for the time being.
🔗Matrix 2.0 Checklist
The following is the current state of the various MSCs:
🟢 MSC4140: Cancellable delayed events - Merged (unchanged).
🟢 Clarifications for MSC4140: Cancellable delayed events - Merged on 29 September.
🟡 MSC4354: Sticky Events - 2 / 8 required approvals (unchanged). Two recorded concerns remain: MSC link formatting and an outstanding rate-limiting comment.
🔴 MSC4480 Sliding Sync Extension: Sticky Events - Still pre-FCP; no formal FCP proposal or approval checklist yet. Implementation links have been supplied.
⚪ MSC3960: Sliding Sync Extension: Receipts - Closed without merging on 30 September, superseded by MSC4551.
🟡 MSC4551: Sliding Sync Extensions: Receipts - Proposed for FCP; 2 / 8 required approvals** (+2). A couple clarifications are needed, but no recorded concerns.
🟡 MSC4538: Sliding Sync Extensions: To-Device messages - Proposed for FCP; 3 / 8 required approvals, with no concerns recorded on the FCP checklist.
🟡 MSC4543: Sliding Sync Extensions: End-to-end encryption - Proposed for FCP; 2 / 8 required approvals, with no concerns recorded on the FCP checklist.
🟡 MSC4143: MatrixRTC – Real-time communication over Matrix - 6 / 8 required approvals (unchanged). Outstanding concerns cover the Sticky Events dependency and an implementation/proposal mismatch.
🟡 MSC4195: LiveKit transport for MatrixRTC - 4 / 8 required approvals (+1). The MatrixRTC dependency remains the only recorded concern; concurrent FCP is permitted.
🟡 MSC4196: Voice and video calling application for MatrixRTC - 2 / 8 required approvals (+1). Dependent on MSC4143.
The team and authors certainly have their work cut out for them, but things are looking cautiously positive!
🔗Dept of Servers 🏢
🔗Zendrite (website)
pat-s announces
Zendrite is a Matrix homeserver written in Go, forked from Dendrite earlier this year.
v3.4.0 is out, and its headline feature is active-passive high availability.
High availability (opt-in).
Run several Zendrite candidates against shared PostgreSQL, NATS JetStream and S3-compatible media storage; a Kubernetes Lease elects one to serve while the others wait as standbys.
A durable ownership generation fences every boundary (database, broker, media, outbound federation and request admission), so a paused or partitioned old leader cannot write after its successor takes over.
Rolling upgrades between compatible builds hand over without failed client requests (search briefly answers 503 while the new leader rebuilds its index), and an upgrade contract refuses builds that would need an offline migration.
HA changes are qualified in CI by a fault-injection harness that runs against real PostgreSQL, a three-node JetStream cluster, a kube-apiserver and a federating peer.
It kills, freezes and partitions leaders, fails over PostgreSQL, loses brokers, and checks that no acknowledged write, to-device message or receipt goes missing.
Federation and sync.
MSC4311 and knocking over federation.
Bundled aggregations for threads, edits and references on every endpoint that should carry them.
Per-thread unread counts (MSC3773).
Large rooms no longer stall sync: a state update in a room of 50,000 members now takes seconds instead of minutes.
Reliability.
Dozens of fixes found while qualifying HA also benefit single-server setups:
Federation transactions are retried instead of silently dropping receipts or to-device messages when the broker cannot take them.
A silent NATS broker is detected in about 30 seconds.
Consumers retry transient failures instead of losing work.
New metrics make a stalled consumer or a struggling broker visible.
Upgrade notes, the full changelog and the HA guide are in the docs and the release.
Chat with us in #dendrite:matrix.org.
🔗Synapse (website)
Synapse is a Matrix homeserver implementation developed by Element.
madlittlemods (Eric Eastwood) reports
This week we have a new release, Synapse 1.162.0. To highlight:
The default room version is now room version 12 (#20130, thanks to @jason-famedly from Famedly).
As a reminder, we've been driving forward Matrix spec compliance by filling in a bunch of tiny gaps in behavior between Synapse and the Matrix spec. This release includes even more fixes (#20115, #20154, #20181, #20200). And we're at the point that we will be advertising support for more Matrix spec versions in the next release ✨.
Also as part of the Matrix spec compliance march, we fixed the flawed MSC4311 implementation originally introduced in Synapse v1.136.0 (#19723). This is a fix around stripped state for invites/knocks: client-side APIs like /sync use stripped state events and we now send full PDUs on the federation-side. This also fixes the incompatibility that Continuwuity v26.6.1+ folks have been experiencing since the stripped state format is strictly validated there. To give the ecosystem time to adapt, Synapse will only apply strict validation to incoming invites and knocks after 2027-06-01.
/sync no longer drops state events in MSC4222's state_after when the since token falls inside a persisted batch of events (#20171).
/relations got a speed boost in large rooms (10-100x purportedly) which means opening the thread panel should be much quicker (#20182).
We got some help with one of the pesky Complement test flakes to ensure the /room_summary endpoint returns fresh and accurate join_rules (#20205, thanks to @jason-famedly from Famedly)
Thank you to all our contributors for helping to make Synapse the best it can be. As always, feel free to stop by #synapse:matrix.org to join in on the discussion and if you encounter a bug make sure to report it.
🔗Dept of Clients 📱
🔗Cinny (website)
Lozenge reports
Cinny 4.12.7 is now available with a small but important set of fixes and maintenance updates. This release updates the sanitize-html and react-router-dom dependency (security fix), fixes "%" sign wraps below the input issue, and correct emoji autocompletion overwriting preceding element.
Try Cinny at https://app.cinny.in
Join us at #cinny-space2:matrix.org
🔗Element X Android (website)
Android Matrix messenger application using the Matrix Rust SDK and Jetpack Compose.
Benoit announces
Last week
Settings are being reorganised: account settings and application settings are now split, the user status moved, and the multi-account section was updated. Still behind a feature flag.
Removing a message now asks for confirmation, and you can give an optional reason.
Fixed a blank screen at launch when the homeserver expires the sliding sync session, and fixed a leak of threaded timelines.
This week we shipped versions 26.09.3 and 26.09.4, with updated SDK bindings and a fix for rustls failing certificate revocation checks on app start. Native Element Call integration is moving forward: calls can now be drawn directly in the app, follow you into picture-in-picture, and be answered through a dedicated call entry point. Multi-account support keeps improving, with incoming verification requests now shown for all signed-in accounts, along with which account is being verified. Each account's avatar thumbnail is now stored in its session database and used as a fallback when showing your other accounts. The sign out and signed-out screens have been redesigned, now displaying account info and scrolling properly on small screens. Automatic back pagination and unread indicators are now enabled by default, and you can choose to display only unread notifications. Search history got buttons to remove a single item or clear the whole history. As usual, plenty of bug fixes and dependency upgrades landed too, including a crash fix in voice message playback.
🔗Element Classic Android
Benoit says
Element Classic Android 1.6.66 is out, with an updated banner about excluding insecure devices, following the banner encouraging migration to Element X in 1.6.64.
🔗Rabble (website)
rig announces
I've been building Rabble, a new desktop Matrix client aimed particularly at voice-heavy communities.
It combines Matrix messaging with push-to-talk and voice channels, with the goal of covering some of the use cases that keep communities on Discord while remaining a Matrix client.
Rabble is built as a native desktop application rather than on web technologies, which keeps it lightweight and gives it direct access to platform APIs for things like global shortcuts and other OS integration.
The first public builds are available for Windows, macOS, and Linux. It's still early, and feedback is very welcome.
#Rabble community
🔗Nexus (website)
Matrix client made with Flutter and a Gomuks backend.
QuadRadical (Ping) announces
Hello TWIM! Nexus was on TWIM last week, but a lot has changed since then, so here's the rundown:
Notable speed improvements: By rewriting our timeline widget and state merge code, performance has been greatly improved. Expect faster room loads, and less hitching.
Support for jumping to out-of-timeline events: This has been an annoyance for a long time, but it's finally fixed! The timeline rewrite made this easier, and the whole feature landed in a diff of only a few hundred lines.
Flatpak repo: Nexus is now available through a Flatpak repo, so updates can happen through flatpak update or your software center of choice. More information can be found at https://nexus.federated.nexus/#flatpak.
Room summaries: Before joining a room, you now see a summary of information about that room:
Clickable room links: With the change above, it was easy to implement clickable room links. Clicking a room link focuses that room if you are joined, or opens a join dialog if you are not.
Event links: Event links work the same way, but also scroll to the linked event.
And, as always, a whole lot of bug fixes 🙂
🔗Initial release progress:
Last TWIM, I told you we were getting close to being ready to release 1.0.0. Well, I have more news: there are only three issues left for the 1.0.0 milestone!
When these are done, I'll release an alpha for 1.0.0 to find any bugs, then hopefully we can have 1.0.0 stable released very soon after. You can take a look at the remaining issues for 1.0.0 here: https://nexus.federated.nexus/milestone/1
🔗Get involved
If you want to help with development or simply keep up with new features, join our Matrix room at #nexus:federated.nexus, or check out the Git repo at https://nexus.federated.nexus.
🔗FluffyChat (website)
The cutest instant messenger in the [matrix].
Krille - Christian K. reports
FluffyChat 2.10.0 will be released this weekend, including finally support for MatrixRTC calls via LiveKit (compatible with Element calls) and a lot of bugfixes and improvements.
You can see all changes here: https://github.com/krille-chan/fluffychat/blob/main/CHANGELOG.md#v2100
With this release comes the first official build for Windows: https://github.com/krille-chan/fluffychat/releases Please be aware that these builds are mostly untested and very experimental. We are happy for any feedback. Native macOS builds are also coming soon.
🔗Matrix Federation Stats 📊
Aine [etke.cc] reports
collected by MatrixRooms.info - an MRS instance by etke.cc
As of today, 20397 Matrix federateable servers have been discovered by matrixrooms.info, 4129 (20.2%) of them are publishing their rooms directory over federation.
The published directories contain 19712 rooms.
The most popular server software among the online servers is:
synapse: 15772 (77.3%)
continuwuity: 1866 (9.1%)
conduit: 545 (2.7%)
dendrite: 285 (1.4%)
Stats timeline is available on 📊 MatrixRooms.info/stats
🧩 Integrations with apps and servers | 💜 Support the project | 👉 How to add your server | 🙅 How to remove your server
🔗Dept of Ping 🏓
Here we reveal, rank, and applaud the homeservers with the lowest ping, as measured by pingbot, a maubot that you can host on your own server.
Join #ping:maunium.net to experience the fun live, and to find out how to add YOUR server to the game.
RankHostnameMedian MS
1vrkknn.net172
2kanp.ai197
3sspaeth.de198
4raccoon.cafe215
5vibb.me272
6szp.lol338.5
7awesomesheep48.ca346
84d2.org376.5
9victorewik.es435.5
10m.starshard.space624
🔗That's all I know
See you next week, and be sure to stop by #twim:matrix.org with your updates!
To learn more about how to prepare an entry for TWIM check out the TWIM guide.

https://matrix.org/blog/2026/10/02/this-week-in-matrix-2026-10-02/

Making sovereignty standard for European governments Element is ...

2026-10-15T04:57:57Z

Making sovereignty standard for European governments

Element is thrilled to be sponsoring the public sector track at The Matrix Conference again, running from October 20th to 23rd, 2026, in Malmö, Sweden.
The flagship Matrix event brings leading Matrix-based deployments and initiatives in the public sector together with the community at large and a mix of vendors from the ecosystem. It has become the key meeting point for leaders that want to ensure digitally sovereign communications within the public sector and beyond.
Genuine digitally sovereign communications need an interoperable open standard, ensuring end-user organisations have the power of choice and that vendors are competing on a level playing field.
It’s no wonder, therefore, that the public sector track at The Matrix Conference has such an impressive line up of presentations:
The European Commission will be introducing a new Digital Workplace service powered by Element and Matrix.
Sweden's eSam initiative (eSamverkansprogrammet) will showcase its work on inter-agency federation across Sweden’s public-sector organisations.
The use of Element at United Nations International Computing Centre (UNICC) for sensitive inter-agency communications, crisis management, and incident response operations
The latest on NATO ACT’s NI2ce Messenger, a messenger solution to provide a safer and more private alternative to the widespread use of WhatsApp and Signal
Updates from government deployments of Matrix in Germany, France and Luxembourg
Forrester joins the conversation
Alongside these major public institutions, Forrester analyst Dario Maisto will present his latest research on digital sovereignty. His session will look at the balance between sovereignty, privacy, and security, before examining the gap between organisations' sovereignty ambitions and where they actually stand today. He'll walk through the practical challenges governments face in reducing dependency, and the role open standards can play in supporting sovereign communications.
Dario recently authored a report introducing a Minimum Viable Sovereignty (MVS) decision framework, alongside looking at where open source helps organisations achieve sovereignty, and where its limits lie - across project longevity, maintainer dependency, and support.
It's a framework that reflects our own approach; enabling governments to make deliberate choices about ownership, deployment, data control, and interoperability. Open standards and open federation are central to that as they let organisations build sovereign communications without being reliant on a single vendor.
We hope to see you there
Real deployments, real challenges, and where sovereign communications is heading - straight from practitioners across the public sector. Join us at The Matrix Conference, and be part of the conversation on the future of sovereign digital communications.
Buy your ticket today and see you in Sweden!

https://element.io/blog/making-sovereignty-standard-for-european-governments/

Element partners with Arawa to bring sovereign, open-standard ...

2026-10-15T04:44:59Z

Element partners with Arawa to bring sovereign, open-standard federated communications to French local authorities

We’re delighted to announce that we’re now working with Arawa to support France's “fédération Matrix des collectivités.”
Arawa has just started working with Adullact, the non-profit coordinating the usage of open source software within local authorities, and Déclic, the federation of OPSN (Public Digital Service Operators), to deliver and support its “Matrix pour les collectivités” project.
The initiative aims to create a “Tchap for the territories” so that French local authorities can collaborate with each other more effectively via interoperable, sovereign and secure communications. The result will be a closed (as in, private) Matrix-based Federation for Local Governments. It also intends to ultimately federate with Tchap to facilitate secure exchanges with government services.
The Matrix-based ecosystem allows local authorities and OPSNs (Public Digital Service Operators) to operate their own servers while communicating within a dedicated closed network. Each organisation retains full sovereignty by relying on its own teams, an OPSN, or a service provider. This federated architecture offers an alternative to centralised, non-sovereign tools and helps strengthen local authorities’ digital sovereignty.
Local authorities can find out more by getting in touch with Arawa.
Element and Arawa
Arawa will use Element Server Suite Pro (ESS Pro) to power the fédération Matrix des collectivités. Under the partnership, Arawa will deploy Element inside its customers' own environments. French authorities will be able to keep their communications data on their own infrastructure, and under their own control, instead of depending on a cloud platform operated in another jurisdiction.
As Element is built on Matrix, the decentralised open standard for real time communications, each deployment is able to federate with other Matrix-based instances - including DINUM’s Tchap and LaSuite - if desired by mutual parties. As a result authorities can communicate securely across organisational boundaries without any form of vendor lock-in, ensuring genuine digital sovereignty for all.
We are delighted to be working with Arawa, a company with a genuine commitment to open source software and to the ecosystem around it. Local authorities have been asking for a messaging tool they actually control, and that means more than self-hosting: because Matrix is an open standard, they can choose their supplier, change their mind later, and still talk to everyone else. We hope this partnership contributes to the decentralisation, interoperability and security of communications in France.
Amandine Le Pape, Chief Operating Officer and co-founder of Element.
Element has generated a great deal of interest among our customers and prospects. Genuine control, the encryption features, the ability to federate with other instances and our associated support offerings all point to one thing: Element is the best choice for organisations looking for a modern, secure, free and open instant messaging tool.
Jean-Philippe Porcherot, President of Arawa
Matrix adoption across Europe’s public sector
Arawa joins an ecosystem of more than 70 Matrix-based vendors and providers, many of which use Element Server Suite Pro as the basis for their own offering.
European governments and public sector organisations continue to adopt Matrix-based communications in order to ensure sovereign communications, through the use of an interoperable open standard that is supported by a competitive ecosystem. Without the ability to easily switch between vendors, an end-user organisation remains beholden to a specific vendor.

https://element.io/blog/element-partners-with-arawa-to-bring-sovereign-open-standard-federated-communications-to-french-local-authorities/

Matrix at DWebCamp 2026 One of the highlights of the early days ...

2026-10-15T03:53:50Z

Matrix at DWebCamp 2026

One of the highlights of the early days of Matrix was attending the inaugural Decentralised Web Summit back in July 2016 at the Internet Archive. This was an amazing opportunity to meet and collaborate with a huge range of decentralisation projects trying to "lock the web open" and fight back against the perils of centralisation: ranging from the original gangsters (the Web, WAIS, Xanadu, and the Internet itself) through to the newer generation of projects.
Fast forward 10 years, and we were very happy to be able to attend the July 2026 incarnation too! This time it was held outside Berlin at the amazing Alte Hölle collective; what better place to fight surveillance capitalism from than a former Stasi holiday camp. Happily many of the faces and projects from earlier DWebSummits and DWebCamps were present and it was fantastic to sync with folks from ATProto, Spritely, Iroh, P2Panda, Willow and others.
Communication for the camp ran primarily on Matrix, and we were very grateful to end up with Matrix featuring in 4 different sessions: A dedicated talk on the current state of Matrix and all the new P2P Matrix development; a fireside chat on 12(!) years of Matrix and what comes next; a panel looking at how decentralisation has evolved since the 2016 summit and where it might go next; and finally a panel on the state of P2P in general.
The reason for talking about it now is that all the videos have now been published - so, if you missed out on attending at the time, now is the opportunity to sit back, relax, return to the beginning of summer and catch up on what happened at DWebCamp. For your convenience and viewing pleasure, here are the main sessions which featured Matrix:
🔗Videos
🔗P2P Matrix: A New Hope
🔗Twelve Years of Matrix: What Worked, What Didn't, and the Road to a Peer-to-Peer Future
🔗The Future of P2P
🔗A Decade of Decentralization: Looking Back, Leaning Forward

https://matrix.org/blog/2026/10/05/dwebcamp-2026/

Putting it online is the easy bit TL;DR Kubernetes and Helm give ...

2026-10-15T03:39:35Z

Putting it online is the easy bit

TL;DR
Kubernetes and Helm give you a standard way to package and deploy software, but the value lives in all the unglamorous decisions that shaped the chart.
For your deployments, you want a pre-assembled Lego set that you can customise with more (or less) bricks, not Lego pieces to assemble yourself. The more moving parts, the more testing and field experience you need.
ESS is a typical example of this, packaging a full Matrix stack, and running more than 10K tests to cover as many real-world situations as possible.
When deploying a service on your infrastructure, it can be tempting to just grab open source containers and roll them out with simple tools. Docker compose or ansible playbooks can do a fantastic job at rolling out a few containers in no time. But putting simple services online is the easy bit. The more containers in your stack, the more difficult it becomes to deploy them consistently, and the more chances for it to break.
A solid deployment is forgiving, battle tested, and has professional support to back it. At Element, we’ve based our ESS Pro Matrix stack on Kubernetes, because we believe it’s the most efficient way to address infrastructure teams’ challenges. Kubernetes itself does half of the work, and our helm chart does the other half.
Kubernetes doesn’t just solve scalability problems
This section is a Kubernetes primer in a few paragraphs for people unfamiliar with it. If you are comfortable with it, you can skip to the next section.
Kubernetes is a platform in itself that lets infrastructure teams deploy container-based services, and that is often seen as “the platform for deployments that scale”. But before even considering auto-scaling, one key selling point of Kubernetes is its declarative nature. You describe what building blocks you want to deploy on your cluster in yaml files called manifests, and Kubernetes figures out how to do it.
A manifest can describe what building blocks you want to deploy in your cluster: a specific container, a volume (storage space) to persist files, a configuration file that other building blocks can use, and many more. For example, a manifest that deploys a Pod containing a nginx container version 1.31.6 looks like this. This is a simple example file that would not be used as is in production.
apiVersion: v1
kind: Pod
metadata:
name: nginx
spec:
containers:
- name: nginx
image: nginx:1.31.6
ports:
- containerPort: 80
That declarative nature means that Kubernetes deployments can be self-healing (to an extent), or at the very least much more forgiving when doing upgrades. If you write a manifest asking for two containers, Kubernetes will deploy the two and ensure that if one crashes, it’s replaced. If you want to update your container to a new version, Kubernetes will:
Pull the new container image
Attempt to start the new container
Check that it has started and is healthy
Remove the old container.
If the upgrade goes wrong, keep the old version running instead.
But deploying the building blocks and assembling them manually is tedious and error-prone. Without anything to help, deploying and wiring the building blocks becomes the responsibility of the infrastructure team who maintain services on a cluster.
Fortunately, infrastructure teams rarely have to deploy building blocks like these manually. Instead, they can deploy pre-assembled Lego sets: helm charts.
Charts are products
A helm chart is a pre-assembled set of Kubernetes building blocks to roll out a functional deployment. Instead of deploying each building block and wiring them together manually, infrastructure teams can use a helm chart that will do it for them.
A simple helm chart is primarily made of two things
A configuration file, better known as a values file, that infrastructure teams can edit to make a deployment that suits their exact needs. It contains safe defaults that the teams can override.
A list of manifest (building blocks) templates to create a consistent deployment. The templates contain placeholders that will be filled by the values from the values file.
All the wiring between the building blocks has already been done by the vendor who wrote that list, so they fall neatly into place once deployed, even after the infrastructure teams customise the values file.
A simple values file can look like this:
serverName: example.com
database:
postgres: enabled
host: db.int.example.com
port: 5432
The manifest templates in the chart will reuse some of those values (e.g. the content of serverName) to deploy and assemble building blocks for a real-world deployment.
Vendor-owned charts shift part of the deployment burden from the infrastructure team to the vendor. Vendors know how their software is meant to be deployed. Instead of just shipping software, they can ship a comprehensive package, that infrastructure teams can configure.
A vendor-owned chart allows easier support by the vendor themselves. Since the deployment is done as intended by the vendor, it’s easier for them to rule out some common deployment pitfalls already covered by the chart and focus on bugs in their products.
A good chart also takes trial and error
While it sounds easy on paper to write a good chart, there are quite a few challenges. The more components in your stack, the more moving parts you have to wire together, the more opportunities there are for things to break.
It’s not very difficult to write tests for a default set of components. But even here, it is possible to do testing at various depths: checking that the charts still make sense when overriding the default values; checking statically that the helm chart doesn’t contain syntax errors and will deploy components in the right order; doing proper integration testing by actually deploying the chart on a test environment, etc.
Writing good charts and good tests requires experience. As a vendor, you need to have a good understanding of how infrastructure teams work and what tools they usually work with, so you can test for how you think they will use the chart.
But even then, some users will use different components, in ways you hadn’t anticipated. The sturdiest charts necessarily have field experience.
ESS is “just” a Matrix chart, and more
Element’s own chart, ESS, is just a helm chart in theory. But when you look closer it comes with a lot more.
We test ESS extensively
On each new release, we do 10,700 tests mutating values on our ESS Pro solution. Put differently: for each possible parameter in the values file, we change it to any value the user could use in a real-world deployment, and we make sure that the chart is still consistent and sensible.
We also run 300 tests for what we call static choreography analysis. We test the order in which building blocks are going to be deployed so that the final deployment is built on a solid foundation once those blocks are assembled together. These tests allow us to detect statically errors that would happen at runtime.
To make the whole stack really robust, we also run 34 integration tests combining various components of our stack (with or without Matrix Authentication Service, with or without Advanced IAM, testing tenants mode, etc), and making sure that the various components respond as expected. In other words: whether you use the full stack or only some parts of it, we’ve got you covered.
We work with real-world deployments
We have worked with and supported 100+ organisations to shape ESS Pro, with 4M+ users in total. Each support request makes our chart sturdier. Each bug found is fixed for everyone.
Because we are supporting large-scale deployments in the public and private sectors, we know the kind of problems you can hit at scale, and it’s reflected not just in our charts but also in the Pro components that come with our paid offering. If we can support NATO, the United Nations International Computing Centre and the Swedish Social Insurance Agency (Försäkringskassan), we can support you.
We are here to support
Despite our best efforts to offer a fully integrated suite of high-quality components, you might still bump into issues. As the maintainers of nearly all the components of ESS, we know how they should be deployed and how they work with one another. Using ESS for Matrix deployments is the fastest way to get sturdy deployments with Level 3 support. We also offer Long Term Support (LTS) versions in our Pro offering, and get them through the same amount of tests.
Give it a go
If you haven’t already, you can give ESS Community a go for your proof of concepts, and upgrade to ESS Pro smoothly when you need Level 3 support, LTS, Advanced IAM features, endpoint management integration, and much more.

https://element.io/blog/putting-it-online-is-the-easy-bit/

This Week in Matrix 2026-10-09 🔗Matrix Live S13E12 - ...

2026-10-15T03:29:09Z

This Week in Matrix 2026-10-09

🔗Matrix Live S13E12 - Foundation & Event updates
🔗Dept of The Matrix Conference 🏛️
Andy says
The Matrix community assembles in Malmö, Sweden in a little over 10 days' time, for our conference, followed by another day of hacking and collaborating in Copenhagen, Denmark! Are you ready to join us?
As mentioned in Matrix Live this week, the event will include a demonstration of cross-border federation in the public sector. Don't miss it!
Don't forget to bring your project stickers with you, for the event sticker exchange.
This really is a must-attend event, get your ticket now here.
🔗Dept of Events and Talks 🗣️
🔗Stammtische (website)
HarHarLinks reports
A Stammtisch ("regular's table") is a German meetup format where those with a shared interest meet regularly for discussion, exchange, and socialising.
Find more community organised events at matrix-community.events!
12 October (2nd Monday of every month) 20:00 CEST: #matrix-stammtisch:ccc.ac at CCCAC
Are you running a Matrix meetup? Add it to the list!
🔗Dept of Spec 📜
Andrew Morgan (anoa) {he/him} announces
Here's your weekly spec update! The heart of Matrix is the specification - and this is modified by Matrix Spec Change (MSC) proposals. Learn more about how the process works at https://spec.matrix.org/proposals.
🔗MSC Status
New MSCs:
MSC4558: Thread names
MSC4556: Notary request limits
MSCs in Final Comment Period:
No MSCs are in FCP.
Accepted MSCs:
No MSCs were accepted this week.
Closed MSCs:
No MSCs were closed/rejected this week.
🔗Spec Updates
Despite the lack of MSCs entering FCP/being accepted/etc. there's been quite a lot of activity on the Matrix 2.0 spec front!
The SCT is hoping to get the Matrix 2.0 MSCs landed before the Matrix conference. Follow along below for how that's going:
🟢 MSC4140: Cancellable delayed events — Merged.
🟢 Clarifications for MSC4140: Cancellable delayed events — Merged on 29 September.
🟡 MSC4354: Sticky Events — 2 / 8 approvals (unchanged). Discussion and implementation work progressing; two formal concerns resolved, three still outstanding.
🔴 MSC4480: Sliding Sync Extension: Sticky Events — SCT review now underway, rather than awaiting initial review. Token/pagination and alignment with other Sliding Sync extensions remain under discussion; not yet proposed for FCP.
🟡 MSC4551: Sliding Sync Extensions: Receipts — Proposed for FCP, 6 / 8 approvals, no formal concerns recorded. Replaces MSC3960, which was closed as superseded on 30 September.
🟡 MSC4538: Sliding Sync Extensions: To-Device messages — Proposed for FCP, 6 / 8 approvals, no formal concerns recorded, ongoing discussions.
🟡 MSC4543: Sliding Sync Extensions: End-to-end encryption — Proposed for FCP, 5 / 8 approvals, no formal concerns recorded, ongoing discussions.
🟡 MSC4548: Sliding Sync Extensions: Account data — Added to this pulse check: proposed for FCP, 6 / 8 approvals, no formal concerns recorded, ongoing discussions.
🟡 MSC4143: MatrixRTC – Real-time communication over Matrix — 6 / 8 approvals (unchanged). Implementation-mismatch concern resolved; Sticky Events is the sole remaining formal concern.
🟡 MSC4195: LiveKit transport for MatrixRTC — 6 / 8 approvals, up from 3. Only the MatrixRTC dependency concern remains; concurrent FCP is permitted.
🟡 MSC4196: Voice and video calling application for MatrixRTC — 6 / 8 approvals, up from 1. Only the MatrixRTC dependency concern remains; concurrent FCP is permitted.
🔗Dept of Clients 📱
🔗Tesseract (website)
Marco announces
Hello, folks! It's been some time since the last update, so here it is:
Tesseract is now in beta! The last missing features (invite dialog and room moderation: kick/ban/unban) were added in 0.9.0.
This doesn't mean new features aren't coming; only that it should be possible to use it as your main daily desktop client.
There have been 7 releases since the last TWIM post and there are too many changes to list here, but I'd like to mention call rooms, directory browser, user status, and simpler encryption setup and recovery.
About encryption setup: in the ongoing effort to make this easier and more user-friendly, a new silent recovery setup was added (only for accounts without recovery set up). Tesseract will set the encryption and recovery silently and save the recovery key in the OS secure storage (only if available), and then periodically nag the user to make sure it is saved in a better/safer place. This way a new user will have a fully functional client with all the end-to-end encryption capabilities set up, right after login. (This can be disabled with a build flag, in case a build without this functionality is needed). Hopefully this will make onboarding new users much simpler.
On a different note, Tesseract is now available in the Microsoft Store, which is something I never imagined I would say out loud, but here we are 🤷🏻 (easier installs, with proper signed binaries, for free; how could I resist?)
For the curious, here are all the recent changelogs. Feel free to drop by the official room!
🔗Element X Android (website)
Android Matrix messenger application using the Matrix Rust SDK and Jetpack Compose.
Jorge says
Hello everyone, this week on the Element X Android team we've been focused on:
Improving the multi-account feature (still behind a feature flag). There is a better UX for selecting which account you're using and more places where this is useful, like when sharing something coming from outside the app.
Global search: we're now able to automatically back paginate and add past history to the search index so you can search for older messages in your encrypted rooms. The feature should be available shortly, too!
Multi-selection of messages in rooms: you'll be able to select and forward several messages into other rooms, instead of having to do it one by one. There are some limits set to prevent spamming. The feature is still a work in progress, so it's behind a feature flag.
Element call native: the VOIP team has been working really hard to deliver a better experience than webview integration, which is known to have limitations and audio bugs we can't fix because the webview environment limits us, so they built a native experience instead. This is behind a feature flag for now, but if you can test it, we'd love to know your feedback.
Unread counts in the room list: we're displaying unread notification counts in rooms now and we've improved their UI too. With backpagination, they should be way more accurate now, although we know there are still some corner cases we need to fix. There is also the option now in the app to display only unread notifications in the room list, instead of displaying also an indicator for unread messages in rooms you don't really care about.
Improving the send queue: we know there are some issue related to the send queue after we changed its logic to try to enforce the order of sent events and are working on fixing those.
We're now automatically dismissing notifications for rooms we know are fully read from other devices.
And many other bug fixes and improvements.
🔗Dept of VoIP 🤙
🔗LiveKit JWT service (website)
Bridging Matrix and LiveKit for Matrix RTC realtime sessions.
Johannes Marbach says
lk-jwt-service v0.8.0 was released yesterday. This release updates the Client-Server endpoints for token requests and delayed leave delegation to the latest state of MSC4195. Some of these changes are breaking, unfortunately. We've considered this acceptable because we're also still wrapping up the client-side implementation for actually using the Client-Server endpoints in matrix-js-sdk and element-call. The legacy, non-client-server endpoints still exist, however, and have received a security fix. Therefore, we recommend updating in either case.
🔗Dept of SDKs and Frameworks 🧰
🔗djangomatrixappservice
Fabian says
Do you want to manage a larger amount of bots (lets say you want to write another bridge)? How about managing them through a web interface? Or just send notifications from your webservice to your users? How about implementing all this in a powerful, python-based web framework?
Well, here is a solution to that! I have completely rewritten pretty much all of the code in the central component of a larger project that i started two and a half years ago during my funding from PrototypeFund.
I call this central component djangomatrixappservice, because it is a Django app that can interact with the matrix application service api. It comes bundled with a matrix-nio based client.
It supports multiple auth types:
Application service identity assertion
Rotating OIDC/MAS tokens
Legacy password login/long-lived tokens
Activity is triggered by…
your code
push notifications directly from the homeserver to your web service
application service transactions to your web service
There is no long-running sync-requests in the background, so this does scale to as many accounts as you like without requiring more energy.
Despite having found ways to unit test a lot of it, there are still important parts that are not covered by that yet, so currently it is very experimental.
I am posting this now, because I am confident that this approach is abstract enough to fulfill a lot of developer needs, but provides enough guidelines to become a common base for different projects. Since the initial migration for a django project is pretty important to get right, this is the perfect time to gather feedback for that.
Next steps include:
Add more documentation on how to get started
Increase the coverage of unit testing
Gather experience from more little projects
The code is hosted on codeberg: https://codeberg.org/alertrix/djangomatrixappservice
Feel free to reach out to me in the #twim-offtopic room or #djangomatrixappservice:alertrix.net
I would love to hear your feedback (how would you want to integrate it in a project) and I am looking forward to posting more about this in the future!
🔗Dept of Built on Matrix 🏗️
🔗OUDEA and bytEM
Tero says
OUDEA and the first public version of bytEM are now live.
As bytEM is built on Matrix / Synapse federation, I thought this might also be interesting for the wider Matrix community. We’ve now reached the point where the architecture, installer and first working implementations can all be explored publicly:
OUDEA – Open Unified Data Exchange Architecture: https://oudea.org
bytEM Installer: https://github.com/liberbyte/bytEM-installer
First public bytEM index / cities.app: https://bytem.de.cities.app/
Current example / demo indexes: https://www.liberbyte.com/indexes.html
The basic idea is to use Matrix federation not primarily for communication, but as the underlying infrastructure for a federated data exchange architecture — allowing independently operated data products to be discovered, referenced and exchanged across organisations.
We would really appreciate any further opportunity to give this air time within the Matrix community, whether at an upcoming Matrix Conference, conference session, community call, or another format you think would fit. Unfortunately my official application to present in Malmö was turned down.
I think it could be an interesting example of Matrix being used well beyond messaging, and we’d be very happy to present and demo what we have built, what we have learned, and where we are taking it next.
🔗Matrix Federation Stats 📊
Aine [etke.cc] says
collected by MatrixRooms.info - an MRS instance by etke.cc
As of today, 20512 Matrix federateable servers have been discovered by matrixrooms.info, 4122 (20.1%) of them are publishing their rooms directory over federation.
The published directories contain 19715 rooms.
The most popular server software among the online servers is:
synapse: 15804 (77.0%)
continuwuity: 1920 (9.4%)
conduit: 543 (2.6%)
dendrite: 284 (1.4%)
Stats timeline is available on 📊 MatrixRooms.info/stats
🧩 Integrations with apps and servers | 💜 Support the project | 👉 How to add your server | 🙅 How to remove your server
🔗Dept of Ping 🏓
Here we reveal, rank, and applaud the homeservers with the lowest ping, as measured by pingbot, a maubot that you can host on your own server.
Join #ping:maunium.net to experience the fun live, and to find out how to add YOUR server to the game.
RankHostnameMedian MS
1vrkknn.net167
2codestorm.net186
3raccoon.cafe192
4sspaeth.de235.5
5ellis.link251.5
6awesomesheep48.ca301
7qwertyad.one317.5
8victorewik.es353
9elisaado.com367.5
10koshchki123.com390.5
🔗That's all I know
See you next week, and be sure to stop by #twim:matrix.org with your updates!
To learn more about how to prepare an entry for TWIM check out the TWIM guide.

https://matrix.org/blog/2026/10/09/this-week-in-matrix-2026-10-09/

Smoother collaboration with integrations People do their best ...

2026-10-15T02:55:35Z

Smoother collaboration with integrations

People do their best work in a state of flow, when they can move from a conversation to a document to a task without breaking their train of thought. That puts the onus on productivity vendors to make their tools work together seamlessly.
Customers running sovereign stacks tell us exactly that. As one put it: "It isn't a problem that the apps are named different things, or that they're made by different vendors. The problem is if they aren't linked."
That's what our integration team is working on, so people can stay in flow across an entire sovereign workplace.
What's shipped already
Files, with Nextcloud
Sharing a file between your chat and Nextcloud used to be a chore. You’d have to download your files and upload them straight back into the chat. Now you can connect your Nextcloud account, browse your actual folders, and share a file into a room.
Nextcloud stays the only source of truth. Rather than dozens of copies flying around with various competing edits, there’s a single file in a single place. The permissions are set for this file, in Nextcloud, once and for all.
Link previews
When you paste a link to another platform such as Nextcloud, share a Jira ticket or a GitHub PR into most chat tools, you get a rich preview. But what about private documents that are only shared with a select few people? In such a case, the link preview would be of limited use: your messaging app doesn’t know that you actually have access to the file, so it can only create a generic preview for it.
Element’s integration team has developed Authenticated Previews. You can link your accounts to your Element, and it will use them to fetch more useful previews. With it, an internal document shows its real title to the people entitled to see it, and nothing to others.
The previews also work with the composer. You see what you're about to share before you send it, rather than being caught by surprise once it makes it to the timeline.
PDF and Markdown previews in the room
Being asked to comment on a forty-page annex used to mean leaving the conversation, downloading the file, reading it somewhere else and coming back with a thought you'd half-lost on the way. It also meant that the downloaded file would linger around forever on users’ machines.
Now the document opens beside the discussion. It never leaves the sovereign workspace suite. It’s gone from the users’ machine as soon as they close the preview.
Next up…
Project management, in the timeline
Work gets decided in conversation and recorded somewhere else, and the two drift apart within a day. We're bringing work items into the room; status and assignee visible right where the discussion is happening. We’ll start with OpenProject.
Richer timeline cards
Previews were the first step. Cards are the next one; more context, and actions you can take without leaving. Documents will open as a live editor, via Collabora, rendering from the customer's own Nextcloud. So the file being edited is the same file in the same folder. Request-and-approve flows will be handled in place rather than in an email thread three hours later.
Upcoming events
The last big piece of a working day that still lives entirely elsewhere. The goal isn't a second calendar, it's that a meeting scheduled is easy to join without switching tabs or hunting for links.
The right tools for you
Your day at a glance
We're researching a home view for Element; one view of what actually needs you today, be it unread conversations, your next meeting, the files and tasks that are waiting. For anyone running Element on its own, that's a better place to start the day than an empty room list. For organisations running a full sovereign stack, it becomes a single authenticated view across the whole workplace, assembled from the tools you already pay for, using your authentication system, which in - for instance - openDesk deployments means Univention's IAM.
It's deliberately not a launcher; much like what we’ve done so far, we want the other tools to be consistently integrated into your Element, so you don’t have to think about where the information lives.
An ‘extensions store’
Having tight integrations and a comprehensive dashboard is great. But not everyone uses the same tools, so users need to be able to find and add the integrations that matter to them.
We’re currently exploring a next generation extensions store to make it simple and easy for people to install what they need.
We’re team players
One of the common traps in our industry is the Not Invented Here syndrome. We don’t need to reinvent the wheel; all the tools in sovereign workplace suites do their job well. We're not replacing the tools we integrate with. Our partners behind them move faster in their own domains than we would, and the ecosystem is better for it.
Rather than reinventing the wheel, the engine, or the safety belt, we prefer assembling the components together so the user can make it to their destination without having to build the car themselves.
With Element tying digital workspace suites together, end users switch context less and focus on what matters more. Our integrations don’t just look good: they also make everyone more efficient.

https://element.io/blog/smoother-collaboration-with-integrations/

openDesk now runs Element Server Suite, direct from upstream ...

2026-10-15T02:40:56Z

openDesk now runs Element Server Suite, direct from upstream

We’re delighted to share that openDesk now deploys Element Server Suite (ESS) directly from Element. The Element frontend still reflects the openDesk product and branding, but now openDesk deploys Element Server Suite (ESS) directly from Element, the original manufacturer and product owner of the software. It brings hardened Kubernetes deployments, next-generation OIDC-based authentication and the complete ESS feature set to Germany’s sovereign office productivity suite.
We're joining ZenDiS on its openDesk stand (Stand 103 in Hall 27) at Smart Country Convention (SCCON) in Berlin, 13–15 October, so come and see us there!
Straight from the source
openDesk now deploys Element using our official ESS Helm chart, which brings three overarching benefits:
Hardened by default. The ESS Helm chart supports Kubernetes Pod hardening in line with the Restricted profile of the Kubernetes Pod Security Standards. Kubernetes describes this profile as "targeted at operators and developers of security-critical applications, as well as lower-trust users". That is exactly the environment openDesk is built for.
One product, one roadmap. Because openDesk runs the same ESS that Element ships to its own customers, new features and fixes reach openDesk providers faster, with the regular openDesk release cycle.
Next-generation authentication. With this move, openDesk providers can now migrate to the Matrix Authentication Service (MAS). MAS puts openDesk deployments on Matrix's next-generation authentication, defined in MSC3861 and built on the OpenID Connect (OIDC) open standard.
The result is a significant step up in security. Authentication follows a widely reviewed industry standard, and sign-in fits cleanly with the Univention Nubus based identity provider in openDesk.
A year of Element Web improvements
Since last year's Smart Country Convention a lot of updates have found their way into openDesk. The most visible change is the new room list, which is now the default for everyone. Rooms can be organised into custom sections, dragged between them, collapsed and reordered, with built-in sections for people and invites, unread-first sorting and a collapsible side panel that gets out of the way during calls.
Calling has matured alongside Element Call; calls show up as tiles in the timeline, incoming calls trigger regular desktop notifications with a decline button, picture-in-picture has been redesigned, and voice calls in direct messages run on Element Call too. Calling is built natively on Matrix and has end-to-end encryption, so calls get the same protection as messages.
Sharing is safer by default. New rooms and DMs no longer expose history to later joiners unless the admin chooses to, a badge in the room info panel shows who can read what, users are asked to confirm before inviting someone they have never spoken to, public rooms carry a warning that they are open beyond the organisation, and operators can block unwanted invites outright.
Link previews have been rebuilt and now work in end-to-end encrypted rooms without the server ever seeing the link, polls have been partly redesigned, and the whole interface has moved to Element's Compound design system with a long list of accessibility and contrast improvements.
For public-sector deployments in particular, Element Web also improved the module API, so vendor-specific customisations such as openDesk's branding, composer and upload behaviour are now clean plug-ins rather than forks.
What it means for openDesk
Element Server Suite Community enables openDesk to deliver an open source chat function, with enterprise-grade extensions available if required from Element Server Suite Pro. For openDesk providers, the change brings a hardened deployment, and a clear path to next-generation authentication. This goes along with a long list of features improving the value and user experience of chat inside openDesk. For the public servants who use openDesk every day, it means the full Element experience.
Above all, it shows what open standards and open source make possible. A sovereign workplace suite can run the original product, straight from its manufacturer, with nothing held back.

https://element.io/blog/opendesk-now-runs-element-server-suite-direct-from-upstream/