| 6 Jul 2024 |
 @emma:rory.gay | In reply to @hexa:lossy.network
anyway, not great that one has to fiddle with room state client limitation | 23:43:10 |
| @emma:rory.gay | even under nheko migrating parent spaces isnt ideal, but it does allow all 4 combinations | 23:43:39 |
| @emma:rory.gay | "only for room members", "only for space members", "official space" or "affiliated space" are the options nheko lists | 23:44:17 |
| @emma:rory.gay | it calls them communities but thats besides the point | 23:44:31 |
| @emma:rory.gay | im not sure what affiliated means though | 23:45:30 |
| 7 Jul 2024 |
|  dminca joined the room. | 09:46:55 |
| dminca | hi, when I leave the NixOS (replaced) space, should I also leave the rooms? | 09:48:15 |
 emily | nope, the rooms are in the new space | 09:48:35 |
| emily | the space room itself just got broken | 09:48:46 |
| dminca | Ah, ok, understood. Thank you :) | 09:49:02 |
 @aloisw:kde.org | The offtopic room shows the replaced space here too, and its icon is pixelated. | 09:51:20 |
| emily | maybe that room got broken or replaced too at some other point…? | 09:52:56 |
| @aloisw:kde.org | I don't think so, the room is still pretty active. | 09:53:30 |
| emily | I remember someone reporting some kind of issue with the offtopic room recently, but I don't remember the details | 09:54:10 |
| emily | if you're still in the old space, maybe that's causing some kind of weird issue | 09:54:18 |
|  Ramses 🇵🇸 joined the room. | 10:05:56 |
| @emma:rory.gay | In reply to @emilazy:matrix.org
if you're still in the old space, maybe that's causing some kind of weird issue its because the canonical space listing was never changed | 11:01:01 |
| @emma:rory.gay | and that requires manual state fuckery... | 11:01:17 |
| emily | canonical space listing? | 11:02:55 |
| @emma:rory.gay | basically, each room in the space has a room -> space relation besides space -> room | 11:04:24 |
| @emma:rory.gay | what happened in the nixos room, and presumably also the case here, is that the room -> space relation (m.space.parent state event with space id) was never updated, so the room was still pointing to the old space
to fix it, you need to set "canonical" to false in the old event, and send a new event with "canonical" set to true | 11:06:02 |
| emily | I see. sounds horrible. | 11:06:20 |
| @emma:rory.gay | tl;dr upgrading a space doesnt touch any events in the rooms in it | 11:07:21 |
| emily | I don't think I understand why a room even needs a canonical space pointer. | 11:08:11 |
| @emma:rory.gay | allows discovery of the space just from the room | 11:09:05 |
 hexa | In reply to @emma:rory.gay
what happened in the nixos room, and presumably also the case here, is that the room -> space relation (m.space.parent state event with space id) was never updated, so the room was still pointing to the old space
to fix it, you need to set "canonical" to false in the old event, and send a new event with "canonical" set to true manual state fuckery | 16:03:36 |
| hexa | because /upgraderoom on the old space doesn't care | 16:03:48 |
| hexa | I fault element for the broken workflow | 16:04:04 |
| hexa | managing a large matrix space just isn't fun | 16:04:22 |
| @emma:rory.gay | element isnt involved in /upgraderoom btw | 16:19:17 |
