Will Hunt

`!storepass` uses `PASS`, rather than sending anything automatically. I don't really want to add any NickServ specific functionality into the bridge, ideally.

We have automated monitoring but the types of failures that we have seen are not fitting the models we expect. The status.matrix.org page is manually updated at the moment, and...

I believe this situation is now improved, we've got monitoring on the bridge for: - Total outages of the process - Increased waves of connections (indicating spam or dangerous behaviours)...

This is https://github.com/matrix-org/synapse/issues/2807. Workaround is to `curl --data '{"type": "m.login.application_service", "username": "your_sender_localpart"}' 'http://yourhomeserver/_matrix/client/r0/register?access_token=your_as_token'` which will give the bot a profile and allow invites to work.

I'm not sure why that's happening, but that sounds more like a synapse issue than ours.

This sounds like the infamous state reset bug to me, I've asked how to proceed with this. (I don't think the bridge can do much about it).

It's not updated automatically yet, we could probably make a change to automatically adjust user nicks as they speak as a first step. Given this could cause quite a lot...

I think this is a mixed bug. We *do' report to the user via the admin room when a message has been explicitly rejected, so I can only imagine unregistered...

Well, if this is all true then it effectively pauses messages in the room when the privacy filter is active..and leaks messages if not. The federated aspect is irrelevant, as...

Hey there, I'd absolutely love to have this change included. It has been a long time coming. Obviously we'd need to be careful to support "legacy" identifiers as the old...