Progress on the spec has been motoring since TravisR
dived (dove?) into it full time a few weeks ago - the Federation API r0 megathread bug
that tracks progress on filling in the gaps on the S2S API is clearing its checkboxes at an impressive rate.
Some points of note regarding current proposals:
- MSC1466 Erik proposes a
soft_logout field to be added to the body of 401 responses, to better help handling of encryption keys. Check the proposal notes
- MSC1452 agreement has been reached on Homeserver Warning Messages
We're going with pinned messages (option 2) and room tags (option 5) as that seems to be where the consensus is: it re-uses existing bits of the spec and room tags also help clients that don't know about this specific room tag to handle the room the right way
- MSC1425 Room Versioning It's likely that in the immediate future we'll want to change the properties of rooms in a way that will not be compatible with existing servers - for example, changing the rules for event auth or state resolution, or changing the format of an event id.
- MSC1318 Documentation describing the anticipated Open Governance of Matrix.org (aka, Matrix.org Foundation)
Python SDK -> Python 3 ?
The maintainers of the Matrix Python SDK
are mulling some major changes to the library. In particular, the desire to use
syntax means they are considering making Python 3.5 the minimum supported version. Go chat about this change
and comment on the proposal issue
Big congratulations to the Riot/Web team on the release of 0.16. You can read all about it here
, but I'll give you the headlines now:
- Replies are now available, there is UX for them and they look great
- Jitsi is now the default video conferencing provider across Web, iOS and Android, with new widget integrations for Riot Web
- New composer (text box) using Slate.js rather than Draft.js, which fixes many existing bugs and improves performance
Meanwhile, Lazy Loading implementation is approaching completion, promising several factors of improved resource utilisation!
Also now available on flathub
Go download nheko and check out the 0.5.2 release notes.
New features just in the last week or so:
- Mark own read messages with a double checkmark
- Add option to specify the scale factor
- Add input field to specify the device name on login.
- Add option to ignore key requests altogether.
- Show device list in user profile & add option to create 1-1 chat.
Plus lots of improvements and bug fixes.
libQMatrixClient and Quaternionkitsune
has been working on resend functionality:
libQMatrixClient and Quaternion have gained ability to resend and discard unsent messages. this means if Quaternion could not, after several attempts, deliver a message, a user can click "Resend" and it will try again
On the subject of libQMatrixClient, it's exciting that Konversation, the KDE IRC client, may in future start to use libQMatrixClient for Matrix support!
announces a Flatpak repo for Matrique
Matrique now has a Flatpak repo. It is the nightly build of the master branch. You can add the repo by typing flatpak remote-add matrique https://b0.gitlab.io/matrique-repo/matrique.flatpakrepo and install it by flatpak install
matrique org.eu.encom.matriqueAs it is still Alpha quality, bugs are expected. Feel free to open an issue if anything goes wrong!
New release of Fractal
to 3.29.6. Notes from the changelog
- Add German translation
- Message right click menu with: view source, reply, copy text and delete
- Styles for quotes in messages
- Initial sync speed up
Incremental improvements to Neo
Neo now has inline youtube and image url previews, and handles room state changes such as name, avatar and topic as they occur.
- Android: a lot of bug fixes and small UI improvements
- iOS: Lazy Loading is coming to life, showing huge improvements in bandwidth usage and performance in the app
Updates on IRC bridges from Half-ShotHalf-Shot
has been working tirelessly on the IRC bridge lately, so I wanted to update on his recent successes:
I've recently been working on mitigating the effects of a netsplit on the IRC bridge, and optimising it to start and run faster. This week I trimmed down the heap usage (where the memory usually goes) to just under a gigabyte on my 10,000 matrix user test bridge. Previously it could spike to as much as 3.5GB. This optimisation is still in a testing phase but results are looking positive.
For reference here is the memory usage of the Freenode process during startup:
And here are the results of my local test bridge before and after the change:
We also made some internal changes to the appservice-bridge to cache the joined state of all the bridge users and therefore avoiding joining rooms which saves us some time on startup.
Matrix for Grafana, and more from Ananace
In his regular spot, Ananace
has made progress on his Matrix sysadmin/ruby suite:
is out now as a security update release. Please update if you haven't already - it fixes two issues concerning event visibility where if you knew the event ID of an event you could read it even if you didn't have access to it; we don't believe these have been exploited in the wild, but you will definitely want to upgrade now.
Meanwhile the Python 3 port is progressing well (all sytests now pass in Python 3, i think!), and intrepid folks are starting to experiment with running it in production.
Decentralised Web Summit & Matrix Live
Meanwhile, Matthew & Amandine have been in San Francisco for the 2018 Decentralised Web Summit
- so this week's Matrix Live is live from SFO and gives a quick overview of the sort of things we got up to! Some of the sessions are already online thanks to the (somewhat unreliable) live stream (e.g. here's Muneeb (Blockstack), Amandine, Danielle (Dat), and Zooko (Zcash) talking about their respective governance models & growing pains over the last 2 years: https://youtu.be/tsz3ffrJDpw?t=12133
). The summit was a massive success, with lots of discussions about decentralised reputation, UI/UX for decentralised apps, metadata-resistance, the balance of P2P versus decentralised-servers, etc. Hopefully some of the conversations we had will result in some major improvements to Matrix in the future!
Edit: Here are the slides for our "Diving into Decentralised Communication" workshop, for those interested in a comparison between Matrix/SSB/Mastodon/Status/Vuvuzela/Briar. They're pretty minimal, as they just formed a framework for discussion, but might still be of interest.