This Week in Matrix 2025-07-25

🔗Matrix Live S11E06 - Element X Accessibility, Encrypted State Events, Element Web Rich Text Pasting

🔗Dept of Status of Matrix 🌡️

Matthew reports

richvdh wrote an excellent writeup of the nightmare from the Element backend team have been working through in detecting and fixing slow-burning database corruption on matrix.org's postgres, which caused the room corruption outage over the last few weeks: https://matrix.org/blog/2025/07/postgres-corruption-postmortem/

Robin Riley (m.org) reports

Please join us in welcoming < polycule >, a geeky and efficient Matrix client, as the newest Ecosystem Member of the Foundation! ✨

Does your community use Matrix? Or do you maintain a community project that builds on Matrix? Join the Foundation as a member! This helps us demonstrate the breadth of the ecosystem, and all members are entitled to participate in our Governing Board elections.

🔗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:

• There were no new MSCs this week.

MSCs in Final Comment Period:

• No MSCs are in FCP.

Accepted MSCs:

• MSC4307: Validate that auth_events are in the correct room
• MSC4291: Room IDs as hashes of the create event
• MSC4289: Explicitly privilege room creators

Closed MSCs:

• MSC3902: Faster remote room joins over federation (overview)
  • Closed as it was more informational than an MSC.

🔗Spec Updates

A reminder to client/bots/bridge/tooling developers to implement and tests the changes introduced by room v12, which addresses an upcoming security disclosure. The date for the coordinated security release is Aug 11th, 2025.

See https://matrix.org/blog/2025/07/security-predisclosure/ for the details.

🔗Dept of Servers 🏢

🔗continuwuity (website)

Continuwuity is a community-driven Matrix homeserver in Rust

nex (she/it) [Continuwuity] reports

Huh, these are the hilltops?

The British summer might have been trying to take half of the continuwuity team, but thankfully, it didn't work. Unlike the continuwuity 0.5.0-rc.7 release, which is working, and in fact, working better than ever! Despite many setbacks since our last release, 0.5.0-rc.6, we've merged 35 pull requests, and closed 12 issues! Our #main:continuwuity.org also reached 300 members, and from our janky measurements, we discovered around 150 publicly federated deployments of Continuwuity. In addition, our GitHub mirror also recently surpassed 60 stars! We can't thank everyone enough for the support ❤️

Enough yap though, I know you're here for the juicy parts of the changelog, hand curated for you (since most people probably don't read the changelog anyway).

🔗You've got mail! 📥

Here's just a couple things from our full changelog:

