{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreidtre37qooh4jyrngxqduef7p3uga76cxkvaxdnipsmiqfkbx7zna",
    "uri": "at://did:plc:qk2qnafs6es6f2znn6gexjid/app.bsky.feed.post/3mopmydr4q7b2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreihaub267vnc4qykkzk6ddwwnskirxwbpwq72f7r3hm7irlyyl4yka"
    },
    "mimeType": "image/png",
    "size": 259040
  },
  "path": "/blog/2026/06/19/this-week-in-matrix-2026-06-19/",
  "publishedAt": "2026-06-19T14:01:07.000Z",
  "site": "https://matrix.org",
  "tags": [
    "https://youtube.com/watch?v=szCfpnMKdow",
    "website",
    "Amandine",
    "details on our blog",
    "Marco",
    "Jorge",
    "v26.06.2",
    "v26.06.1",
    "Florian Heese",
    "MSC4195",
    "self-hosting guide",
    "PR1",
    "PR2",
    "PR",
    "Yan 't' Minagawa",
    "jobs:matrix.org",
    "Aine [etke.cc]",
    "MatrixRooms.info",
    "MRS",
    "etke.cc",
    "📊 MatrixRooms.info/stats",
    "🧩 Integrations with apps and servers",
    "💜 Support the project",
    "👉 How to add your server",
    "🙅 How to remove your server",
    "pingbot",
    "maubot",
    "ping:maunium.net",
    "twim:matrix.org",
    "the TWIM guide"
  ],
  "textContent": "## 🔗Matrix Live - A Federated Data Marketplace\n\nToday's Matrix Live: \n    https://youtube.com/watch?v=szCfpnMKdow\n  \n\n## 🔗Dept of _Status of Matrix_ 🌡️\n\n### 🔗Governing Board (website)\n\nThe Governing Board is an advisory board to The Matrix.org Foundation and with elected representatives from all across the Matrix ecosystem.\n\nAmandine announces\n\n> 🗳️ Election notice!\n>\n> And that’s a wrap for this 2026 Governing Board election season! 🏁\n>\n> We are super excited to announce our new and re-elected Governing Board members: congratulations all, and welcome!\n>\n> Representatives of the Ecosystem members\n>\n>   * Kim Brose (Matrix Community Events)\n>   * Nico Werner (Nheko-Reborn)\n>   * Jade Ellis (Continuwuity)\n>\n\n>\n> Representative of the Platinum member\n>\n>   * Neil Johnson (Element Creations)\n>\n\n>\n> Representatives of the Spec Core team\n>\n>   * Alexey Rusakov\n>   * Richard van der Hoff\n>\n\n>\n> Representatives of the Guardians\n>\n>   * Matthew Hodgson\n>   * Ross Schulman\n>\n\n>\n> Representatives of the Individual members\n>\n>   * Max\n>   * Mathieu Velten\n>\n\n>\n> Representatives of the Silver members\n>\n>   * Yoan Pintas (DINUM)\n>   * Niklas Zender (Famedly)\n>\n\n>\n> We will also welcome a new Governing Board member who joined as a replacement of his ex-colleague at Automattic: (single Gold member): Nick Mills-Barrett!\n>\n> Also a huge thank you to all of those who will be leaving the board, your support was greatly appreciated.\n>\n> Check out the details on our blog\n\n## 🔗Dept of Clients 📱\n\n### 🔗Tesseract (website)\n\nMarco reports\n\n> A native desktop client, built on top of the matrix-rust-sdk.\n>\n> It runs natively on Linux, macOS, and Windows, supports multiple accounts, full text search (even encrypted rooms, via an opt-in client side index). It requires MAS-enabled servers and simplified sliding sync.\n>\n> The website has a little simulated client to show you how it looks.\n>\n> This started as a personal AI-assisted coding experiment (not gonna lie). After a month, it's my main client in all my systems (except my phone of course), so I wanted to share it with the community. Just to be clear, all the AI-assisted development went to the UI and interface with the SDK. All the matrix protocol handling and encryption is still very much human-based as it should be. (Full story in the repo's README)\n\n### 🔗Element X Android (website)\n\nAndroid Matrix messenger application using the Matrix Rust SDK and Jetpack Compose.\n\nJorge reports\n\n> Hello everyone! This week we released v26.06.2 which contains all the goodies in v26.06.1 and a security fix. While the vulnerability needs having a modified APK to be exploited in the wild, we recommend you to update as soon as possible. Sadly, due to some issues on our side when building the APKs these were not reproducible by F-Droid so a version can't be found yet in their store. We're working on fixing that at the moment.\n>\n> Other than that, some other things we've worked on these days are:\n>\n>   * Fixing UX issues in live location to polish the feature.\n>   * In-room and global message search is in the initial stage.\n>   * A simplification of how the network stack of the SDK integrates with Android is almost finished, which should also improve start times of the app as a side-effect.\n>   * Element Call has been updated in the app and now works edge-to-edge when on landscape.\n>   * Support for properly displaying RTL text in an LTR configuration (and viceversa) is in the works.\n>\n\n>\n> And lots of bug fixes, some of them thanks to the help of external contributors. Thank you!\n\n## 🔗Dept of VoIP 🤙\n\n### 🔗Element Call (website)\n\nNative Decentralised End-to-end Encrypted Group Calls in Matrix.\n\nFlorian Heese announces\n\n> Hello from the Element VoIP team! 👋 Two things to share this week.\n>\n> #### 🔗Element Call — Multi-SFU is coming\n>\n> This has been in the crafting for a long time, as we progress towards the final MatrixRTC spec and implementation.\n>\n> **🆕 Multi-SFU lands in one of the next Element Call releases 🆕** and will become the default, so we can explore our implementation under real-world conditions.\n>\n> Some background: as part of the MatrixRTC spec work, a LiveKit transport has been defined (MSC4195). Until now, a call ran over a single SFU, chosen by an election among the participants. Following the DNA of Matrix — decentralisation — the logical next step is Multi-SFU: every participant uses their own backend, and the election requirement disappears entirely.\n>\n> This preserves clear ownership. You upload your media to your home SFU. Media from remote participants you consume from _their_ SFU. The result is a fair resource share. However, it requires every deployment to carry a MatrixRTC backend.\n>\n> ⚠️ **One ask** — same as with the previous Element Call release: every Matrix site deployment needs to announce its MatrixRTC backend properly. Please make sure your config is up to date (self-hosting guide).\n>\n> #### 🔗MatrixRTC Authorization Service — delegated leave-membership handling\n>\n> An important step towards delegated leave-membership handling for MatrixRTC:\n>\n>   * The client side already landed (PR1, PR2),\n>   * **🆕 and now the backend follows 🆕** : lk-jwt-service can take over the MSC4140 \"dead man's switch\" for call membership (details see PR).\n>\n\n>\n> Why delegate? Until now, every client kept its own delayed leave event alive: a heartbeat over the network. That pull-style approach fails exactly when things are already failing: mobile radio, suspended tabs, flaky networks. The dead man's switch fires although you're still in the call. People unintentionally pop out of meetings. 🫥\n>\n> The SFU, however, has authoritative knowledge of who is connected. And lk-jwt-service has always sat next to it issuing the SFU's access tokens. Now it finally exploits that position: it keeps the delayed leave event refreshed while you're in the call, and fires the leave the moment the SFU reports you gone.\n>\n> Bonus: this allows much more relaxed timeout constants. That means far less heartbeat traffic towards the homeserver _and_ more reliability. Normally you trade one for the other.\n>\n> ⚠️ **Heads-up:** no release cut yet as the delegations currently live in memory only, so a service restart drops them. A persistence layer comes first.\n\n## 🔗Dept of Jobs 💰️\n\n### 🔗Matrix Jobs Room\n\nYan 't' Minagawa announces\n\n> The Matrix Jobs room has long been one of the most active places in the ecosystem for sharing job opportunities, freelance work, consulting gigs, and project collaborations.\n>\n> Unfortunately, after a recent room upgrade, around 90% of the membership did not automatically make the move to the new room. As a result, many people who were previously participating are no longer receiving job postings.\n>\n> If you're looking for work, hiring, or simply want to stay informed about opportunities in the Matrix ecosystem, please make sure you've joined the upgraded room:\n>\n> #jobs:matrix.org\n>\n> Please also share this with colleagues and community members who may have been part of the old room. Let's help reconnect the Matrix jobs community and make sure job postings reach the people looking for them.\n\n## 🔗Matrix Federation Stats 📊\n\nAine [etke.cc] says\n\n> collected by MatrixRooms.info - an MRS instance by etke.cc\n>\n> As of today, `19368` Matrix federateable servers have been discovered by matrixrooms.info, `4183` (`21.6%`) of them are publishing their rooms directory over federation. The published directories contain `17958` rooms.\n>\n> The most popular server software among the online servers is:\n>\n>   * synapse: `15324` (`79.1%`)\n>   * continuwuity: `1528` (`7.9%`)\n>   * conduit: `578` (`3.0%`)\n>   * dendrite: `326` (`1.7%`)\n>\n\n>\n> Stats timeline is available on 📊 MatrixRooms.info/stats\n>\n> 🧩 Integrations with apps and servers | 💜 Support the project | 👉 How to add your server | 🙅 How to remove your server\n\n## 🔗Dept of Ping 🏓\n\nHere 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.\n\nJoin #ping:maunium.net to experience the fun live, and to find out how to add YOUR server to the game.\n\nRank| Hostname| Median MS\n---|---|---\n1| vrkknn.net| 167\n2| shork.ch| 177.5\n3| raccoon.cafe| 185\n4| melthecat.dev| 185\n5| continuwuity.codestorm.net| 203.5\n6| vibb.me| 220.5\n7| codestorm.net| 223\n8| nerdhouse.io| 227.5\n9| waywardinn.com| 315\n10| awesomesheep48.ca| 322\n\n## 🔗That's all I know\n\nSee you next week, and be sure to stop by #twim:matrix.org with your updates!\n\nTo learn more about how to prepare an entry for TWIM check out the TWIM guide.",
  "title": "This Week in Matrix 2026-06-19",
  "updatedAt": "2026-06-19T14:01:07.000Z"
}