| 16 Jul 2025 |
 K900 | And can't reach the origin server of the event | 20:14:14 |
| K900 | It will see an inconsistent state of the room | 20:14:15 |
 Zhaofeng Li | But if A explicitly blocks matrix.org by policy and a newly-joined homeserver doesn't configure additional trusted servers, the room will still be (partly) unusable, right? | 20:15:57 |
| K900 | Kinda | 20:16:50 |
| K900 | It depends on how you even join the room | 20:16:57 |
| K900 | Because you need to talk to another server to join a room | 20:17:11 |
| K900 | So if you just can't federate, you can't do that either | 20:17:26 |
| Zhaofeng Li | In reply to @k900:0upti.me
Because you need to talk to another server to join a room let's say the newly-joined homeserver can talk to all homeservers including B and matrix.org (both blocked by A) | 20:18:20 |
| K900 | Can they talk to A though? | 20:18:42 |
| K900 | If they can talk to A, they'll fetch the keys directly | 20:18:47 |
| K900 | So B and the new server will be on different sides of the split | 20:19:17 |
| Zhaofeng Li | In reply to @k900:0upti.me
Because you need to talk to another server to join a room * let's say the newly-joined homeserver can talk to all homeservers including B and matrix.org (both blocked by A) except for A which is down forever | 20:19:55 |
| K900 | Like fundamentally Matrix room state is not consensus, it's CRDT | 20:21:49 |
| K900 | So different participants seeing different states is expected | 20:22:02 |
| K900 | And ideally everything gets reconciled in the end | 20:22:17 |
