| 18 Jul 2025 |
 Cat | The reason why communities with corporate influence tend to organise healthy is because corporations learned how to organise properly already. They know that Security, IT administration and Human Relations are not something that the same people are good at. So separate them.
Communities need to understand that your admins need not be moderators. Leave moderation to moderators and administration to administrators even if they sometimes are the same creature with diffrent hats.
So thats the TLDR of what my post will be about and this will materialise in Draupnir with Draupnir supporting this pattern of having a team own stuff so that team members can come and go without it being a security risk. | 17:33:21 |
| Cat | So since Draupnir must be able to create your rooms now it also needs a manual room upgrade command even if its a rudementary one at that. | 17:34:24 |
 emily | In reply to @0x4a6f:matrix.org
I did something back then: https://github.com/NixOS/infra/wiki/Tombstoning-a-room-on-Matrix good grief has @k900:0upti.me really been doing this | 17:35:22 |
| Cat | Thats a creative solution to the problem. | 17:36:54 |
| Cat | using 2 tombstones. | 17:37:03 |
| Cat | https://gitea.blesmrt.net/mikaela/scripts/src/branch/master/bash/matrix-upgrade-room.bash is the script i like to refer to. | 17:38:08 |
| emily | I'm inferring that the bug v12 tries to fix is "an attacker can make a room's state permanently screwed up beyond fixing" | 17:39:22 |
| emily | though I wouldn't have expected them to put out that softening statement on the urgency if any arbitrary attacker can do that, hmm | 17:39:35 |
 f0x | huh, but the predecessor event_id being the tombstone wasn't even that important right, just happens to be what Synapse does since it can create chicken and egg at the same time | 17:40:00 |
| Cat | its important but the exact event ID is not. | 17:41:02 |
