🔗Matrix Live

🔗Dept of Spec 📜

Andrew Morgan (anoa) {he/him} says

Here's your weekly spec update! The heart of Matrix is the specification - and this is modified by Matrix Spec Change (MSC) proposals. Learn more about how the process works at https://spec.matrix.org/proposals.

🔗MSC Status

New MSCs:

MSCs in Final Comment Period:

Accepted MSCs:

Closed MSCs:

  • No MSCs were closed/rejected this week.

🔗Spec Updates

Lots of new MSCs this week - thank you to everyone proposing new ideas or clarifications to the spec!

We have just one MSC this week from the Tuesday pings. Get it below.

  • MSC3572: Relation aggregation cleanup (disposition: close)
    • Since this MSC was written, it has been shown that having (unstable) prefixes in the unsigned field of events is useful. Hence the general consensus from the SCT has been to close this MSC as it stands.
    • Needs 1 checkmark from the SCT (started the week needing 2).

🔗Dept of VoIP 🤙

Andrew F announces

🔗VoIP call membership reliability

The VoIP team is hard at work finalizing the foundations of MatrixRTC. The current main topic is "reliable call member state", which has many different possible solutions and is very important to get right.

We've been making progress, and this week we can share a demo of the first implementation of reliable state, shown in the video below this post.

Here's an explanation of the demo:

- Two users join a call, and each users' client sends a state event to communicate its membership in that call. The room state is used to render the call participant count.
  • Then, one of the users forcefully closes its Element Call tab, and cannot send anything to the homeserver anymore.
  • But, in just a few seconds, the other user sees the call participant count drop. This means the room state was "magically" updated even though the client of the user who left is disconnected!

Why this is so important and how this is achieved can be found in the Matrix Live video of this week (at the top of this TWIM entry).

For the technical details on how the demo works, see MSC4140 for the basis of its implementation of the participant count cleanup.

A demo of two users doing a voice call

🔗Dept of Servers 🏢

🔗Synapse (website)

Synapse is a Matrix homeserver implementation developed by Element

Matthew says

Native Sliding Sync in Synapse is coming. Not remotely ready for primetime yet, but we sent the first ever traffic from Synapse with native sliding sync through to Element X on Wednesday, and it looked like this:

A demo of native sliding sync in Synapse using Element X

A demo of native sliding sync in Synapse using Element X

🔗Dept of Bridges 🌉

tulir says

I wrote a blog post about writing a new bridge using the megabridge architecture introduced in my previous post: https://mau.fi/blog/megabridge-twilio/

🔗Dept of Clients 📱

🔗Kazv (website)

kazv is a convergent matrix client and instant messaging app.

tusooa reports

We got a new developer for the Kazv Project, April Simone (@apr_simone:matrix.org, https://lily-is.land/apr3vau ). She has been doing incredible work, including a patch to display a preview of room members on the room settings page. Lots of thanks to her!

🔗Dept of Ops 🛠

🔗matrix-docker-ansible-deploy (website)

Matrix server setup using Ansible and Docker

Slavi announces

matrix-docker-ansible-deploy has upgraded its default reverse-proxy server Traefik to the recently released version 3. See this blog post to learn about its new features.

Since HTTP/3 support is no longer considered experimental in Traefik v3, the playbook now enables it by default.

See our Traefik v3 and HTTP/3 are here now changelog entry for details.

Slavi says

matrix-docker-ansible-deploy has added support for matrix-alertmanager-receiver - a component helpful to those wishing to more easily integrate Prometheus' alerting service (Alertmanager) with Matrix.

See Setting up Prometheus Alertmanager integration via matrix-alertmanager-receiver for more details.

🔗In the News 📰

Matthew says

https://www.foundation.org.uk/Blog/2024/A-call-for-action-and-a-roadmap-for-the-new-UK-gov is an interesting proposal to the new UK Government to support open source, using Matrix as an example!

🔗Matrix Federation Stats

Aine says

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

As of today, 9576 Matrix federateable servers have been discovered by matrixrooms.info, 2930 (30.6%) of them are publishing their rooms directory over federation. The published directories contain 161312 rooms.

Stats timeline is available on MatrixRooms.info/stats

How to add your server | How to remove your server

🔗Dept of Ping 🏓

Here we reveal, rank, and applaud the homeservers with the lowest ping, as measured by pingbot, a maubot that you can host on your own server.

🔗#ping:maunium.net

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

RankHostnameMedian MS
1girlboss.ceo263
2awawawawawawawawawawawawawawawawawawawawawawawawawawawawawawaw.gay303
3sulian.eu359
4plocki.org375
5uwu.sulian.eu423
6hacklab.fi453
7mx.scalie.zone503
8pain.agency534.5
9codestorm.net566
10awawi.nexus576

🔗#ping-no-synapse:maunium.net

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

RankHostnameMedian MS
1girlboss.ceo116.5
2doctoruwu.uk139
3awawawawawawawawawawawawawawawawawawawawawawawawawawawawawawaw.gay160.5
4hacklab.fi194
5h.hackclub.app198
6cwt.grin.hu261
7uwu.sulian.eu319
8puppygock.gay371.5
9reallyaweso.me375
10inu.is377

🔗That's all I know

See you next week, and be sure to stop by #twim:matrix.org with your updates!

The Foundation needs you

The Matrix.org Foundation is a non-profit and only relies on donations to operate. Its core mission is to maintain the Matrix Specification, but it does much more than that.

It maintains the matrix.org homeserver and hosts several bridges for free. It fights for our collective rights to digital privacy and dignity.

Support us