Matrix Live

Dept of Status of Matrix 🌡️

Matthew says

Very happy to announce that the Spec Core Team has been reviewing how to make more progress on MSCs and get more organisational diversity into the SCT, and we've decided to expand the team - unanimously voting to add both tulir and clokep to the team effective today. Huge thanks to both tulir and clokep for being up for joining and donating their time... and looking forwards to their contributions in helping get MSCs to and through their Final Comment Period and merged into the spec!

Josh Simmons says

We’re excited to be forging stronger ties with other open source foundations, so that we can work together and lean on one another’s areas of expertise. Last week we announced that the Matrix.org Foundation joined OpenForum Europe as a supporter alongside Mozilla and many others.

Adding to that, we’re pleased to share that we have become an affiliate of the Open Source Initiative and joined their Open Policy Alliance, and we’ve also joined the Eclipse Foundation as an associate member.

We look forward to going further, faster, together! 🚀

Continue reading…

This year again the Matrix.org Foundation was at FOSDEM, and what a huge energy boost it has been for us! Between a Fringe Event for the Matrix community to gather, a booth where the vast majority of people came by to show their support for our work, a devroom with four hours of awesome Matrix content, and last but not least a main track talk where Matthew covered what we had been doing for the past year… It has been a very intense weekend!

Continue reading…

Matrix Live

No Matrix Live this week, but there will be plenty of Matrix talks (live!) on Sunday at FOSDEM in the Matrix devroom, and at Matthew's main track talk. The talks are livestreamed, so you can follow even if you aren't at FOSDEM (or if you are in FOSDEM but the room is full). If you are at FOSDEM, you can also find live Matrix people at the matrix.org stand in Building K, level 2.

Dept of Status of Matrix 🌡️

Josh Simmons announces

Announced today during the EU Open Source Policy Summit in Brussels, the Matrix.org Foundation and Mozilla have joined OpenForum Europe as supporters. OpenForum Europe has proven an effective convener and advocate for open source and open standards in Europe, and we’re glad to help further that work.

Josh Simmons announces

This week the Matrix.org Foundation launched a new fundraiser, shared some high level budget figures, and kicked off a series diving into our emerging roadmap!

We’ve made huge strides over the last year, with the Foundation more robust and independent than ever before, and there’s a lot to be excited about in the future. Critically, we still need more organizations to step up to fund our work before January 2025.

Huge thanks to Beeper, Gematik, Fractal Networks, Fairkom, Thunderbird, and the hundreds of individuals who have already stepped up! Learn more in our blog post and become a member today 🚀

Continue reading…

A new fundraising drive

Today we launch a new fundraising drive, talk about the scope of the Foundation's work, and begin to unpack our emerging roadmap for the future. There is a lot going on and we need your help to keep it going!

At the end of 2022 Matthew and Amandine sounded the alarm: the Foundation needed more support. To deliver that, they launched the Foundation's membership program. They also introduced open governance, and committed to hiring a Managing Director to act as a robust, neutral steward.

You can help: If you are already sold on Matrix, become a member today. To find out how the last year has gone, and how your support helps us to serve the Matrix ecosystem, read on.

Over the last year, there are lots of positive, healthy signs for Matrix. New members like Beeper and gematik — and hundreds of individuals ​— boosted our annual revenues from £82K to £364K. The open network has grown from 80.3M to 115M addressable users. We've invested in long-term interoperability efforts at the IETF. And we've shifted focus from experiments to polish, usability, and advocacy.

We've supported development of core libraries, and subsidize hosting for FOSS communities like GNOME and KDE. The Foundation runs the Matrix.org homeserver, with over 250K daily active users, and operates several public bots and bridges. And indeed, the Foundation hired a Managing Director 👋.

You'll find a full accounting of our 2023 activity and finances in our first Annual Report, slated to come out around April 2024.

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:

• MSC3981: /relations recursion (merge)

Accepted MSCs:

• No MSCs were accepted this week.

Closed MSCs:

• No MSCs were closed/rejected this week.

Spec Update

For those familiar with Travis' weekly task lists of MSCs for the Spec Core Team to review in the Office of the Matrix Spec Core Team room, a new weekly list is now being posted in the Matrix Spec & Docs Authoring room. This list is aimed at technical writers who can help by converting MSC authors' words into PRs against the spec text itself.

