The Matrix.org Foundation and community are very happy to announce that this year, they will be in full force at FOSDEM, with a community event right before the conference, a booth to welcome everyone during the conference, and a dev room to explore topics in depth!
Thib (m.org) says
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!
Find all the dates & details on our Call for Proposals
Hello everyone,
The Matrix.org Foundation is excited to host a Matrix.org Foundation and Community devroom in person next 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.
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:
- MSC4220: Local call rejection (m.call.reject_locally)
- MSC4218: Improving performance of profile changes
MSCs in Final Comment Period:
Accepted MSCs:
- No MSCs were accepted this week.
Closed MSCs:
- No MSCs were closed/rejected this week.
Spec Updates
Steady progress across a range of MSCs this week. Iām particularly excited to see MSC2409 to reach FCP given its widespread use. Perhaps MSC4203: Sending to-device events to appservices is next?
spaetz says
The German Data Protection Officer is creating a catalogue of criteria to assess messengers. They still take feedback till Nov 15. List of criteria is available in German and English.
Toot: https://social.bund.de/@bfdi/113306169664247379
English criterion pdf link is: https://www.bfdi.bund.de/SharedDocs/Downloads/EN/Konsultationsverfahren/3_Messengerdienste/Katalog-SMA-Front-End.pdf?__blob=publicationFile&v=2
TravisR 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:
- No MSCs are in FCP.
Accepted MSCs:
Closed MSCs:
Spec Updates
Matrix 1.12 went out last week! This release contains a few Trust & Safety improvements, bug fixes for authenticated media, an ability to mark rooms as unread, and several other quality of life features. Check it out, and get an early preview for what the next release might look like š
If thereās something youād like the Spec Core Team to take a look at, let us know in our office room: #sct-office:matrix.org
Synapse is a Matrix homeserver implementation developed by Element
Devon Dmytro announces
This week we released v1.116.0rc2. Here are a few of the highlights:
- Guests can now use the new media endpoints to download media, as described by MSC4189
- Add initial implementation of delayed events as proposed by MSC4140
- Add implementation of restricting who can overwrite a state event as proposed by MSC3757
- Add an asynchronous Admin API endpoint to redact all of a userās events, and an endpoint to check on the status of that redaction task
ā¦and a whole lot more. Check out the release notes for the full set of changes! 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.
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:
- Comparison of proposals for ignoring invites
- MSC4191: Account management deep-linking
- MSC4190: Device management for application services
MSCs in Final Comment Period:
- No MSCs are in FCP.
Accepted MSCs:
- No MSCs were accepted this week.
Closed MSCs:
Spec Updates
A further 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!
TravisR announces
Earlier in the week matrix.org started requiring authentication to access media, and it looks like most users didnāt notice (a good thing)! Smooth rollouts like this are thanks in large part to the developer ecosystem preparing users for the change with code - thank you to everyone who has been working hard at improving how media is shared in Matrix ā¤ļø.
Thereās always going to be problems which reveal themselves after the deployment happens, and it looks like most of the issues weāre tracking have workarounds or patches on the way. If youāre seeing errors for images/files, please update your client. Web users may need to refresh the page multiple times before things start working because of how browsers (donāt) work. If youāre still seeing issues, it may be a bug in your client: please report it to the developers so they can take a look.
Developers, protocol designers, and future MSC writers may also be interested in āAuthenticated media & how to ship spec featuresā in LAB 4 at this yearās Matrix Conference in just a couple of weeks! Weāll be discussing how such a massive feature (and technically breaking change in the spec) gets 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, this talk is for you. The advice should be transferable to features smaller than authenticated media too, hopefully š
TravisR announces
Something weāre excited to see is several servers have already enacted their media freeze for unauthenticated media! Matrix.org is doing so on Wednesday, September 4th, 2024 (just a few days away) during UK business hours. Other Synapse admins can enable this freeze on their servers by setting
enable_authenticated_media: Truein theirhomeserver.yaml. Admins using other server projects should consult their documentation, though please note that some projects are actively working on adding relevant support.For those interested in statistics, matrix.org is seeing about 80% of requests being authenticated so far. We anticipate this number will rise before Wednesday, but not significantly.
For more information on the media freeze, check out our blog post: https://matrix.org/blog/2024/06/26/sunsetting-unauthenticated-media/
The Foundation has updated its policy for accepting upstream contributions to our projects. We no longer require the use of ārealā or ālegalā names as part of the Developer Certificate of Origin (DCO). We thank the community members who reached out to let us know that our policy was a barrier for them, and we are excited to welcome contributions from people who were previously excluded.