blob: 49a3cc8700732d03efb78d451a36b43e4362bafc (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
|
# Blacklisted due to https://github.com/matrix-org/matrix-spec/issues/942
The only membership state included in a gapped incremental sync is for senders in the timeline
# Flakey
AS-ghosted users can use rooms themselves
AS-ghosted users can use rooms via AS
Events in rooms with AS-hosted room aliases are sent to AS server
Inviting an AS-hosted user asks the AS server
Accesing an AS-hosted room alias asks the AS server
If user leaves room, remote user changes device and rejoins we see update in /sync and /keys/changes
# This will fail in HTTP API mode, so blacklisted for now
If a device list update goes missing, the server resyncs on the next one
# Might be a bug in the test because leaves do appear :-(
Leaves are present in non-gapped incremental syncs
# We don't have any state to calculate m.room.guest_access when accepting invites
Guest users can accept invites to private rooms over federation
|