This is the final step for getting an MSC integrated into a new release of the Matrix spec, and anyone can try their hand at it! It would also very much help the Spec Core Team by freeing up more bandwidth for review of the MSC backlog, as well as push forward the protocol itself. Thank you!

If you have any questions, feel free to ask them in the relevant Matrix rooms.

Random MSC of the Week

The random MSC of the week is... MSC4003: Semantic table attributes!

This MSC proposes expanding the set of suggested, interpreted HTML tags in Matrix clients to include additional tags related to tables. With them, more control over table rendering is possible. The proposal itself includes one such (albeit fairly arbitrary) example

The proposal is well-written and straight-forward, so do feel free to have a look if the subject interests you!

Continue reading…

We join our voices to technology companies, trade associations and other supporters in asking EU member states to align the Council's position on the CSA Regulation to the position agreed by the Parliament.

Safeguarding encryption should be a priority in negotiations, ensuring the protection of rights and freedoms around privacy and security of communications.

A copy of the open letter sent to ministers can be read below.

Open letter to EU Member States on the proposed CSA Regulation

Dear Ministers of the Interior, Justice, and Economy of EU Member States,

We write to you as small and medium-sized companies and organizations from Europe, concerned about the proposal for a Regulation on Child Sexual Abuse (CSA). Collectively, we call on you to ensure that your country’s position on this file is brought as close as possible to the European Parliament’s (EP) one. We all agree that ensuring children are safe online is one of the most important duties of tech companies and for this reason, we find the European Commission’s proposed Regulation extremely worrying. If it were implemented as proposed, it would negatively impact children’s privacy and security online, while also having dramatic unforeseen consequences on the EU cybersecurity landscape, on top of creating an ineffective administrative burden¹. The European Parliament recently adopted its position on the file, acknowledging that scanning technologies are not compatible with the aim of having confidential and secure communications. The crucial changes it therefore puts forward for the proposal reflect the opinions of the European Data Protection Supervisor (EDPS), the Council legal services as well as countless experts in cryptography and cybersecurity². It also reflects the opinion of between 63% and 69% of the companies, public authorities, NGOs and citizens consulted by the European Commission in its Impact Assessment³. As small and medium-sized tech companies and organizations, we share their concerns as we know that looking for specific content – such as text, photos and videos – in an end-to-end encrypted communication would require the implementation of a backdoor, or of a similar technology called “client-side scanning”. Even if this mechanism is created with the purpose of fighting crime online, it would also quickly be used by criminals themselves, putting citizens and businesses more at risk online by creating vulnerabilities for all users alike.

Data protection is a strong competitive advantage

As tech companies operating within the European Union, we have built products and services in line with the strong data protection framework of the EU which still serves as an example and inspiration across the world.

The GDPR allowed for the creation of ethical, privacy-first tech companies in Europe, that would otherwise never have been able to compete against Big Tech. It gave European companies a strong competitive advantage in that field internationally and allowed consumers to finally be able to find alternatives to American and Chinese services. Our users, both within the EU and beyond, have come to trust our commitment to safeguarding their data and this trust is a key driver of our competitiveness. The learning curve for adapting to the necessary administrative burden brought about by the GDPR was high but was worth it. However, the CSA Regulation could threaten this unique selling point of European IT companies and would also add a new administrative burden which we fear could overwhelm both our companies and law enforcement bodies. Considering the volume of communications and content transiting through our services, even an insignificant error rate of the technologies applied to scan for abusive material would result in millions of false positives to be manually reviewed every day.

The CSA Regulation could erode trust and safety online

In a world where data breaches and privacy scandals are increasingly common, the EU's reputation for stringent data protection is a unique selling point for businesses operating within its borders. It provides us with a competitive edge, assuring our customers that their information is handled with the utmost care and integrity. This trust, once eroded, is challenging to rebuild, and any measures that compromise it such as mandatory scanning, or mandatory age verification have the potential to harm businesses both large and small. Furthermore, the EU has recently adopted Regulation 2023/2841, which mandates that EU Institutions and bodies to consider the use of end-to-end encryption among their cybersecurity risk-management measures. There are also multiple ‘cyber’ EU proposals currently on the table, such as the Cyber Resilience Act and the Cybersecurity Act. Supporting an opposite approach for the CSA Regulation would only undermine the EU cybersecurity framework creating a contradictory, incoherent and inefficient new set of measures that companies would not be able to enforce without putting citizens and businesses at risk.

