Thib

🔗Matrix Live

🔗Dept of Status of Matrix 🌡️

🔗Community Year In Review 2024

Nico announces

So, how was your year? NO! DON'T TELL ME NOW! But read on!

Some might remember the year in review for 2023 or 2022, well, this year is still 2024 and I decided to do another one!

If you don't remember, here is the gist of it: It is a room, where you can post about what you did, experienced or otherwise found interesting in 2024. You can also give some predictions for 2025, if you are so bold! Then, on the 31st, I will compose those into a blog post and you can read what others had to say! Now, the exact dates are a bit muddy, last time I was late and there is no guarantee I won't be late this time, but you have until the 30st to compose something you want to share.

There are no exact restrictions on what projects can participate or that what you share has to be a project, but we try to ring out the year with positive vibes from the community in general. Please also try to look at the overall year, if you just want to report on the week, well, there is something called "This Week in Matrix" for that!

Now, you probably are asking the important question, where is that room? Well, you can guess it from last years alias, but for everyone else:

Join #year-in-2024:neko.dev!

Have a good one, merry christmas and see you next year!

Part time reporter, Nico

PS: If you want examples, check out https://blog.neko.dev/posts/matrix-year-in-review-2022.html or https://blog.neko.dev/posts/matrix-year-in-review-2023.html

Continue reading…

The Matrix.org Foundation has been made aware that an international investigative operation took down a service called MATRIX which was used by a cybercriminal network, which has no relationship with the Matrix.org Foundation or the Matrix protocol itself.

The takedown site has a Matrix-the-movie branding, which is a probable source of confusion. The app showcased doesn’t look like any of the Matrix clients we’re aware of.

In a statement to the Matrix.org Foundation, Europol confirmed that the MATRIX cybercriminal network and the Matrix protocol are entirely unrelated. Europol states:

The Matrix protocol (matrix.org) is by no means connected to the Matrix secured communication service that was targeted in OTF Continental.

A statement from the Dutch police confirms that this is unrelated: "Matrix is ​​also the name of a company and communications protocol of the same name, which has nothing to do with the crypto communications service Matrix."

🔗Matrix Live

🔗Dept of Status of Matrix 🌡️

Thib (m.org) announces

We want to know everything about the bugs you squashed, the features you developed, and the docs you wrote. And even better, not only do we want to know about it, we want you to tell the Matrix community about it during our FOSDEM Fringe event, or even to tell the world about it in our FOSDEM Devroom!

Our Call for Proposals is still open for the DevRoom until December 1, so don't miss your chance to advertise your project!

But we're not limiting our presence to a DevRoom, we will also organize a fringe event before FOSDEM and have a booth during the wole event. Want to grab a limited edition T-shirt? Now's your chance to sign-up and help us staff the booth. All details are in our blog post.

Continue reading…

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!

Continue reading…

🔗Matrix Live

🔗Dept of Status of Matrix 🌡️

🔗Matrix at FOSDEM 2025

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

Continue reading…

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.

Continue reading…

🔗Matrix Live

🔗Dept of Spec 📜

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:

• MSC2409: Proposal to send EDUs to appservices (merge)

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?

Continue reading…

🔗Dept of Social Good 🙆

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

🔗Dept of Spec 📜

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:

• MSC4213: Remove server_name parameter
• MSC4211: WebXDC on Matrix

MSCs in Final Comment Period:

• No MSCs are in FCP.

Accepted MSCs:

• MSC4170: 403 error responses for profile APIs

Closed MSCs:

• MSC3060: Room labels
• MSC4214: Embedding Widgets in Messages

🔗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

Continue reading…

🔗Matrix Live

🔗Dept of Status of Matrix 🌡️

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: 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.

For more information on the media freeze, check out our blog post: https://matrix.org/blog/2024/06/26/sunsetting-unauthenticated-media/

Continue reading…

🔗Matrix Live

🔗Dept of Status of Matrix 🌡️

Josh Simmons (he/they) says

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.

Continue reading…