Andrew Morgan (anoa) reports
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://matrix.org/docs/spec/proposals.
MSCs in Final Comment Period:
- MSC3773: Notifications for threads (merge)
- MSC3715: Add a pagination direction parameter to
- No MSCs were accepted this week.
- No MSCs were merged this week.
This week has seen more review on threads from the Spec Core Team, as well as some further aggregations work. See the FCP list above! MSC3771 (Read Receipts for Threads) and MSC3856 (Threads List API) are also looking quite close to starting FCP.
In other news, yours truly has written up some words (adapted from some internal docs written by @erikjohnston) amounting to a simplified guide to writing MSCs. The hope is that it'll help spell out the process in a more succinct manner, as well as provide answers to common questions/edge cases.
The document's words are still in flux, and still only exist as a PR; so do feel free to leave some suggestions or feedback if you have some!
The random MSC of the week is... MSC3775: Markup Locations for Audiovisual Media!
I recommend looking at MSC3574 (marking up resources) first as MSC3775 builds upon it. But as for MSC3775 itself, the MSC adds support for annotating media - storing those annotations as events in a Matrix room!
This could be useful for building a decentralised app for marking up audio files. Collaborative audio editing anyone?
As far as I can tell, this MSC is currently waiting for MSC3574 to progress before it itself moves much further. But feel free to check out both in the meantime if you're interested.
Synapse is a Matrix homeserver implementation developed by the matrix.org core team
Brendan Abolivier announces
This week we've released Synapse 1.67! This Synapse release is the first one to use Poetry 1.2, and also removes the long-deprecated TCP-based replication protocol. Synapse workers are now required to use the Redis-based protocol which we introduced back in 2020. If this isn't already the case for your deployment of Synapse, see the documentation for workers as well as the upgrade notes, to update your configuration.
In other news, Synapse 1.68 (which is due to release on the 27th of September) will introduce a couple of changes in dependencies. The minimum supported SQLite version will be raised to 3.26, meaning that Synapse 1.67 is the last version of Synapse supporting SQLite versions 3.22 to 3.26. In addition to this, a Rust compiler will be required for source checkouts, as we are starting to introduce Rust code in Synapse (as I mentioned last week). This latter change should not impact installations that use
pip install matrix-synapse, Debian packages from
matrixdotorg/synapseDocker image to manage and run Synapse. See the upgrade notes for more information about these two changes.
Matrix Kubernetes applications packaged into helm charts
This week sees some of the usual updates to my Helm Charts, with element-web being updated to 1.11.5 and matrix-synapse to 1.67.0.
An Email to Matrix bridge. 1 room = 1 mailbox.
- speed up email delivery
- StartTLS enabled automatically if TLS cert and key are provided
msgtypeby attachment's mime-type (received image -> got rendered image in your matrix client; received audio -> got audio player in your matrix client; etc)
A multi purpose multi platform bridge, formerly known as matrix-github
Hello gang. This week, another hookshot release. They do come fast!
We've fixed a bug which had the potential to cause crashes when JSON logging is enabled, and written a whole torture test for the logger to ensure it won't do that again. We've also made some quality of life improvements to the GitLab connection type :)
The highlights are:
- Ready/draft state changes for GitLab merge requests are now reported. (#480)
- Merge GitLab MR approvals and comments into one message. (#484)
You can get the latest release here
But I have a bit more for you this week, we're working on a few new features to hopefully improve the lives of developers out there building webhook integrations.
First, we are adding the ability to view requests and logging from within the widget UI. This means you can now debug why your webhooks might not be working without having to leave your client. This includes the ability to log debug messages and read them back later!
Secondly, we're adding some new sci-fi functions to the scripting environment. The first of which will allow you to embed images / videos into the message output, with a function to to create matrix content URLs from a regular URL.
Finally, and this is probably the most sci-fi. We're working on a feature for you to load scripts from other rooms for use in your webhook. This means developers will be able to build whole webhook handling libraries within rooms, and then share those libraries across the federation. At the moment, this looks a bit like:
const resultOfScript = await loadMatrixScript("matrix:r/my-room-alias:domain/$my-event-id"); // ... mutate the result return = resultOfScript
We're still thinking about how to ensure it's both performant, and safe but the initial results are looking quite good.
That's all we have for you in bridging corner today, have a good weekend 👋
A Matrix-KakaoTalk puppeting bridge.
It has been brought to my attention that the KakaoTalk service has been updated to block older clients, and unfortunately this bridge is affected. As of this writing, using the bridge may get your KakaoTalk account banned! It has happened to both me and at least one other person, so this isn't just a hypothetical risk.
To be clear about this, I've updated the
masterbranch to throw an error on startup, which must be manually removed from source code if you wish to continue using the bridge at your own risk.
It's currently unknown what it takes to log in safely, but discussion about it is ongoing (albeit intermittently) in the discussion channel (linked below).
Once the bridge is safe to use again, I'll post a TWIM update about it 🙂
A Minimal, simple, multi-platform chat client for the Matrix protocol.
Quadrix v1.3.3 has been released! It's available for mobiles and desktops in the respective app stores. This release introduces:
1) a new menu structure making it easier to add new functions without affecting the main UI,
2) new page animations in the "wide" app layout (on desktops and tablets) when switching between rooms or going back to the home screen, and
3) for PinePhone enthusiasts, Wayland display on KDE and SXMO UI's (it was already available on Phosh).
A client for matrix, the decentralized communication protocol
Tobias Fella reports
- Will now show you the exact time a message was sent at when hovering over a message's timestamp (Thanks to James Graham)
- Context Menus will now open more reliably
- You will also no longer see useless horizontal scrollbars
- Thanks to the GSoC work by Snehit, NeoChat now has some support for spaces: at the top of the room list, you can select a space to make the room list only show rooms of that space
- Audio playback has been fixed
- A few problems relating to message input have been fixed, most notable that reply and edit texts will now only be visible in the correct room when multiple rooms are opened at the same time (Thanks to James Graham)
- Quitting NeoChat now is less crashy
- Adding custom emojis has been fixed (Thanks to Jan Bidler)
- Links in spoilers will now be correctly hidden
- You can now edit notification settings for each room (Thanks to James Graham)
- NeoChat will now better follow Kirigami's style of progress indicator and the system's color for text selection (Thanks to Bharadwaj Raju)
Matrix client for Emacs
Ement.el, a Matrix client for GNU Emacs, has finally been published on the official GNU ELPA package repository. Now the current stable release can be installed by any Emacs user by simply using the command
M-x package-install RET ement RET. More improvements to come. Feel free to join us in #ement.el:matrix.org.
Secure and independent communication, connected via Matrix. Come talk with us in #element-web:matrix.org!
- On Web we’ve been working on perfecting the app and fixing bugs
- Also in the roadmap and currently in development:
- Updates to the composer. We’re working on improving the composer and creating a WYSIWYG version (What You See Is What You Get). Keep your eyes peeled for more info in the coming weeks!
- There are also improvements to the ‘forgot password’ flow on their way. We made these same improvements to the mobile apps some weeks ago and received great feedback.
In labs (you can enable labs features in settings on develop.element.io or on Nightly):
- Threads work continues as 2 of our 3 MSCs make their way into their FCP (Final Comment Period). We’re excited to bring improvements to you and will be dropping them straight into the product as soon as they’re ready.
Secure and independent communication for iOS, connected via Matrix. Come talk with us in #element-ios:matrix.org!
- Following this week’s release of the new app layout we’re heads down reading feedback and looking for improvements. We hope you’re enjoying it as much as we are - use the Feedback button in the top-left to let us know!
- The team is also making improvements on the next generation of the Element app for iOS (Element X).
- We’re experimenting with merging together the sliding sync mechanism and the new timeline API.
- We’ve added support for reactions, redactions, permalinks and replying, we have a new log out mechanism and soft logout, and we’ve also overhauled the UI.
Secure and independent communication for Android, connected via Matrix. Come talk with us in #element-android:matrix.org!
Not only are we hard at work smashing bugs but we’re also working on 2 big updates for the coming releases:
- The new app layout! While you can currently access this via Labs, we’re closing bugs and addressing feedback that will allow us to make it the default layout for all users. Check out more info here
- Also coming up, starting a DM when the first message is sent. No more waiting around for the room to be created before you say hi to the recipients - your invite and message will be received together. Yey! :ta_da:
We’re also working on a fix for the bug that’s making verifying others difficult.
Next-gen crypto-included SDK for developing Clients, Bots and Appservices; written in Rust with bindings for Node, Swift and WASM
Major Milestone: yesterday Sliding Sync was merged into
main, now available behind the
sliding-sync-feature flag and enabled by default for
matrix-sdk-ffifor your convenience. This, too, means the
jack-insliding sync-test client is merged and part of our
labssection - go out and have a try! Furthermore the key verification for crypto-js has been merged, as well as support for logging out, including tracking the soft-logout state in FFI, and support for sending
Similarly the new Timeline API, is making big leaps forward, we expecting it to land, too. It will also be available behind a feature-flag replacing the previous
experimental-timeline-feature. If you were using that, please pay close attention to what is going on, as it will replace most of if not all of the previous API and data store.
Both will be available, also together, in the upcoming release 0.6 of matrix-sdk, which we expect to land before the end of the month. It was slightly pushed back as the
sync eventchanges turned out to be more of a rabbit hole than anticipated.
👉 Wanna hack on matrix rust? Go check out our
help wantedtagged issues and join our matrix channel at Matrix Rust SDK.
Matrix server setup using Ansible and Docker
matrix-docker-ansible-deploy now has much-improved Synapse worker support:
- we've added support for Stream writer workers
- we've added support for running multiple federation sender workers (until now, we only supported 1 at most)
- we've added support for running multiple pusher workers (until now, we only supported 1 at most)
- we've added support for running background tasks on a worker
- we've restored support for
appserviceworkers (we had removed support for these after Synapse v1.59.0 deprecated them and redid how this type of worker is meant to be spawned)
- we've restored support for
user_dirworkers (we had removed support for these after Synapse v1.59.0 deprecated them and redid how this type of worker is meant to be spawned)
- we've made it possible to reliably use more than 1
media_repositoryworker (until now, using more than 1 could have caused issues due to us not correctly restricting where media background tasks run)
Some backward incompatible changes were made, which could affect some people.
People who are using some reocmmendation configuration like
matrix_synapse_workers_preset: one-of-eachwill now get 9 additional worker processes by default.
To learn more, see our changelog entry
Your matrix server on your conditions
@twim:cadair.com We're happy to announce that the etke.cc Matrix hosting service is now better prepared to serve German customers!
Besides having completely localized the website (see etke.cc in German here) and Matrix server ordering flow, we're now also able to offer customer support in German.
If you're in Germany and would like to get a managed self-hosted Matrix server, neither self-hosting difficulties nor the language barrier is getting in the way anymore.
New bot to help admins of large rooms. Capabilities:
- The admin can add a reaction signature to the user, which will be added by the bot to each message from this user, for example: "spammer"
- The admin can fix violations of the rules of the room by the user. The counter of violations is also displayed as a reaction under each user message in the form: "N ❗️", where N is the number of violations.
- The bot captures who added the signature or violation, when it happened and for what reason (description). All this can be asked from the bot by any member of the room
- The user can add his own description, which the bot will report to any member of the room on the appropriate request.
- The moderator can switch the language that the bot speaks in this room. Message translations are stored in standard po files.
Anybody can try bot by invite @react-sig-bot:sibnsk.net to his room.
Source code for the bot: https://github.com/progserega/matrix-reaction-signature-bot
World Wide Web Consortium (W3C)'s TPAC (Technical Plenary and Advisory Committee, i.e. "Annual W3C Conference") takes place, 12-16 September, Vancouver, BC, Canada: https://www.w3.org/2022/09/TPAC/
W3C now has a public Matrix space: #w3.org:matrix.org
Join #ping:maunium.net to experience the fun live, and to find out how to add YOUR server to the game.
Join #ping-no-synapse:maunium.net to experience the fun live, and to find out how to add YOUR server to the game.
See you next week, and be sure to stop by #twim:matrix.org with your updates!