The EU Parliament's proposal goes in the right direction

Therefore, we applaud the European Parliament for its resolute stance in defending the European citizens' right to privacy and secure communication. The European Parliament’s commitment to these principles is not only a testament to its dedication to human rights, but also a beacon of hope for businesses like ours that prioritize data protection and security. The position of the Parliament includes alternatives to scanning which have a minimal impact on cybersecurity and data protection, and which experts believe would be both more effective and more efficient than mandatory scanning. Such changes of paradigm would mean going beyond the false dichotomy between privacy and security, while also making the proposal respect the proportionality principle, as requested by the Regulatory Scrutiny Board. Even if not perfect in our eyes, the changes the European Parliament made in its position are a good compromise to maintain digital security and confidentiality and to better protect children online. We believe that these changes strike the right balance between child protection and safeguarding privacy and cybersecurity.

As representatives of the vibrant European small businesses community, we encourage EU Member States to continue championing the values of privacy, cybersecurity and data protection. These principles not only align with the EU's commitment to human rights, but also serve as a foundation for a thriving and competitive business environment. Let us defend and strengthen these principles, ensuring that the EU remains an advocate of privacy in the global marketplace.

For these reasons we call on you to:

• Ensure that Council’s position is aligned as closely as possible to the European Parliament’s. This will allow for a swifter adoption of the Regulation while building on the important work of the European Parliament.
• Maintain the high level of fundamental rights - and in particular data protection – enjoyed by citizens in the European Union.
• Refrain from forcing companies like us to conduct mass surveillance of private correspondence on behalf of law enforcement agencies.
• Guarantee a high level of cybersecurity in the EU by protecting end-to-end encryption and bringing the necessary safeguards in the text. Client-side scanning and backdoors in particular should not be mandated.
• Preserve the confidentiality of correspondence.
• Minimize the administrative burden of the proposal by making it more effective and efficient, through alternatives to mass scanning.

Signed,

• Blacknight Solutions (Ireland)
• Element (United Kingdom)
• Mail.de GmbH (Germany)
• Matrix Foundation (United Kingdom)
• Nextcloud (Germany)
• Open-Xchange (Germany)
• Renvis (Greece)
• TelemetryDeck (Germany)
• Tresorit (Switzerland)
• E Foundation (France)
• Logilab (France)
• Mailfence (Belgium)
• Murena (France)
• Olvid (France)
• Proton (Switzerland)
• Surfshark (Lithuania)
• Threema (Switzerland)
• Tuta (Germany)

Trade associations and supporters:

• ACT | The App Association
• Defend Democracy
• Gate 15
• Myntex
• Quilibrium
• Studio Legale Fabiano
• Cyberstorm
• Encryption Europe
• ISOC-CAT
• Privacy & Access Council of Canada
• SecureCrypt

Matrix Live

Dept of Status of Matrix 🌡️

Josh Simmons announces

Have you seen the Stack Overflow Developer Survey results for 2023?!

Of the 83,830 folks surveyed, Matrix was the #1 chat tool in terms of current users' satisfaction. It was also rated as the most desirable among the open source tools with open governance, but there is a lot of room for improvement in awareness. We’re excited to build on this 2024! 🚀

Continue reading…

Matrix Live

No Matrix Live this week, but a YouTube playlist of the Matrix talks given at FrOSCon!

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:

• MSC3981: /relations recursion (merge)

Accepted MSCs:

• No MSCs were accepted this week.

Closed MSCs:

• No MSCs were closed/rejected this week.

Spec Update

For those familiar with Travis' weekly task lists of MSCs for the Spec Core Team to review in the Office of the Matrix Spec Core Team room, a new weekly list is now being posted in the Matrix Spec & Docs Authoring room. This list is aimed at technical writers who can help by converting MSC authors' words into PRs against the spec text itself.

This is the final step for getting an MSC integrated into a new release of the Matrix spec, and anyone can try their hand at it! It would also very much help the Spec Core Team by freeing up more bandwidth for review of the MSC backlog, as well as push forward the protocol itself. Thank you!

If you have any questions, feel free to ask them in the relevant Matrix rooms.

