Thib (m.org)

🔗Matrix Live

🔗Dept of Status of Matrix 🌡️

Matthew reports

Last week US Senators Wyden (D) and Schmitt (R) wrote an open letter to the US Department of Defense encouraging them to adopt Matrix more widely, rather than wasting money on unencrypted, centralised or closed systems. The letter also reveals a whole bunch of info at the end about the US Navy's Matrix deployments. This feels like a huge step change forwards - not only is the FBI encouraging citizens to use end-to-end-encryption in the wake of realisations that the public telephone network is insecure, but US Senate is pushing for Matrix adoption (without any lobbying from us, I hasten to add). You can read more about it at the Element blog (Element provides the deployments for the US Navy).

P.S. it really is bleakly amusing that we've been constantly pointing out that legislation like EU's ChatControl and the UK's Online Safety Act are catastrophically flawed because the surveillance backdoors they propose will be exploited and abused by attackers. And here we are, with the lawful intercept backdoors in the US public phone system being compromised by attackers, causing the FBI to recommend non-backdoored E2EE instead. We live in a very strange timeline.

Continue reading…

🔗Matrix Live

🔗Dept of Status of Matrix 🌡️

Thib (m.org) says

Don't forget that Matrix will be in full force @ FOSDEM:

• The CfP for the Matrix Devroom closes on Sunday, December 1
• We already have quite a few volunteers to help us with the booth, but we're always looking for more hands! People who sign up before December 15 are entitled to a limited edition t-shirt :)
• Two organizations have already shown their commitment to the community by offering to sponsor the Fringe Event right before FOSDEM. Pizzas and drinks will be covered, but if other organizations want to sponsor too we can work on more opportunities together!

Continue reading…

🔗Dept of Servers 🏢

🔗Synapse (website)

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.

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:

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

• MSC4018: Reliable call membership
  • Succeeded by MSC4140: Cancellable delayed events.

🔗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!

Continue reading…

🔗Matrix Live

🔗Dept of Spec 📜

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 😇

Continue reading…