This Week in Matrix 2020-05-15

15.05.2020 00:00 β€” This Week in Matrix β€” Ben Parsons

Open Tech Will Save Us πŸŽ™

Second edition of OTWSU took place this week! Chance to watch it if you haven't already, or (pro-tip), watch it again.

  • Mike Hoye from Mozilla talks about "Verbs in the fediverse"
  • Eugen (@[email protected]) discusses "how we keep running at scale" as a Q&A
  • ... and a new VIP tour of Dendrite, the next-gen Matrix Homeserver, from our own neilalexander and Kegan!

Dept of Status of Matrix 🌑

Bundeswehr switching to Matrix

Oleg said:

German army reported in December 2019 their intentions for Matrix.

Now they decided to replace Stashcat with Matrix in this autumn.

Around 50'000 account are planned.

Riot will be used as a Matrix client. The E2EE by default and device Cross-Signing will be extensively used.

Full article (in German):

Mozilla are happy with their deployment!

About a year after this tweet, four months after deployment of our open source @matrixdotorg instance, community participation in the Mozilla project has increased from 4x to 10x across all the projects that previously relied on IRC.

— mhoye (@mhoye) May 12, 2020

For more from Mike check out the OTSWU recording above, he's on first.

Dept of Spec πŸ“œ


anoa announced:

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

MSC Status

Merged MSCs:

  • No MSCs were merged this week.

MSCs in Final Comment Period:

New MSCs:

Spec Core Team

In terms of Spec Core Team MSC focus for this week, MSC2526 has entered FCP. We'd like to keep the E2E MSCs in flight in focus, but are also conscious that room v6 is coming up. We're sticking the MSCs for the latter alongside the existing E2E ones in the focus queue, for a total of 5. Those MSCs are: MSC2366 (verification flows), MSC2399 (UISI messaging), MSC2540 (canonical JSON validation), MSC2209 (notifications auth rules), and MSC2240 (room version 6).

Dept of Servers 🏒

Dendrite / gomatrixserverlib

Dendrite is a next-generation homeserver written in Go

Neil Alexander announced:

  • Dendrite now implements /get_missing_events, which improves inbound federation reliability significantly

  • State resolution v2 implementation in gomatrixserverlib now uses significantly less overall memory and performs far fewer allocations

  • A skeleton keyserver component has been added - it returns no keys for now but that is enough to satisfy Riot when creating DMs

  • Canonical alias is now set if needed when the room is created

  • Reduced the number of HTTP 500s returned by the media API

  • Sync API topology logic and tokens have been reworked

  • Server keys are now cached in memory using an LRU cache, regardless of database or fetchers used

  • Federated joins now attempt all listed servers more reliably

  • Federated joins in response to an incoming invite should now work, particularly in cases where the room had previously been joined and left

  • Some Prometheus statistics are now available for the LRU caches

  • Sync API storage layer has been deduplicated quite a bit

  • Display name and avatar URL are now sent in join content again after a regression

  • Fixed a bug in the membership updater when matching added and removed state

  • Fixed a bug where a response to a federated device query would not contain all required fields

  • Fixed a bug where /sync could panic after joining a room

Get a real demo of Dendrite from Open Tech Will Save Us #2


Conduit is a Matrix homeserver written in Rust

timo said:

This week I worked on presence and end to end encryption, but they are not working yet.

Meanwhile, Valkum got sytest integration working! This means each time a new commit is pushed to a branch, CI automatically picks up on that and lets a lot of tests run on the homeserver - the same tests that synapse uses. Currently we have 8% of all tests positive on Conduit.

Client-Server APIs: 8% (56/667 tests)


  Registration             :  53% (17/32 tests)
  Login                    :  26% (5/19 tests)

  V1 CS APIs               :  10% (3/30 tests)
  Misc CS APIs             : 100% (1/1 tests)

  Profile                  :  33% (2/6 tests)
  Devices                  :  17% (2/12 tests)

  Presence                 :   0% (0/10 tests)
  Create Room              :  31% (4/13 tests)

  Sync API                 :   1% (1/85 tests)
  Room Membership          :   0% (0/15 tests)

  Room State APIs          :   0% (0/14 tests)
  Public Room APIs         :   0% (0/7 tests)

  Room Aliases             :   0% (0/15 tests)

At the same time, MTRNord tried to integrate opentracing into Conduit and Paul worked on a docker file to make installation easier.

Thanks to my supporters on Liberapay.

See the bottom of this post for some more interesting numbers!


anoa offered:

Synapse v1.13.0rc2 shipped this week with the following notable improvements:

  • SSO support in User-Interactive Authentication sessions

  • Cross-signing device list bug fixes

  • The ability to run in worker mode using redis as a backend (which will soon be considered the default transport for Synapse workers)

  • Some admin api improvements and additions well as all the usual bug fixes and especially performance improvements. See the changelog for the full details and please test if you can! A full release is expected early next week.

Speaking of next week: work will involve getting room version 6 ready to ship, alongside even more performance work - especially moving event processing off the master process (the code for which is already running successfully on Half-Shot's own homeserver)!

Dept of Bridges πŸŒ‰


Icewind told us:

I've been working on a new puppet bridge for steam chat mx-puppet-steam, while I would still consider it to be in alpha state, most of the things needed for day to day chatting are functional.

It bridges both one on one and group messages, shows the proper name, avatar and online status of your frends and handles embedded images in one on one chats.

I have a docker image for it if that helps:


Tulir reported:

As promised last week, mautrix-whatsapp now has end-to-bridge encryption (currently on the e2be branch, will be merged to master soonβ„’). It works mostly the same way as the other bridges.

Dept of Clients πŸ“±

It's a big, big week for client news! We must take a deeper look at some of these projects soon!

Ditto v0.4.1 Released!

Annie offered:

What is Ditto?

Ditto is a mobile client for iOS and Android! It's available on TestFlight and Google Play (beta) - download link available on the website below.

What's New?


  • Reactions support! πŸ˜„πŸŽ‰

  • Add a visual hint if a message is sending or could not be sent

  • Send pending messages when the connection to the homeserver is back


  • Update to React Native 0.62.2

  • Major performance improvements!


  • Redacted events have a proper message

  • Switched push gateway to https


Half-Shot said:


I got really bored in lockdown, as we all have. I stared at my TV, and it stared back at me. While it's definitely a privacy nightmare to start developing apps for these things, I couldn't help myself. I got stuck in, and secured myself a LG Developer Account.

The LG set of smart TVs use WebOS, as like the name suggests, runs apps in it's special variant of Chromium. I was lucky to be running a recent OS and had access to Chromium 53! And NodeJS 0.12!! Sarcasm aside, there are some very troubling versions of WebOS with much older versions of the browser, so I was happy to be developing against something with strong ES6 support. Despite the absolutely awful onboarding experience, the WebOS SDK itself was pretty good. matrix-tv was written to be a general large screen matrix client, so it talks to the TV's own libraries through an abstraction layer :)

Anyway, this client is the culmination of a lazy Sunday afternoon's work. It features very basic support for viewing a room, but I hope to expand it at some point. It supports running in a web browser and the aforementioned OS, but support for more variants is easy to add. I'm looking into how to design for the large screen beyond making fonts bigger, because the unique constraints on memory and UI are fun challenge.


Nheko is a desktop client using Qt, Boost.Asio and C++17. It supports E2EE (with the notable exception being device verification for now) and intends to be full featured and nice to look at