Random MSC of the Week

The random MSC of the week is... MSC4003: Semantic table attributes!

This MSC proposes expanding the set of suggested, interpreted HTML tags in Matrix clients to include additional tags related to tables. With them, more control over table rendering is possible. The proposal itself includes one such (albeit fairly arbitrary) example

The proposal is well-written and straight-forward, so do feel free to have a look if the subject interests you!

Continue reading…

This year again the Matrix Foundation and Community will have plenty of opportunities to meet at FOSDEM! Together with our awesome community, we’re organising a FOSDEM Fringe Event before FOSDEM itself, we will have a booth to meet everyone and spread the word about Matrix, and a devroom to go more in depth on Matrix topics.

Continue reading…

Dept of Status of Matrix 🌡️

Josh Simmons reports

We’re excited to announce the timeline for our first ever elections as we take the next big step in open governance for Matrix. We’re also introducing two new membership tiers to increase community representation by including open source projects and foundations on the Governing Board.

Read about this and more in our latest blog post.

Dept of Spec 📜

Matthew says

I dusted off MSC4016 (Streaming and resumable E2EE file transfers) over the holidays and turned it from a WIP into a full MSC, complete with draft proof-of-concept clientside implementations for the streaming attachment fileformat (hypothetical 'v3 attachments') at https://github.com/matrix-org/matrix-encrypt-attachment/pull/26 and https://github.com/matrix-org/streaming-files-test. Some of the benefits this would bring include:

• zero-latency file transfer (receiver can start decrypting & playing the download as soon as the upload begins)
• halving file-transfer duration (as you don't need to wait for the upload to finish before you start to download it)
• resumble uploads via tus
• unlimited file transfer size, given it's streamed - no longer limited to ~1GB to fit inside v8's 1.4GB heap on Web.
• O(1) memory usage for sending files, given it's streamed (great for share extensions)

It works by switching from AES-CTR to splitting the file into blocks, and encrypting each one as AES-GCM, muxing into a very simple file format which provides basic headers to allow framing for incremental decryption and random access. Given this changes the security model of attachments significantly, and given the fileformat is homemade, this MSC is now blocked on needing some serious cryptographic review before it proceeds any further :)

Matthew says

I just came across https://benstokman.me/blog/my-thoughts-on-msc-4080/ and https://benstokman.me/blog/my-new-thoughts-on-msc-4080 - an interesting discussion on the design of CryptoIDs (Client-Owned Identities - MSC4080); the cornerstone of mainstream account portability in Matrix. (Account Portability work is currently paused for a bit, but it shall return...)

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:

• No MSCs were closed/rejected this week.

Spec Updates

It's been a quite week from the perspective of the MSC Status list, but there has definitely been activity across various MSCs (at least according to my inbox). MSC3981 has seen discussion, as has MSC4041 and MSC2448 (we're considering switching the proposal to Thumbhashes).

More to come next week I suspect!

Dept of Servers 🏢

Synapse (website)

Synapse is a Matrix homeserver implementation developed by the matrix.org core team

Andrew Morgan (anoa) reports

Happy New Year!

Following on from the release of v1.98.0 (the final release of 2023), as well as seasonal holidays, we expect to return to our usual 2-week release schedule. Starting with a release candidate on Tuesday, January 9th.

As a reminder, Element is switching its development on Synapse to be AGPLv3 at https://github.com/element-hq/synapse, and development from Element's side now continues there (see the blog post if you haven't already). We have done our best to migrate issues from the now-archived matrix-org/synapse repo over, as well as preserving issue and PR numbers. PRs were not migrated, and their PR number has been reserved by a stub issue instead. Huge thanks to Erik and WillL for figuring out the plan there and implementing it (and working with GitHub's heavy rate limits on issue creation!). As well as fixing up CI, packaging, etc. etc.

As things have been a bit topsy-turvy with the migration (and of course the holidays), there's not a huge list of changes to report from the development side. But we did have a few excellent community contributions.

Thanks to @dklimpel, @loelkes, @lanker, @FadhlanR, and @adamjedrzejewski for their PRs!

Expect an increased pace of developer pick right back up from next week, as folks return from holidays.

Dept of Bridges 🌉

matrix-hookshot (website)

A multi purpose multi platform bridge, formerly known as matrix-github

