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.
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
...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.
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.
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!
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 😇
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!
