We already have quite a few volunteers to help us with the booth, but weāre always looking for more hands! People who sign up before December 15 are entitled to a limited edition t-shirt :)
Two organizations have already shown their commitment to the community by offering to sponsor the Fringe Event right before FOSDEM. Pizzas and drinks will be covered, but if other organizations want to sponsor too we can work on more opportunities together!
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.
The SCT has been spending a lot of its time doing the normal review function, ensuring spec PRs and MSCs get the review they need to move forward. This is largely expected to continue for the rest of the year, with a spec release planned for early/mid-December. Watch this space for updates there :)
The SCT is also taking an administrative break for the holiday season: reviews will continue, but updates in the SCT Office may be less frequent over the next month. Specifically, the Weekly Pings are on pause for next week (December 3rd, 2024) and December 15th, 2024 until January 8th, 2025. If you have something for the SCT to review or consider in future pings, let us know in the SCT Office - weāll pick it up as part of our normal work.
Howdy folks! Itās been a while since we announced a Hookshot release but there is finally a new one, and itās got a decent chunk of Interesting Things in it š.
Hookshot 6.0.0 ( / 6.0.1) is now out and breaks new ground:
šļø Support for encrypted rooms is now considered stable š„³.
šļø You can now set an expiry time on incoming webhooks, so if you want a short lived webhook then you can easily configure that from either a bot command or widget. There are a bunch of config options for fine tweaking too. See the docs for more information.
You can read up on the details for encryption support here but weāre broadly happy to say that it should work for most people. Hookshot includes some full integration tests to ensure that we do not break support for encryption in the future, so weāre quite happy with how this has landed.
Finally, weāre sunsetting support for Node 20 and bumping our supported versions to Node 22+. This is in line with our policy of only supporting the Active LTS.
Weāve published releases of 1.9.6 and 1.9.7 on GitHub with 1.9.6 available on TestFlight but have decided to delay the App Store release due to a few hiccups around mxc URLs. Weāve fixed these today, so expect a new 1.9.8 release to land on TestFlight next week.
1.9.8 includes the new Share Extension which supports sending an image, video, file, URL or plain text directly to a room/DM. We have also enabled local echoes for media uploads which weāve been testing for the last couple of weeks and has made a huge difference in how fast the app feels.
The implementation for sending/editing/removing media captions was finished this week, which will also be available in 1.9.8.
Knocking on a room is implemented for the external user. Weāre now focussing on showing these to the relevant room members to accept/reject.
Exploration has begun for showing all Media/Files within a room.
Bonus update for Element iOS: Weāve fixed a bug when resetting cross signing, it will be available in 1.11.21 scheduled to hit TestFlight on the 10th.
We are making progress on knocking rooms (AKA ask to join). The release is postponed for a few days until we fix some remaining bugs.
We are starting to work on the media viewer: we will have a gallery and it will be possible to swipe left and right to navigate between media items.
Captions are getting some new feature: new action to āEditā, āCopyā and āDeleteā the caption Also they will be displayed in the media viewer.
Messageflag is an unread message indicator for Linux desktops, designed to be unobtrusive and relatively lightweight. I built it in response to the memory usage and disk writes generated by my Matrix and email clients even when Iām not actively using them. It displays an icon in my desktop panel when new messages are waiting, allowing me to see at a glance when I have new messages without having to keep those apps running all the time.
A few notable features:
Handles multiple accounts concurrently
Can play a sound when new messages arrive
Can use the Scroll Lock light like an indicator icon (X11 sessions only)
Supports Matrix and IMAP email accounts
Includes a verify-by-fingerprint tool for Matrix sessions/devices
Desktop agnostic
Relatively low memory usage
Minimal disk writes (good for low-power machines running on SD cards)
Few dependencies (all available in Debian-based Linux distros)
The first maintenance release in 0.9.x line - version 0.9.1 - is here. 0.9.0 came out somewhat rough, with a few bugs and regressions found early on, which this release fixes. Details (and the Git tag) are, as always, at https://github.com/quotient-im/libQuotient/releases/tag/0.9.1
Previously weāve introduced the concept of appservice-managed (or system-managed) users, plus Synapse had user types for a while now, so we decided itās time for⦠emojis! Basically, on user avatars, you may notice a small badge with an icon and tooltip that shows you whatās this specific userās role is. š§ā You (Admin) can see something like š”ļø System-managed (Bot) or š¤ Regular User. Documentation
Hello all! About time I got around to writing a post for TWIM.
For those of you writing bots for Matrix, especially using python, and you havenāt heard of us, this might interest you: NioBot v1.2.0 has been released!
Regarding this release in particular, you really should read the changelog - so much has changed since the previous versions that including them all in this twim would likely make you fall asleep before you could finish reading it.
If you havenāt heard about NioBot before, NioBot is a bot-focused library built on top of matrix-nio. The project was started as I felt the need to have a reusable library to cutdown on boilerplate across my bots, but I decided that itād be a better idea to just have a generalised bot framework that anyone could use for any sort of bot.
NioBot comes feature packed with all of the things you need to make a functional bot, without you needing to do any of the repetitive and sensitive behind the scenes. NioBot takes care of all of the parsing, internal functionality, utility, and stateful management, so you can focus on writing high quality commands, rather than worrying about the rest.
If the below code sample tickles your fancy, feel free to check it out with some of the links below!
Meet other matrix users, chat about Matrix, the rest, and everything else, discuss your Matrix ideas, sign each other in persona, and maybe spice the evening with a good mate or beer.
Every first Wednesday of the month in the c-base at 8pm (ātil the next pandemic).
While weāre talking about bluesky - there have been lotsofdiscussions recently about why Bluesky should use Matrix for its DMs (perhaps using Pseudo IDs to support DIDs, layering Matrix over atproto, or expressing the Matrix CS or even SS API as an atproto lexicon, etc).
In an ideal world, Matrix (or a vendor like Element) would have the $ to work on this fulltime as next-gen R&D, much as we implemented Cerulean back in 2020 as our proposal to Twitter for building bluesky on top of Matrix. Right now, though, this will only happen unless someone in the community steps up to have a go at it (or explicitly puts down money to fund it).
So: consider this a formal call to arms to anyone in the Matrix community whoās excited by blueskyās mainstream decentralisation success to figure out and contribute a proposal & demo for using Matrix to power E2EE DMs in atproto! Iāve spoken to the bluesky team about it, and theyāve made it clear that they donāt have much/any bandwidth to support from their side right now (unsurprisingly, given the rate at which theyāre scaling). However, they also havenāt decided how to do E2EE DMs yet, so thereās no harm in showing some code and making a proposal!
Thereās a huge range of different possible architectures here, which could include one or more of:
Expressing (some of) Matrixās CS API as an ATproto lexicon, and focus on surfacing existing public unencrypted data on ATproto as public Matrix chatrooms? (and then add E2EE later)?
As of today, 10519 Matrix federateable servers have been discovered by matrixrooms.info, 3187 (30.3%) of them are publishing their rooms directory over federation.
The published directories contain 21096 rooms.
See you next week, and be sure to stop by #twim:matrix.org with your updates!
To learn more about how to prepare an entry for TWIM check out the TWIM guide.
The Foundation needs you
The Matrix.org Foundation is a non-profit and only relies on donations to operate. Its core mission is to maintain the Matrix Specification, but it does much more than that.
It maintains the matrix.org homeserver and hosts several bridges for free. It fights for our collective rights to digital privacy and dignity.