Tulir Asokan

Making it configurable doesn't really solve anything. I'll probably include proper disambiguation in megabridge, but I couldn't find any Go libraries for [UTS #39](https://www.unicode.org/reports/tr39/) confusable detection, so will need to...

It's supposed to be added by the caller https://github.com/mautrix/go/blob/main/crypto/machine.go#L395

It being a regression is just speculation, could be it has always been like that. I only noticed it recently when sending events to certain rooms was very slow and...

Implementations seem to implement what's described in the MSC, so removing the needs-checking label

The MSC requires an opinion from product-centered folks, so marking this as ready for review. The [current spec](https://spec.matrix.org/v1.10/client-server-api/#mentioning-the-replied-to-user) is just a recommendation, so following it is not required and this...

Probably won't bother with this since refresh tokens aren't required and the entire auth system is about to be replaced. I can add the refresh token to the login response...

It'll probably be changed eventually as mentioned in https://mau.fi/blog/2024-08-mautrix-release/, fairly low priority though as there's nothing exploitable

This probably needs to be configurable. Bridges in particular currently expect that proxy settings only apply to the remote network, not Matrix.

Env vars are added for the whole program, not individual `ClientSession`s

Nowadays we have [appservice pinging](https://spec.matrix.org/v1.11/application-service-api/#pinging), so the backoff should just be reset after a successful ping (initiated by the appservice) rather than manual server admin intervention.