MTRNord

🔗Matrix Live

🔗Dept of elections 🗳️

Josh Simmons (away, back May 9th) announces

Voting has started for the Governing Board elections and runs till May 31 – but don't delay, vote today! 🗳 Huge thanks to all of the nominees who have thrown their hat in the ring.

All eligible voters should have received an email from the election system. All of the results will be published on the blog on June 3. Read our announcement post or visit our election center for more info.

🔗Dept of Spec 📜

Andrew Morgan (anoa) 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:

• MSC4145: Simple verified accounts

MSCs in Final Comment Period:

• MSC3967: Do not require UIA when first uploading cross signing keys (merge)

Accepted MSCs:

• MSC4132: Deprecate Linking to an Event Against a Room Alias
• MSC3939: Account locking

Closed MSCs:

• MSC1951: Custom sticker packs and emoji (mk II)
  • Superseded by MSC2545
• MSC2461: Proposal for Authenticated Content Repository API
  • Superseded by MSC3916

🔗Spec Updates

As an early heads up, Trust & Safety at the Foundation is working on an important update to Matrix, MSC3916 - Authenticated Media. This change will mean that all clients (and servers) will need to present a valid access token in their Authentication header to access media - which is critical to ensure that URLs are only visible to the correct users, and prevents abuse of Matrix for hosting binaries. More details will be published as we work to get everything released - we wanted to get the information out there as early as possible in the meantime. Let us know if you have any questions.

Matrix.org plans to freeze unauthenticated media endpoints within a couple of months after the spec release, which is expected in the next few weeks. "Freezing" means that media uploaded or cached before the freeze will remain accessible via unauthenticated endpoints indefinitely, but any media cached or uploaded after the freeze will require authentication. The unauthenticated endpoints will be deprecated but will still serve old media on matrix.org.

To ensure a smooth transition, we encourage you to start testing against the unstable endpoints and unreleased server builds. The changes for Synapse are being developed here, and for MMR here. Both are expected to release their changes soon. Once MSC3916 passes FCP, stable endpoints will become available. While releasing unstable support to users isn't required, having patches ready will help speed up the rollout.

We know this is a quicker rollout than usual, but with your help, we can improve user safety and security across the ecosystem. Most clients should find this update straightforward, but if issues are encountered, please reach out in #matrix-client-developers:matrix.org or on the MSC discussion. The team is monitoring the room to help clients adopt the change.

Web browser clients might face the most challenges, given the need to specify an Authentication HTTP header on media requests, so reviewing this pull request and its dependencies could provide useful implementation insights.

Thank you for your support. If you have any questions, let us know. We look forward to a smooth transition with minimal user-visible impact 🙂

Continue reading…

🔗Matrix Live

🔗Dept of Status of Matrix 🌡️

🔗Governing Board Elections 2024 - Voting Starts on May 18, 2024

Thomas B says

Only two weeks remain until the first Governing Board Elections.

🔗Who are the nominees?

You can find the names of the nominees on the election page, but who are they, and what are their visions for the future? The nominees' campaigning has been underway since April 27. Members of the ecosystem are already quite active at #ecosystem.forum:matrix.org. Feel free to join and meet the nominees for the ecosystem members group.

Please, other constituencies, also find a place to meet, greet, and chat with members where people can get to know you better.

With Josh Simmons (away, back May 9th)'s permission, I opened the space #governing-board-nominee-campaigning-bonfire:matrix.org with several rooms for the different constituency groups.

Members: Come and join to meet the nominees! Nominees: Come and join to share your ideas with members!

Continue reading…

🔗Dept of communities

🔗Ubuntu Matrix homeserver just went live 🎉

Nils announces

Even if we are formally still in testing phase until the end of the Ubuntu 24.04 cycle, the Ubuntu Matrix homeserver reached a state in which we can consider it live.

Although Ubuntu used to be IRC-only, we are now adopting Matrix to cater to a wider, diverse audience, including less technical users and younger generations. Matrix allows us to do so while staying true to the values that brought us Ubuntu, Linux and FOSS. When selecting the tools we use, we are always focused on open-source, privacy and freedom respecting software. We believe that Matrix offers all the modern features we need without compromising our values. Moreover, Matrix will make it easier for us to interact with neighboring communities such as Fedora and KDE.

There is still a lot of work to do, but we want to take a moment to thank the Ubuntu and Matrix communities for their great effort and dedication to this project.

You can read more about it on this Discourse thread and of course, you can now join our Ubuntu community from any Matrix federated server. A good start is the Ubuntu Community Space

Continue reading…

🔗Matrix Live

🔗Dept of Spec 📜

🔗Weekly Spec Update

Andrew Morgan (anoa) 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:

• MSC4060: Accept room rules before speaking
• [WIP] MSC4059: Mutable event content
• [WIP] MSC4058: Additive events

MSCs in Final Comment Period:

• No MSCs are in FCP.

Accepted MSCs:

• No MSCs were accepted this week.

Closed MSCs:

• No MSCs were closed/rejected this week.

🔗Spec Updates

In the new MSCs section there are new flurry of MSCs from Travis.

Matrix 1.9 has also been given a scheduled release date of November 29th, 2023.

Travis has also put out a call in the #sct-office:matrix.org for folks to add/apply feedback to any MSCs related to custom emotes and stickerpacks, as that feature is due to be reviewed (and consolidated) by the Spec Core Team this week or early next week.

🔗Random MSC of the Week

The random MSC of the week is... MSC4034: Media limits!

This MSC facilitates a few new features related to the storage of user media on homeservers. First, it proposes additional metadata on the /_matrix/media/v3/config endpoint to inform clients of the total number of bytes they're allowed to store on the homeserver, as well as the maximum number of total files they're able to store.

