Our guest for Matrix Live is Rich, to talk about how the Synapse team is hard at work to hunt those pesky spinners. Faster room joins now? Yes! But only for the brave!
Hello everyone! For this week's spec update you get me, Travis, instead of anoa (sorry). The heart of Matrix is the specification, modified by Matrix Spec Change (MSC) proposals - learn more at https://spec.matrix.org/unstable/proposals/
Be sure to read the Spec Core Team (SCT) section in today's update for some exciting news about Matrix though - this has a good chance of affecting how the MSC process works in the future.
The SCT has been powering through MSCs for the second week in a row, using a new internal process to encourage activity and hopefully keep momentum going. If there's an MSC you think should be on the agenda, please visit the #sct-office:matrix.org and raise it for consideration ๐
We've also been at IETF 114 to talk about MIMI - an initiative to define a standard for messaging interoperability inspired by the DMA. Matrix appears to fit perfectly into this use-case, so we've been talking with various folks involved to ensure Matrix is on the radar, including preparing our own Internet-Draft to demonstrate how it could work. MIMI is not currently a working group within the IETF, but the expectation is that it will be soon - we look forward to this happening, and are eager to contribute to the process here - or proposing Matrix itself to IETF as an initiative in its own right.
This MSC covers an Extensible Events (MSC1767) schema definition for translatable text! This would allow a client to send a message in multiple languages, with the receiver able to choose which language they're prefer to see the message in (ideally falling back to a default or machine translation if their preferred language was not available).
Like other MSCs that rely on Extensible Events, MSC1767 will need to land before this MSC can. But until then, it's great to see all of the wonderful things this feature will allow Matrix to do!
Greetings! We have been hard at work on Synapse this week. Work on faster room joins continues. In addition, Synapse 1.64.0rc2 was released. Notable features include:
support for room version 10
per-room rate limiting for room joins
support for Implicit TLS for sending emails
and much more, as well as a number of bugfixes, improvements to the documentation, and other changes to make Synapse leaner, faster, and generally more awesome.
This week The Construct server runs on Alpine Linux using freshly cut docker images building on the 0.7 release announced last week. A few images are available for preview while a more complete matrix is filled out. I am proud to announce to TWIM that Construct offers the most compact docker image for a Matrix server at just under 15 MiB; the only caveat is that media
thumbnailing won't be available.
Itโs holiday season but that wonโt slow us down! Weโve been hard at work fixing defects and improving features.
Our recently released new search experience is continuing to be improved. This week weโve added more accessibility, so it can be helpful to all.
Weโve completely finished the migration of our tests.
Thereโs a new โuse caseโ screen for users who sign up, it asks folks who they'll talk to the most on Element and, in the future, that will help us to tailor the experience.
In labs (you can enable labs features in settings on develop.element.io or on Nightly):
Itโs an exciting week for both our mobile teams as weโre ready to release our new authentication flow! If youโve been reading TWIM for a while youโll know that weโve been working hard, across all Element teams, to improve our onboarding experience. Part of this work on iOS was a new Create Account flow.
Weโre rolling the changes out slowly, so donโt panic if you donโt see the new experience yet!
In even more exciting news, our test coverage has increased with a big bump. Weโve gone from 12% to 51%!
Weโve also continued to make updates and improvements to our location sharing feature.
On the ElementX front we have our first proof of concept for sliding sync (sync v3) working and weโve almost finished setting up snapshot and integration testing. We also have Rust logs, a new authentication service and performance tests incoming.
Finally, the account deactivation button has had a change of copy - this keeps us inline with Apple guidelines around deleting and deactivating accounts.
Our new Nightly releases are now available and allowing us to catch any bugs or regressions even faster - exciting!
It will soon be easier than ever to create an account on Element, so if youโve been waiting for an update before you recommend us to others, itโs nearly time! Weโll be rolling these changes out slowly over the next week or so.
Alongside the new create account flow will be an updated sign in and reset password experience. Check it out and let us know what you think.
Also in this release weโve added a โmatch system settingsโ to the Font size screen.
Mac builds are enabled, which means, that olm is bundled into macOS and iOS builds too. So no need to build olm yourself anymore.
trixnity-crypto has been introduced, which contains the matrix e2e-encryption stuff and was previously located in trixnity-client. The relocation allows you to possibly use this in e. g. appservices. Key trust level calculation, key backup, key verification will be moved into it too.
client: basic event relation support has been added to be prepared for the next matrix spec
It's been a week of quite, constant progress on many fronts, most not that visible to the outside observer. For once, the progress on integration sliding sync into element-x for iOS has taken up speed, with many smaller bug fixes and additional features exposed through the FFI being added and performance optimisations. After the internal jack-in testing tool, this is the first actual trial of sliding sync for rust (and after the js-implementation, only the second client to actually use sliding sync overall)โand it has been tremendous. Latest tests put the loading time to first view on the first 20-ish rooms at a 150ms range ๐.
Note: this is a new Discord bridge. The playbook still retains Discord bridging via matrix-appservice-discord and mx-puppet-discord. You're free too use the bridge that serves you better, or even all three of them (for different users and use-cases).
By the end of last week we received a bunch of proposal for talks and workshops for the conference.
It were all together 32 proposals and we accepted almost all of them.
We released already multiple versions of our schedule. The current version is 0.5 htmljson
There is even some space left for late comers. In case you decide spontaneously to come and want to talk let us know, we will find a way.
You now get tickets for the summit for the fantastic price of 0 euro. We like to know in advance how many people will come.
If you have already a ticket and canโt come please let us know. So we can give them to people on the waiting list.
If you'd rather listen to Yan and me talking about the Matrix Summit and its schedule, we recorded a podcast episode for you to get informed on the go.
The team of effektio, the mobile-first organizing app build on matrix, is happy to announce the new website. Aside from the revamped team section, we are particularly excited about the new product progress page, as the questions "what are you building exactly, and how far are you with the progress" are commonplace. With the product page we hope to provide more clarity what we mean, in actual features, when we say "organize yourself, your friends, family, clubs and all other communities from the palm of your hand". Each feature also links right into the specific section of the Github project, so you can get an unobstructed view of the actual progress happeningโand contribute, if you like.
An episode with the maintainers of Threematrix, the 100% Rust bridge between Matrix and Threema!
In addition to that, Open Tech Will Save Us will be back on Wednesday 27 at 16:00 UTC! The topic will be "what makes a platform", or more specifically: "are Linux or the web platforms". There are many fascinating topics to discuss, such as "is it possible to create an app for Linux" (it's not as simple as it sounds), "why are some people against theming?", or "why do developers want to use platforms".
And to answer that, who other than the Linux desktop most advanced projects GNOME and KDE, and people working on Matrix, the protocol that wants to become as unmissable as the web itself, and more specifically on a deeper integration of widgets with Matrix clients?
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.
Lots of MSCs moving through the pipeline in the last couple weeks! As always, be sure to take a look at those in Final Comment Period above - only a few days left to comment on them before they merge/close!
Otherwise the Spec Core Team is looking to try and get a handle on the current MSC backlog - this means taking a look at all of the open MSCs, triaging them and organising them into a loose priority queue. This is likely to take quite a while to do and may not ever be complete - but should give us and everyone else an idea of what's expected to land in upcoming Matrix spec versions.
The idea this MSC proposes is to add a possible m.softkick field to room membership events of type "leave", which if present will inform clients that the user has only been kicked temporarily, and they are welcome to rejoin.
This helps with the IRC bridging use case laid out in the MSC.
I use Zeal โ an offline documentation browser using the same docsets as Dash for MacOS.
It allows me to browse MDN, ExpressJS docs, NodeJS docs and other languages and formats while not relying on the Internet when traveling.
They have "208 awesome docsets", and I guess you know which one I'm missing โ or used to miss, until I packaged it myself.
If you use Dash or Zeal, give it a try. Let me know, if you find pages that are not working.
I hope that Matrix will be included in their list of user-contributed docsets.
Note, this is not an official release distribution of the Matrix Spec. Enjoy at your own risk of this breaking or not getting updated.
Construct server has been refurbished to support the Ubuntu 22.04+ platform. I am happy to
report that Construct performs faster and more reliably than ever before. It's been
a long time since the last update due to COVID-related health problems, but development
has picked up again. I'd like to thank @manu_kamath:matrix.org and @uis246 for their
contributions, and of course Yan Minari for keeping things together over the past year.
Additional work implementing the latest MSC's will continue in the coming weeks so I
encourage everyone to show support in #construct:zemos.net and contribute if possible.
Several enhancements have taken place this release, so I'd just like to highlight one
here: The media database has been eliminated and has been integrated into the main
events database. Construct did always store media in rooms by splitting files
into blocks, but it offloaded the content block to separate storage leaving just a
hash of the content in the matrix event. Construct now stores blocks directly in event
content via hardware-accelerated base64 encoding. The result performs better because
there's only one database query instead of two, and the room can be shared between
servers in a Construct Cluster.
Construct is a performant and robust Matrix Server and Natural Language Processor.
Please be mindful of any laws in your country which require registering your instance
for commercial use.
This week we've released Synapse 1.63! This release includes a few features such as better rate limiting for invites, as well as experimental support for MSC3827 which allows filtering public room search results by room type. The latter will, once stabilised, allow for better discoverability of public spaces since it will allow clients to specifically look for them. Read all about this new release on the matrix.org blog: https://matrix.org/blog/2022/07/20/synapse-1-63-released
We've also spent some time clarifying documentation and prompts about the usage statistics Synapse automatically reports if configured with report_stats set to true. The new documentation page lists exactly what is reported and how this reporting works. This clarification work included removing the use of "anonymised" when referring to this feature to make it clearer that, even though Synapse does not report identifiable information about users and rooms, it does report the homeserver's name (i.e. the value of the server_name configuration setting).
Since people seemed to like seeing updates on my Helm Charts; matrix-synapse got bumped to 1.63.0 and then 1.63.1, as well as receiving some expanded handling of workers - all worker instances now come with both startup- and liveness probes attached by default.
Say hello to a new bridge in Matrix universe (or rather fediverse): Threematrix. As you might've guessed from the name: It's a bridge between the Threema messenger and Matrix. Threema is a very popular messenger in europe, especially in German speaking countries (it's a swiss company). We've just released our very first alpha version โ it's a very simple bot bridge for now, but we have quite a lot of improvements on our todo list. Currently, it only works with the (paid) Threema Gateway API product, but we're trying to talk to Threema to come up with a more affordable hobbyist pricing model for bridge use. Feel free to follow our releases in the GitHub repo, follow our Mastodon account and join our Matrix room to stay up to date or ask any questions.
P.S.: We're two freelance developers and we're being funded by the German Prototype Fund program. If you're an OSS developer in Germany, check them out!
Hello all -- since our last TWIM announcement, Hookshot has been updated from 1.7.2 to 1.8.1. Aside from usability fixes and documentation improvements, there have been some notable changes to generic webhook support:
XML webhook payloads are now decoded instead of being treated as blobs of text. This means they render more nicely as room messages, and more importantly, it allows them to work with custom JavaScript transformations. (#410)
GET requests for generic webhooks are no longer supported by default. For details, refer to the documentation. (#397)
I got a fantastic release for you to day and it won't fit inside a normal sized update so without further ado, here are the highlights:
Notification counts ๐ฏ (LorenDB, d42)
You can now see notification counts in more spaces, like your task bar or in
the community sidebar.
For better work-life balance you can hide the notification counts on a per
space basis.
For notification counts in the task bar your desktop environment needs to
support the Unity protocol.
Notifications are also preserved across restarts now.
Moderation ๐ฎโโ๏ธ
You can now change the permissions and aliases of a room.
Permissions are shown in the Memberlist
A new /redact command to redact an event or all messages by a user.
You can now provide a reason when inviting, knocking, kicking and banning
users.
Faster startup โก
On at least some systems startup should now be instant even with thousands
of rooms.
Encryption improvements ๐ก๏ธ
Support for the most recent changes to Matrix E2EE including fallback keys,
no longer relying on the sender_key.
Compatibility and stability improvements when dealing with different base64
encodings and when verifying users and devices.
Fetch the whole online key backup at the click of a button.
Integration with external apps ๐บ๏ธ (LorenDB)
Nheko now has a D-Bus API, which you can enable in the settings menu.
This allows applications like KRunner or Rofi to list and switch between
rooms.
If you are reading this a bit early, the release builds might still be cooking, but they should be available in the next few hours. There about 40 more features and at least 30 bugfixes waiting for you, so checkout the release here: https://github.com/Nheko-Reborn/nheko/releases/tag/v0.10.0 . I'd like to thank as always everyone who contributed to this release, it has been a pleasure to work with you folks and I hope I will see a few of you in the next release as well.
As you might be able to tell, moderation features were a big topic this release. But they are clearly not done yet and I expect more of those to land in the future now that Nheko is fairly mature. There are also a few other cool features planned, so while this release is exciting, there will always be more! Same bad client, same bad... wait, this is not my outro!
Please give this release a whirl and tell us how you like it in #nheko:nheko.im!
Release 1.4.28 has been dropped, to give us time to fix the regression and performance issue added when key share history was worked on. The next RC 1.4.30 will be done next week as usual.
We have started to work on using the new Realm Kotlin SDK (we are using the legacy Java SDK at the moment): it should improve the stability of the app (and so the crash free session) and improve devX. Nearly all the possible blocking points have been handled. This will force us to use suspend methods, which will be useful for ElementX.
Latest tweaks on FTUE have been merged on develop. We will iterate on a few things, but we are close to releasing the feature! New wordings for FTUE are waiting for translations on Weblate. Thanks to all the contributors!
We have set up a nightly build using Firebase app distribution. We keep it internal for the moment, we will see in the future if we want to open it to the community.
New project! open-super-dapp-android is a fully open source, open standard, decentralized "super app" including a secure, encrypted Matrix compatible messenger based off of the Element Messenger, and an Ethereum crypto wallet and web3 browser based off of Alpha Wallet. Our mission is to foster, and provide access to, a decentralized and secure digital commons for all. Github repo: https://github.com/2gatherproject/open-super-dapp-android
OSD is a downstream project of Element, aiming to provide the functionalities of a "super app" like WeChat, just as an open, distributed and not-for-profit app instead of a proprietary, closed and for-profit one.
This software is pre-alpha, actively seeking contributors, donors and maintainers/leaders. Get in on the ground floor and help build something amazing!
Currently, Open Super dApp builds and runs with full functionality of the Element messenger and Alpha Wallet in the same Android app, with all existing tests passing. Efforts to further integrate their functionalities are just beginning.
Next steps include:
Demonstrate easy to use person to person Ethereum payment functionality between Matrix users.
Provide a powerful and easy to use messaging and payment javascript API for use by web3 applications accessed through the Open Super dApp. Produce sample web dApps using this API.
Centralize cryptographic secrets between the wallet and the messenger.
Build a parallel iOS version for iPhones using Element iOS and Alpha Wallet iOS.
This week has seen an merges of many minor, partially longer-pending PRs into the mainline code base: among them a fix for a longer pending CI problem with Apply builds, an update to latest ruma and many minor fixes and style improvements. We've also gotten the Crypto-bindings for the JS in web using WASM a lot further, the only thing remaining for a release are some last minute PRs and fixes in the release infrastructure. But the most changes to the code base this week have been coming from the appservice department, who've submitted, reviewed and merged a whopping seven PRs this week, fixing various problems and adding a bunch of appservice specific features.
Beyond purely code changes this week has seen a lot of project starts, too: For ones, with the help of the rust team, the iOS Team has started integrating the Sliding-Sync/Sync V3 into the upcoming Element-X-Series; the team has put up the first PR to add integration tests against an actual synapse server (some issues pending); a workshop set out the first ideas for the new upcoming timeline API; and a very interesting draft PR was brought in from community member docweirdo proposing a new API on top of the existing SDK to have futures wait for actual completion - no more sending a message and observing sync for the appropriate response yourself.
Synapse Maintenance Container โ Docker container with tools for synapse & postgres database maintenance
A lot of things added and changed, and I'm sure I missed something, so I will go with a release candidate this time
New in v0.4.1-RC1
enable PGPASSFILE support for better database password handling
add tools to detect and maybe fix synapse issue 12507 and 13026 (No state group for unknown or outlier event)
internal: added an extension for mautrix-go to serve synapse admin api requests
lots of iternal changes
stui is a typical golang binary, it's also available as stand alone version from the release page
Tools for No state group for unknown or outlier event
[docker run -it --rm registry.gitlab.com/mb-saces/synatainer:0.4.1-RC1] stui 12507 --help
[docker run -it --rm registry.gitlab.com/mb-saces/synatainer:0.4.1-RC1] stui 13026 --help
The tools scan the database for the issues and tells you which rooms are affected. Adding the --fix option, it ~~destroys your database~~deletes the bogus extremeties. Use at your own risc. And make a backup.
The doc have still a lot of space for improvementsโฆ
Start the container without command and let do its magic :)
What it does by default:
daily:
purge all rooms without local members
run the state autocompressor (500/100)
weekly:
delete old remote media (>90 days)
delete old message history from public joinable rooms (>180 days)
Because I don't like having to change my display name to tell coworkers when I'm away, I've written a maubot plugin for an auto-responder bot.
It allows me to signal when I'm away, at which point anyone who sends a message in an existing DM will be sent an automated reply so they know that I'm away, when I'll be back, and how to reach out to me in case of emergencies (it does this once per DM until I come back). When I'm back, I just need to tell the bot and it will automatically turn off the auto-responder and give me a summary of the DMs in which I've missed messages while I was away.
I just created a simple bot that generates a MSC url from the specified MSC id.
The source code for the project can be found at https://mau.dev/minecraftchest1/mscbot/. And example instance can be found at @maubottest1:synapse1.arsrobotics.org Demo and use the bot in #msc-bot:synapse1.arsrobotics.org
My release tracking bot received a bunch more work since the last update. It now supports tracking repos, groups, and user stars on GitHub, GitLab (both .com and self-hosted), as well as Gitea (though Gitea requires a token for reading stars). And also tracking "releases" - a.k.a. tags - on bare Git repos, at least as long as they don't require SSH key authorization. Things are getting ever closer to a 1.0 release, with only really some missing bang commands and error reporting being the remaining pieces.
The Matrix Summit 2022 is a community event taking place Thu, 25th to Sun, 28th Aug
at c-base in Berlin. Today's the last day to propose presentations and workshop. The exact deadline is 22:22 (Europe/Berlin).
Will you be in Berlin and have a Matrix project to talk about? Can you organise a workshop about how to use Matrix? How does your community or workplace use Matrix?
Submit your proposal now!
FrOSCon is a conference that takes place in Siegburg/Bonn, Germany on 21st and 22nd August. Most presentations will be German, but there are some in English as well. It's all about free, open source software.
And, best of all, we'll have an entire DevRoom track for a day โ full of Matrix. Furthermore, you can come by the Matrix stand for that famous hallway track. โจ I know I'll be there. ๐
This week Matthew gives us a general update on everything Matrix and Element. What is going on with Sliding Sync, OpenID Connect or P2P Matrix? Let's find out!
We're also pleased to announce the next episode of Open Tech Will Save Us has been scheduled. We will be talking live and interacting with you on July 27, 16:00 UTC (18:00 CEST) on the subject of platforms with people from GNOME, KDE and Element.
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.
The Spec Core Team took a concentrated effort to work through our priority backlog of MSCs, resulting in the decent amount of MSCs hitting FCP this week!
Thankfully the community has nearly matched this number by adding quite a few more MSCs into the fray. But we're still up by 1!
Perhaps one of the most exciting MSCs to move forwards is MSC2676: Message editing, which allows users to edit events (including messages) that they've previously sent. Part of the aggregations work, this functionality has been used extensively throughout the ecosystem. But only now is it making its way into the spec proper. I'm also personally excited about MSC2285: Private read receipts, which allows users to read a room's contents without advertising it.
Of course the above MSCs are still in Final Comment Period; a 5 day period where anyone can raise their concerns about an MSC before it is accepted. So if you have any last-minute comments, be sure to get them in now!
Another MSC I'm personally excited about! This MSC provides an endpoint on the homeserver to request the rooms (or spaces) you have in common with another user. I would find this useful for incoming DMs from users I may or may not know. Note that the client may not already have this information if it is making use of lazy loading room members, so it needs a way to ask the server for this information.
Looks like the MSC is currently sitting in the Spec Core Team's review backlog. We'll get to it soon!
The Synapse team has been hard at work! This week we published Synapse 1.63.0rc1. Among the notable features are support for MSC3827: filtering /publicRooms by room type, allowing for better discovery of Spaces. You can read more about that here. In addition, the release contains a number of bugfixes, updates to the documentation, and internal changes focused on reducing memory usage and increasing performance, as well as supporting the long-standing goal of faster room joins. More on these next week in the official release announcement!
Good news, as you might have noticed, conduit.rs is back online and better than ever! Matrix.org is so kind and donates this Linux server to me. I already host a discord appservice and handle 23k messages per day and, most importantly, now I'm at the top of both #ping rooms ;)
You can now edit aliases in Nheko! This means you can publish your own aliases in the room directory as well as in the room. If an alias can't be used by people (because it isn't listed in the room directory), that alias is highlighted in red with an easy option to fix it (if you have permissions to do so). You can also easily switch the primary (canonical) alias of the room.
With this the feature set I wanted to have for the next release is complete. I wanted to focus on improving moderation and room management capabilities in Nheko and it does now have a very basic sets of capabilities to do so. I do already have plans to expand on them though!
So instead of working on new features, I will be focusing on bug fixes. For a start if someone has the username room, Nheko will now omit the reply fallback to prevent pinging the whole room. The verification window now also should always be big enough to show its contents and we now properly explain to users, why emojis might look different on different devices fixing an issue reported via Twitter... There is also a new icon for the room directory (it is now a building, very punny, huh?).
Tobias has done some internal refactoring, which will allow us to create more automated tests and prepare for the eventual Qt6 migration
Nvrwhere has improved NeoChat's Timeline layout: On a wide window, the bubbles will now be centered in the window, in order to better use the space while not stretching the timeline out too far
He's also fixed several papercut issues around the UI, for example editing and replying using the keyboard shortcuts
The browser will now properly open when clicking on a link when using wayland
The first part of Snehit's GSoC project is almost ready to land: The room list is gaining a list of spaces, which can be used to filter for the rooms included in that space
We're also moving forward on the E2EE support, with NeoChat now allowing a user to send an encrypted message into a matrix room - provided libQuotient supports it ๐
Tobias is also working on improved Reaction & Emoji pickers, which will allow users to select different variants like skin tones and which will behave better on mobile devices
After some successful testing on current registration flows, we are running testing sessions on the new and improved registration flows over the next week.
We are also moving away from spreadsheets over to TestRail, a test case management tool which will help us track regressions and issues. Weโll be offering our community testers a change to try it out over the next few weeks.
Started experimenting with matrix-react-sdk for an improved crypto(graphy) experience
The share screen button in video rooms on desktop has been temporarily removed until the underlying issues can be resolved
We have removed most of unused code in the Element Web repositories and are working on setting up tools to avoid forgetting to remove unused code in the future
The new search experience and DM flow have received some bug fixes and polish in addition to more polish to CSS
Final commenting period expected to start next week
Weโve been tackling our process around reviewing PRs to reduce review time, taking a two pronged approach at focusing on reviewing new PRs quickly and resolving our oldest non-draft PRs every week
Did you know that some of our issues in GitHub are labelled with โHelp wantedโ and โgood first issueโ if theyโre especially suited for community contributions?
In the works (you can enable labs features in settings on develop.element.io or on Nightly):
Version 1.8.22 RC was released to TestFlight and comes with the following changes:
In-app notifications are now available.
A shiny new offline indicator that's visible in more parts of the app.
A handful of fixes for issues when making calls.
Unfortunately this build was rejected following the latest requirements for account deletion in the App Store Review Guidelines. Weโre looking into ways we can resolve this problem.
We have started to use Sentry to provide more insights into technical issues encountered whilst using the app.
Work continues on implementing the new app layout.
1.4.28 is being prepared with the following changes:
Makes the build process compatible with F-Droid again!
Fixes for voice messages not playing and some characters showing in their escaped html form - such as quotes showing as "
Nightly builds are on the way, these builds will be under a separate Application ID allowing them to be installed alongside the production Element app. Expect more information to come soon.
Weโre investigating general performance regressions across the app, with some improvements already in the pipeline.
In the last two weeks or so, we've made some UX improvements:
unified SSO and ordinary login cards
unified media and regular file-uploads, and improved drag-and-drop support
improved feedback while validating login and registration input
We also added one feature that friends of mine were requesting ๐: annotations can now be equipped with a "motivation" (part of the w3c web annotation data model, mentioned in MSC3574), and filtered by motivation. This makes it easy to, for example, mark some discussions as "questions" about the text, which is pretty useful when managing a class.
And I've now finally managed to cut a long-overdue new 2.6.0 release of the Ruby SDK, which includes better support for concurrent multi-threaded usage as well as improvements on Ruby 3.0+. (The tests are currently green for Ruby 2.6 to 3.1)
The team is proud to announce the first release of @matrix-org/matrix-sdk-crypto-nodejs to npmjs.com (0.1.0-beta.1) for all the best npm user friendliness you can get. This marks the first release of the crypto ffi for nodejs from the rust team supreseeding the previously existing project. It is also the very first release for nodejs featuring the great new vodozemac core (replacement of libolm). We've marked this as a beta release while we work out any remaining minor hickups or problems, so if you see something, say something! However, the main point of contact to it for most people is probably TravisR |s Nodejs Bot SDK, which is already consuming that beta in its latest release.
After a year of working on different ways to support encryption, the bot-sdk has finally stabilized on the rust-sdk crypto crate for crypto bindings internally. Tutorials on how to get your bot/appservice set up and working with the new crypto code are here (note that for appservices you'll need to turn on EDUs and MSC3202 in Synapse). If you run into problems, please report bugs or pop by #matrix-bot-sdk:t2bot.io on Matrix for help.
Alongside support for encryption, v0.6.0 brings a whole lot of other functionality for appservices, Synapse Admin API users, and bots wanting to make use of real DMs. Check out the full changelog here.
axon.sh v0.17.0 has been released which adds support for managing per-user ratelimits, and includes a fix for a bug related to server discovery. Please try it out and report your experience in #axon:matrix.thisisjoes.site, I'd appreciate feedback!
A whole heaping of work has landed for my release tracker project, with it now supporting tracking releases for projects (loose projects, all users stars, or all projects under a namespace) on both GitHub and GitLab (for .com as well as self-hosted instances).
Documentation is currently still a bit lacking, but hoping to have more information both on setting it up as well as using it Soonโข.
my conference talk at ACCU this year is now out on YouTube: Matrix is a Distributed Real-time Database. I explain what Matrix is, and show how to use curl to send and receive messages, and why it's "interesting" to write a server, and, as the title hints, I introduce the idea that Matrix can be for a lot more than messaging.
Reminder: Matrix Summit Conference Berlin call for participation ends next week
As announced earlier, there will be a conference all about matrix. (See TWIM 2022-07-01)
We encourage everyone with matrix-related projects, products and ideas to come around and give a talk: From the past to the future, from the moment of the idea, the story of the creation or the vision of the future. Weโd like to understand the principles as well as the technology. The conference is from people for people, so if youโd like to talk about yourself, your community, your organization, please do. Showcase yourself and your relation to the Matrix world. Let's get to know each other!
We aim to compile a versatile program. We are open to contributions of any length, from 5 minutes (lightning talks) to presentations and talks to workshops and hacksessions up to 5 hours. Weโll come together to discover, celebrate and enjoy the world of matrix. Also, if you have any arty, cultural or playful contribution in mind, please offer it.
โก๏ธ Proposals for the Matrix Summit in Berlin can be submitted until next Friday (2022-07-22 22:22, TZ=Europe/Berlin) via pretalx. ๐
Rick and I talk about the the brand new Chatterbox. Is it Riot Embedded rebranded? Did the world need yet another embedded chat solution? Can I host mine? Can I make it clever? Let's find out!
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.
While the name may not make much sense to the layperson, the idea of a "canonical" Direct Messaging room (DM) is one that would always be referenced whenever a DM between two people is requested. That is, instead of potentially having a few different DM rooms with someone, both you and the other person would always know which room to use when DM'ing each other.
We don't really have this today. DM rooms are just group rooms with only you and someone else in them. If you attempt to DM another user, your client will try to guess the best room to use for this through some clever heuristics. What's lacking is a defined way to always arrive at the same room for this action.
This MSC attempts to define one, and would allow other functionality to be built on top of it, such as definitively knowing which room to send user-to-user data into, and to read from.
This week the Synapse team released Synapse 1.62! It features a lot of changes, including a fairly big update of spam checker callbacks, performance improvements around syncing and device management, improved customisation of .well-known client files, and much more. Read all about it on the Matrix.org blog: https://matrix.org/blog/2022/07/06/synapse-1-62-released
Apart from this, we've been working on refining and fine-tuning our processes as a team over the past few weeks, which, among other things, resulted in the creation of this documentation that gives contributors some insight on how we review pull requests on Synapse. Olivier has also landed his work on running Complement (our next-gen integration test suite) against instances of Synapse using workers, which is a massive improvement for our CI.
Hello again TWIM, updates to my Kubernetes charts have been rolling along as usual, though I've been a bit more silent about them. This week sees the addition of a synatainer chart though, for those who want it for maintaining their K8s Synapse. (And the Synapse chart was also updated to 1.62.0, and element-web to 1.11.0)
If you have any questions, comments, requests for assistance, etc with them then #matrix-on-kubernetes:fiksel.info is where you want to go.
The k8s-at-home dendrite helm chart now optionally configures ingress resources for dendrite in polylith mode. It has also had some bugs fixed and been updated to support the most recent version of dendrite.
Note: The PR (https://github.com/matrix-org/matrix.org/pull/1348) to publish Quadrix on the matrix.org client list has been submitted more than a month ago, but still awaiting approval. Anyone here can help?
You can now edit aliases in Nheko! This means you can publish your own aliases in the room directory as well as in the room. If an alias can't be used by people (because it isn't listed in the room directory), that alias is highlighted in red with an easy option to fix it (if you have permissions to do so). You can also easily switch the primary (canonical) alias of the room.
With this the feature set I wanted to have for the next release is complete. I wanted to focus on improving moderation and room management capabilities in Nheko and it does now have a very basic sets of capabilities to do so. I do already have plans to expand on them though!
So instead of working on new features, I will be focusing on bug fixes. For a start if someone has the username room, Nheko will now omit the reply fallback to prevent pinging the whole room. The verification window now also should always be big enough to show its contents and we now properly explain to users, why emojis might look different on different devices fixing an issue reported via Twitter... There is also a new icon for the room directory (it is now a building, very punny, huh?).
You have probably seen it, this week Element released Chatterbox, an embedded chat client you can use to build chat assistants, chatbotsโฆ or probably other use cases we didn't even think of. It's OSS and really just a lightweight Matrix client. Rick talks about it in greater length with me in today's Matrix Live.
Fix for missing end tokens in sync responses from Synapse >= v1.61.0 (Thanks to Tom Price for !20).
A prettier animation while loading comments.
/ipns/latest.cactus.chat is updated to point to the latest release, so sites linking there should already be using the new version.
Also, while we're here: we're surprised and delighted to so many people using Cactus Comments!
We just crossed 300k guest users registered on cactus.chat (roughly equivalent to 300k unique anonymous users). ๐
An unfortunate side-effect is that we're having to up our hosting game to keep up with you all - and it's getting a bit expensive on our student budgets.
We set up a donations page on Open Collective, in case any of you would want to help out. โจ๐ซ
After a long hunt, we've eventually found a significant problem with napi-rs, the layer we use in between Rust and Node.js for the crypto-nodejs, in the way it manages the memory coming from async functions in rust. With that out of the way and the last remaining features implemented, we are on the final stretch into in putting out the first prerelease of crypto-nodejs-bindingsโbrace for it to come near your next npmjs.com early next week ๐ค๐ค.
<matrix-room-element/> is a web component (vanilla JS/HTML/CSS & distributed un-minified) that can be imported and inserted in any web page, to display the content of a (public, soon with authentication, and private room support) matrix room.
To explain what it's for: Using the UnifiedPush standard, ntfy enables self-hosted (Google-free) push notifications from Matrix (and other) servers. Especially useful for users of Google-free Android (such as from f-droid).
If you try it, please report any feedback or problems or improvements in #matrix-docker-ansible-deploy:devture.com . Any updates to the scripts or docs may appear first on my branch before being merged into the playbook.
The option for reports to be polled via the synapse admin API (rather than configuring proxy pass-through)
The option to disable the displaying new reports in moderation room (so that you can use the TrustedReporters protection without the abuse reports features)
A !mjolnir rules matching <entity> command to search watched lists.
Glob support to the kick command.
A background queue for kicking (to reduce the load of large glob kicks)
A slight improvement to the performance of the redact command
An improvement to documentation (including dedicated setup documentation)
A new mute action for the since command !mjolnir since 1day mute 100