Tulir Asokan
Tulir Asokan
The token is the registration code, not related to the relay secret
Discussion about the issue on the original MSC: https://github.com/matrix-org/matrix-spec-proposals/pull/3952#discussion_r1172839435
@mscbot concern no client implementation for user-defined fields
That's already listed in the roadmap file
Everyone can switch back to QR code login (but may need to unlink existing devices if you already linked some via google login)
It uses whatever google messages picks by default, shouldn't be affected by the bridge
The `name` field has to be changed to be treated differently from conduit, and the relevant version should preferably be in the main section of semver rather than in the...
Check ```sql SELECT timestamp FROM message WHERE timestamp>2000000000000; SELECT last_read_ts FROM user_portal WHERE timestamp>2000000000000; SELECT dispatched_at, completed_at, cooldown_until FROM message WHERE dispatched_at>2000000000000 OR completed_at>2000000000000 OR cooldown_until>2000000000000; ```
Oops, the first one seems like a pgadmin bug, but the other two just had mistakes in the query ```sql SELECT message.timestamp FROM message WHERE message.timestamp>2000000000000; SELECT last_read_ts FROM user_portal...
The issue is that `client` and `federation` are not listed in resources, but I'm not sure if requiring them for the new endpoints is intentional or not. If it's intentional,...