Matrix Live 🎙
Loads of coverage is available, take a look!
- see also https://thestack.technology/element-messenger-matrix-protocol-one-to-watch/
Dept of Spec 📜
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://matrix.org/docs/spec/proposals.
- No MSCs were merged this week.
MSCs in Final Comment Period:
Spec Core Team
In terms of Spec Core Team MSC focus for this week,
Room Version 8 has been proposed as part of MSC3289! This intends to include the new "restricted" room version from MSC3083, which allows access to a room based on one's membership in another room, as is most useful for features related to Spaces.
sorunome has been working on MSC2545:
Sorus Image Packs MSC2545 is taking shape more and more! While barely anything happened on the actual MSC itself, nheko recently implemented a sticker picker based on it, and there is a PR for fluffychat for a sticker picker, too, finally making stickers interoperable between clients of different vendors!
Here's a video of fluffychats sticker picker in action: https://gitlab.com/famedly/fluffychat/uploads/26382317e2424d7566eb18e102ddd6cb/fluffy-sticker-picker.webm
Dept of Servers 🏢
callahad told us:
🚨 Yesterday we published Synapse 1.38.1 which mitigates a client bug triggered by changes to /sync responses in 1.38.0. Specifically, new Element Android sessions were unable to decrypt messages in end-to-end encrypted conversations.
⚙️ Otherwise, we've been doing quite a lot of internal / infrastructure work. Notably, we've completed the move from three separate CI systems to just one: GitHub Actions. We're also, for the first time, publishing Debian packages for our Release Candidates. We hope these changes move us towards a more reliable and seamless release process.
We'll have a lot to talk about re: Synapse 1.39 next week, but until then, enjoy the weekend! 🏖
Homeserver Deployment 📥️
And this week too has brought updates to my Helm Charts, with element-web being updated to 1.7.33 and matrix-synapse to 1.38.1
Dept of Bridges 🌉
Fair told us:
A bridge for LINE Messenger based on running LINE's Chrome extension in Puppeteer.
This week brings plenty of usability improvements:
There is now the
list-contactsbot command to--you guessed it!--list the Matrix puppets of all of your contacts.
It's now possible to sync a chat with a LINE user by inviting their Matrix puppet to a DM, instead of having to wait for someone to send you a message in LINE for the bridge to auto-sync it. This is especially useful with
LINE group chats that haven't been used recently are now included in the set of chats that get bridged on a
The number of chats to sync at startup time & on-demand is now configurable, as a bridge config setting & a parameter to the
These changes make it possible to sync LINE chats/groups that previously may not have gotten synced, due to the intricacies of how LINE on Chrome handles chat history (especially on first use of the bridge).
Issue page: https://src.miscworks.net/fair/matrix-puppeteer-line/issues
Dept of Clients 📱
Nheko is a desktop client using Qt and C++17. It supports E2EE and intends to be full featured and nice to look at
Nico (@deepbluev7:neko.dev) told us:
LorenDB has rewritten the invite dialog as well as the memberlist in Qml. This means they work now much more reliably and show the users in appropriate colors and a few other small improvements.
Apart from that, Nheko now has support for sending stickers! This is based on Sorunome's awesome MSC2545, so no integration manager is needed and it is trivially easy to share your sticker packs (just invite someone into the same room!). You can use stickers from your account data or upload stickers into a room so every room member can use it. If you found a sticker pack you like, you can enable a pack from a room globally by going into Nheko's room settings. You can check my current preferred set of stickers here: matrix:r/nico's-stickers:neko.dev
Currently you can't edit a sticker pack yet from Nheko. Support for that will come in the near future. Until then you can use either FluffyChat, Element's DevTools or my hack to import Telegram sticker packs into a room. Note that Nheko's sticker pack support is incompatible with integration server based sticker packs like the one Element uses. On the other hand, you don't need an integration manager to use them! Custom emote support based in the image packs MSC is coming in the future to Nheko too.
Furthermore we fixed some bugs to move E2EE in Nheko out of Beta. We are close now and we have a plan!
That's all, don't get your hands too sticky!
Alexandre Franke announced:
It’s been three weeks already since our last update and we have a fair amount of new things to report.
As I write this, our interns Alejandro and Kai are at GUADEC, the annual GNOME conference, presenting during the interns lightning talk. The former has submitted a couple of merge requests (!793 and !794) that were necessary for the UI to accommodate his upcoming multi-account work. The latter has provided a view for when no room is selected. As for their mentor, Julian, he changed member loading so it only happens once a room is opened, to improve performances. He also changed Matrix event handling to use
SyncRoomEvent, which paves the way for display of various message types in the timeline of a room.
Giuseppe offered two nice additions to the login view:
in the form, one can now type enter to login (it previously required to click on the button in the headerbar)
errors are now displayed, providing useful feedback on why the login may have failed.
And to conclude this summary, we welcome 🎉 newcomer Veli Tasalı who fixed a papercut I reported: when typing long messages, buttons next to the message entry were expanding along with the entry and now they keep nicely aligned.
- We’ve been shepherding MSC3083 into FCP to improve private spaces
- We’ve also been working on restricted room support in Synapse and Element Web & Android
- We’ve been improving onboarding experiences for Spaces, improving 3pid invites on Android, improving email invites and making matrix.to aware of spaces
- On iOS, we’ve finished the first implementation of Space navigation which we can share soon!
- We’re also figuring out what’s missing to mature Spaces enough to exit beta
- Call event tiles for 1:1 calls merged, for better summaries of call history.
- 1:1 screen sharing ready to merge!
- Looking at bug where jitsi calls stay always-on-screen even when hung up.
- Released v1.7.33
- Message bubbles PR merged!
- Updated desktop to electron 13, complete with new n-api build of seshat (thanks, Poljar!)
- More work on changelog tooling
- We cancelled the release of 1.4.6 because of the discovery of high profile bugs or crashes . We will release 1.4.7 on the App Store on Monday. Those releases contain mainly bug fixes and papercuts
- Voice messages are almost there. They are on develop under a LABS settings. They should be part of the next release candidate next Wednesday.
- There are several papercuts in progress: URL preview, decryption of notifications content by default, removal of local contacts from the DM room list tab, removal of the room directory from the group room list, etc to list the major ones.
- Release 1.1.14 which fixes an important issue regarding message decryption is live on the PlayStore, on the beta channel, and will be in production quite soon. A patch has been applied to matrix.org to fix the problem.
- Beside that, we are still polishing the spaces and voice messages
Šimon Brandner shared some images of the new VoIP UX:
Naturally the screen sharing feature will allow you to share your own screen, rather than Šimon's!
New keyboard shortcuts:
- Navigating room list with arrow keys when there's no room open (and esc to close the current room)
- Global shortcut to open Beeper
Rooms are opened where you left off (like Telegram, WhatsApp, etc) instead of at the bottom
Updated unread room indicators: a colored circle around the room avatar (screenshot here)
We've integrated the LinkedIn bridge into Beeper. The bridge is in beta and is generally ready for use. Since the last update, we moved it to GitLab, added a Docker image, and implemented reaction and redaction handling in both directions! We also fixed a bunch of bugs across the board to improve reliability.
The Android SMS bridge mentioned in the last update is progressing. It should be ready for self-hosted use in a few weeks, so our next update will probably include that.
Related to the SMS bridge, I've made mautrix-syncproxy, which is a microservice to do the
/syncing required for end-to-bridge encryption (to-device events and such) in the cloud and forwarding the data to the normal appservice transaction endpoint. When combined with mautrix-wsproxy, it allows the SMS bridge to only have a websocket connection, which uses significantly less battery than a HTTP request every 30 seconds. The sync proxy partially implements MSC3202 and the to-device part of MSC2409 (partially because it only does individual users rather than all appservice-owned users).
We're hiring React, iOS, Android and SRE/Devops engineers. If you're interested, check out https://jobs.ashbyhq.com/beeper or DM Eric Migicovsky.
Dept of SDKs and Frameworks 🧰
Ananace told us:
Just tagged and pushed version 2.4.0 of the Ruby SDK, along with an updated image for the example bot. This version adds support for the Matrix URIs as well as some basic spaces functionality, it also fixes some errors due to the removed empty
/syncfields in Synapse 1.38.0
Feel free to drop by #ruby-matrix-sdk:kittenface.studio for any questions or comments.
Dept of Bots 🤖
Hebbot (This Week in X bot)
Felix told us:
Several GNOME contributors and I have been following TWIM and really enjoyed the concept. Since open source is about
stealingsharing ideas, we wanted to deploy something similar for GNOME.
I gave this room's beloved twim-o-matic a try and fiddled a bit with the code. But I soon found that it is too specialised for matrix.org. That's when I decided to write a project agnostic TWIx bot based on matrix-rust-sdk called Hebbot!
Here is how it looks in practice with a companion website for GNOME. If you’re interested in how it looks behind the scenes, have a look at this blog post which explains how it works.
I released a first version on July 17, but I’m already working on making it smarter for a next release. In the meantime you can already use it for your project!
Love it, though I wish twim-o-matic had more of my attention! Maybe we can retire it and use Hebbot..?
Dept of Interesting Projects 🛰️
Matrix Plugin for OctoPrint
This week I have developed a new plugin for OctoPrint which is a tool for controlling and monitoring 3D printers, which sends notifications about your prints and status of your 3D printer to matrix. The existing OctoSlack plugin also has Matrix support but fell foul of the /sync response changes in Synapse 1.38, and also sent the images from the camera to Matrix as inline images rather than m.image events, so they didn't render on some clients.
My new plugin can send messages on most events supported by OctoPrint, but the core events which are configurable through the OctoPrint web UI are print started, paused, completed and failed as well as print progress notifications. If you want Matrix notifications for your 3D prints, you can install the plugin through the official OctoPrint plugin repository or by installing from the GitHub repository. If you have any feature requests or pull requests, contributions to the plugin are very welcome.
Here is a preview of a print progress notification from something I was printing last night:
Matrix in the News 📰
Matrix & IRC | Size & Stability
Following on from my post about how I'd like to convince Ansible to move to Matrix, I looked into the relative sizes of the networks, took a look at the active users in our channels, and even took a shot quantifying bridge restarts and netsplits to assess relative stability. Check it out here
New Public Rooms 🏟️
A new Beyond Chat room (#beyond-chat:matrix.org) has been created! This room is meant for discussing various projects that build on Matrix for use cases beyond chat, such as collaborative documents, blogs, generic key-value databases, tools for thought, etc. Please join if these topics interest you. 😄
The Beyond Chat chat room is where Ryan chats about uses of Matrix beyond chat
Dept of Welcomes 👐
Robert Long announced:
Hey everyone, my name's Robert Long. I've just joined Element last week and I'm coming in to work on the VoIP team. This week I started working on full mesh video conferencing and I'm super excited to share more as the work progresses!
Welcome Robert! Can't wait to see progress here. We'll even bring back the Dept of VoIP :D
Final Thoughts 💭
Room of the week
Hi everyone! Did you ever feel lost in the Matrix world? The room directory is big, but it's still hard to find something you like. Or are you a room moderator, but there is not much activity in your room because it doesn't have enough users?
This is why I want to share rooms (or spaces) I find interesting.
This week's room is: #godot:feneas.org
"A very helpful and friendly place for general discussion or questions pertaining to the FOSS Godot game engine and using it to make games, whether one is just beginning to learn or wish to discuss more advanced aspects of game (or Godot) development."
If you want to suggest a room for this section, tell me in #roomoftheweek:fachschaften.org
Royal Navy using Matrix!
Amazing to see @Navy_Innovation showing off low-bandwidth @matrixdotorg decentralised comms to 1SL (Head of the @RoyalNavy) using Titanium: our CivTAK Matrix plugin. At this rate Matrix is on track to become the common language across the entire public sector!⚓️📻🇬🇧 https://t.co/UDIA2GBVm9— Element (@element_hq) July 23, 2021
Dept of Ping 🏓
Join #ping:maunium.net to experience the fun live, and to find out how to add YOUR server to the game.
Join #ping-no-synapse:maunium.net to experience the fun live, and to find out how to add YOUR server to the game.
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