| 15 Jul 2025 |
 K900 | This is the meta room | 19:36:15 |
 crunch | Gotcha thanks | 19:36:23 |
| crunch | Also is there a specific troubleshooting room or would that work? | 19:37:58 |
 bandithedoge | In reply to @crunch:kde.org
Also is there a specific troubleshooting room or would that work? just use the general room, also check the room list if you're having issues with some specific nix project | 19:39:03 |
| crunch | Nah its with nixpkgs | 19:39:22 |
| crunch | Thanks though | 19:39:29 |
| 16 Jul 2025 |
 Zhaofeng Li | (context: https://matrix.to/#/!6oudZq5zJjAyrxL2uY:0upti.me/$_ORWFlB70CFEKR_0D8fBbmJIrD4F3m28r31jpuQCmjA?via=matrix.org&via=envs.net&via=tchncs.de)
By the way, I just want to confirm if this is correct: If someone's homeserver (A) is unable to federate with (or otherwise allow connection from) a subset of other homeservers (B), the room is eventually cooked as other homeservers rely on A's events in the auth chain. Is this right? Will the same thing also apply if A goes down completely for an extended period of time?
| 20:10:37 |
| K900 | Not really | 20:11:00 |
| K900 | It will eventually consistent itself | 20:11:05 |
| K900 | Server B will try to fetch missing events from the federatin | 20:11:21 |
| K900 | * Server B will try to fetch missing events from the federation | 20:11:22 |
| K900 | And when A comes online, if ever, the state should reresolve | 20:11:43 |
| Zhaofeng Li | but B cannot know the servers keys of A (by policy) | 20:12:03 |
| Zhaofeng Li | and if A goes down forever, no newly-joined homeservers can ever know its keys | 20:12:23 |
| K900 | Most homeservers will trust keys fetched from matrix.org | 20:12:48 |
| K900 | Which are cached ~forever on matrix.org | 20:12:54 |
| K900 | You can configure other servers to be trusted relaying parties for keys | 20:13:38 |
| Zhaofeng Li | In reply to @k900:0upti.me
Most homeservers will trust keys fetched from matrix.org Ah, so this is the part that I'm missing | 20:13:45 |
| K900 | But if a certain server is configured to not trust anyone else | 20:14:14 |
| 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 |
