Weāre happy to announce that this year again we will have a DevRoom at FOSDEM!
We have half a day to talk about all the great projects we have been working on as a community. Our devroom should be on Sunday afternoon, even if itās not completely set in stone for now.
You can submit a talk following one of the two formats:
20 min talk + 10 min Q&A, for topics that can be covered briefly
50 min talk + 10 min Q&A, for more complex subjects which need more focus
Be quick, the Call for Proposals ends on December 1st and we canāt extend it. FOSDEM organizers will close all DevRooms CfPs, and we canāt bypass it!
Next Friday (November 15th) the governing board will have its first official meeting! Topics include the governing structure (how do we decide stuff), forming committees (how do we work on topics and who participates where), selecting a chair and vice chair for the board (to steer meetings) and define how we want to communicate. Some of those topics are still in flux and will be defined further throughout this week. If you are interested, your representatives might be able to tell you more and answer your questions!
We are looking forward to having our first official meeting as the board and hopefully we will have productive results to share with you all soon!
Earlier this year, the members of the Matrix Foundation voted for members from their own constituency to represent them at the Governing Board.
Nico, Bram and myself were elected to represent the Ecosystem.
While we are usually approachable and responsive in all kinds of ways, there are some topics or situations better to discuss synchronously.
We therefore starting today Wednesday 6th November start with weekly office hours every Wednesday at 17:00 German time (CET = UTC+1 during winter). šø
We will be responsive to chat in the Ecosystem Public Forum room and will also share a link to a (video) call there.
Please find more detail in the announcement post over here.
Update: Our first office hours went great! We covered quite a lot of topics both between us representatives and the community members who joined - so much so that we overran our time slot by 50% š There is going to be one more office hour next week before the first official governing board meeting, so join the office hour (or write us async) if there is any topic you want us to bring up with the governing board. We would also like to emphasise that we are offering this way of communication for you, the community, so please give us feedback over at the Ecosystem Public Forum in regard of the choice of time slot, etc.
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.
There was a flurry of PRs to the spec website itself this week. In addition to the myriad of fixes and clarifications, the underlying technology got an update!
There was no new release this week, but we have been working hard on getting a few specific things ready to go for the release.
You can expect the v1.119.0rc1 release to be out early next week.
Alongside the usual allotment of new features and bug fixes, we have been working hard on:
Lifting the minimum supported Python version to 3.9
Updating Synapse test infrastructure in order to pull in the latest version of Twisted (24.10.0)
Thank you to all our contributors for helping to make Synapse the best it can be.
As always, feel free to stop by #synapse:matrix.org to join in on the discussion and if you encounter a bug make sure to report it here.
Iāve also dabbled in some MbedTLS support, but it is still unstable(and slow), done slightly more work with avatars, and fixed some known bugs that would make handling Parsee annoying.
As of next(v0.3 will probably be out by 2025), I am mostly working on optional
Janet extension support, to make Parsee even more powerful and extensible.
We released a new version of Tammy including some UI fixes for older Android devices. For those who are hearing about Tammy for the first time: Tammy is a new multiplatform Matrix messenger powered by Trixnity Messenger.
This is the first 0.0.97 pre-release primarily focused on migration to libQuotient 0.9. Not much to talk about aside from this. The release notes and some prebuit binaries can be found at the usual place.
In the new RC EX iOS will be capable of also receiving verifications requests through the SAS protocol (while before was only able to send them)
We also added a toggle to enable media optimisation that will process media files, to save up data and memory space by compressing them. The option is on by default but can be turned off
The work for implementing sending, receiving and accepting/declining knocks on rooms is progressing
Alongside knocking we are also implementing management of room aliases
Weāll begin by discussing technical and under-the-hood updates before moving on to UI features.
SYNAPSE_ADMIN_VERSION env variable
Starting from the least interesting - if you want to build Synapse Admin yourself in an environment where git is unavailable,
you can now use SYNAPSE_ADMIN_VERSION env var to set version, instead of relying on git tags.
Logout that actually does the job
Earlier, the logout did send a request to the Matrix logout API endpoint, but didnāt clean up things like local storage that is used as a state/session store. Well, now it does š¤·
Proper restrictBaseUrl despite its type
Previously, you could limit Synapse Admin instance to work with specific homeserver(-s) using the restrictBaseUrl config var that accepted both string (like "restrictBaseUrl": "https://example.com") and slice (like "restrictBaseUrl": ["https://example.com", "https://example.net"]). Such an approach has proven to be problematic in multiple cases, but today the last inconvenience with it has been solved - now single-item slices will be treated the same way as the string does (and yes, they are treated differently in the UI), using the only value of the slice.
Configuration in /.well-known/matrix/client
We found out that people tend to use Synapse Admin instances hosted outside their actual servers, and even use a single Synapse Admin instance to manage multiple servers. Unfortunately, such a setup means you canāt rely on the config.json file that comes with Synapse Admin instance because it wonāt contain server-specific configurationā¦ So, here is the solution - just add configuration to your /.well-known/matrix/client file under cc.etke.synapse-admin key, here is an example of how to mark mautrix-telegram puppets as appservice-managed users:
when creating or updating users. With this change, a new button has been added to the userās create/update form where you can generate a random password in 1 click.
Experimental Features and Rate Limits controls are here!
As of today, 10391 Matrix federateable servers have been discovered by matrixrooms.info, 3184 (30.6%) of them are publishing their rooms directory over federation.
The published directories contain 22281 rooms.
See you next week, and be sure to stop by #twim:matrix.org with your updates!
To learn more about how to prepare an entry for TWIM check out the TWIM guide.
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.
