Sorry folks, no matrix live this week, your regular programming will continue next week.
A big week in spec land.
If you've been waiting all this time to start implementing some of the privacy improvements the team has been making over the last few months, now's the best time to do it. Clients interacting with identity servers or 3rd party identifiers (3PIDs) have some changes to make, and identity servers themselves have a whole new authed API so they can expose terms of service requirements to users.
Check out the specs at https://matrix.org/docs/spec/client_server/r0.6.0 and https://matrix.org/docs/spec/identity_service/r0.3.0
You can read all about it here
- MSC2334 - Change default room version to v5
- Our fastest FCP ever - less than 24hrs!
Final Comment Period
The Spec Core Team have chosen MSC1756 (cross-signing), MSC2324 (new spec process), and MSC2313 (ban lists) to focus on this week :)
- 0.10.1 has been released on the app store. It includes minor improvements and bug fixes like the call issue. Full release descriptions can be found on respective repos: Riot, matrix-ios-kit and matrix-ios-sdk.
- This release includes better logging to track app kills in background but it seems that iOS13.2.2 released by Apple yesterday fixes the issue. We are looking for more feedbacks on that topic.
- On develop, the app can now use the integrations manager advertised by the homeserver.
We have finished implementing long click on a Room item, to configure notification settings of the room and to be able to leave the room. We can now ignore user (after a report of content only for the moment). The list of ignored users is displayed in the setting. Users can be un-ignored. We are also working on improving performance and improving code structure. As usual, we have also fixed some bugs. A release will be done at the beginning of next week, then we will try to work on the login flow and account creation flow.
We are working on the Integration Manager management.
Neil had this to say:
Additionally they have been working furiously to make some progress against e2ee device cross signing and have just merged the ability to authenticate via DMs. It's behind a labs flag and will only work if both parties are enabled, but this is big step towards our cross signing dreams. Watch this space for more cross signing features over the coming weeks.
Alexandre Franke offered:
Seshat gained the ability to encrypt the event database and index. A PR has landed and is awaiting review. Now your Matrix client can securely store and index your E2EE messages.
I took time to port Quaternion from Qt Quick Controls 1 (deprecated upstream) to Qt Quick Controls 2, the lighter UI widgets kit that Spectral also uses. Most of regressions are fixed and the result is likely to land in the master branch sometime next week. The overall looks will remain the same, just a minor refresh of visuals. Aside from improving performance the porting should help to solve widget scaling issues on multi-monitor configurations.
- Released version 0.1.4, which fixes a number of bugs and cleans up a lot of the code
- I'm considering converting the algorithm code only to TypeScript (it's a mess rn)
- I said this last week, but I think I finally got all the bugs out of the internal algorithm 🤞
- I'm also working on a proper explanation of how the algorithm works (An explanation of just the events is here)
This week we shipped 1.5.1 which contains a small bug fix to prevent a potential DoS vector.
Aside from that we’ve continued to work on sharding out the database which we’ll put live once we have migrated matrix.org onto new hardware (woo!) and finally we’ve been fixing some bugs affecting event auth rules.
Coming up on the horizon are ephemeral messages (the ability to send messages with a specific ttl), more io perf work and a bit further down the line we’ll dust off our attempts to shard out room processing from the master process, meaning Synapses running in worker mode will have much more CPU headroom.
Black Hat told us:
I'm working on writing Synapse workers in Rust. Only a few things are working, but the performance seems good.
Just pushed the K8s-optimized Synapse 1.5.1 image
another Synapse container image, but this one is new: If you had problems with LDAP in the official Synapse image, try this image: https://gitlab.com/famedly/container/synapse-ldap/container_registry. It's based on the official images, but updates the LDAP auth provider to the latest commit of the master branch. The official image comes with the latest version released to pypi.org, which is a bit older. Aside of that change, it's exactly the same, so you can use it as a drop in replacement.
Black Hat told us:
my multi-arch synapse docker image is updated to synapse 1.5.1
It gets a tombola of versions at the list of Public Synapse Homeservers https://www.anchel.nl/matrix-publiclist/
Hey folks, I've released
0.13.1which fixes a critical bug in
0.13.0where messages from matrix would crash the bridge. Users brave enough to be running
developdo not need to do anything. https://github.com/matrix-org/matrix-appservice-irc/releases/tag/0.13.1. This would only have affected you if you tried to install or update the
0.13bridge in the last two weeks.
See you next week, and be sure to stop by #twim:matrix.org with your updates!