Nico ( announced:

  • Nheko now supports SSO. If your server uses SSO, you may want to test that, if it works for you, but I did successfully sign into the Mozilla homeserver.

  • We improved hinting on the login and registration pages, so it should be easier to enter correct credentials.

  • Replies now have a max height by default. If you want to see the full reply, you need to click on it to navigate to the reply.

  • Nheko now has a red unlocked padlock, when an unencrypted message is sent in an encrypted room.

  • red_sky has been hacking along on reactions. Displaying them is now in master, for sending he is currently reworking the emoji picker, so that it can be attached to the timeline more easily and it is easier to search, etc.

Nheko has it's own weblate btw, if anyone feels like translating a bit of stuff:

Pattle: version 0.16.0

Pattle is a client written for Flutter using Dart

Wilko said:

A new version has been made available and will become available on Google Play and TestFlight!

Because of corona this might take longer than usual.


  • Huge performance improvements! All SDK processing now happens in a different isolate (comparable to a thread)!

  • Also huge start up time improvement! When opening the app you should see your chats in less than or equal to a second! (will vary per device)

  • You'll now see two checkmarks when a message is read!

  • Add Dutch translations! (thanks to Louis!)

  • You can logout now!

  • An error along with a stack trace is now shown when the initial sync fails. You can use it to inform me and make an issue!

  • For the launcher icons vectors are now used on Android when it's supported

  • Contributing is now easier, you don't have to sign a CLA anymore!

Get Pattle

Issues or suggestions

If you stumble upon any issues or would like to suggest features, please do so here!

You can login via GitHub and!

Follow development

Follow development in!


benoit reported:

We are making progress on Identity server feature implementation (PR in review). Also we are working to integrated call with WebRTC, integration manager (widget, Jitsi, sticker) and we are stabilizing the application, especially on the cross-signing part.

Expect a new corrective release at the end of the day!


gomuks is a terminal based Matrix client written in Go. Source on GitHub

Tulir offered:

I was able to solve a few annoying bugs like message history disappearing and switching rooms taking time (it turned out that read receipts were being sent synchronously), so I decided to release gomuks v0.1.0.


krille said:

FluffyChat 0.13.1 is out with:

  • New status feature

  • HTML rendering of messages

  • Markdown support

  • Enhanced chat list design

  • New translations (Polish, Hungarian)

  • Lots of minor fixes and refactoring



Nio is a client written with SwiftUI

kilian told us:

Since the last updates, there's been a few cool new features and changes added to Nio:

  • message text field supports multiple lines of input

  • edit badges instead of "(edited)"

  • markdown message rendering

  • spanish translation

  • blurhash support for incoming images (so find some Nheko-using friends! πŸ˜„)

  • sending images

  • and a few minor and internal fixes

Join us in for discussion and more fun 😊

Riot-Android 0.9.11

benoit reported:

Riot-Android: Version 0.9.11 (with Matrix SDK 0.9.34) has been released on the PlayStore, and should be available for all during the week-end. It contains fixes on the identity server feature (the "missing token" thing), and also support Jitsi call with configured domain.


Manu offered:

On the cross-signing side, we have been working on the implementation of SSSS (to recover all private keys from the HS) and on UI polishments.

On the maintenance side, the new push mechanism from Apple has been implemented but it needs more work to work properly.

Riot integration with NextCloud

Riot-web integration with NextCloud exists! Source at

Dept of SDKs and Frameworks 🧰


Benedict offered:

This SDK is now on maven central. I also introduced support for implementing Application Services. The project can be found here: . It will be used by Matrix-SMS-Bridge, which only needs one telephone number. The latter will be released next week, when everything works fine (

Matrix Dart SDK: v0.31.0

Wilko said:

  • Add the ability to defer all processing to a different isolate

    When you use isolated: true on Homeserver.login or MyUser.fromStore, everything will be handled for you and the SDK works the same.

    This only works on platforms with the Dart VM (not web).

  • Updaters are now globally registered per MyUser id.

    This means for now only one Updater per MyUser is allowed. Updaters are created when a MyUser instance is retrieved via Homeserver.login or MyUser.fromStore

  • Add ability to specify what rooms to load from store when retrieving user

  • The previousBatch param from Room.copyWith is removed (wasn't used)

  • Add ability to override context in MyUser.copyWith and MyUser.merge

  • Updater and Homeserver are less coupled now

  • When a Context is changed with copyWith, all child objects' contexts are also changed

  • Fix bug in read receipt parsing (thanks to MatMaul!)

  • Sync errors are now pushed to the updates stream

  • Fix access token not being passed to logout API

  • Add type to RequestUpdate, so you can see which type of call

    the update was caused by

  • Moor has been updated

  • And other minor fixes!

Get it on pub, and see the source here!

Dept of Bots πŸ€–

JupyBot - First proof of concept

rdi said:

What is JupyBot

The purpose of the bot is to provide a link with Jupyter kernels running either on your local computer or somewhere else on a server. You can access your kernels through the bot with the chat interface. The kernels will answer to your commands through the same interface.

Since this is still a proof of concepts, the number of features is limited (command line text, string and pictures are the only output formats supported. No widget, no funny javascript) and they are few safeguards against infinite loops and other entertaining bugs.


This is right now just a proof of concept. We want to see if such a bot can be useful for people and how. What features would be interesting, what can be integrated in the present clients,... Therefore, in the short term, we want to focus on the possibility of easy testing for users and easy contributions for people who want to add their ideas. On the mid- and long term, a lot of ideas can be realized; it will depend on the feedback. These are just some examples. Short term:

  • proper error catching

  • fallback for non supported Jupyter formats on (i.e. a lot)

  • testing on termux on a tablet or smartphone

  • solve the problem with nio-matrix and upload in chunks of images.

  • Dockerized version

Middle term:

  • use of opsdroid as a framework

Longer term:

  • local server integrated to locally command the bot service.

  • make full use of jupyter capabilities with a client suited for it (for instance a Jupyterlab plugin)




lub reported:

I made a little bot that scrapes , because they've disabled their RSS feeds for some time now. It regularly scrapes all posts of a configured category and sends messages for new articles to all rooms the bot is a member of. It works like a RSS bot, except the source is a website instead of a RSS feed.

In the readme there are also some public instances, which you can just invite instead of hosting your own bot.

midori jabbot

Torrey Searle told us:

I've added matrix support into a chat bot, you can see the chat bot in action at and it's project page is here
it's main highlight is anybody can add new commands to it in chat using its scripting language
any any existing bot command can be used as a function in new scripts you write
The scripting language to add new commands can be found here
you can do things like
!script print "HELLO world";
or make a new command
!script sub hello { print "HELLO World"; }
that would result in a new command !hello being made
print also has 2 output stream, one for rich format and one for basic formatting
!script print "Hello World!"; print HTML "Hello <b>World</b>";

Dept of Events and Talks πŸ—£

Matrix will be featured in a Rust London meetup on the 27th May 2020.

New Public Rooms 🏟

Ludwig offered:

Hey, I have created a room for designers workin on matrix stuff to join:

The goal is to improve cohesion and collaboration for all things design (UI, UX, interaction...) Over time, it should become a place for people to

  • ask design-specific questions

  • share cool stuff and be praised for all the good work you're doing

  • develop and document a common understanding of the semantics of matrix

  • make sure the user experience is amazing, even as we all figure out how to federate. Probably most designers work on single clients right now, but there are important UX questions that can only be answered ecosystem-wide. Maybe we'll end up with a design guide for people to use alongside the spec.

Final Thoughts πŸ’­

Let's test homeservers against sytest, then unfairly pit them against one another! This week we're comparing Conduit and Dendrite - let's see the results!

Federation APIs1% (1/103 tests)27% (28/103 tests)
State APIs0% (0/13 tests)46% (6/13 tests)
Key API17% (1/6 tests)33% (2/6 tests)
Query API0% (0/5 tests)80% (4/5 tests)
send_join API0% (0/8 tests)38% (3/8 tests)
make_join API0% (0/2 tests)50% (1/2 tests)
Auth0% (0/19 tests)5% (1/19 tests)
room versions0% (0/7 tests)29% (2/7 tests)
Federation API0% (0/14 tests)36% (5/14 tests)
get_missing_events API0% (0/6 tests)33% (2/6 tests)
Backfill API0% (0/4 tests)0% (0/4 tests)
Invite API0% (0/10 tests)10% (1/10 tests)
send_leave API0% (0/1 tests)0% (0/1 tests)
Public Room API0% (0/1 tests)100% (1/1 tests)
Device Key APIs0% (0/7 tests)0% (0/7 tests)
Non-Spec API0% (0/50 tests)0% (0/50 tests)
Client-Server APIs8% (56/667 tests)33% (225/672 tests)
Registration53% (17/32 tests)62% (20/32 tests)
Login26% (5/19 tests)32% (6/19 tests)
V1 CS APIs10% (3/30 tests)10% (3/30 tests)
Misc CS APIs100% (1/1 tests)100% (1/1 tests)
Profile33% (2/6 tests)100% (6/6 tests)
Devices17% (2/12 tests)17% (2/12 tests)
Presence0% (0/10 tests)0% (0/10 tests)
Create Room31% (4/13 tests)92% (12/13 tests)
Sync API1% (1/85 tests)40% (34/85 tests)
Room Membership0% (0/15 tests)47% (7/15 tests)
Room State APIs0% (0/14 tests)36% (5/14 tests)
Public Room APIs0% (0/7 tests)14% (1/7 tests)
Room Aliases0% (0/15 tests)67% (10/15 tests)
Joining Rooms0% (0/8 tests)75% (6/8 tests)
Leaving Rooms0% (0/1 tests)100% (1/1 tests)
Inviting users to Rooms0% (0/14 tests)7% (1/14 tests)
Banning users0% (0/5 tests)20% (1/5 tests)
Sending events0% (0/3 tests)100% (3/3 tests)
Getting events for Rooms0% (0/10 tests)60% (6/10 tests)
Typing API0% (0/5 tests)0% (0/5 tests)
Receipts0% (0/4 tests)0% (0/4 tests)
Read markers0% (0/1 tests)100% (1/1 tests)
Media APIs10% (2/21 tests)24% (5/21 tests)
Capabilities API0% (0/2 tests)50% (1/2 tests)
Logout0% (0/4 tests)75% (3/4 tests)
Push APIs21% (12/58 tests)8% (5/59 tests)
Account APIs20% (2/10 tests)40% (4/10 tests)
Ephemeral Events0% (0/1 tests)0% (0/1 tests)
Power Levels0% (0/2 tests)83% (5/6 tests)
Redaction0% (0/5 tests)0% (0/5 tests)
Third-Party ID APIs16% (3/19 tests)16% (3/19 tests)
Guest APIs0% (0/35 tests)49% (17/35 tests)
Room Auth0% (0/25 tests)52% (13/25 tests)
Forget APIs0% (0/4 tests)25% (1/4 tests)
Context APIs0% (0/4 tests)0% (0/4 tests)
Room Upgrade APIs0% (0/21 tests)0% (0/21 tests)
Room Versions0% (0/40 tests)75% (30/40 tests)
Device Keys3% (1/37 tests)3% (1/37 tests)
Tagging APIs0% (0/8 tests)75% (6/8 tests)
Search APIs0% (0/6 tests)0% (0/6 tests)
OpenID API0% (0/3 tests)0% (0/3 tests)
Send-to-Device APIs0% (0/12 tests)0% (0/12 tests)
Server Admin API0% (0/1 tests)0% (0/1 tests)
Ignore Users0% (0/3 tests)0% (0/3 tests)
User Directory APIs0% (0/11 tests)0% (0/11 tests)
Application Services API4% (1/25 tests)20% (5/25 tests)

That's all I know 🏁

See you next week, and be sure to stop by with your updates!

Announcing GSOC 2020 Participants!

11.05.2020 00:00 β€” GSOC β€” Ben Parsons


Google Summer of Code participants were announced last week. This year Matrix was assigned SIX students!

This is the most students we've have taken on in a single year, made possible by Matrix now acting as an umbrella organisation for multiple projects - this year that's Ruma, Nheko and OpsDroid. There are also students working on projects from the core team: go-neb, matrix-js-sdk and matrix-ircd.

We received dozens of applications this year, which made narrowing our focus to six students difficult, but we are proud to announce:

Devin Ragotzy, who has been involved with the Ruma project in the past, will work on Ruma procedural macro refactoring and more

Arnav Tiwari will work with Travis and myself to create HTML Embeddable Matrix Chat Rooms

Nikolaos Filippakis will work to support E2E encryption for go-neb. Kegan, one of the original go-neb authors is particularly excited about this one

Brooks Karlik will update matrix-ircd: Move matrix-ircd to async/await. This will be a welcome upgrade for anyone using that project!

Tyagdit will work with Cadair and the OpsDroid team on Enabling E2EE in Opsdroid Matrix Connector

Chethan Reddy, last but not least, will work with Nico and the Nheko gang on Adding Features in End-to-End encryption for Nheko-Reborn

Congratulations all, and also congratulations and thank you to the projects the students will be working on!

Find out all about Matrix @ GSoC on Google's dedicated site, and keep reading the Matrix blog where we'll have updates from the students.

PS Alejandro DomΓ­nguez has a Matrix related project too: they'll be working under the GNOME organisation to add Multi account support to Fractal.

This Week in Matrix 2020-05-07

07.05.2020 00:00 β€” This Week in Matrix β€” Ben Parsons

Matrix Live πŸŽ™

Matthew and Amandine discuss the week, including E2EE by default!

Dept of Status of Matrix 🌑

What a week!!

Lots happening this week! Cross-signing landed - this is a massive achievement for the team, and will go a long way to helping the user experience for new users especially. Read more in the major Riot blog post here. Time to start getting less-technical friends on Matrix!

Google announced their Summer of Code programme acceptees: Matrix have six students this year, our most ever! We'll make a new blog post next week welcoming the students!

Last month we hosted Open Tech Will Save Us meetup 1, so hold on to your keyboard as we announce Open Tech Will Save Us meetup 2!

Meetup 2 will feature:

  • Mike Hoye from Mozilla talking about "Verbs in the fediverse"
  • Eugen (@[email protected]) will talk about "how we keep running at scale" as a Q&A
  • +MORE

Dept of Spec πŸ“œ

anoa offered:

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

MSC Status

Merged MSCs:

MSCs in Final Comment Period:

New MSCs:

Spec Core Team

In terms of Spec Core Team MSC focus for this week, MSC2474 has entered FCP. Keeping with the E2EE theme, we've switched focus to MSC2526. So the new list of MSCs for next week is: MSC2366 (verification flows), MSC2399 (UISI messaging), and MSC2526 (deleting key backups).

Dept of Servers 🏒

Dendrite / gomatrixserverlib

Dendrite is a next-generation homeserver written in Go

Neil Alexander said:

  • Some of the work for /get_missing_events has been done now for filling gaps in the room DAG

  • Federation sender performance and parallelisation have been dramatically improved, which helps a lot in big rooms

  • Retries, backoff and blacklisting have also been implemented in the federation sender to handle cases where remote homeservers are unavailable much more gracefully

  • Retrieving missing state when receiving incoming events over federation is a bit more robust now

  • Creating direct chats now works

  • Invites are mostly working now overall, both locally and over federation

  • RespState and RespStateJoin have been fixed in gomatrixserverlib

  • Room joins and leaves are now handled by new code across the roomserver and federation server perform APIs, which reduces complexity significantly


Neil offered:

  • Redis live in production for! We did not expect this to translate into a significant improvement in performance directly, but it means that we can add new workers without any extra overhead on the master process which has been very useful in supporting cross signing.

  • Fixing bugs leading to messages getting stuck at the bottom of the timeline as well as messages not making it to sync at all.

  • Lots of improvements to deal with the extra load generated by cross signing.

All of these changes will be available in v1.13.0 which should have a release candidate ready rsn.

Next week, we continue to work on sharding changes, further SSO support and ensuring that cross signing adoption is as smooth as possible.


Gnuxie said:

Architect is a homeserver project written in Common Lisp. We intend to create a high performance homeserver using the meta-programming features of Common Lisp to reduce the amount of redundant and timely code that needs to be written and maintained.

architect events

I created a json-schema library, to generate class definitions directly from the Matrix specification. These classes also have information attached to them to allow for serialisation, using a metaclass from json-clos.

This is done entirely dynamically without writing to source files. The invocation of json-schema that creates classes for the client-server, server-server and application-service protocols is only about 20 lines.

I definitely approve of separating out the event library and generating it from the spec - Ruma also has this approach.


Conduit is a Matrix homeserver written in Rust

timo told us:

This week I refactored most of the data handling code to make it both more efficient and easier to read. I started by splitting a file called "" into multiple smaller files that handle just one part of the database, like "", "" or "". I continued improving the code by making methods return iterators instead of vectors and propagating errors instead of crashing directly. Lastly, I added a few comments here and there and made sure everything works.

Meanwhile, @Valkum experimented with CI and @MTRNord is working on FluffyChat Flutter support.

Finally, I want to thank my supporters on Liberapay.

Dept of Bridges πŸŒ‰

matrix-signal bridge

witchent told us:

After a few weeks of work the matrix-signal bridge is now functional again. In the process I also added the possibility to send audio and video files among other things.

If you want to try it out go to


mx-puppet-bridge is a general bridging library that supports (double)bridging and relays. The goal is to make it as easy as possible for others to bridge new third-party protocols to matrix. Support room Donate

sorunome reported:

mx-puppet-bridge now supports emote synchronising using revolution's custom emotes! The discord protocol implementation (mx-puppet-discord) already utilizes this

Easybridge is a multi-user bridge for small Matrix servers

LX reported:

Easybridge is a multi-user bridge for small Matrix servers, with the idea of making it easy for non-technical users to bridge their external accounts into Matrix. Once configured next to a server, users can just go to a dedicated web page and add their accounts with a simple form. Currently supported protocols include IRC (buggy), XMPP (basic feature only), Mattermost (quite in good shape) and Facebook Messenger (has issues with disconnections). Available at the following link:


Half-Shot offered:

Hello one and all. Today we're releasing the 1.2.0 of the slack bridge. No notable changes from the last RC this time, but another release should follow this one soon to make changes to the provisioning system :)

Dept of Clients πŸ“±


gomuks is a terminal based Matrix client written in Go. Source on GitHub

Tulir offered:

gomuks's e2ee support is now on the master branch. The basic olm/megolm things like key distribution work fine, but no advanced stuff like key import/export or device verification yet.

I'll probably add e2be to mautrix-whatsapp next and then add some of the advanced e2ee stuff to gomuks. I'll also make a v0.1.0 release in gomuks after I figure out some bugs in message history loading.


Nheko is a desktop client using Qt, Boost.Asio and C++17. It supports E2EE (with the notable exception being device verification for now) and intends to be full featured and nice to look at

Nico ( reported:

Apart from some further speedups, we've been working on reactions. Nheko can now display them and sending them should be done soon too. We also fixed a few bugs, when people reported them and you can now select, who you want to reply to by using a keyboard shortcut (Alt+Arrow keys for now). We will probably release a new version once reactions are done.


RiotX v0.19.0

benoit said:

We have released RiotX v0.19.0 on the PlayStore on Tuesday! This is a pretty huge release, including all the work on cross-signing, but also other features like changing account password, deactivating account, saving media to Gallery, etc., without forgetting a lot of bug fixes. More detailed change log can be found here:

We are now working to implement the main missing features compare to Riot-Android, with the target to upgrade Riot-Android with RiotX codebase in a few weeks.


Manu offered:

This week has mostly been another cross-signing week to improve it and to fix bugs. We released 0.11.2 on Monday. We are going to release 0.11.3 with the work we made this week. It should be available in the App Store tomorrow.

We also released MatrixSDK 0.16.4 with the last version of AFNetworking. That means apps using the MatrixSDK should be able to publish to the App Store again. There is no more usage of UIWebView.

Radical Native

stoic offered:

Your favorite way of electron-free searching through encrypted rooms in Riot Web was just updated to v0.1beta11, featuring:

New translation projects for RiotX and Nio

Take a look at and see if you can help with translation there.

Nio (client) translations are also now available on Weblate - go forth, translate and help Kilian out. Or, "aushelfen" him, as he might say.


Revolution is a riot-web fork that has things like custom emotes. Have you heard of it before? Well, it's been around for about two years already!

You can try it out on or build it yourself from the repos at

git clone <>
cd matrix-js-sdk

yarn install
yarn build

yarn link
cd ..

git clone <>
cd matrix-react-sdk

yarn link matrix-js-sdk
yarn install

yarn build
yarn link

cd ..
git clone <>

cd riot-web
yarn link matrix-js-sdk

yarn link matrix-react-sdk
yarn install

yarn build
yarn electron # this also launches the app

Dept of SDKs and Frameworks 🧰


Ruma is a Rust project to create a comprehensive set of APIs for Matrix. Previously there was a Ruma homeserver project.

jplatte offered:

Things are progressing at a fast pace, and after a few weeks of mostly pre-releases, we've now got

ruma-events 0.21.0

With this release, it is now easier than ever to work with malformed and / or custom events. Some big changes are already being planned for the next release.

ruma-api 0.16.0

We basically just deleted lots of code that is no longer needed with ruma-events 0.21.0. We also got rid of the dependency on the url crate, which really didn't have a very good reasont o be there.

ruma-client-api 0.8.0

With this release, ruma-client-api is basically up-to-date with r0.6.0 of the matrix specification. Special thanks to @iinuwa for updating a bunch of those endpoints, and for adding support for the user-interactive authentication API!

Dept of Bots πŸ€–

Opsdroid home-assistant bot

Oleg reported:

After seeing the fabulous matrix live opsdroid party I decided to release my home-assistant bot.

I use this bot for triggering home-assistant automations via matrix. All commands and actions can be configured using just a config file.

P.S: Thanks for Opsdroid! ❀︎


Awesome example of life imitating art! After we recorded the Matrix Live last week I resolved to get Opsdroid and Home Assistant running!

New Public Rooms 🏟

/r/AV1 discord bridged to Matrix

dandellion reported:

Anyone here is interested in AV1 (the new open video codec) and related modern codecs?

I have bridged the /r/AV1 discord to

Dept of Interesting Projects πŸ›°

Doctor Who watchalongs

Brendan said:

The Matrix community editions of the Doctor Who watchalongs continue! Next up on our line-up is another two-parter on Sunday (May 10th), we'll be pressing play on The Zygon Invasion at 7PM BST, then on The Zygon Inversion at 8PM BST! Joining us on Twitter will be Peter Harness (writer) & Ingrid Oliver (Petronella Osgood aka The Osgoodsβ„’οΈŽ), and maybe more πŸ™‚

As always, to join the fun or know first-hand when the next event will happen, head over to

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 to experience the fun live, and to find out how to add YOUR server to the game.

RankHostnameMedian MS

That's all I know 🏁

See you next week, and be sure to stop by with your updates!

Cross-signing and End-to-end Encryption by Default is HERE!!!

06.05.2020 00:00 β€” General β€” Matthew Hodgson

Hi all,

As of today, Matrix is end-to-end encrypted by default for private conversations.

Three years have passed since we first announced End-to-end Encryption in Matrix and started to beta test it in Riot - and after an enormous amount of polishing and refinement on its user experience, we are finally declaring it out of beta and enabling it by default for all new private conversations in Riot. As Riot is currently the most common Matrix client, this means that Matrix as a whole should now be considered end-to-end encrypted by default for DMs and invite-only rooms.

Work on E2EE in Matrix has progressed in waves since we first shipped it - including:

  • adding keysharing (letting you share encryption keys between your devices to improve reliability)
  • making Riot Web's encryption resilient to running concurrently in multiple tabs
  • adding online key backup (so you don't lose all your history if you lose all your devices)
  • making encryption resilient to restoring the app from a backup
  • adding interactive key verification via emoji to make the verification process easier.

However, our goal was always to enable E2EE by default for all private rooms, which means having feature parity between unencrypted and E2EE Matrix so that we can enable encryption without any negative impact on usability. The high-level remaining items were significant:

  • Cross-signing: verifying your own logins so others don’t have to.
  • Adding QR codes for even better verification UX, to make cross-signing as painless as possible.
  • Replacing the old prototype UI for E2EE with final polished UI/UX.
  • Ability to support non-E2EE clients.
  • Ability to search encrypted rooms.
  • Ability to view file indexes in encrypted rooms.
  • Fixing the remaining β€œUnable to decrypt” errors.

Over the last few months the Riot team has been almost entirely focused on implementing solutions to these items - and we're finally at the point where the switch can be flipped and as of Riot Web/Desktop 1.6, Riot iOS 0.11.1 and RiotX Android 0.19, all new private rooms will be encrypted by default; completing the transition we began at FOSDEM 2020 when we landed cross-signing E2E-by-default in the development branches of Riot.

For full details, please go check out the massive deep dive over at the Riot blog - also featuring all the other recent progress in Riot!

Heads up that encrypted traffic is slightly heavier on the server than unencrypted (due to exchanging keys, verification traffic, and keybackup traffic), and so there is a risk that the already-over-popular server instance may feel a little hugged to death. However, unprecedented Synapse performance breakthroughs are on the horizon in the coming weeks which will fix this - and, of course, you can (and should!) be using your own instance anyway.

Thanks everyone for helping us test encryption over the years and getting us to this point: cross-signing provides a more secure way of tracking device trust than almost any other comms system out there, and we hope that you'll agree the improved UX has been worth the wait.

Next stop: Synapse performance, and rebuilding Riot's first time user experience!


Matthew, Amandine & the Matrix Team.

(Comments over at HN)

This Week in Matrix 2020-05-01

01.05.2020 00:00 β€” This Week in Matrix β€” Ben Parsons

Matrix Live πŸŽ™

Dept of Status of Matrix 🌑

Cross-Signing is close, please test

Next week, Cross-Signing is planned for release!

Please test this weekend, and report any issues you may find! passes 3 Million bridged users

TravisR said:

Over 3 million people from Telegram and Discord have now been brought into the Matrix universe through Of those people, around 230 thousand are active each month and 15 thousand are dedicated users of the bridges daily.

While this is a huge milestone for,it underlines the importance of self-hosting: having a couple giant bridges is great for accessibility, though where possible it’s heavily encouraged that people self-host. Hosting the bridges yourself on your own homeserver gives you better control of what passes through your server, reduces your dependence on third parties like, and gives you better performance.

During peak periods, sees about 10 messages per second passing through it. Half of those messages are generated by the Telegram bridge alone. The other half is dealing with federation and the various other bridges and bots on In terms of media, a new image is uploaded every 2 seconds, leading to 5.8 TB of media being stored. The database is 3 TB and holds 236 Million events - roughly 131 Million of which are sent by

Thank you to everyone who has used in the past 3 years - it’s been more successful than ever imagined. Here’s to another year and a bunch of self-hosting. :)

Dept of Spec πŸ“œ

anoa said:

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

MSC Status

Merged MSCs:

  • No MSCs were merged this week

MSCs in Final Comment Period:

  • No MSCs are currently in FCP.

New MSCs:

Spec Core Team

In terms of Spec Core Team MSC focus for this week, MSC2454 has entered FCP, and as such we've decided to instead focus on MSC2399. So the new list of MSCs for next week is: MSC2366 (verification flows), MSC2399 (UISI messaging), and MSC2472 (Symmetric SSSS).

Dept of Servers 🏒

Dendrite / gomatrixserverlib

Dendrite is a next-generation homeserver written in Go

Neil Alexander announced:

  • Room version 5 support added - Dendrite now supports all current room versions!

  • Room version 5 will now be used by default when creating new rooms.

  • Backfill over federation has been implemented and it honours history_visibility correctly.

  • Strict key validity checking has been fully implemented in gomatrixserverlib in support of room version 5. Some key expiry bugs have also been fixed.

  • Back-pagination tokens are now generated correctly for events that have the same depth.

  • It's now possible to limit the number of Postgres connections - thanks tomasji!

  • Some progress towards working invites has been made.

  • Federated room joins are now performed by the federation sender as a part of an on-going remodelling.

  • Some bugs with URL query vs. path escaping have been fixed in gomatrixserverlib.

  • A number of internal APIs have been merged together.

  • Some new tests have been added to the sync API.

v5 rooms! this is a sign of huge progress in Dendrite!


Neil offered:

We’ve spent time this week working with the Riot teams to tweak performance for cross signing. We’ve also fixed a few performance regressions ahead of next week's 1.13.0 release (which will be a big one, more details when it lands).

With any luck we’ll have Redis in production on next week, we don’t think this will give us a huge performance win, but there is certainly overhead in having so many workers using the previous replication streaming method.

Our sharding project continues, and Erik has been trying to move the event stream entirely away from the master process which in itself could be significant for overall perf once ready for production.

Aside from that we continue to improve SSO support and we have a really great community PR from sandhose that implements OpenID Connect support. We are really looking forward to getting that merged. The admin API is also getting plenty of community love with awesome-manual and dklimpel leading the charge.

Next week, look out for 1.13.0 and hopefully some more good news on sharding.

P2P Matrix

kegan told us:

Version 0.0.6 has been released on which has the following changes:

  • Room version 5 is supported by default.

  • Backfill is much more reliable.

  • Backfill now does all PDU checks required of it

You might get kicked out a few times whilst the service worker shifts around, you can force things by going to chrome:serviceworker-internals or about:debugging#/runtime/this-firefox to unregister the worker manually. Logs will state version 0.0.6 on update.

All the benefits from Dendrite (above) will feed into this.


Conduit is a Matrix homeserver written in Rust

timo said:

There was a lot of progress this week!

  • First server-server communication by requesting a remote public room list

  • Paginated message loading

  • Message notifications

  • RiotX support

  • Changing the nickname works properly now

  • Forget rooms

Thanks to my supporters on Liberapay.

Dept of Bridges πŸŒ‰


Half-Shot announced:

Hey all, the IRC bridge has reached another milestone, 0.17.0. This is a medium sized release, containing a few nice to have features like predicting nickname conflicts and some work around user deactivation. Importantly, this release authenticates the provisioning endpoint so if you run an integration manager or script that makes use of it, ensure that it handles requests appropriately. You can see the changelog in


mx-puppet-bridge is a general bridging library that supports (double)bridging and relays. The goal is to make it as easy as possible for others to bridge new third-party protocols to matrix. Support room Donate

sorunome told us:

  • event syncing/storage is now properly handled on a per-room basis, rather than a global one

  • automatically renew double-puppeting if shared secret auth is enabled

  • Enhance reply support matrix->remote: The remote protocol gets in the callback now proper information on the event replied to

  • Add remote->matrix reply fallback


  • Implement skype quotes / matrix replies

  • various stability fixes

Dept of Clients πŸ“±

Pattle: version 0.15.0

Pattle is a client written for Flutter using Dart

Wilko told us:

A new version has been made available and will become available on Google Play and TestFlight!

Because of corona this might take longer than usual.


  • A lot has changed internally, expect to have a smoother experience!

    (See also the Matrix Dart SDK release)

  • A new logo is here!

    Designed by bo_rad!

  • Logging in has completely been revamped

  • For the initial sync (after login) a splash screen is shown

  • Chats in the overview are now separated by two tabs: Chats and channels

  • There's now a navigation drawer, which will be filled with useful actions in the future. For now it's just a place to go to Settings

  • Message times are now shown on the same line, if possible

  • Replies have been redesigned

  • Buttons or list tiles that didn't do anything have been removed to avoid confusion

  • Image sending has been improved, the image is now shown immediately in the timeline

  • Push notifications don't popup when the respectful chat is opened

  • Push notifications are now grouped by chat

  • Push notifications are hidden when opening the respective chat

  • Messages are immediately marked as read, previously was after 2 seconds of having it opened

  • Some colors in the dark theme have been altered

  • Ability to create a chat has temporarily been removed, it wasn't functioning well and will be completely redone

Get Pattle

Issues or suggestions

If you stumble upon any issues or would like to suggest features, please do so here!

You can login via GitHub and!

Follow development

Follow development in!



gomuks is a terminal based Matrix client written in Go. Source on GitHub

Tulir announced:

gomuks now has experimental support for end-to-end encryption on the e2ee branch. It supports both text messages and media downloads. The majority of the work happened in mautrix-go (also on the e2ee branch). This also means that mautrix-whatsapp will get support for end-to-bridge encryption in the near future.

What megolm implementation are you using?

My own based on matrix-nio, the e2ee implementation guide and the spec. libolm bindings stolen from


Nio is a client written with SwiftUI

kilian told us:

Nio received some cool new features this week.

  • New Dutch and Chinese (simplified) translations (besides English & German)!

  • Edited messages are now displayed correctly.

  • An edit action has been added to the event context menu, long press a sent message to go into edit mode (looks cool as well!).

  • When entering a full MXID into the username field on logging in, Nio will automagically prefill the homeserver URL (if a well-known config is present server-side).

  • Rich text markdown message display including clickable links detection is now in the works!

Best part about all of these changes: They were contributed by others, I did nothing but merge the PRs! Open-Source ❀️ Shout out to,, and

Nio well known


benoit announced:

RiotX will finally be an update of Riot-Android on the PlayStore and RiotX beta will then be removed from the PlayStore. We will implement everything to let users upgrade their application without being forced to log in again.

While we are finalizing cross-signing, quadS, bootstrap, etc. on RiotX, we have started studying and implementing the main missing features: identity server and related functionality (terms of service consent, invite by email, search in contact list, bind emails and phone numbers, etc.), integration manager (terms of service consent,widgets, send stickers), WebRTC audio and video calls, Jitsi conference integration, and other important missing features like UI and UX to invite people to a room, etc. We are also fighting an annoying bug related to the navigation inside a timeline.

It's also now possible to deactivate your account using RiotX.

It's worth noting that people can contribute to translate RiotX by using new dedicated Weblate projects. Thanks!


Nheko is a desktop client using Qt, Boost.Asio and C++17. It supports E2EE (with the notable exception being device verification for now) and intends to be full featured and nice to look at

Nico ( announced:

  • fernie contributed a smoother scroll behaviour and a loading indicator for individual rooms

  • We fixed some readability and styling issues

  • We fixed a major bug in 0.7.1, where you couldn't accept invites

  • We fixed a bug, where nheko would pin a core to 100% CPU on highdpi screens, because it tried to resize avatars all the time...

  • We also reduced CPU usage by a lot. Nheko now only uses 0.7% CPU on my system again and that's just the presence updates I get every 100ms or so...

There will probably be a release in the near future to get those fixes to people not running master.

The reduced CPU usage is mostly not resorting the whole room list all the time, but keeping the partially sorted room list around and not storing pending read receipts in the database but just applying them all the time without checking, if we are waiting on a receipt :D

Riot Web

A glossy Matrix collaboration client for the web.

Ryan told us:

Several more RCs this week have brought us ever closer to the release of cross-signing! A variety of verification, login, and toast issues related to cross-signing have been fixed in the RCs this week. Please do test over the weekend, as we're planning to release early next week if no issues are found.

Luxury Dark Theme for Riot

Dylan said:


OCRCC embeddable Matrix chatbox

Brendan told us:

Nomadic Labs have built an open-source embeddable chatbox using Matrix for the OCRCC (Ontario Coalition of Rape Crisis Centres) to allow survivors of sexual violence to communicate and seek help safely with OCRCC facilitators. This chatbox lives at - and it has a pretty nice feature set, including end-to-end encryption support.

They've also built a E2EE-capable bot to connect people with facilitators, which can be found here:

This is a really exciting project! Very stylish design and great to see people using Matrix for something so practical and positive. πŸ‘

Dept of SDKs and Frameworks 🧰

Matrix Dart SDK: version 0.30.0

Wilko told us:

The whole SDK has been refactored!

  • All data objects such as MyUser, Room, etc. are now immutable

  • Add MoorStore, which uses moor (thanks to MatMaul for the idea and initial implementation!)

  • The SqfliteStore (was in a separate package) is now deprecated

  • LocalUser has been renamed to MyUser

And a lot of other changes!

How it works

The user has a stream of Updates, user.updates. An Update contains the latest 'snapshot' of data associated with the user. It also contains a delta MyUser, where all properties are null, except those that are changed. For example, if a user started typing in a certain room, and we're syncing, there will be an Update in user.updates, where delta has 1 Room in delta.rooms, with only the room where the user started typing, reflected in room.typingUserIds. All other properties of the Room will be null. This is all assuming that this is the only change in the sync. If more happened, it will be reflected in delta.

For more info, see the README

Some features previously present may not have been added yet again.

They will be added in the future!

Get it on pub!

Join to learn more!

πŸ§™ Polyjuice Client

Polyjuice Client is a Matrix library for Elixir

uhoreg announced:

To better serve the wizarding community's transformation needs, I have released v0.2.2 of Polyjuice Client, a Matrix library for Elixir. This release adds support for some more Matrix endpoints, and allows paginating through room history using Elixir's streams.


jplatte and iinuwa offered:

We've iterated through a few new pre-releases of our libraries to bring some usability improvements. Here are a few highlights:

  • Implemented User-Interactive Authentication API and some other endpoints to bring us very close to full r0.6.0 compatibility

  • Updated the representation of events to allow preserving original JSON alongside typed event structs

  • Tidied up some our repositories, improved CI build times

  • Began work on Server-Server API in ruma-federation-api

Dept of Ops πŸ› 

matrix-chart v1.1.1

Typo Kign announced:

v1.1.1 of dacruz21/matrix-chart is out and now supports the IRC bridge! dacruz21/matrix-chart is a secure, scalable way to deploy a complete Matrix homeserver stack, complete with bridges and useful services, into Kubernetes. As always, come visit if you have any questions or need support!

buildbot-matrix plugin available

haywo said:

buildbot-matrix v0.0.1 released:

  • A plugin for the Buildbot CI framework

  • It sends build status notifications to a specified matrix room

  • available on PyPi, install with pip install buildbot-matrix

Dept of Bots πŸ€–


Cadair said:

Opsdroid has released v0.18 this week, which contains a load of stuff. The main matrix related changes are:

  • A generic event type for all unsupported matrix events, so you can now react to and send any custom events.

  • Implementation of the join room event in the matrix connector so you can react to users joining a matrix room.

  • A fix for mxc urls in messages, so inline images etc work.

  • A fix for the opsdroid memory to allow per-room matrix room state databases. This will hopefully be merged into core for the next release.

Picard Opsdroid Skill

Related to this release the picard skill for bridged slack/matrix community management has been updated, and now (for the first time) works with a release version of opsdroid rather than some random branch 🀣. This involved adding support for lots of different events to the slack connector in opsdroid.

See Matrix Live this week for a neat introduction to OpsDroid

New bot to share Jitsi call URLs

Cadair reported:

I wrote a bot to share Jitsi call URLs. The main objective is to allow people on the other side of bridges to get the URL for a jitsi call. When a jitsi widget is added to a room (v2 widget from riot-web) it will post a message with the plain jitsi URL. It also provides a !jitsi command which allows people to create a jitsi call with a custom URL, and if the bot has permission it will be added as a widget in the matrix room. It has a bunch of other config options you can tweak it with. The main thing you might find it useful for if you are not in a bridged room is you can use it to quickly add a jitsi widget for any conference URL. The bot can be found here: and it uses the opsdroid framework. I have also hosted a version

CovBot v0.1.5

Peter Roberts said:

  • Add regional data for Findland, Wales, Northern Ireland and Scotland with thanks to

  • Get UK and England regions from a new source as Public Health England stopped providing their CSV data, again thanks to

  • Send m.notice by default but use m.text in IRC bridged rooms to avoid annoying IRC users.

  • Make logging more consistent which helps with debugging.

MIT licensed on GitHub.

Dept of Interesting Projects πŸ›°

Doctor Who watchalongs

Brendan offered:

We're still having a great time watching Doctor Who with folks from the wider Matrix community. The next one scheduled is happening on Wednesday (May 6th) at 7PM, and we'll gather to watch The Girl in the Fireplace (series 2 episode 4) together, with tweets from Steven Moffat (writer) and Sophia Myles (Madame de Pompadour) bridged to the room πŸ™‚

As always, if folks want to tag along and join the fun, feel free to join !

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 to experience the fun live, and to find out how to add YOUR server to the game.

RankHostnameMedian MS

That's all I know 🏁

See you next week, and be sure to stop by with your updates!

New Categories for Matrix Spec Changes

29.04.2020 22:37 β€” General β€” Andrew Morgan
Last update: 29.04.2020 20:50

On April 14th, the Spec Core Team conducted a long-overdue retrospective about the things that were working in the Matrix Spec Proposal process, and those that were not.

The most glaring item on the list was the sluggish pace that many Matrix Spec Changes (MSCs) take throughout the proposal process, as well as the general lack of activity from the Spec Core Team members on proposals that have not yet started a Final Comment Period.

We deeply apologize for the frustration this has likely caused many MSC authors, and want to shed some light on the reasoning behind it, and what we plan to do to prevent leaving authors in the dark about why there may be no Spec Core Team activity on their proposal.

Proposal Triaging

There are currently 136 open MSCs that have yet to undergo Final Comment Period (FCP), 75 of which are marked as proposal-in-review, and 20 that have a FCP proposed. Relative to the 65 MSCs that have ever been closed, this is a lot of outstanding ideas, features and maintenance changes.

The Spec Core Team itself is made up of 8 members, each of which have separate full-time jobs. All team members are well-placed to be on the team given their wide breadth of knowledge across the Matrix ecosystem, however the majority are some of the most busy pushing forward Matrix's reference implementations - without which, Matrix will unquestionably fail. This limits the amount of MSCs that the team can effectively work on at a given time.

The team understands that there are MSCs that provide incredibly useful features, such as support for LaTeX in messages or the ability to "knock" on rooms, and would undoubtedly like to see them land at some point.

But there is also a large backlog of MSCs that provide even more fundamental fixes and additions to the protocol that the team needs to prioritise. These include things like cross-signing devices, the communities rewrite and finally merging reactions and edits into the spec.

While we announce what MSCs we're focusing on during a given week during TWIM, it's not as clear which items we're looking to pull from the backlog next. To help tackle this, and to help keep us honest, we've begun putting each MSC into either "feature", "maintenance", or "core" buckets. This materialises in the form of github tags, which can be used to filter the list of MSCs like so: feature, maintenance, core. For a given timespan, we’ll pick a track and pull MSCs out of that category when possible. More information about MSC categories are now detailed on the proposals page.

As for the next 6 to 12 months, we plan to work on items from the β€œcore” category. We need to get Matrix to a point where it can compete with other, proprietary chat protocols and items in "core" are decidedly the proposals that will take us the furthest in that direction. This doesn't mean we won't occasionally look at an MSC in a different category, but it will heavily influence our prioritisation.


We'll try this approach out over the next few months and see how it goes. The next Spec Core Team retro will occur in the middle of May, where we will review the process once again.

For now, if you have any feedback please come and chat with us in :)

This Week in Matrix 2020-04-24

24.04.2020 19:39 β€” This Week in Matrix β€” Ben Parsons
Last update: 24.04.2020 19:23

Matrix Live πŸŽ™

Some snapshots of what the team has been working on. Look out for a clear explanation from Erik about Synapse performance (and what will be done about it!), and lots of other goodies

Dept of Status of Matrix 🌑

Tchap used by French fire and rescue services

Brendan announced:

Tchap, the Matrix deployment in the French government, recently opened to French fire and rescue services:

Rescue18 (a French non-governmental news website for emergency services) echoed this announcement earlier this month, praising the security aspect of the platform and the possibility it offers to improve social and professional exchanges throughout the hierarchy as well as the rest of the government and public services.

Article is all in some other language - thanks Brendan for providing this summary.

Dept of Spec πŸ“œ

anoa said:

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

MSC Status

Merged MSCs:

  • No MSCs were merged this week

MSCs in Final Comment Period:

  • No MSCs are currently in FCP

Well, MSC2457 should be. It's waiting for a redeployment of mscbot.

New MSCs:

Spec Core Team

We've switched up our focus to the following MSCs: MSC2366 (verification flows), MSC2454 (SSO UI Auth), and MSC2472 (Symmetric SSSS). Expect a blog post next week describing the new MSC categories.

Dept of Servers 🏒


Neil said:

Last week

  • Shipped 1.12.4 a patch release to fix some cross signing related bugs.

  • Redis support to replace our existing cross replication system, merged to develop. This is a precursor to the sharding project. We have a PR to support cache invalidation across workers which, once merged should make it relatively easy to pull off event persistence from the master process. Just removing event persistence could give some decent perf wins, but the prize is then splitting persistence to run across across multiple workers.

  • A final PR to support SSO for user interactive auth will merge imminently, thereby freeing up full cross signing support for worker installs.

  • Aside from that we’ve been working on fixing a weird bug where rooms can end up with zero forward extremities and generally showing Sygnal some love.


  • Put Redis into production

  • Ship 1.13.0 which will contain Redis support as well as a host of SSO bug fixes.

  • Merge our new caching config logic to give finer granularity on cache settings.

  • Merge cache invalidation and try to get events persistence running in its own worker.

Ben added:

Cross signing, oh cross signing! Can you believe itβ€½ Cross signing!!!

Matrix Corporal

matrix-corporal manages your Matrix server according to a configuration policy

Slavi reported:

matrix-corporal v1.9.0 has been released. It adds support for preventing certain users from creating rooms (that is, from using the /createRoom API). I've been thinking about developing this feature for a while now, as people have been requesting it frequently.


matrix-media-repo is a highly customizable multi-domain media repository for Matrix

TravisR announced:

v1.1.2 is out with a bunch of fixes to the Docker image. Check out for details, and for support.


Conduit is a Matrix homeserver written in Rust

timo told us:

Conduit is a Matrix homeserver written in Rust

This week I worked a lot on getting the first bit of federation working. My goal was to query the public room list of another server and forward it to a client.

This involved setting up a keypair to sign the json I send to the server and putting authorization headers into my requests. Most of the work is already done and reports it's all good.


Sadly there seems to be a problem with the signing, because other homeservers reject requests: Unable to verify signature: <class 'nacl.exceptions.BadSignatureError'> Signature was forged or corrupt. I'll continue to work on this in the next week(s).

Thanks to my supporters on Liberapay.

Dendrite / gomatrixserverlib

Dendrite is a next-generation homeserver written in Go

Neil Alexander said:

  • Dendrite now supports perspective key fetching as a configurable option, and will automatically attempt to use the perspective key servers for keys that couldn't be fetched directly

  • Dendrite now uses a newer version of the Sarama library

  • Some caching has been added to the roomserver API for room versions, which should help quite a bit with performance over federation and handling transactions

  • Auth checks for /send_join are now quite a bit more robust

  • A bug has been fixed where the default state filter limited the amount of room state that was visible after a join

  • gomatrixserverlib has quite a bit of new support for backfilling now, which will be wired into Dendrite soon

  • gomatrixserverlib has new primitives for v2 invite responses and /get_missing_events requests

  • Invite support is being worked on currently, which should also enable support for creating DMs in Riot

Synapse Deployment πŸ“₯


Ananace told us:

A bit late to the party - was rebuilding my cluster at home to EL8 - but pushed the Kubernetes-optimized docker images for Synapse 1.12.4


Mathijs reported:

The image for synapse v1.12.4 including jemalloc and mjolnir anti-spam has been released to avhost/docker-matrix:v1.12.4.

Dept of Clients πŸ“±


aa13q told us:

Matrix native integration for the Sailfish OS, KDE and other linux systems called telepathy-tank got attertion from the community this week and @aa13q updated it a bit thanks to @Kaffeine. Writing the post for the TWIM has grown into the small blog post, so @aa13q shared it sepatetely:


Nheko is a desktop client using Qt, Boost.Asio and C++17. It supports E2EE (with the notable exception being device verification for now) and intends to be full featured and nice to look at

Nico ( offered:

Nheko released two new version, 0.7.0 and 0.7.1. The second one mostly fixes some minor issues in the 0.7.0 release, which we got from all the people trying it out. Thanks for reporting them!

Since 0.7.0 is pretty big, please read the release notes on github:

Some of the highlights:

  • Support for rich replies

  • Support for encrypted media

  • .well-known support

  • Mute/Unmute rooms

  • Key import compatibility fixes for Riot

  • Reduced memory usage, performance optimizations and fixes for some nasty memory corruption and crashes

You can get the latest release on github or maybe someone actually packaged it already for your distro.

We hope you will try it out and have a good experience! If you don't, you can complain to us in or open an issue in our bugtracker.


gomuks is a terminal based Matrix client written in Go. Source on GitHub

Tulir announced:

gomuks got a fancy initial sync loading bar so it no longer looks like it's broken after you log in. Implementing end-to-end encryption in mautrix-go has also been slowly progressing, might have something working in a few weeks.

Riot Web

A glossy Matrix collaboration client for the web.

Ryan offered:

This week we released a fourth RC for Riot Web 1.6, the upcoming release with cross-signing, addressing a few issues found through everyone's testing and feedback. Please do continue to test, the latest RiotX build, and also E2EE search in Riot Desktop Nightly.


Dept of SDKs and Frameworks 🧰


Benedict told us:

I created an client-sdk to interact with matrix in Spring Boot. It is written in kotlin and should also work with Java. You can find the repo here:

It contains also a bot-sdk to write bots by adding a dependency and a few lines of code only. It is tested with unit-tests, but integration-tests against a real matrix-server are currently missing. A simple ping bot works and is also integrated in the repo as example.

Currently I'm working on getting this to Maven Central.

Dept of Ops πŸ› 


This Ansible playbook is meant to easily let you run your own Matrix homeserver.

Slavi told us:

Thanks to Rodrigo Belem's efforts, matrix-docker-ansible-deploy now supports bridging to Slack via the mx-puppet-slack bridge. See our Setting up MX Puppet Slack bridging documentation page for getting started.

Dept of Interesting Projects πŸ›°

Doctor Who watchalongs

Brendan offered:

As per the previous edition of TWIM, we had a blast on Sunday watching and reacting to Doctor Who episodes The Stolen Earth and Journey's End.

The next watchalong will be this Friday (Apr 24th), and we'll be watching another two-parter together, Human Nature & The Family of Blood, starting from 7PM BST! Guests such as Paul Cornell (writer), Charles Palmer (director) & Lor Wilson (Lucy Cartwright aka Daughter of Mine) will also be discussing the episode along for even more fun and behind the scenes!

This means that if you're reading this when this edition of TWIM goes out, and you fancy watching some Doctor Who this evening, join the fun at πŸ˜€

And if not, feel free to join the room anyway to find out when the next watchalong is happening πŸ™‚

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 to experience the fun live, and to find out how to add YOUR server to the game.

RankHostnameMedian MS

That's all I know 🏁

See you next week, and be sure to stop by with your updates!

Synapse 1.12.4 released

23.04.2020 19:04 β€” Releases β€” Neil Johnson

A small patch release containing features and bugs to support the upcoming launch of cross signing. We are very close now :)

Get 1.12.4 from github or any of the sources mentioned at

Changelog since v1.12.3

Synapse 1.12.4 (2020-04-23)

No significant changes.

Synapse 1.12.4rc1 (2020-04-22)


  • Always send users their own device updates. (#7160)
  • Add support for handling GET requests for account_data on a worker. (#7311)


  • Fix a bug that prevented cross-signing with users on worker-mode synapses. (#7255)
  • Do not treat display names as globs in push rules. (#7271)
  • Fix a bug with cross-signing devices belonging to remote users who did not share a room with any user on the local homeserver. (#7289)

This Week in Matrix 2020-04-17

17.04.2020 00:00 β€” This Week in Matrix β€” Ben Parsons

Matrix Live πŸŽ™

Matthew & Amandine update on cross-signing

Dept of Spec πŸ“œ

anoa offered:

Here's your weekly spec update!

MSC Status

Merged MSCs:

  • No MSCs were merged this week

MSCs in Final Comment Period:

  • No MSCs are currently in FCP

New MSCs:

Spec Core Team

We had our first Spec Core Team retro in a very long time this week, with a new regular schedule of every month. It ran about an hour overtime - there was a lot to talk about. We'll post the conclusion in a separate blog post soon.

Dept of Servers 🏒

Dendrite / gomatrixserverlib

Dendrite is a next-generation homeserver written in Go

Neil Alexander reported:

  • Rooms now default to version 4

  • Backfill messages are now topologically ordered

  • Searching for backward extremities when backfilling is now improved by preventing duplicate prev events

  • HTTP tracing and SQL tracing environment variables have now been added

  • Direct key requests are now parallelised (which can help to speed up room joins substantially)

  • Events in /messages responses are now topologically ordered

  • gomatrixserverlib can now perform signature checks with strict validity checking as optional

  • We now return far less 500 errors over federation which helps federation with Synapse

kegan announced:

New version released which supports v4 rooms as well as improvements in how we publish rooms into directories of local nodes.

Conduit (Rust Homeserver)

A Matrix homeserver written in Rust

timo announced:

This week I spent some time improving Riot support. Now there should be a lot less warnings and some new features: typing events, read receipts, better room directory, invites, user search.

The only bigger bug that exists currently is that the message history is not automatically loaded when you join a room. Sometimes reloading the page helps, but not always. The reason for that is that Riot calls the deprecated /initialSync endpoint, which I do not support (I hope someone works on Riot to fix that).

In the next few weeks I plan to improve the single-homeserver experience further and add permission management, while also working on federation.

Check out the repository on and our Matrix room on If you want to try out the server yourself, you can try to connect to it using (though it might be offline when you read this).

I also want to thank my supporters on Liberapay for their kindness 😊.

I tested the performance of Conduit yesterday by running a ruma client that sends a /send request in a for loop 10k times, which took ~46.8 seconds (all locally on my pc). This means the server can handle ~210 /sends per second under these circumstances.


The flamegraph shows what the cpu is spending most of its time doing. Plateaus are things that take time. You can see most of the time is used for a function in sled::io (I spoke with one of the devs and they said this is expected, but will be improved in the next release)


Neil told us:

We continue to focus on performance and spent a good chunk of time improving worker replication test coverage to build confidence that our upcoming changes will work as expected. Erik has been working on how to how to factor out cache invalidation which is now starting to take good shape. Once we have that, factoring out things like event persistence are next on the horizon.

Aside from that we’ve been working with the Riot client teams as they near release for cross signing, fixing bugs and improving performance on key actions.

SSO support continues to improve, and more fixes for user inactive auth for worker'd installs will land next week. Poor old Rich has been banging his head against a sync bug blocking develop, but hopefully he has broken its back now, and we'll get that merged asap.

Finally we experienced some operational issues with push over the weekend, so we spent some time cleaning up and figuring out how to make things more resilient.

Coming up, performance, cross signing support, SSO improvements.

The Construct

Construct is a performance-focused homeserver written in C++

Tulir reported:

Update from Jason:

The Construct server made significant progress this week with end-to-end encryption, client compatibility, application services support, and build-related enhancements. I'd like to thank Yan Minari for contributing spec-compliant code paths for application services in the user registration system. Special thanks this week to Tony O. for continued work on the NixOS ( derivation for reproducible builds, in addition to contributing fixes to Nio for optimal compatibility with Construct. I'd also like to thank Wessel for contributing a much needed reorganization of the Dockerfiles in preparation for Construct operating on many more platforms. Many thanks to Nico for working with the team this week in on various compatibility fixes to mtxclient and Nheko; the responsiveness when using Nheko with Construct is mind-blowing. I'd also like to thank David Vo (a.k.a. auscompgeek) for also contributing to Nio toward Construct compatibility.

Finally, I owe much appreciation to tulir, jochen, qy and others for setting up brand new installations this week and providing feedback in Construct is the first and only federating alternative to Synapse. It is written in C++ for maximum performance, the lowest possible TCO, and designed for horizontal scaling with Construct Cluster. If you are interested in starting a low-cost Matrix hosting service, Construct may be your ideal choice. To stay informed and show your support please visit us in today!

Dept of Bridges πŸŒ‰ bridges bumper pack edition

Half-Shot announced:

Hello, this week has been busy for us over in bridge corner. We've released:

matrix-appservice-bridge 1.12.2

Which includes a bunch of small fixes, including a performance improvement to StateLookup hits. Apparently it's bad to hit the homeserver with 1000s of concurrent /state requests on startup. Most importantly it also includes a critical fix to the addAppServicePath function, which previously did not authenticate requests, see the CHANGELOG for more information on that.

matrix-appservice-irc 0.17.0-rc3

We're still working on the RCs for this release, having discovered and fixed a bunch of failures that can happen around getting connected to IRC. Be aware that the above security fix is applied in this release, which means provisioning requests will now be authenticated.

matrix-appservice-slack 1.2.0-rc1

This is another big load of bug fixes, with many thanks to our new bridge crew member, Christian!. This release includes the above security fixes, as well as some metrics improvements to track activity on the bridge.

matrix-appservice-gitter 0.1.1

The gitter bridge has been updated to include the changes from the matrix-appservice-bridge releases, as well as updating some dependencies.

Dept of Clients πŸ“±


WIP Command line Matrix client using matrix-rust-sdk

devinr528 announced:

A clickable command-line client Matrix written in Rust. Although, still in the early stages, enough has been implemented to show a working demo. rumatui uses tui to power the UI and matrix-rust-sdk for all communication with the server. So far the message formatting has been the most visually satisfying feature, although implementing it was not much fun. The goal of the project is to have a UI driven command-line client, useable from either keyboard and/or mouse.

Big thanks to @poljar for allowing me to work on matrix-rust-sdk, @jplatte for the opportunity to work with the ruma crates and everyone in the Matrix community for being so helpful!

Check it out! Help is welcome, although as matrix-rust-sdk develops the design and structure of rumatui will evolve quickly. is the room to join.



Nheko is a desktop client using Qt, Boost.Asio and C++17. It supports E2EE (with the notable exception being device verification for now) and intends to be full featured and nice to look at

Nico ( reported:

Nheko is preparing for the 0.7.0 release! You can find the first release candidate here:

0.7.0 will contain a lot of work, including replies, e2ee attachments and a completely rewritten timeline (the full changelog is too big for TWIM, but you can find it in the github releases). It also fixes a lot of issues. We should probably released it a lot earlier, but we always had one more feature we wanted to finish... For the future we plan to do smaller, more regular releases!

If you want to see Nheko translated to your language, you can translate it here:

If you are a packager, it would be awesome if you can check, that you don't have any build issues. If you need support, just message us in !

Riot Web

Ryan reported:

Cross-signing and E2EE by default for private rooms is nearly here! πŸŽ‰ It would be great to have more people testing this, as we're very close to release, and extra testing will help reveal those last issues. Please help test cross-signing on (suggesting develop since there's already some fixes there beyond the RC on staging) and the latest RiotX build. It would also be great to test E2EE search in Riot Desktop Nightly.

Matthew added:

e2ee by default and cross signing and encrypted search is almost here - please test the release candidates! (urls at


benoit announced:

We are finalizing cross-signing, QuadS and bootstrap. We will release a new version next week. We are still working on migration of the database from Realm to sqldelight solution.


Manu reported:

Let me copy Riot-Web and RiotX-Android: Cross-signing and E2EE by default for private rooms is nearly here! πŸŽ‰.

A TestFlight will be available over the weekend. Here is the link if you want to join the program. This release candidate still needs some polish but a new release will be definitely available on the AppStore next week.

In parallel of that, the maintenance work is going well. We are erasing our technical debt as much as possible. The new Apple Push API raises some privacy concerns. We may no longer be able to offer CallKit as it requires events to go in clear between servers.

Dept of SDKs and Frameworks 🧰


Ruma is a Rust project to create a comprehensive set of APIs for Matrix. Previously there was a Ruma homeserver project.

jplatte said:

Many of you will probably have heard already, but Ruma is now officially dead. The homeserver, that is. Outside of that, the API definitions in ruma-client-api have seen some work and our first two endpoints in ruma-federation-api have been written! ruma-api and ruma-identifiers are also being worked on, with the following new releases being published in the past week:

  • ruma-api 0.15.1 was released with a small bugfix

  • ruma-identifiers 0.15.0 was released with loads of changes; this might be the last 0.x release!

  • identifiers are now stored as strings (with minimal additional data)

  • before, we would parse the server name into a url::Host

  • this means that parsing now doesn't allocate at all under some circumstances, and obtaining the string representation of one of our identifier types is essentially a no-op

  • there no longer is a single non-optional dependency, everything that requires them is now behind a feature flag

  • some new helper functions have been made available, mostly around user IDs

Dept of Bots πŸ€–

CovBot v0.1.4

Peter Roberts reported:

  • When there are a lot of matches ask the user to be more specific rather than sending a huge list.

  • Let user know if we can't make sense of the age given to !risk.

  • Fix formatting of !compare tables on old Riot for android.

  • Refactor into separate files for bot and data sourcing.


Dept of Interesting Projects πŸ›°

Doctor Who confinement watchalongs

Brendan offered:

We've been doing Matrix editions of Emily Cook's Doctor Who watchalongs since confinement started around Europe. The concept is pretty simple: on a given day, at a given time, everyone presses play on the same episode. Folks are then free to then watch it on their own, or discuss the episode as they watch it in the Matrix room and/or in the Jitsi call. We're also bridging tweets sent from directors, writers, comedians, etc. watching the episode at the same time to Matrix.

If folks are interested in joining in, head over to!

The next watchalong is planned for next Sunday (Apr 19th) at 7PM BST; and we'll be watching the epic two-episode long season finale "The Stolen Earth" & "Journey's End", with Russell T Davies (writer), Graeme Harper (director), David Tennant (The Doctor) and Catherine Tate (Donna Noble) tweeting along (and possibly more to come) πŸ˜€

Tweetalong bot

Brendan reported:

To relay the tweets from guests during Doctor Who watchalongs, I've written a simple bot that reads the timeline of a Twitter list, optionally filters it by a hashtag, and posts the tweet to a Matrix room.

The code is available at, and there's already an instance running in if folks want to see it live.

Dept of Guides 🧭

Lots of new guides this week! I particularly encourage you to read neilalexander's guide to state resolution - I found it very approachable.

Matthew said:

neilalexander wrote a kickass guide to how state resolution works and should be implemented:

and then

Kaushik Chakraborty wrote an awesome NixOS tutorial for setting up Synapse+Riot+Jitsi as a response to my Debian one!


...and Pablo Fredrikson recorded a fantastic video run-through in Spanish of setting up Synapse on Docker!

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 to experience the fun live, and to find out how to add YOUR server to the game.

RankHostnameMedian MS

Final Thoughts πŸ’­

While discussing the use of QML in Nheko, aa13q became extremely energised, so I'm including this piece:

Qt/QML fanboy here, feel free to skip, just a love letter to the framework :D

Qt/QML is super-awesome, it's hard to describe how pretty declarative syntax is and how beautiful MVC approach with native Qt C++ side integration %) It is very hard to contribute to HTML/CSS/JS projects when you have seen QML once.

Talking about resources, there are even projects for very low-level embedded boards with arm cortex m7 core [1,2]

I'm actually thinking Qt is the bright future of very wide development areas. I'm both frightened and intrigued looking at relatively low popularity of the project. Since I want it to live and prosper even more but afraid of the possible mistakes for even harder tasks. The better popularity of the project will be harder to coordinate and the future tasks will be even harder. Similar to other cool projects (like matrix! :) I guess it's very challenging to balance between running as hard as you can and not to "die" from exhaustion %)

I don't even know is there something similar comparing to the Qt project, that's also why I'm worried about the future of the project %)

So-called software crisis (the late 60s – mid-80s [3,4]) was successfully overcome by introducing Object-Oriented Programming (it's always funny to see some people who are more into functional programming hates OOP in that context [5]) And notably Alan Kay is not only OOP pioneer (Smalltalk language) but also a first GUI applications developer. While the current OOP languages like Java and C++ are quite imperative, OOP is not only about the objects but also about the messages between them (Smalltalk is probably a nice example here too).

Qt in that context restores interesting balance to quite imperative C++ introducing the so-called meta-object system (for the messaging between objects). After that in ~Qt5, the declarative QML approach was introduced to develop these ideas even more. Not only GUI subject matter could be expressed with QML (like Qt Quick), but the others too (for example, QBS build system).

Sorry for typos and poor style, not a native speaker :) And I could be wrong in my views.

[3]: Cox, Brad J. There Is a Silver Bullet // BYTE Magazine, October 1990.
[4]: Dahl, Ole-Johan. The Birth of Object Orientation: the Simula Languages / Owe, Olaf; Krogdahl, Stein; Lyche, Tom (eds.). From Object-Orientation to Formal Methods. Essays in Memory of Ole-Johan Dahl. New York: Springer, 2004.

That's all I know 🏁

See you next week, and be sure to stop by with your updates!

This Week in Matrix 2020-04-09

09.04.2020 00:00 β€” This Week in Matrix β€” Ben Parsons

Open Tech Will Save Us #1

This week we held the first in a series of virtual meetup events, Open Tech Will Save Us.

We were really excited to make this event feel like a real meetup - with a live chat, and interactivity from the chance to ask questions of the speakers. There was a great response, with participants in a 100+ user room chatting about the talks and generally adding to the atmosphere.

Lineup included:

Dept of Spec πŸ“œ

anoa said:

Here's your weekly spec update!

MSC Status

Merged MSCs:

  • No MSCs were merged this week

MSCs in Final Comment Period:

  • No MSCs are currently in FCP

New MSCs:

Spec Core Team

This week the Spec Core Team will be focusing on MSC2457 (password invalidation), MSC2454 (SSO UI Auth), and MSC2472 (Symmetric SSSS), which each have proposed FCPs in flight.

Before next TWIM we'll be carrying out a long-overdue retro to go over how we've been doing in the last few months. We'll then continue to do those regularly once a month and post conclusions from those meetings here.

Dept of Servers 🏒

Conduit (New Rust Homeserver)

timo told us:

This week was really successful for the homeserver project. Not only does event sending and syncing work properly, but creating/joining rooms, state events and the public room directory works as well. But the biggest archievement I made this week is Riot support.

Big thanks to MTRNord for fixing bugs in Riot web and deploying an instance of Riot with all patches applied and to jplatte and @iinuwa for improving the ruma libraries.

Today we did the first actual test of the new homeserver. We had ~5 people sending and syncing messages in a room and all of them were able to send messages almost instantly. We'll see how well that scales when we implement federation in the future.

Check out the repository on and our Matrix room on If you want to try out the server yourself, you can try to connect to it using (though it might be offline when you read this)


Dendrite / gomatrixserverlib

Neil Alexander told us:

  • Support code for version 3 and version 4 rooms has now been merged.


Neil told us:

The main focus continues to be performance and we are starting to make good progress in figuring out how to split out and shard the event streams. This is a project where most of the bang will come all at once, rather than there being multiple small incremental improvements.

Aside from that we continue to improve the SSO experience, landing UIA support for CAS providers. We also made a small change to the default behaviour so that only room admins can enable e2ee (applies to new rooms only).

Next week, is more of the same. Expect a few short term performance improvements (specifically to help with cross signing UX) and more SSO support.

Dept of Bridges πŸŒ‰

Gitea webhooks bridge

s7evink told us:

As of this PR Gitea has the ability to directly send webhooks to Matrix. Currently it's only in the master branch, but should be in Gitea 1.12.0 which is due by May.

script for forwarding unread Wilma messages to Matrix

mijutu said:

I wrote a script for forwarding unread Wilma messages to Matrix. Wilma is a website and mobile app for teacher-parent communication. Download the script from and give feedback at

mijutu seems to lament:

Recently Wilma usage increased from occasional messages to everyday messages, so I had to do something.

vurpo gave us some background:

Wilma has been widely used and well-known in Finland for over a decade, but not sure how well-known it is elsewhere?
There was just an article (not in English) about the origins of Wilma, that was interesting
So someone got an Amiga in the 80s and decided to make a scheduling program for their local school, and add a bit of time and now there is a web interface, login for students, teachers, and parents with messaging, homeworks, grades and everything

mautrix-facebook and mautrix-hangouts

Tulir told us:

As promised last week, mautrix-facebook and mautrix-hangouts now support end-to-bridge encryption. It works the same way in all bridges, so the instructions from the mautrix-telegram wiki work for all of them.

πŸ‘¨β€πŸ’» IRC Bridge

Half-Shot reported:

Hello everyone. The IRC bridge has hit 0.17.0-rc1. This release is lighter than past releases, but fixes a few nasty bugs. Please test and report back :)

Highlights include:

  • Disconnect a PM room from IRC when another user is invited, and disallow invites to PM rooms.

  • On name change, inform Matrix users, if their preferred IRC name is taken.

  • Add ability to deactivate users permanently via the DebugAPI.

  • Two bugfixes on the !storepass feature, both bugs would cause the user to be unable to use the bridge 😟.


mx-puppet-bridge is a general bridging library that supports (double)bridging and relays. The goal is to make it as easy as possible for others to bridge new third-party protocols to matrix. Support room Donate

sorunome offered: also supports plumbed rooms now. That means that this one little library supports all types of bridges mentioned in Yay!

Skype bridge in matrix-docker-ansible-deploy

Slavi told us:

Thanks to Rodrigo Belem's efforts, matrix-docker-ansible-deploy now supports bridging to Skype via the mx-puppet-skype bridge. See our Setting up MX Puppet Skype bridging documentation page for getting started.

ofono SMS/MMS bridge

Somehow it seems we never previously featured untidylamp's ofono SMS/MMS bridge. This is a Python3 project to bridge Matrix and SMS/MMS messages via ofono.

They say:

I'm running this with ubuntu touch on my nexus 5. The goal is to have this hosted on my PinePhone.

integration for Kallithea

andrewsh announced:

speaking of integrations, I wrote an infra-basic integration for Kallithea three years ago:

Dept of Clients πŸ“±

Riot Web

Ryan said:

v1.5.16-rc.1 is now available at with quite a few things, including:

  • default in-app home page for new users

  • a simpler SSO sign in flow

  • SSO user authentication support for flows like removing sessions (requires homeserver support as well)

  • better read marker behaviour for grouped events like room creation

  • support for Jitsi configuration via .well-known from the homeserver

  • lots of cross-signing polish

Overall, the team is focused on finishing up cross-signing which is targeting release next week (assuming there are no surprises). πŸŽ‰


valere said:

Wild SQLDelight migration branches popup'ed in PR

Main Focus is still on getting cross-signing out No release this week, but here is develop change log:

Develop Change log:

Features ✨:

  • Cross-Signing | Bootstrapping cross signing with 4S from mobile (#985)

Improvements πŸ™Œ:

  • Cross-Signing | Setup key backup as part of SSSS bootstrapping (#1201)

  • Cross-Signing | Gossip key backup recovery key (#1200)

  • Show room encryption status as a bubble tile (#1078)

Bugfix πŸ›:

  • Cross- Signing | After signin in new session, verification paper trail in DM is off (#1191)

  • Failed to encrypt message in room (message stays in red), [thanks to pwr22] (#925)

  • Cross-Signing | web <-> riotX After QR code scan, gossiping fails (#1210)


Tulir told us:

gomuks got some minor improvements:

  • commands to download and open any files (rather than just images like before)

  • a toggle for markdown and html input


Manu said:

We continued to improve the implementation of cross-signing. One of added features is the gossip of the private key of the key backup: when you complete the security on a new sign-in, this new device automatically retrieves all message keys from your key backup. All your e2ee history is available with no additional effort.

Meanwhile, we have been updating the Riot iOS codebase to better support iOS 13 SDK and Xcode 11.x. Check for the progress of this work.

Dept of SDKs and Frameworks 🧰

libQuotient 0.6 beta

kitsune announced:

libQuotient 0.6 beta is out - developers and packagers are most welcome to try it out and iron the wrinkles before the release. This release is not too different from libQMatrixClient 0.5.3 that already incorporated many fixes from the main line; however, it includes: the new name (libQuotient, that is); proper rate-limiting (wait times advised by the homeserver are respected); the library is less prone to crash at logout and closing a connection; and, finally, initial work on E2EE done over the last year's Google Summer of Code is included in the library now. The list is fairly brief, as I didn't have too much time to work on Quotient in the last 6 months; but now that my switching jobs and continents is more or less complete, we're going to move faster.


jplatte reported:

Endpoints are continually being updated, and instead of just repeating this vague statement again and again, here is a number: at least 60% of our endpoint definitions are up-to-date with r0.6.0.

We're also getting lots of feedback from conduit's development. Some of things we're now planning to change based on that will require large-scale refactorings that haven't yet started, but will hopefully happen in the coming months.

matrix-rust-sdk progress

poljar said:

The matrix-rust-sdk is steadily progressing, improvements have been made on many fronts thanks to devinr528 (better event emitting, easier tests, room name calculation...).

The encryption side of things has been going on as well and a sneak peek can be found here

Dept of Ops πŸ› 

matrix-docker-ansible-deploy Jitsi

Slavi announced:

matrix-docker-ansible-deploy's Jitsi setup has seen lots of improvements around authentication, thanks to teutat3s. Refer to our Jitsi docs page for getting started or to learn how to rebuild your existing Jitsi installation in a more secure manner.

I asked: does this include the most recent version?

Slavi said:

it should! We've updated all Jitsi images today and reworked some things, due to a new release from the Jitsi guys, which fixes some security issues.

Dept of Bots πŸ€–

Send Sentry issues to a Matrix room

jaywink offered:

If you want your Sentry issues to a Matrix room, there is now a new bot for that: . Currently it supports a simple "projects to rooms" mapping and should work with both legacy webhook integrations and integration platform webhooks.

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 to experience the fun live, and to find out how to add YOUR server to the game.

RankHostnameMedian MS

That's all I know 🏁

See you next week, and be sure to stop by with your updates!