Several potential speakers asked us to extend the deadline of our CfP for the Matrix Devroom at FOSDEM. We are extending the deadline to Friday 8th December. You will find below the Call for Participations amended. Please submit your talks to https://pretalx.fosdem.org/: we're looking forward to reading them!
Unfortunately no Matrix Live this week, your host and editor apologises for the inconvenience!
Josh Simmons says
This week we were sorry to announce that we are not able to bring the Libera.Chat bridge back online. We have already begun working through clean up tasks, such as clearing ghosts, and expect to be done by December 22. If you see any bridge artifacts left past that point, please let us know.
We know that many communities and individuals were relying on the bridge, and we regret the impact this situation has on them.
If you are one of those who have relied on the bridge in the past, you may be asking: what now? You do have options.
People who need a bridge for their community can run their own: the matrix-appservice-irc software is still maintained. Only its Libera.Chat instance, which was configured to persist connections across restarts, is being shut down. Please be mindful of the network, and read Libera.Chat’s recommendations and their Matrix FAQ when doing so.
For more information, read our full announcement and Libera.Chat’s announcement.
Christian Paul (jaller94) reports
Wikidata is an open knowledge base, containing structured information to be read by humans and machines. I love it and I contribute to it a lot.
This week, I added a few more items from the Matrix ecosystem which I want to highlight:
You may have heard of this event series called Matrix Community Summit (Q123583505). In the past, we've had the Matrix Community Summit 2022 (Q123583515) and the Matrix Community Summit 2023 (Q123583556).
One output of these community summits is the Matrix Salon Podcast (Q123583531), which is a podcast featuring community members. Check it out! After all, you already seem to be interested in Matrix (Q22906785) given you're currently reading This Week In Matrix (Q123583570).
Hey all,
We’ve just pushed out Matrix 1.9! Our last release was Matrix 1.8 and brought us a whole new room version. Matrix 1.9 continues a theme of an annual maintenance release, bringing with it mostly clarifications and bug fixes.
Today’s release sees just 1 MSC formally merged to the specification, though this is expected for a maintenance release. For the last 2 months (and beyond), we have largely been focused on changes which haven’t settled enough to be MSCs yet, such as interactions with the More Instant Messaging Interoperability (MIMI) working group at the IETF.
This post covers a lot of what we’ve been up to for the last few months, and what we expect to get done for the Matrix 1.10 release cycle. As always, the full changelog for Matrix 1.9 is at the bottom of the post :)
One of the major features of Matrix is its ability to connect multitudes of messaging providers with a common communications fabric - a feature that is extremely useful in light of the EU’s Digital Markets Act (DMA) which requires gatekeepers to interoperate with other messaging providers.
We’ve been working with the MIMI working group at the IETF to establish a federation protocol for DMA-style messaging alongside our own experiments like MSC3995: Linearized Matrix. The proposed protocol for MIMI is based upon the Linearized Matrix work, but is primarily designed for an MLS-centric environment.
Discussions and experiments will continue over the next several months, and you can read all about our progress so far in TWIM 2023-11-10.
We mentioned in Matrix 1.8’s release that we’d be taking a look at MSC2545, MSC1951, MSC4027, and MSC3892 - a family of MSCs collectively called “custom emoji/stickers”. Our review started relatively late in the Matrix 1.9 release cycle (sorry), and we started thinking about interactions with MSC3916/MSC3911 where media is linked to a specific event.
We haven’t had a chance to really dig into the specific possible concerns on these two features overlapping, but do welcome feedback and suggestions for what might impact custom emoji/stickers over on our dedicated tracking issue. We’ll continue working through the problem space in the Matrix 1.10 release cycle, and hope to get both linked media and custom emoji/stickers up for FCP.
With each release we aim to have a plan for what the next release will look like, giving us a direction or theme to follow. Noting that the next release cycle has a lot of holidays (and FOSDEM) in it, we’ve got an initial list of things to look at, grouped by theme:
This list is not final and will be iterated upon over the next couple of weeks. If you’ve got an MSC to add or remove, let us know in the SCT Office on Matrix. For all of the MSCs above, we aim to get them to a FCP-accepted state at a minimum, and merged to the spec if time permits (and makes sense - looking at you, Extensible Events).
Matrix 1.9 is a relatively light maintenance release, but it still has a changelog! Read on for full details.
Backwards Compatible Changes
Spec Clarifications
m.call.negotiate schema and example. (#1546)via property is required for m.space.parent and m.space.child as per MSC1772. Contributed by @PaarthShah. (#1618)/publicRooms API that the server name is case sensitive. (#1638)m.room.name event with an absent name field is not expected behavior. (#1639)GET /initialSync. (#1647).m.rule.suppress_notices push rule not being valid JSON. (#1671)event_property_is and event_property_contains push conditions to PushConditions object. (#1673)fallback property set to true. (#1676)Spec Clarifications
m.receipt EDU. (#1636)No significant changes.
No significant changes.
No significant changes.
No significant changes.
Spec Clarifications
Backwards Compatible Changes
Spec Clarifications
m.mentions object. (#1635)m.receipt event in Client-Server API. (#1637)fieldname in appservice Protocol definition. (#1646)Today we are sorry to announce that we are not able to bring the Libera Chat bridge back online. We have already begun working through clean up tasks, such as clearing ghosts, and expect to be done by December 22. If you see any bridge artifacts left past that point, please let us know.
If you are one of those who have relied on the bridge in the past, you may be asking: what now? You do have options.
People who need a bridge for their community can run their own: the matrix-appservice-irc software is still maintained. Only its Libera Chat instance, which was configured to persist connections across restarts, is being shut down. Please be mindful of the network, and read Libera Chat’s recommendations and their Matrix FAQ when doing so.
uhoreg reports
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:
- No MSCs were accepted this week.
Closed MSCs:
🔗Spec Updates
Matrix 1.9 is due out next week. Keep your eyes peeled for an update.
Andrew Morgan (anoa) announces
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:
- MSC4080: Cryptographic Identities (Client-Owned Identities)
- MSC4079: Server-Defined User Home Pages
- MSC4078: Transparent pusher creation
- MSC4077: Improved process for handling deprecated HTML features
- MSC4076: Let E2EE clients calculate app & E2EE-room badge counts themselves
MSCs in Final Comment Period:
- No MSCs are in FCP.
Accepted MSCs:
- No MSCs were accepted this week.
Closed MSCs:
🔗Spec Updates
Cross-posting from TravisR's announcement in the Office of the Spec Core Team room...
🔗Matrix 1.9
The next release, Matrix 1.9, is scheduled for release on Wednesday, November 29, 2023. This will largely be a maintenance release, but if there's anything you think we might have missed, please let us know.
🔗Matrix 1.10
The Spec Core Team is now accepting MSC and feature suggestions towards the Matrix 1.10 release, due sometime around FOSDEM in February (unsure if it'll be before or after). So far we've got the following features up for consideration:
- Extensible Events (at least proposing FCP on the majority of the core system; plan to merge for Matrix 1.11)
- Encrypted appservices (like MSC2409)
- Custom emoji/stickers (merge)
If there's specific MSCs, or even vague ideas you'd like the SCT to focus on, let us know in the Office of the Spec Core Team room. The SCT will generally find it harder to actually write the MSCs ourselves, but if you're planning on implementing a feature that will need spec review, let us know so we can ensure bandwidth is made available for that review to happen.
🔗Random MSC of the Week
The random MSC of the week is... MSC3394: New auth rule that only allows someone to post a message in relation to another message!
This MSC is paving the way towards the use case of a room where, for instance, announcements can be made by admins, while general users can start or participate in a thread branched off from an announcement. But they otherwise would not be able to make "top-level" posts.
This feature is common in services such as Telegram, for announcement or support rooms. And it would be nice to be able to support the same kind of use case in Matrix.
It looks like I dropped the ball on keeping up with the discussion on this one. So excuse me while I go do that!
Building on last year's success, the Matrix.org Foundation is excited to host a Matrix.org Foundation and Community devroom in person this year again at FOSDEM. Half a day of talks, demos and workshops around Matrix itself and projects built on top of Matrix.
We encourage people working on the Matrix protocol or building on it in an open source project to submit a proposal! Note that companies are welcome to talk about the Matrix details of their open source projects, but marketing talks are not welcome.
Josh Simmons announces
The Matrix.org Foundation is proud to join with Mozilla, the Electronic Frontier Foundation, and over 400 security experts, researchers, and NGOs in sounding the alarm about the EU's proposed eIDAS reform.
As written, the proposal radically expands the ability of governments to surveil their citizens and residents across the EU.
We encourage citizens and residents of the EU to pay close attention and look for ways to get involved – urgently.