We had our first Governing Board gathering today at the Matrix Conference in Berlin, with 17 of the 20 members present (4 of which joined remotely)! We got to know each other a little better and discussed many things including Trust & Safety and how we communicate with each other and with the community.
Since this wasn't an official meeting, no votes were taken. The first official meeting of the Governing Board will be taking place soon!
The Matrix Conference 2024 is over, the videos are being cooked and the slides are being uploaded.
We'll be sharing the recordings with you as soon as they're ready.
In the meantime, a big thanks to everyone who attended, spoke, and helped make it happen. We hope you had a great time and learned a lot about Matrix and the community. We hope to see as many or more of you next year!
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.
Hello from the Matrix Conference 2024! richvdh, matthew, tulir, travisr, kitsune and I (anoa) are around - come find us at the conference if you want to talk spec!
And a final call to developers, protocol designers, and future MSC writers to attend the "Authenticated media & how to ship spec features" and "MSC Process Guidance" talks in LAB 4 at this year's Matrix Conference! We'll be discussing the spec process itself, as well as how large features (and breaking changes in the spec) get designed, developed, and deployed with support from the MSC process.
If you're thinking about how to get your idea for a feature out in the hands of users, these talks are for you!
Haven't worked that much compared to the last three months(kinda am
at a somewhat important year with school), but I've fixed up some
issues and started adding PEP avatars this week, with VCard-based ones
coming right up later, and got up static CI builds with some experimental
MbedTLS to replace the previous OpenSSL/LibreSSL in that regard(bringing in
binaries in the ~2MBs compared to the previous 5(!)).
Will probably be working on more important user concerns, mostly
involving the syntax for bridged users/MUCs and actual documentation for
regular users, though except slightly less time allocated to the project,
as I said, I got school, and a slightly more interesting project I have
to contribute to that has already gone pretty far!
This month's mautrix releases include the first megabridge releases of the Meta and Google Messages bridges, as well as a new Google Voice bridge. On the non-bridge side, I started a new project for some reason: Meowlnir. Read the full post at https://mau.fi/blog/2024-09-mautrix-release/.
We are thrilled to announce that WorkAdventure β the open, decentralized platform for building 2D virtual offices and events β is now also a Matrix client! Every WorkAdventure user will now have a Matrix account automatically created.
This is a huge win for WorkAdventure users. Even when someone is not connected to WorkAdventure, they can still be contacted through a Matrix client like Element X on a mobile phone, directly from WorkAdventure.
We believe this will also be a significant benefit for the Matrix community, as it opens a new use case for Matrix that makes it stand out from other messaging apps.
Tweak your Matrix rooms in style. You can now choose your own UI colors in Matrix Wrench.
If you're working with Live Location Sharing (MSC3488, MSC3672), you may want to debug it using Matrix Wrench. It supports a static string, the browser's Geolocation API, and GPX files as input. When selecting a GPX file, it replays the recorded track in real time."
I'm thrilled to announce the release of Trixnity 4.7. It basically adds support for Matrix 1.11, ensuring that Trixnity stays up-to-date with the latest protocol standards. Additionally, users now have the ability to cancel message sending while the media of a message is being sent. There are several internal improvements and some bugs have been fixed in this release as well.
Support for authenticated media has been implemented. You should be able to load images again!
Single HTTP client implementation has been merged, network connections should now be more responsive!
Unit tests have been fixed, this should help catch bugs more reliably to ensure stability
JSON canonicalisation code has been merged, which passes all tests from spec. If you find an incorrect case, please do submit patches to add them to the unit tests!
Fixed a bug where joining a room that allows viewing history without joining would fail.
Fixed a bug with sending state events that contain special characters in state keys (eg. /). Bots & clients no longer need to work around this.
Added a function to the base Policy content class to calculate a Draupnir-compatible state key, this allows moderation bot authors to easily be in line with Draupnir's state keys :)
Add some more utility functions to make developer UX more friendly.
Reduced log output so you can follow what's actually going on.
Fixed a bug that causes sync to break completely due to trusting event schemas too much.
πChanges on ModerationClient's LibMatrix branch
Support for storing sync data offline, allowing users to not do an initial sync every time the app is reloaded
Fixed some bugs with how sync changes are processed. Messages should no longer disappear
Optimised sync processing, didn't benchmark but it's noticeably faster for most users. Maybe by a factor of 20x?
Added support for a whole load of Synapse admin API's. Client authors can now include support for deactivating users, managing the media repository, and so much more!
Partial support for Custom profile properties (MSC4133), though this will land in main branch independently!
Licensing: Have you been put off by our choice of AGPL v3? We'd love to hear about it! Is there a better license we could use? Do you have suggestions on how we could maybe implement exemptions?
Packaging & testing: We would like to get a CI pipeline and packaging going. Are you experienced with Git? We'd love to have you on board to ensure that our packages are as easy to install & use as possible!
Public code browsing accessibility: Would it help to set up read-only GitHub/GitLab/Codeberg/Forgejo mirrors? Would you be interested in contributing if these existed?
E2EE: Do you have experience with Matrix' E2EE? We'd love to hear from you in terms of implementing it in LibMatrix!
If you want to help out on these topics, please feel free to reach out at #libmatrix:rory.gay!
(N.B. Sorry, matrix.org users, the room is currently inaccessible. We hope to have this resolved soon!)
Lots of tools have been added, updated or reworked since the original post back in May!
A short list of major changes:
A general tool list has been added, as well as a Labs section! Visit your nearest RMU instance to learn all about them!
Policy list editor can create new policies (even in bulk!, though beware, bulk addition is still very much in beta, "works but no guarantees")
Bulk writing of bans via Policy List Editor has deprecated the "Mass CME Ban" tool, which had been written to cover a very specific use case. This opens up the tooling for a lot more users, especially when dealing with spam waves!
Partial support for the concept of authenticated media, though I'd like to raise a severe epilepsy warning!
Lots of stability and improvements due to upstream Rory&::LibMatrix changes and improvements
Some tools have seen a 60%+ performance improvement! (Policy List Editor mainly)
Membership history viewer is now more informative about what actually changed, enabling more uses for the tool
Joining a space's children is now recursive
The "first party" instance is available at https://mru.rory.gay, and is a clientside-only web app!
If RMU has provided value in your daily routines or as a one time thing, please do consider donating over at Liberapay!
As of today, 9926 Matrix federateable servers have been discovered by matrixrooms.info, 3064 (30.9%) of them are publishing their rooms directory over federation.
The published directories contain 22153 rooms.
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.