Half-Shot says

matrix-hookshot 5.1.1!

Hello wonderful people. I hope you all are having/had a good break. Over in bridge towers we've been working on a few holiday treats in the shape of hookshot improvements. Let me lay them down for you:

• dark mode 🌗 is now a thing! We've moved the majority of the components used in the widget to use Compound, which means a more coherent style and light/dark support. It's still early days so please log bugs as you find them. Also, the dark mode is triggered by whatever the browser believes is your operating systems preference, so currently we don't match any overrides your Matrix client might be setting.
• Lots of bug fixes around bits of widget interface not updating properly, particularly around feeds.
• Node 18 support has been dropped, as it's not long for this world and we would like to focus on Node 20/21 support.
• We have added a list and remove command for webhooks.
• We now tell you if your bot doesn't have enough PL to speak, meaning you don't need me to confirm it for you :)
• The GoNEB migrator has been removed, though you can still migrate in a prior release and upgrade.

You can grab the release from here

Dept of Clients 📱

Moment (website)

A Matrix client; forked from Mirage.

Maze announces

Moment release 0.7.4

I bet no one was expecting this! After 2 years, finally another release of Moment (fork of the old client Mirage)!

Not much has changed. Mostly we're just keeping up to date with dependencies. But you will notice a couple differences:

• 👍 Emoji reactions to messages are now displayed (previously not visible)
• 🖉 Edited messages are displayed properly (previously only fallback text)
• 🚀 Almost all UI animations were removed, to fit the "snappy powerclient" idea

Fractal (website)

Matrix messaging app for GNOME written in Rust.

Kévin Commaille announces

It is a new year 🎆️, and what better way to celebrate this than to release Fractal 6.rc? It has been only 2 weeks since our latest beta release, but we have been hard at work during the holidays.

Here is an excerpt:

• Matrix URIs can be opened with Fractal, it is even registered as a handler for the matrix scheme
• Our Join Room dialog now shows some room details as a preview upon entering an identifier or URI
• The verification flow was rewritten to rely more on the Matrix Rust SDK, hopefully solving most issues that occurred before
• Room members now have a profile page that allows, among other things, to kick, ban or ignore them
• Speaking of ignoring users, the list can be managed from the account settings
• The dialog to view an event’s source was reworked to show more details about the event

… and a lot of other improvements, fixes and new translations thanks to all our contributors, and our upstream projects.

It is available to install via Flathub Beta, see the instructions in our README.

As the version implies, it should be mostly stable and we expect to only include minor improvements until the release of Fractal 6.

If one of your New Year’s resolutions is to contribute to an open source project, take your pick amongst our issues. Any help is very welcome!

Element X Android (website)

Android Matrix messenger application using the Matrix Rust Sdk and Jetpack Compose

benoit announces

Version 0.4.0 of Element X Android is live on the PlayStore. It includes new features like Read Receipt, Chat backup and Mentions, and lots of other features and bugfixes. Full details here: https://github.com/element-hq/element-x-android/releases/tag/v0.4.0. We are now focusing on performance, testing and stabilizing the application, in particular around the Rich Text Editor.

Lots of new features are planned for 2024, stay tuned!

Element Web/Desktop (website)

Secure and independent communication, connected via Matrix. Come talk with us in #element-web:matrix.org!

Florian Heese says

Video rooms Jitsi backend deprecation

Hello from the VoIP team,

In the past months we've had a lot of progress on Element Call our scalable video and voice conferencing solution with calling built natively on Matrix and so benefitting from Matrix’s end-to-end encryption. Now is the time to slowly convert the existing video solutions to default to Element Call. We are starting with video rooms, which will be using the Element Call stack by default in the near future. If you (still) have a Jitsi video room, you will need to re-create it to make use of Element Call.

Stay tuned

Dept of SDKs and Frameworks 🧰

Rory&::LibMatrix (.NET 8 matrix bot/client library)

Emma [it/its] ⚡️ reports

Happy 2024! It's been a while since I last posted a TWIM update... Any help I can get is super appreciated!

Changes

