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.
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.
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
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.
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
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: True in their homeserver.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.
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.
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.
It's another week, and there's been steady progress on a few MSCs. Other than those listed above, there was a partial implementation of MSC4133: Support for custom profile fields for Synapse. Personally I find the prospect of finally being able to attach arbitrary profile information to users. Very exciting!
We imagined The Matrix Conference as a gathering place for hackers, project managers, digital sovereignty leaders, and innovators. I’m proud to announce that we definitely succeeded in building a schedule covering that range of topics!
We received more than 60 high-quality proposals and ended up building 5 tracks over the course of 2 “core” conference days. The tracks cover everything from sovereignty and collaboration in the public sector to digital rights, Matrix internals, the social impact of Matrix, and Matrix as the foundation for products.
With more than 60 very high quality proposals, it's been difficult to select talks that would make it to the conference.
We are thrilled to announce the schedule of the conference, and we're looking forward to listen to that fantastic line up tell us about the future of Matrix, Matrix in the public sector, Matrix in the wild, or the social impact of Matrix!
If you're an organisation and want to get some visibility in the Matrix ecosystem, we have a few sponsorship packages left at https://2024.matrix.org/sponsor/.
Don't forget to book your ticket to attend. Head to https://2024.matrix.org/register/ and tell us whether you want merch or not in addition to your ticket!
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 is one outstanding concern on this MSC for improved clarity, however the author appears to have already addressed this point. Looks like it's only a matter of time before FCP beigns on this one.
Requires 1 more tick from the SCT (Started the week needing 6)
Once again, thank you to everyone who is writing PRs against matrix-spec, especially Johennes and Kladki who combined have had lots of PRs (and MSCs!) created and merged recently. Cheers!
The enthusiasm around The Matrix Conference is simply mind-boggling! In less than 2 weeks, the project leads of state-sponsored deployments, key digital rights activists and the Matrix community at large sent us more than 60 high-quality proposals 🤯
We're really excited to help the key players in the ecosystem meet in Berlin, and I can't wait to see the fantastic talks people are working on. While the team works on producing a proper schedule for it, organisations that want to increase their brand awareness in the Matrix Ecosystem can still sponsor the conference. Let your marketing department know, pass them our sponsorship brochure!
This week at Element, Benoit walks us through how he checks that the translations are consistent in Element, and Hugh tells us everything about the awesome QR Code Login in Matrix Auth Service!
This week we released Synapse v1.110.0rc2, which contains experimental support for account suspension, report room API, more native Sliding Sync functionality and more.
Check out the release notes for more details! Also, if you can, please test v1.110.rc2 in non-critical environments.
(Note: I've linked to rc1 release notes, since all the changes are in rc1, which unfortunately was only partially released due to a packaging issue. rc2 fixes this.)