This Week in Matrix 2019-11-15

2019-11-15 — This Week in Matrix — Ben Parsons

Matrix Live 🎙

This week I spoke to Annie from the Ditto project.

Find out more:

#ditto:elequin.io
Testflight: https://testflight.apple.com/join/9M0ERlKd
Feedback: https://ditto.upvoty.com

Dept of Spec 📜

MSC2354: Device to device streaming file transfers

Mathijs offered:

I opened my first MSC, to use webrtc for streaming file transfers from device to device (rather than account to account)

Spec

anoa said:

New MSCs

In Final Comment Period

Merged MSCs

The Spec Core Team's focused MSC's continue to be MSC1756 (cross-signing), MSC2324 (new spec process), and MSC2313 (ban lists).

Dept of Servers 🏢

Synapse

anoa said:

This week saw work on implementing message retention policies, the continuation of migrating matrix.org to new hardware and some other little fixes.

The public rooms directory is also set to private by default now. Please read the accompanying blog post for the reasoning behind it.

Ruma updates

We missed it at the time, but the Ruma project has some updates to share, focused on the ruma-events projects.

https://www.ruma.io/news/new-releases-2019-11-05/

Known Matrix Server Selector Websites

Over in #matrixservers:raim.ist, grin provided this list-of-lists of Matrix public home servers:

Dept of Bridges 🌉

mautrix-whatsapp

Tulir reported:

mautrix-whatsapp now has basic relaybot support. Since WhatsApp doesn't have usable bots, relaybot in this case means using a normal account as a relay. To enable the relaybot in your bridge instance, copy this config block into your config, update is as needed, and simply log in normally in the configured relaybot management room.

matrix-appservice-slack 1.0.2

Half-Shot announced:

Hey all, matrix-appservice-slack 1.0.2 has been released. This contains a small number of bug fixes and doc changes.

Dept of Clients 📱

Pattle: version 0.14.0

Wilko announced:

A new version has been made available and should soon be on Google Play!

Note that this version will not be on TestFlight (yet) because notifications are currently only implemented on Android (using Firebase, so same goes for F-Droid for the time being).

Changes

  • Show notifications when receiving a new message!
  • Username is not checked whether it's available anymore

This was done for a future feature (registration), however, a different approach will probably be taken.

Get Pattle

Issues or suggestions

If you stumble upon any issues or would like to suggest features, please do so here! You can login via GitHub and Gitlab.com!

Follow development

Follow development in #app:pattle.im!

Pattle 0.14.0

Kotlin projects: koma and Continuum

yuforia told us:

koma, Kotlin library:

  • Implement timeout in coroutines instead of waiting for timeout errors from HTTP library, which makes it easier to change the timeout on demand and may improve performance to some degree
  • Make use of experimental feature contracts in Kotlin 1.3 to avoid cast errors when inline class is used in non-local returns
  • Add API for getting thumbnails

Continuum, desktop client based on koma, version 0.9.28:

  • Use thumbnails of images and avatars to reduce data usage

https://matrix.org/_matrix/media/r0/download/matrix.org/GMyoaOATXbdcgKnGXCgpDnEA

Riot web

Bruno said:

Riot web should gain a new design for the member panel, with a UX more suited for a world where cross-signing is a thing. Will land today or early next week behind a feature flag on /develop.

There are some screenshots on the PR: https://github.com/matrix-org/matrix-react-sdk/pull/3620

Riot-Android

benoit offered:

Riot-Android: we are working on widget permission: new widget permission UX and use integration manager defined on the homeserver by default.

Riot iOS

Manu offered:

Riot iOS: We have fixed the display of terms for integrations. Riot iOS 0.10.2 is on his way to the App Store

RiotX

benoit offered:

RiotX: We are working on registration and login flow. Also spoiler are rendered and can even be sent using /spoiler command. It's also possible to block (ignore) and unblock users. Performance have been improved, and we are now using the new FragmentFactory. We are working on room detail screen, sticker rendering, and lots of other fun features. We schedule a release at the beginning of next week.

Dept of SDKs and Frameworks 🧰