• Lots and lots of code cleanup
• Sync deserialisation uses a compiled model now (still slow, but turns out this only affects debug builds)
• Floating point numbers are now sent as strings (since matrix doesnt like floats)
• Some internal fields were renamed to be more clear
• Join rules are now mapped
• Added utility function to get a room's avatar url as a resolved URI
• Added support for setting identity assertion on client instances (for appservices)
• Added overload to get member list as a list instead of an async enumerable
• Added GetAsObject and GetAsJson to MatrixException, to allow serialization
• Hot paths no longer use typed event content, due to the overhead of deserializing it
• Rewrote initialization of a client instance to be cleaner

And, as always:

• The code is available at cgit.rory.gay
  • All contributions are more than welcome, be it documentation, code, anything! Perhaps, example usecases, bots, ...?
• Discussion, suggestions and ideas are welcome in #libmatrix:rory.gay (Space: #mru-space:rory.gay)

elm-matrix-sdk

Bram says

This week, beta version 2.1.0 of the Elm SDK has been published!

The minor update is similar to version 2.0.0, where it introduces a new module Matrix.Event but offers no major functionality at the time. The API interactions are planned to come after implementing an exposed Matrix.Room module for interactions with Matrix rooms.

This week, I would love it if you take a look at the Matrix.Event module, and let me know if the documentation is sufficient and meets your requirements. I'd love to hear your feedback in the Matrix room #elm-sdk:matrix.org.

Dept of Events and Talks 🗣️

The Matrix Community met at the 37th Chaos Communication Congress

erebion 🏳️‍🌈♾ ☎️ 2142 says

The 37th Chaos Communication Congress, sort of a school reunion of hackers, recently ended. From the 27th to the 30th of December 2023, a bunch of nerdy people met up in Hamburg (northern Germany) to discuss all the cool stuff they had been up to. Topics ranged as wide as technology, society, politics and even food hacking as well as a whole lot of other interesting things (talks can by the way be found at https://media.ccc.de/ and most are already uploaded, wow!). We had a Matrix Community Assembly there. An assembly is basically an area for like-minded people to meet up and talk about their topics, in this case Matrix.

We answered questions, sold merch, talked about Matrix-related projects, had workshops about topics like setting up Hookshot, took group photos, tapped beer via Matrix, handed out a bunch of cool new Matrix Community stickers and even fixed some Matrix servers. And Nico bridged the whole Eventphone network to his Matrix account while tinkering and got very confused.

If you have said hello at the event, then also say hello at #chaosevents:matrix.org!

Dept of Interesting Projects 🛰️

matrix-site

urp announces

An example minimal website, dynamically sourcing its content from a public matrix room that anyone can read and publish to.

It uses a custom event io.gitlab.ugrp.post (with two keys, title and text) and provide an interface for guest and registered users to create a new post (cannot edit yet, tbd).

The site is built in vanilla HTML, CSS and Javascript, using the @sctlib/mwc library of web-components (the new version v0.2.1 allows to register a formTemplate and displayTemplate to be able to display and create and custom event in a room).

This is all prototypes (and examples), experimenting using public matrix data outside of traditional chat clients (see also matrix-static). The objectives are to allow users to manage and display their data in environments they control, and subscribe to event feeds from sources they chose.

Dept of Guides 🧭

Josh Simmons says

New year, new homeserver! I completed a migration from managed Matrix with EMS to self-hosting using the matrix-docker-ansible-deploy project. It was a bit tricky as someone new to self-hosting Matrix, but a lot of folks helped along the way and the matrix-docker-ansible-deploy project greatly simplified the process.

I wrote up my notes in the Foundation blog in hopes that they'll be helpful, especially for other folks like me who were on small EMS plans that are being discontinued.

Matrix Federation Stats

Aine announces

collected by MatrixRooms.info - an MRS instance by etke.cc

As of today, 8389 Matrix federateable servers have been discovered by matrixrooms.info, 2269 (27.0%) of them are publishing their rooms directory over federation. The published directories contain 168449 rooms.

How to add your server | How to remove your server

Dept of Ping

Here we reveal, rank, and applaud the homeservers with the lowest ping, as measured by pingbot, a maubot that you can host on your own server.

#ping:maunium.net

Join #ping:maunium.net to experience the fun live, and to find out how to add YOUR server to the game.

#ping-no-synapse:maunium.net

Join #ping-no-synapse:maunium.net to experience the fun live, and to find out how to add YOUR server to the game.

That's all I know

See you next week, and be sure to stop by #twim:matrix.org with your updates!