284 lines
22 KiB
Markdown
284 lines
22 KiB
Markdown
+++
|
||
date = "2024-01-12"
|
||
title = "This Week in Matrix 2024-01-12"
|
||
path = "/blog/2024/01/12/this-week-in-matrix-2024-01-12"
|
||
|
||
[taxonomies]
|
||
author = ["Thib"]
|
||
category = ["This Week in Matrix"]
|
||
|
||
[extra]
|
||
image = "https://matrix.org/blog/img/matrix-logo.png"
|
||
+++
|
||
|
||
## Matrix Live
|
||
|
||
No Matrix Live this week, but [a YouTube playlist of the Matrix talks given at FrOSCon](https://www.youtube.com/playlist?list=PLl5dnxRMP1hXHswESs8M9mJFgPjclhQDp)!
|
||
|
||
## Dept of Spec 📜
|
||
|
||
[Andrew Morgan (anoa)](https://matrix.to/#/@andrewm:element.io) 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](https://github.com/matrix-org/matrix-spec-proposals/pull/3981) (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](https://matrix.to/#/#sct-office:matrix.org), a new weekly list is now being posted in the [Matrix Spec & Docs Authoring room](https://matrix.to/#/!KzgjYxOASBbBMrtCXC:matrix.org/$QqpbS4hdFuxy6vPIz80eeGjnGXwJWJInMJFlNqG7y98?via=matrix.org&via=element.io&via=envs.net). 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](https://github.com/matrix-org/matrix-spec-proposals/pull/4003)!
|
||
>
|
||
> 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!
|
||
|
||
<!-- more -->
|
||
|
||
## Dept of Servers 🏢
|
||
|
||
### Synapse ([website](https://github.com/matrix-org/synapse/))
|
||
|
||
Synapse is a Matrix homeserver implementation developed by Element
|
||
|
||
[Erik](https://matrix.to/#/@erikj:jki.re) says
|
||
|
||
> This week the Synapse team has released [v1.99.0rc1](https://github.com/element-hq/synapse/releases/tag/v1.99.0rc1)! This is the first release under the new AGPL3 license (see the [blog post ](https://element.io/blog/synapse-now-lives-at-github-com-element-hq-synapse/) if you haven't already). The new release is mostly bugfixes and minor performance improvements, but also include some new configuration options.
|
||
>
|
||
> Thanks to [@zeeshanrafiqrana](https://github.com/zeeshanrafiqrana), [@Dmytro27Ind](https://github.com/Dmytro27Ind) and [@loelkes](https://github.com/loelkes) for their contributions to this release!
|
||
|
||
## Dept of Clients 📱
|
||
|
||
### Quaternion ([website](https://github.com/quotient-im/Quaternion))
|
||
|
||
A Qt5-based IM client for Matrix
|
||
|
||
[kitsune](https://matrix.to/#/@kitsune:matrix.org) reports
|
||
|
||
> ### Quaternion 0.0.96
|
||
> After another two-year wait, the new claimed-stable version of Quaternion is out! Although [release notes](https://github.com/quotient-im/Quaternion/releases/tag/0.0.96) put beta E2EE support as the biggest thing, in fact the biggest thing is that stable Quaternion is finally on par with NeoChat in running on the most recent libQuotient (0.8.x, that is). Packagers who were sitting back waiting for this to happen (yes, Debian) - it's now time to really get to work and update both libQuotient and Quaternion.
|
||
> Otherwise, it's pretty much the same minimalistic and fast desktop client as it used to be. Packages for Windows and macOS are next to release notes, Flatpaks have been published a few minutes ago - go and grab it!
|
||
|
||
### Nheko ([website](https://nheko-reborn.github.io))
|
||
|
||
Desktop client for Matrix using Qt and C++17.
|
||
|
||
[Nico](https://matrix.to/#/@deepbluev7:neko.dev) reports
|
||
|
||
> Well, this week I should have really been doing other stuff, but I did not!
|
||
>
|
||
> First of all we sent out a call to update the translations. Apparently that was quite successful, there are like 20 commits with translation updates from the last 2 days now... If you find your language to be out of date, don't hesitate to jump on <https://weblate.nheko.im/projects/nheko/nheko-master/> to fix it.
|
||
>
|
||
> Because telling other people what to do is quite exhausting, I needed some time to relax. So I spent all night optimizing the room switching logic. Specifically because of how ListView works in Qml, the timeline used to render about 100 messages when switching a room, when instead only 10 or so can be visible at one. This is for the simple fact, that an incomplete message has a size of 0, so the ListView tries to fill the timeline with more messages. That can easily be worked around by setting an incomplete message size to something reasonable like 100. In most cases they do need more space than that and if they don't, the ListView will quickly notice. As a result switching rooms is now about 10 times faster.
|
||
>
|
||
> Another fun thing slowing down room switching were video messages. Obviously those take a long time to display, I thought, it is a video after all. But do you know why that is slow? Well, it takes about 5ms to load the video and 500ms to find the audio output... So that is clearly stupid, why would we spend 100 times as much time on looking for an audio output, when the user isn't even playing the video yet? So we now only initialize the audio output, when a user clicks the play button, which makes scrolling much smoother. If only I had investigated that years ago instead of just brushing it off as "probably normal"... We now also show you if the video is already downloaded instead of making you click the download button first just to immediately ask you to click play.
|
||
>
|
||
> Another thing that has been bugging me endlessly... you couldn't really use the arrow keys in most cases on macOS. This meant "up" to edit, "Ctrl+up" to switch rooms, etc didn't work. Turns out macOS keys are just weird. They actually send "Num+up" when you press up, making Nheko think you are using the numpad. Anyway, after years this is fixed now.
|
||
>
|
||
> Annoyed by always mistyping the password on the Steam Deck, Bubu added a button to show you the text you just entered. Meanwhile q234rty improved our hack to make the color palette work in windows in cases where the window pointer gets reused. We also now have arm flatpaks again for the nightlies. Since my new arm board never arrived (because communication is hard!), we now spend 3h cross-compiling it... Duam also added a toggle to disable swipe gestures. You can also now delete image packs (thanks to Emma) and there is a /command to ignore people now and a button on invites thanks to NepNep!
|
||
>
|
||
> That's all, I now really need to work on the things that have been piling up... otoh, look, shiny food!
|
||
|
||
### Element X iOS ([website](https://github.com/vector-im/element-x-ios))
|
||
|
||
A total rewrite of Element-iOS using the Matrix Rust SDK underneath and targeting devices running iOS 16+.
|
||
|
||
[Ștefan](https://matrix.to/#/@stefan.ceriu:matrix.org) announces
|
||
|
||
> We're ramping back up after the holidays and first on our list are whatever bugs didn't want to stay in 2023.
|
||
>
|
||
> * [Fixed issues around timeline items flickering](https://github.com/element-hq/element-x-ios/pull/2295)
|
||
> * Improved text handling on the message composer in [1](https://github.com/element-hq/element-x-ios/pull/2297), [2](https://github.com/element-hq/element-x-ios/pull/2327) and [dictation on iOS 17+](https://github.com/matrix-org/matrix-rich-text-editor/pull/922)
|
||
> * [Fixed the reporting screen not being displayed](https://github.com/element-hq/element-x-ios/pull/2307)
|
||
> * [Fixed draft composed messages being lost unexpectedly](https://github.com/element-hq/element-x-ios/pull/2323)
|
||
> * [Completed our monthly notification placeholder rotation dance](https://github.com/element-hq/element-x-ios/pull/2298)
|
||
> * [The app is now faster in loading member profiles](https://github.com/element-hq/element-x-ios/pull/2324)
|
||
> * and we might even have a [workaround for one of our biggest crashers](https://github.com/element-hq/element-x-ios/pull/2301)
|
||
>
|
||
> Note: none of the items above are available in a release build yet. Please see our [releases page](https://github.com/element-hq/element-x-ios/releases) for details.
|
||
|
||
## Dept of SDKs and Frameworks 🧰
|
||
|
||
### Rory&::LibMatrix (.NET 8 matrix bot/client library/SDK) ([website](https://cgit.rory.gay/matrix/LibMatrix.git))
|
||
|
||
[Emma [it/its] ⚡️](https://matrix.to/#/@emma:conduit.rory.gay) announces
|
||
|
||
> Any help I can get is super appreciated!
|
||
>
|
||
> ## Changes
|
||
> * RemoteHomeserver now has a way to *attempt* to create an instance without throwing if it fails
|
||
> * Initial sync detection is more reliable now and requires less retries
|
||
>
|
||
> ## New features
|
||
> * Messages can now be dynamically built (see `MessageBuilder`, the message factory implementation), maybe I'll be using it to post these next time?
|
||
> * Some event types now have User-Interface-friendly names (mainly policy types)
|
||
>
|
||
>
|
||
> _**And, as always:**_
|
||
>
|
||
> * The code is available at [cgit.rory.gay](https://cgit.rory.gay/matrix/LibMatrix.git)!
|
||
> - 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](https://matrix.to/#/#libmatrix:rory.gay) (Space: [#mru-space:rory.gay](https://matrix.to/#/#mru-space:rory.gay))
|
||
> * Got a cool project that you're working on and want to share, using LibMatrix? Be sure to let me know, I'd love to hear all about it!
|
||
|
||
### elm-matrix-sdk ([website](https://github.com/noordstar/elm-matrix-sdk-beta))
|
||
|
||
[Bram](https://matrix.to/#/@bram:matrix.directory) says
|
||
|
||
> This week has a relatively small update: a [patch update 2.1.1](https://package.elm-lang.org/packages/noordstar/elm-matrix-sdk-beta/2.1.1/) that, given Elm's enforced semantic versioning, means there's no API changes! Only internal ones.
|
||
>
|
||
> The main development is taking place in a separate branch, which creates the timeline. ⏲️ This is quite a difficult part of the SDK which takes some serious architecture to figure out! If you're curious, then [Nico's blog post](https://blog.neko.dev/posts/nhekos-event-store-v2.html) is a good example of a timeline design and the complexity that it requires.
|
||
>
|
||
> If you would like to see more about the timeline design, join the conversation at [#elm-sdk:matrix.org](https://matrix.to/#/#elm-sdk:matrix.org) and feel free to offer help and/or tips about how to design the timeline.
|
||
|
||
### matrix-rust-sdk ([website](https://github.com/matrix-org/matrix-rust-sdk))
|
||
|
||
Next-gen crypto-included SDK for developing Clients, Bots and Appservices; written in Rust with bindings for Node, Swift and WASM
|
||
|
||
[bnjbvr](https://matrix.to/#/@bnjbvr:delire.party) announces
|
||
|
||
> A few days late, we're happy to announce that we've shipped the 0.7.0 release of the Matrix Rust SDK 🥳 As a reminder, this SDK powers next generation Matrix clients, like [Fractal](https://wiki.gnome.org/Apps/Fractal), [iamb](https://github.com/ulyssa/iamb) or the [Element X](https://github.com/vector-im/element-x-android/) [apps](https://github.com/vector-im/element-x-ios/), among others.
|
||
>
|
||
> This has been the first release for a long long time (the last one was around mid October 2022), so there are plenty of new features including, but not limited to:
|
||
>
|
||
> * added sqlite as a storage backend, that becomes the new default over `sled` (which has been removed),
|
||
> * support for authentication via OpenID Connect (aka OIDC), allowing simplified sign-in management when running along the [Matrix Authentication Service](https://github.com/matrix-org/matrix-authentication-service),
|
||
> * client support for the unreasonably fast [MSC3575 aka Sliding Sync](https://github.com/matrix-org/matrix-spec-proposals/pull/3575), for instant room list synchronization (*requires a server supporting it),
|
||
> * many new cryptography features, including secret storage, initial support for dehydrated devices, key backup support, automatic cross-device signing setup, and so on and so forth, as well as many bugfixes and performance improvements
|
||
> * an exciting new crate implementing opinionated high-level features making it easier to build clients: the [matrix-sdk-ui](https://docs.rs/matrix-sdk-ui/latest/matrix_sdk_ui/index.html). Use the new `RoomListService` and `EncryptionService`, and get a fully functional, high performance client using Sliding Sync by default in no time!
|
||
> * work on FFI bindings for the Rust SDK to be used in Swift and Kotlin code bases,
|
||
> * generally more support for client-server APIs: notification settings, read receipts and markers, and so on.
|
||
> * and your usual load of numerous simplifications of the existing public APIs, refactorings, performance improvements, etc.
|
||
>
|
||
> The rest of our changelog contains more details for each crate: [matrix-sdk](https://github.com/matrix-org/matrix-rust-sdk/blob/main/crates/matrix-sdk/CHANGELOG.md#070), [matrix-sdk-base](https://github.com/matrix-org/matrix-rust-sdk/blob/main/crates/matrix-sdk-base/CHANGELOG.md), [matrix-sdk-crypto](https://github.com/matrix-org/matrix-rust-sdk/blob/main/crates/matrix-sdk-crypto/CHANGELOG.md).
|
||
>
|
||
> Thanks to all the contributors of this release ❤️
|
||
> Happy hacking! 🦀
|
||
|
||
## Dept of Bots 🤖
|
||
|
||
### Spam Police ([website](https://github.com/jjj333-p/spam-police))
|
||
|
||
[jjj333_p (any pronouns)](https://matrix.to/#/@jjj333:pain.agency) announces
|
||
|
||
> Meet Spam Police, the moderation bot that is new to the scene, now in its first stable release! It has been a long time coming (~2 years), but in my defense I (the main and pretty much only dev) am a full time college student and this has been a project that I hack away at during vacation.
|
||
>
|
||
> Spam Police began because about 2 years ago the Matrix platform began experiencing the growing pain of becoming somewhat mainstream of being periodically flooded with scam posts. As someone who has fought scammers since my early teens, I was driven to get to work on a bot that would detect these scams in abandoned rooms and post a warning, as well as logging these posts to a room so that the moderation groups I was apart of could add the scam accounts to their banlists. As I left those groups for various personal reasons I made the decision to turn [#jjj-tg-scams:matrix.org](https://matrix.to/#/#jjj-tg-scams:matrix.org) into a Mjolnir compatible banlist, however during my time in said moderation communities I learned about a lot of the drawbacks of Mjolnir/Drapunir and made the decision to make my own attempt at a true moderation bot.
|
||
>
|
||
> Spam police is aimed to be a Mjolnir replacement for small communities or ones migrating from other platforms and don’t want to selfhost. Currently the only noteworthy features of Spam Police is Mjolnir-type banlist writing and following, and automatic maintenance of [#jjj-tg-scams:matrix.org](https://matrix.to/#/#jjj-tg-scams:matrix.org), however a lot of the work that has been put into Spam Police has been into making it very easily extensible, so there is more to come! Spam Police can be selfhosted as it is AGPLv3 (<https://github.com/jjj333-p/spam-police>), however it is intended to be run in a more centralized manner, filling the gaps that Drapunir leaves for those not wishing to selfhost, or looking for an experience more familiar to the moderation bots on Discord. With this first release I ~~hope~~ expect that while Spam Police is still somewhat limited in features it is prepared for general public use in it’s designed use-case.
|
||
>
|
||
> If you have any questions feel free to join [#anti-scam-support:matrix.org](https://matrix.to/#/#anti-scam-support:matrix.org) and feel free to lurk in [#jjj-tg-scams:matrix.org](https://matrix.to/#/#jjj-tg-scams:matrix.org) and watch its scam detection process in action! And don’t forget to check out our github <https://github.com/jjj333-p/spam-police> for more information and a command/usage guide.
|
||
|
||
### Matrix Reminder Bot ([website](https://github.com/anoadragon453/matrix-reminder-bot))
|
||
|
||
[HarHarLinks](https://matrix.to/#/@kim:sosnowkadub.de) announces
|
||
|
||
> Matrix Reminder Bot is a small standalone bot with which you can set and receive reminders for yourself or your rooms over Matrix written in Python using [matrix-nio](https://github.com/poljar/matrix-nio/).
|
||
>
|
||
> If you have attended Matrix (community) events in the past [you might have](https://cfp.summit2022.matrixmeetup.de/matrix-summit-conference-2022/talk/WTWWZ8/) heard me ~~ranting~~ [talking about](https://programm.froscon.org/2023/events/2985.html) it [before](https://summit2023.matrixmeetup.de/conference/talk/DUK9YE/), among other similar small tools.
|
||
>
|
||
> I still use it quite a lot, despite not too much activity on the codebase with the last release dating back to July 2021.
|
||
> Anoa, the original author, recently granted me maintainership on the repo, which is why I am happy to share some news about it with you today:
|
||
>
|
||
> **We have released [v0.3.0](https://github.com/anoadragon453/matrix-reminder-bot/releases/tag/v0.3.0) of Matrix Reminder Bot!**
|
||
> You can find the release artifacts in the usual places: [PyPI](https://pypi.org/project/matrix-reminder-bot/), [Docker Hub](https://hub.docker.com/r/anoa/matrix-reminder-bot), [GHCR](https://github.com/anoadragon453/matrix-reminder-bot/pkgs/container/matrix-reminder-bot).
|
||
>
|
||
> In December, reminder bot received a very notable contribution from [@svierne](https://github.com/svierne): It is now possible to configure who may or may not interact with your instance of the bot!
|
||
> This change will mandate that you update your bot's configuration once you update, because we deem it important for administrators to manage the access to their services. The provided example configuration file has been updated to reflect this and defaults to the previous setting, but we suggest you consider limiting access.
|
||
>
|
||
> A key functionality that allows the bot to work, is sending notifications to specific people. This was historically done by literally mentioning their name, which lead to some grief when unintentionally mentioning people. MSC3952: Intentional Mentions tries to address this issue and was included in Matrix Spec v1.7. Again thanks to [@svierne](https://github.com/svierne), reminders will now use this new field correctly to notify you of your reminders!
|
||
>
|
||
> Beyond that, I started to remove the cobwebs of 2 years inactivity by updating dependencies, adding CI, etc. Notably, that makes pre-built docker images available not only on [Docker Hub](https://hub.docker.com/r/anoa/matrix-reminder-bot) like they always were, but also on [GHCR](https://github.com/anoadragon453/matrix-reminder-bot/pkgs/container/matrix-reminder-bot).
|
||
>
|
||
> If you have any questions or want to follow the project, you can find the repo [here](https://github.com/anoadragon453/matrix-reminder-bot) and a dedicated room at [#matrix-reminder-bot:matrix.org](https://matrix.to/#/#matrix-reminder-bot:matrix.org) (we also have a Hookshot for it now!).
|
||
|
||
## Dept of Events and Talks 🗣️
|
||
|
||
### FOSDEM 2024 ([website](https://fosdem.org/2024/))
|
||
|
||
[Thib](https://matrix.to/#/@thib:ergaster.org) announces
|
||
|
||
> The Matrix Foundation and Community will be at FOSDEM in Brussels between February 2 and 4, with a main track talk, a devroom and a booth! Find all the details [on our blog](https://matrix.org/blog/2024/01/matrix-presence-fosdem/).
|
||
|
||
### Matrix Salon Podcast (English episode)
|
||
|
||
[Christian Paul (jaller94)](https://matrix.to/#/@jaller94:matrix.org) announces
|
||
|
||
> Meet Bram, who has many Matrix projects like the Matrix Event Directory, various games and the "tomato video".
|
||
>
|
||
> Episode: <https://podcasters.spotify.com/pod/show/matrix-podcast0/episodes/Bram-English-episode---Matrix-Community-Summit-2023-e2ebuk3>
|
||
>
|
||
> RSS feed: <https://anchor.fm/s/cdb34188/podcast/rss>
|
||
>
|
||
> Fediverse post: <https://mastodontech.de/@jaller94/111743486844936832>
|
||
|
||
### Matrix Federation Stats
|
||
|
||
[Aine](https://matrix.to/#/@aine:etke.cc) says
|
||
|
||
> collected by [MatrixRooms.info](https://matrixrooms.info) - an [MRS](https://gitlab.com/etke.cc/mrs/api) instance by [etke.cc](https://etke.cc?utm_source=twim&utm_medium=matrix&utm_campaign=federation-stats)
|
||
>
|
||
> As of today, `8438` Matrix federateable servers have been discovered by matrixrooms.info, `2307` (`27.3%`) of them are publishing their rooms directory over federation.
|
||
> The published directories contain `168930` rooms.
|
||
>
|
||
> [How to add your server](https://gitlab.com/etke.cc/mrs/api/-/blob/main/docs/indexing.md) | [How to remove your server](https://gitlab.com/etke.cc/mrs/api/-/blob/main/docs/deindexing.md)
|
||
## Dept of Ping
|
||
|
||
Here we reveal, rank, and applaud the homeservers with the lowest ping, as measured by [pingbot](https://github.com/maubot/echo), a [maubot](https://github.com/maubot/maubot) that you can host on your own server.
|
||
|
||
### [#ping:maunium.net](https://matrix.to/#/#ping:maunium.net)
|
||
Join [#ping:maunium.net](https://matrix.to/#/#ping:maunium.net) to experience the fun live, and to find out how to add YOUR server to the game.
|
||
|
||
|Rank|Hostname|Median MS|
|
||
|:---:|:---:|:---:|
|
||
|1|envs.net|236|
|
||
|2|icbm.codes|284.5|
|
||
|3|ailuro.space|294|
|
||
|4|nerdhouse.io|302|
|
||
|5|fostered.uk|373|
|
||
|6|benstokman.me|439|
|
||
|7|sulian.eu|721|
|
||
|8|casavant.org|910|
|
||
|9|aguiarvieira.pt|1102.5|
|
||
|10|matrix.org|1165.5|
|
||
|
||
### [#ping-no-synapse:maunium.net](https://matrix.to/#/#ping-no-synapse:maunium.net)
|
||
Join [#ping-no-synapse:maunium.net](https://matrix.to/#/#ping-no-synapse:maunium.net) to experience the fun live, and to find out how to add YOUR server to the game.
|
||
|
||
|Rank|Hostname|Median MS|
|
||
|:---:|:---:|:---:|
|
||
|1|matrix.its-tps.fr|180|
|
||
|2|fostered.uk|197.5|
|
||
|3|matrix.maymundere.org|212|
|
||
|4|nerdhouse.io|217|
|
||
|5|matrix.org|301|
|
||
|6|inu.is|311.5|
|
||
|7|herkinf.de|401.5|
|
||
|8|shiftsystems.net|998.5|
|
||
|9|puppygock.gay|1922|
|
||
|10|darkness.services|4189|
|
||
|
||
## That's all I know
|
||
|
||
See you next week, and be sure to stop by [#twim:matrix.org](https://matrix.to/#/#twim:matrix.org) with your updates!
|