matrix-bot-sdk v0.4.0-beta.15

TravisR reported:

v0.4.0-beta.15 of the matrix-bot-sdk has been released. v0.4.0 final is a themed release for lightweight bridges, and so far much of the common functionality is there. Some of the more niche and large features have yet to land, but the final release is still on the horizon (see what's left here). Please give it a test (npm install [email protected]) and report any issues to #matrix-bot-sdk:t2bot.io.

BETA FIFTEEN

Seshat new release

@poljar:matrix.org offered:

Seshat got a new release 🎉. Seshat now supports transparent index encryption. The PRs for Riot-desktop have been updated and encryption has been enabled for the index. The PRs are currently awaiting review, encrypted search will come to a place near you really soon™.

Dept of Ops 🛠

New guide about installing Synapse using only free resources

@ptman:feneas.org offered:

I (and hopefully others) feel that matrix needs more home servers. That's why I wrote a guide for setting one up using free resources and @benpa was kind enough to include it on matrix.org: https://matrix.org/docs/guides/free-small-matrix-server/

Room Directory defaults in matrix-docker-ansible-deploy

Regarding the recent discussions about room security, Slavi has been thinking about default settings for his ansible playbooks:

I wasn't entirely convinced what we should do about it. For my own personal (family & friends) homeserver, I have a few rooms published (this room being one of them), which are all public and OK to be published publicly. I was okay with the old defaults. Still, I can see how people may expect stricter defaults though. I've leaned on following this advice and making it not publish by default. I've made that change here.

Dept of Bots 🤖

Matrix-Alertmanager v0.1.0

@jaywink:federator.dev reported:

Matrix-Alertmanager, a bot that relays Prometheus Alertmanager alerts to Matrix rooms, gets a new release v0.1.0. Thanks to "daniego" the messages are now HTML formatted. Also dependencies have been bumped, Matrix JS SDK by "Lyr" and all the other deps by me. For more info: https://git.feneas.org/jaywink/matrix-alertmanager

alertmanager

Dept of Events and Talks 🗣

aa13q offered:

I've made a presentation about Matrix at the local 2600 meetup at Saint Petersburg, Russia recently. And now translated the text retelling into English too. It's an introduction presentation in general but (thanks to kitsune! :) it also contains good comments about the parts I've missed :) Would be happy to get feedback about the typos/etc. I hope it could be helpful to somebody who is willing to tell about Matrix in other local places :) https://aa13q.ru/#!posts/2019-11-01-matrix-2600/meta.md

@jaywink:federator.dev reported:

Not a part of the organizers, but syncing here for wider reach. There is a "FediConf 2020" conference being planned to happen in Barcelona sometime between May and September next year. It will be a conference for a wide audience of federated folk, so Matrix people might be interested in joining up. There is a poll for dates, a forum and also a Matrix room: #fediconf:matrix.libertalia.world

kitsune said:

in a complete coincidence with aa13q, I also talked about Matrix at Tokyo LUG. Plenty of good discussion. TLUG folks are extremely interested in decentralised identities and data retention as next most important frontiers in Matrix evolution.

Dept of Ping 🏓

RankHostnameMedian MS
1dodsorf.as457
2neko.dev507
3tedomum.net545.5
4aime.lesmatric.es572.5
5maunium.net579
6dmnd.sh630
7freitrix.de641
8matrix.vgorcum.com647.5
9kolosowscy.pl780
10grin.hu822

That's all I know 🏁

See you next week, and be sure to stop by #twim:matrix.org with your updates!

Avoiding unwelcome visitors on private Matrix servers

2019-11-09 — General, Security — Matthew Hodgson

Hi all,

Over the course of today we've been made aware of folks port-scanning the general internet to discover private Matrix servers, looking for publicly visible room directories, and then trying to join rooms listed in them.

If you are running a Matrix server that is intended to be private, you must correctly configure your server to not expose its public room list to the general public - and also ensure that any sensitive rooms are invite-only (especially if the server is federated with the public Matrix network).

In Synapse, this means ensuring that the following options are set correctly in your homeserver.yaml:

# If set to 'false', requires authentication to access the server's public rooms
# directory through the client API. Defaults to 'true'.
#
#allow_public_rooms_without_auth: false

# If set to 'false', forbids any other homeserver to fetch the server's public
# rooms directory via federation. Defaults to 'true'.
#
#allow_public_rooms_over_federation: false

For private servers, you will almost certainly want to explicitly set these to false, meaning that the server's "public" room directory is hidden from the general internet and wider Matrix network.

You can test whether your room directory is visible to arbitrary Matrix clients on the general internet by viewing a URL like https://sandbox.modular.im/_matrix/client/r0/publicRooms (but for your server). If it gives a "Missing access token" error, you are okay.

You can test whether your room directory is visible to arbitrary Matrix servers on the general internet by loading Riot (or similar) on another server, and entering the target server's domain name into the room directory's server selection box. If you can't see any rooms, then are okay.

Relatedly, please ensure that any sensitive rooms are set to be "invite only" and room history is not world visible - particularly if your server is federated, or if it has public registration enabled. This stops random members of the public peeking into them (let alone joining them).

Relying on security-by-obscurity is a very bad idea: all it takes is for someone to scan the whole internet for Matrix servers, and then trying to join (say) #finance on each discovered domain (either by signing up on that server or by trying to join over federation) to cause problems.

Finally, if you don't want the general public reading your room directory, please also remember to turn off public registration on your homeserver. Otherwise even with the changes above, if randoms can sign up on your server to view & join rooms then all bets are off.

We'll be rethinking the security model of room directories in future (e.g. whether to default them to being only visible to registered users on the local server, or whether to replace per-server directories with per-community directories with finer grained access control, etc) - but until this is sorted, please heed this advice.

If you have concerns about randoms having managed to discover or join rooms which should have been private, please contact [email protected]

Client-server r0.6.0 and Identity Service r0.3.0 releases

2019-11-08 — General — Travis Ralston

Hey all,

For the last several months the team has been working on tightening up privacy in Matrix, and with the 1.4 release of Synapse and Riot quite a lot has been done in the area. One of the remaining pieces was to release all the specification changes to help other client/server implementations achieve the same goals, and now we've done that.

The Client-Server r0.6.0 and Identity Service r0.3.0 spec releases both cover the privacy improvements added through a number of MSCs in the last few months. Of particular note is that identity servers are now expected to support terms of service endpoints, which requires authentication that clients might need to worry about - check the spec changelogs for details.

The full changelog for the Client-Server r0.6.0 release is:

  • Breaking Changes

    • Add id_access_token as a required request parameter to a few endpoints which require an id_server parameter as part of MSC2140. (#2255)
  • New Endpoints

    • Add POST /account/3pid/unbind for removing a 3PID from an identity server. (#2282)
  • Backwards Compatible Changes

    • Add M_USER_DEACTIVATED error code. (#2234)
    • Remove bind_msisdn and bind_email from /register now that the identity server's bind endpoint requires authentication. (#2279)
    • Add m.identity_server account data for tracking the user's preferred identity server. (#2281)
    • Deprecate id_server and make it optional in several places. (#2310)
  • Spec Clarifications

    • Add missing format fields to m.room.message$m.notice schema. (#2125)
    • Remove "required" designation from the url field of certain m.room.message msgtypes. (#2129)
    • Fix various typos throughout the specification. (#2131, #2136, #2148, #2215)
    • Clarify the distinction between m.key.verification.start and its m.sas.v1 variant. (#2132)
    • Fix link to Olm signing specification. (#2133)
    • Clarify the conditions for the .m.rule.room_one_to_one push rule. (#2152)
    • Clarify the encryption algorithms supported by the device of the device keys example. (#2157)
    • Clarify that /rooms/:roomId/event/:eventId returns a Matrix error. (#2204)
    • Add a missing state_key check on .m.rule.tombstone. (#2223)
    • Fix the m.room_key_request action value, setting it from cancel_request to request_cancellation. (#2247)
    • Clarify that the submit_url field is without authentication. (#2341)
    • Clarify the expected phone number format. (#2342)
    • Clarify that clients should consider not requesting URL previews in encrypted rooms. (#2343)
    • Add missing information on how filters are meant to work with /context. (#2344)
    • Clarify what the keys are for rooms in /sync. (#2345)

The full changelog for the Identity Service r0.3.0 release is:

  • New Endpoints

    • Add /account, /account/register, and /account/logout to authenticate with the identity server. (#2255)
    • Add endpoints for accepting and handling terms of service. (#2258)
    • Add /hash_details and a new /lookup endpoint for performing hashed association lookups. (#2287)
  • Backwards Compatible Changes

    • Deprecate the v1 API in favour of an authenticated v2 API. (#2254)

This Week in Matrix 2019-11-08

2019-11-08 — This Week in Matrix — Neil Johnson

Matrix Live 🎙

Sorry folks, no matrix live this week, your regular programming will continue next week.

Dept of Spec

A big week in spec land.

Client-server r0.6.0 and Identity r0.3.0 spec releases

TravisR offered:

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

anoa announced:

Approved MSCs

Final Comment Period

New MSCs

The Spec Core Team have chosen MSC1756 (cross-signing), MSC2324 (new spec process), and MSC2313 (ban lists) to focus on this week :)

Dept of Clients 📱

Riot-iOS

Manu offered:

  • 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.

RiotX

benoit reported:

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.

Riot Android

benoit offered:

We are working on the Integration Manager management.

Riot Web

Neil had this to say:

The Riot gang landed 1.5.1 which contained the emoji picker (thanks Tulir!).

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.

Fractal

Alexandre Franke offered:

We did a couple bugfixes including one for a long standing crasher and another more recent crasher.

Seshat

@poljar:matrix.org said:

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.

Quarternion

kitsune said:

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.

Matrix Notepad

@kb1rd:kb1rd.net reported:

  • 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)

Dept of Servers 🏢

Synapse

Neil said:

This week we shipped 1.5.1 which contains a small bug fix to prevent a potential DoS vector.

Separately we merged support for label based filtering into develop and are now working on allowing admins to configure message retention policies.

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.

Rust Workers

Black Hat told us:

I'm working on writing Synapse workers in Rust. Only a few things are working, but the performance seems good.

Department of Ops

Kubernetes

Ananace announced:

Just pushed the K8s-optimized Synapse 1.5.1 image

Docker - improved LDAP

JCG reported:

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.

Docker - multi-arch

Black Hat told us:

my multi-arch synapse docker image is updated to synapse 1.5.1

Docker

Mathijs said:

The images for synapse v1.5.1 were pushed to docker hub for avhost and my personal repo.

Server Tombola

@mj:nltrix.net offered:

It gets a tombola of versions at the list of Public Synapse Homeservers https://www.anchel.nl/matrix-publiclist/

Dept of Bridges 🌉

Half-Shot announced:

Hey folks, I've released matrix-appservice-irc 0.13.1 which fixes a critical bug in 0.13.0 where messages from matrix would crash the bridge. Users brave enough to be running develop do 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.13 bridge in the last two weeks.

Dept of Ping 🏓

RankHostnameMedian MS
1maunium.net492.5
2aryasenna.net633
3matrix.vgorcum.com656
4room409.xyz686
5kolosowscy.pl717.5
6uraziel.de740
7nltrix.net757
8dodsorf.as777.5
9neko.dev885
10casavant.org918.5

That's all I know 🏁

See you next week, and be sure to stop by #twim:matrix.org with your updates!

Fun and games with certificate transparency logs

2019-11-06 — General — Matthew Hodgson

Hi all,

This morning (06:11 UTC) it became apparent through mails to [email protected] that a security researcher was working through the TLS Certificate Transparency logs for *.matrix.org,*.riot.im and *.modular.im to identify and try to access non-public services run by New Vector (the company formed by the original Matrix team, which hosts *.matrix.org on behalf of the Matrix.org Foundation, and develops Riot and runs the https://modular.im hosting service).

Certificate Transparency (CT) is a feature of the TLS ecosystem which lets you see which public certificates have been created and signed by given authorities - intended to help identify and mitigate against malicious certificates. This means that the DNS name of any host with a dedicated public TLS certificate (i.e. not using a wildcard certificate) is visible to the general public.

In practice, this revealed a handful of internal-facing services using dedicated public TLS certificates which were accessible to the general internet - some of which should have been locked to be acessible only from our internal network.

Specifically:

  • kibana.ap-southeast-1.k8s.i.modular.im - a Kibana deployment for a new experimental Modular cluster which is being set up in SE Asia. The Kibana is in the middle of being deployed, and was exposed without authentication during deployment due to a firewall & config error. However, it is not a production system and carries no production traffic or user data (it was just being used for experimentation for hypothetical geography-specific Modular deployments). We firewalled this off at 07:53 UTC, and are doing analysis to confirm there was no further compromise, and will then rebuild the cluster (having fixed the firewall config error from repeating).
  • AWX deployments used by our internal Modular platform, which were behind authentication but should not be exposed to the public net.
  • Various semi-internal dev and testing services which should be IP-locked to our internal network (but are all locked behind authentication too).

Additionally, certain historical Modular homeservers & Riots (from before we switched to using wildcard certs, or where we’ve created a custom LetsEncrypt certificate for the server) are named in the CT logs - thus leaking the server’s name (which is typically public anyway in that server’s matrix IDs if the server is federated).

We’re working through the services whose names were exposed checking for any other issues, but other than the non-production SE Asia Kibana instance we are not aware of problems resulting from this activity.

Meanwhile, we’ll be ensuring that semi-internal services are only exposed on our internal network in future, and that Modular server names are not exposed by CT logs where possible.

TL;DR: You can list all the public non-wildcard TLS certs for a given domain by looking somewhere like https://crt.sh/?q=%25.matrix.org. This lets you find internal-sounding services to try to attack. In practice no production services were compromised, and most of our internal services are correctly firewalled from the public internet. However, we’re reviewing the IP locking for ones in the grey zone (and preventing the bug which caused an experimental Kibana to be exposed without auth).

We’d like to thank Linda Lapinlampi for notifying us about this. We’d also like to remind everyone that we operate a Security Disclosure Policy (SDP) and Hall of Fame at https://matrix.org/security-disclosure-policy/ which is designed to protect innocent users from being hurt by security issues - everyone: please consider disclosing issues responsibly to us as per the SDP.

This Week in Matrix 2019-11-01

2019-11-01 — This Week in Matrix — Ben Parsons

Dept of Spec 📜

Spec Updates

anoa reported:

Merged MSCs

Final Comment Period

New MSCs

No other new MSCs appeared this week.

MSCs the Spec Core Team are focusing on next week are: MSC2244 (mass redactions), MSC1946 (SSSS), and MSC2313 (ban lists).

Dept of Servers 🏢

Synapse 1.5.0 released

Various updates including a security fix, check the announcement.

Several packaging projects have been updated to deploy the new version:

Like always the mvgorcum/docker-matrix repo also includes the release candidates, as they were released.

Install Party

Brendan announced:

A couple of weeks ago I shouted here about a project I've been working on named Install Party, which provides tools for provisioning and managing servers for Matrix homeserver install workshops/parties.

Since then, I've been working on improving it, and today it's finally reached v1.0! This version includes configurable DNS and infrastructure providers, the ability to create multiple server in one run, user-defined post-install scripts, as well as codebase cleanups and a better documentation.

You can find more details about the project and this release at https://brendan.abolivier.bzh/install-party-1.0/, and in #install-party:abolivier.bzh 🙂

Dept of Bridges 🌉

mautrix-telegram

Tulir told us:

  • Parallelized file transfer: The bridge now has an option to use multiple telegram connections and a streaming connection to the Matrix media repo when copying files. This should make it much faster and use less ram for big files.
  • Matrix doesn't have native captions, so !tg caption <text> now exists to send the next image or file to telegram with <text> as the caption.
  • Animated sticker bridging and helm charts were merged into master.

matrix-appservice-node 0.4.1 released

Half-Shot reported:

Bridges-in-nodejs-fans, today we have released 0.4.1 of the matrix-appservice-node library. For those not aware (presumably most), this library is a barebones piece of kit that helps you to listen over the AS api for transactions, in a more barebones manner than matrix-appservice-bridge. The changes in this release are a total transformation of the library into Typescript, and updating dependency packages which had gotten out of date.

EDIT: I cocked up the release, so have a 0.4.1

matrix-appservice-bridge 1.11.1 released

Half-Shot offered:

Also, https://github.com/matrix-org/matrix-appservice-bridge/releases/tag/1.11.1

Dept of Clients 📱

Ditto Chat project announcement

Annie said:

Officially announcing a new mobile client project: Ditto Chat

  • Project Status

    • Minimum Viable Product is on TestFlight
    • Can: login, send / receive messages
  • Tech Stack

    • Bare React Native - no Expo
    • matrix-js-sdk
  • Vision

  • I want Ditto to be a chat app that is user-friendly and performant for the average user, rivaling apps like GroupMe, Messenger, and WhatsApp.

  • Later on, I want Ditto to have a desktop / browser version and be stable enough for regular use.

CONTRIBUTORS: I would love to have some help on Ditto if anybody is looking for a side project! Join #ditto:elequin.io for updates.

More photos: http://dittochat.org

Check out the room at #ditto:elequin.io.

Ditto image

miitrix

sorunome offered:

Miitrix has received some updates!

  • Save state and resume when starting up - no need for an initial sync each time anymore!
  • Send read receipts
  • Send typing notifications
  • Remove HTTPC and only use CURL to add support for servers that don't have TLS1.1 anymore! And way faster!

Support room: #miitrix:sorunome.de Donate: https://liberapay.com/Sorunome

Miitrix was featured as a star attraction at MozFest last weekend, thanks Soru!

Continuum 0.9.27

yuforia reported:

Continuum, desktop client in Kotlin, version 0.9.27:

Added notification viewer.

https://matrix.org/_matrix/media/r0/download/matrix.org/ziPiTnybBwEEcSMPZRjhNlsV

Fractal

Alexandre Franke told us:

We fixed redaction, it’s working again. We still don’t remove the messages from view but there is a WIP merge request to do just that.

#matrix-client-developers:matrix.org

f0x announced:

#matrix-client-developers:matrix.org has been revived, intended for discussion between developers of different Matrix clients.

This is the room to head to for Matrix Client developer chat.

Matrix Notepad

KB1RD announced:

Version 0.1.2 update brings a major overhaul of the user interface. The main features are:

  • A new sign in dialog (with password authentication. No access tokens!)
    • Those who are already signed in will stay signed in
    • Also created a Matrix Notepad logo
  • Technically, a single Matrix client is used instead of re-creating it each time a new document is opened
    • This makes document loading faster
  • Added a document list and an add button
  • Added the document room ID to the URL
  • Fixed various bugs that have been encountered. Maybe I can finally say that it's bug-free!

Riot v1.5.1-rc.1

Riot v1.5.1-rc.1 is up on https://riot.im/staging with a collection of bugfixes, some further a11y fixes and... a new reaction picker from tulir!

Dept of Bots 🤖

matrix-episode-bot

anoa told us:

I made a bot that can give you links to TV show episodes that get mentioned in rooms: https://github.com/anoadragon453/matrix-episode-bot

It's not as cool as it sounds. Basically you put all the titles and links in a config file and whenever someone says e.g "I really like S05E09", it'll give you the name of that episode and a link to it. You can also just mention an episode title and it'll give you the link.

Made with nio-template.

Dept of Ping 🏓

RankHostnameMedian MS
1matrix.tetraodon.nl336
2room409.xyz490
3nora.codes491
4freitrix.de491
5matrix.dapor.net492
6stratum0.org500
7midov.pl503
8bau-ha.us537
9linuxgl.ch539
10maunium.net577

That's all I know 🏁

See you next week, and be sure to stop by #twim:matrix.org with your updates!

NextPage 2