No, just some statistics about how many people are using Matrix already anyway. The Matrix bridge going down is not really different from any other kind of netsplit on the IRC side.
AFAIU it was just a restart of the matrix.org ↔ OFTC bridge, but by the way how IRC works it shows everyone on the bridge as having left on the IRC side, and because of how the bridge works (to reduce resource usage on OFTC’s side mostly) they will probably only re-appear on the IRC side after they wrote something. On the Matrix side this was not visible at all.
With 2/3 of the people already using Matrix anyway and expecting it to work like Matrix, we also end up with such hard to read messages on the IRC side: You need to click on 4 different links to get the whole message.
For someone who used IRC last time in late 90s and never used Matrix could you clarify this part: “…No user registration would be allowed on that server (except for admin), users can register on whichever other matrix server.”. Which “other matrix server” is meant here and why so complicated (e.g. can users use oauth to register)?
Just like IRC, Matrix is a distributed network of many servers. Unlike with IRC, user authentication is not central to a single server but managed by each server individually. Similarly, rooms are managed per server (and their “handle” contains the server’s hostname), but users from any server can use rooms from any other server, or talk to users from any other server.
You could register your user on matrix.org, for example, and then still communicate with the GStreamer Matrix room that is created on gstreamer.org. As can users from the GNOME Matrix server, or your own one, or any other really.
The plan here was to use the gstreamer.org Matrix server only to manage the existence of the GStreamer room(s), and have user management and all that be handled elsewhere.