Second, a new endpoint /_matrix/media/v3/usage would allow users to query how much of their total number of bytes/files they're currently using.

Both of these features would allow homeservers to set and communicate media usage quotas to clients, instead of simply returning an error when the user tries to upload media that would exceed it.

Seems like a very sane proposal to me! If this is something that you think would be useful to the Matrix spec, please don't hesitate to weigh in with your support/feedback :)

🔗Call to Action for server owners

Aine announces

Hey there, Matrix Homeserver Owners!

I'm Aine from etke.cc, and I want to tell you about a fantastic project we're working on: Matrix Rooms Search. It's a search engine for Matrix Federation public rooms.

Recently, we introduced MSC1929 integration into Matrix Rooms Search. This feature automatically notifies server owners by email if a room on their server is reported for any issues. It's an important step toward enhancing safety within the Matrix Federation.

However, we've noticed that the adoption of MSC1929 across Matrix servers is relatively low, despite the fact it is going to the proposed Final Comment Period soon. This is where we need your help!

On behalf of the MRS project, we're reaching out to you to add (or update, if you previously configured it) MSC1929 support to your homeserver. Together, we can make the Matrix Federation a safer and more secure environment for everyone.

So, how can you do this? It's simple! You just need to serve the /.well-known/matrix/support file with the following structure on your homeserver's domain. If your Matrix ID is @you:example.com, the file should be available at https://example.com/.well-known/matrix/support:

{
  "contacts": [
    {
      "email_address": "[email protected]",
      "matrix_id": "@your:mxid.here",
      "role": "admin"
    }
  ]
}

If you're using mdad, there's a handy guide to assist you in setting this up.

By taking this step, you'll be contributing to a safer and more secure Matrix Federation. We invite you to join us in the #mrs:etke.cc room, where you can connect with others who are interested in the MRS project.

Let's work together to make the Matrix Federation a better place for all of us. Your support means a lot, and it's a step in the right direction for a more secure and connected future.

Continue reading…

🔗Matrix Live

🔗Dept of Spec 📜

Andrew Morgan (anoa) announces

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:

• There were no new MSCs this week.

MSCs in Final Comment Period:

• No MSCs are in FCP.

Accepted MSCs:

• No MSCs were accepted this week.

Closed MSCs:

• MSC4052: Hiding read receipts UI in certain rooms
• MSC3968: Poorer features
• MSC3969: Size limits

🔗Spec Updates

Lots of discussion surrounding MSC2702 this week, spread across a few threads.

Otherwise, the SCT are planning to add a general "MSC Checklist" to the PR template for MSC's, which contain various do's and don'ts for the contents of MSCs. Our hope is that this will eliminate a lot of repeating errors or gotchas that we find during review, as well as prevent them from slipping through unnoticed. More to follow soon!

🔗Random MSC of the Week

The random MSC of the week is... MSC3959: Sliding Sync Extension: Account Data!

This is an additive MSC to MSC3575; the core Sliding Sync MSC. As the title suggests, it adds an extension to Sliding Sync which allows clients to pull down changes to both user and room Account Data.

Clients can activate this extension when making a request to the sliding sync endpoint. See the Extensions section of MSC3575 for details.

Continue reading…

🔗Dept of Spec 📜

TravisR announces

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:

• MSC4045: Deprecating the use of IP addresses in server names
• MSC4044: Enforcing user ID grammar in rooms

MSCs in Final Comment Period:

• MSC4040: Update SRV service name to IANA registration (merge)
• MSC3930: Polls push rules/notifications (merge)

Accepted MSCs:

• MSC3958: Suppress notifications from message edits
• MSC3061: Sharing room keys for past messages

Closed MSCs:

• No MSCs were closed/rejected this week.

🔗Spec Updates

This last week the SCT has largely been preparing for the spec release happening on August 23rd, 2023 and working on getting some of the IETF/MIMI work into MSC shape. It's largely business as usual at the moment for the SCT :)

Matrix 1.9's planned work will be finalized on Monday as well, ahead of the Matrix 1.8 release on Wednesday. Please raise any MSCs or general feature areas to the SCT before Monday in #sct-office:matrix.org for them to be considered. The SCT will have limited/no bandwidth to look at things not raised for consideration.

Continue reading…

🔗Matrix Live

🔗Dept of Spec 📜

Andrew Morgan (anoa) 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:

• There were no new MSCs this week.

MSCs in Final Comment Period:

• No MSCs are in FCP.

Accepted MSCs:

• No MSCs were accepted this week.

Closed MSCs:

• No MSCs were closed/rejected this week.

🔗Spec Updates

No movement through the process on the surface for any MSCs according to the above chart, but some things have been happening! Other than the usual background hum of IETF work, conversations across many MSCs have been moving along. We also saw MSC3930 (Polls push notifications) have FCP proposed! The latter would stop a notification from being generated every time someone voted in a poll, which is sorely needed.

A reminder that in keeping with the spec's quarterly release schedule, Matrix v1.8 is due to release this month and Matrix v1.9 is due for November. We want to plan well ahead for the v1.9 release though, so if you would like to see anything in particular land in v1.9, please raise that concern in the Office of the Spec Core Team room!

See this message in the same room for more information including the currently planned v1.9 spec changes.

🔗Random MSC of the Week

The random MSC of the week is... Refine and clarify how presence works!

This is a very old "MSC" (still on google docs), but it's come up and I've seen folks taking a look at revamping presence recently, so I figured it may be interesting to share.

The document lists a number of confusing behaviours that come with the current presence spec (at the time, though it hasn't moved much since then). There is also a bullet-point list of what a redesigned presence could look like.

Given the conversation on the GitHub issue, this document appears lost to time. But perhaps someone will find it useful today.

Continue reading…