• 🕵️ Policy Server support is now fully implemented! Now there's only tuna in your timeline, not spam 🐟️ (#857)
• 🚀 Upgrading a room will now update its space references, meaning you don't need to manually re-add rooms to spaces after upgrading. Upgrading a space now also keeps the references to all the rooms inside of it. (#907)
• 🤖 In an effort to make the server easier to run in an open-registration context, we added support for reCaptcha during the registration flow. OIDC/next-gen auth is still a work in progress, but hopefully this will offer some protection in the meantime! (#900)
• 🔍 The ability to entirely disable read receipts and typing indicators has been added, so even people on your own server won't know when you've read their DM but mentally tuned out of the conversation. (#898)
• 🚫 User suspension and suspend on register have both been added, allowing for greater trust and safety for shared & public servers. (#876, #887)

And just because why not, Jade threw in some changes that have resulted in sweeping performance improvements across the board!

Huge thanks to members of the community, such as Shuroii and transgwender for contributing fixes to the Nix flake, Oddlid for the read receipts & typing indicator changes, rooot for implementing additional federation timeout configuration granularity. It's awesome to see members of the community contributing, and we can't wait to see more in future!

🔗Gimme gimme! 🫴

Manners! Say please next time. You can download the latest release on our forge. Docker images are also available using forgejo.ellis.link/continuwuation/continuwuity:latest.

We don't currently mirror our releases anywhere yet, however, our source code is also available on GitHub, GitLab, and Codeberg. A few members of the community also mirror, some include releases, so if you have issues with any/all of the forges above, don't hesitate to join our community (below) and ask!

🔗What's next ✨

Gosh, it never stops does it! Well, I suppose you can have more, as a treat. BUT, the powers that be (my dopamine receptors) tell me that I have to ask that you give us a star on GitHub, as it helps us get promoted to people who might not have heard of us :)

You can also #main:continuwuity.org, and explore our #space:continuwuity.org, where we have a room for important announcements, a rich offtopic room, and our dev room where we discuss features and bugs. If you run your own continuwuity server, you should also #announcements:continuwuity.org, as important announcements are sent there (and may not be mirrored to the main room).

Anyway, as per usual, most things we're planning to tackle are on our issue tracker, or in a pull request.

🔗Got a penny to spare? 🪙

Although we will never charge to use continuwuity, hetzner keeps sending me this funny email saying I owe them money or something, so I figured it doesn't hurt to mention that we do accept donations. If you would like to, and are able to, feel free to send a few coins in the direction of myself or Jade!

*--

Anyway, that's all for this round. Hope to see you next time! Back to you in the editing room, TWIM editor. I left you a cookie :D

🍪

🔗Dept of Clients 📱

🔗Neochat (website)

A client for matrix, the decentralized communication protocol

Tobias Fella says

It's been... a while since the last update on NeoChat, so I won't go into all the details of what we've done since last time; instead, you'll just hear some of the highlights from the last weeks:

• We're preparing for the new room version. Current versions of NeoChat already work mostly fine, just a few small touch-ups were required.
• Joshua has made many small improvements to the user interface, like showing useful information when viewing a room invitation.
• Tobias has gone over our crash reports and fixed a few of the most common crashes.
• James made it possible to configure the behavior for when a room is marked as read.
• In the background, our work on using matrix-rust-sdk-crypto for end-to-end encryption is progressing.

🔗Dept of SDKs and Frameworks 🧰

🔗matrix-rust-sdk (website)

Your all-in-one toolkit for creating Matrix clients with Rust, from simple bots to full-featured apps, with bindings to Swift, Kotlin, WebAssembly, Go and more

poljar reports

As the summer comes along, things continue to improve. The team has welcomed two interns who are working on exciting new features in the SDK:

• Shrey is implementing full text search support for end-to-end encrypted rooms.
• Skye is tackling encrypted state events as proposed in MSC3414.

This week also brought a variety of improvements across the SDK:

• Room version 12 support has landed, thanks to Kévin Commaille (#5436, #5433, #5337)

• Exclude insecure devices:
  Work continues on strengthening encryption by allowing clients to ignore unverified devices
  (#5319)

• MSRV bumped to 1.88 to enable use of let-chains and other 2024 edition features
  (#5432)

• Leaving rooms now also leaves their predecessors, improving behavior in room upgrades
  (#5418) – thanks to our intern Shrey!

• Downloads are no longer cancelled after 30 seconds. You can now download big media files. (#5437)

• Threaded messaging APIs got a cleanup, making it easier to send messages in threads
  (#5427)

🔗Dept of Ops 🛠

🔗Matrix Connectivity-Tester Alerts

MTRNord (they/them) reports

Hi everyone, this week I bring you a few new things :)

Additionally, you can now find a staging deployment at https://stage.connectivity-tester.mtrnord.blog/ next to the stable deployment at https://connectivity-tester.mtrnord.blog/ If you find any errors, please report them via https://github.com/MTRNord/rust-federation-tester or https://github.com/MTRNord/matrix-connection-tester-ui/.

🔗Email Alerts

The service now supports automated email alerts. You can register for them, and it will check roughly every hour and email you if the check failed. This should allow you to have a better overview of your system and spot bugs when you make changes more easily.

🔗OpenAPI docs for the backend

The backend now automatically generates some OpenAPI docs at /api-docs of the API. This is an ongoing thing and not fully entirely correct yet, but it is hopefully only getting more complete.

Also note that as part of this work, the API surface changed quite a bit. In case you used the API, you will need to change things.

🔗Roadmap

As part of the future goals, I am currently in progress of splitting the UI into server-server and client-server API checks. I am hoping to get this done rather soonish so it is easier to read the check results.

🔗Dept of Events and Talks 🗣️

🔗Matrix Community Summit 2025 – Next Week in Berlin

Yan reports

From July 31 to August 3, the Matrix Community Summit returns to c-base Berlin. Expect BarCamp-style sessions, workshops, co-working, and plenty of opportunities to connect and collaborate. The event is fully community-organised and open to all.

Ticket sales are open now at low cost, with optional shirts and round-the-clock venue access: https://matrix-community.events/conferences/2025-summit.html

On Wednesday, July 30, the week begins with the first Cross-Messenger Communication Crossover Meetup – an informal gathering for anyone working on or interested in interoperability between messaging systems, Matrix and beyond.

More info and Matrix room links on the website.

🔗Matrix in the News 📰

Benedict says

Last week, all statutory health insurance companies in Germany (more than 90) released the TI-Messenger for patients and integrated it into their electronic patient records apps. This means that ca. 75 million patients can now theoretically talk to their healthcare providers. The TI-Messenger is based on Matrix in a closed federation. As far as I know, there are five manufacturers and they are using Open Source Software from the Matrix ecosystem. Four of them use Trixnity in the client and all use Synapse in the backend. Unfortunately, there are also many that don't give anything in return.

🔗Matrix Federation Stats

Aine says

collected by MatrixRooms.info - an MRS instance by etke.cc

As of today, 12839 Matrix federateable servers have been discovered by matrixrooms.info, 3701 (28.8%) of them are publishing their rooms directory over federation. The published directories contain 18119 rooms.

Stats timeline is available on MatrixRooms.info/stats

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.

🔗#ping:maunium.net

Join #ping:maunium.net to experience the fun live, and to find out how to add YOUR server to the game.

Rank	Hostname	Median MS
1	tuwunel.love	156.5
2	continuwuity.codestorm.net	169.5
3	bi-vibes.com	178.5
4	continuwuity.rocks	193
5	nerdhouse.io	247
6	beeper.com	301
7	emzee.me	354
8	rom4nik.pl	372
9	poweron.dk	384
10	feralfox.net	390

🔗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.