| 14 Apr 2024 |
 Qyriad | Idk | 21:56:42 |
 admin (Moderation Team) | can you flush cache and reload? | 21:57:06 |
| admin (Moderation Team) | before I go ballistic on the room | 21:57:14 |
| Qyriad | No effect | 22:01:21 |
| Qyriad | Oh it was the audio room, huh | 22:05:04 |
| Qyriad | Alright yep this appears to have worked well! Thank you! | 22:15:13 |
| 15 Apr 2024 |
 @fractivore:cyberia.club | eyyyy the room is completely broken for me now. The old one shows a message about being upgraded, while the new one says I'm not allowed to send messages. | 05:33:51 |
| @fractivore:cyberia.club | * eyyyy the room is completely broken for me now. The old one shows a message about being upgraded, while the new one says I do not have permission to post to the room. | 05:34:51 |
| @fractivore:cyberia.club | * eyyyy the #audio:nixos.org room is completely broken for me now. The old one shows a message about being upgraded, while the new one says I do not have permission to post to the room. | 05:35:49 |
 hexa | Then it likely copied permissioms from the old room. | 05:36:01 |
| @fractivore:cyberia.club | In reply to @hexa:lossy.network
Then it likely copied permissioms from the old room. I don't understand. I had permission to post to the old room. If it copied permissions, wouldn't I have permissions to post to the new one as well? | 05:38:54 |
| @fractivore:cyberia.club | or, it copied them after I left? | 05:40:11 |
| @fractivore:cyberia.club | Just in case, I tried leaving the room and rejoining it, but no dice. | 06:48:19 |
| Qyriad | I don't appear to have permissions either | 06:51:21 |
| admin (Moderation Team) | should be fixed | 06:56:34 |
| admin (Moderation Team) | it was the room permissions, which I locked down on the old room, before upgrading | 06:56:50 |
| @fractivore:cyberia.club | Thanks for fixing it! | 14:13:16 |
 K900 | I think #macos:nixos.org is scuffed now too | 14:15:20 |
| hexa | always has been! | 14:57:22 |
| hexa | * always has been | 14:57:29 |
| admin (Moderation Team) | fixed | 14:59:02 |
| @fractivore:cyberia.club | So the rooms are having desync issues right? Do we know what's causing that to happen? | 16:15:43 |
| K900 | The redactions on the nixos.org server | 16:16:03 |
| @fractivore:cyberia.club | And the fact that those keep triggering this bad state... is a protocol-level bug? I'm just trying to understand better | 17:19:29 |
| @fractivore:cyberia.club | Like, there's some ambiguity in the protocol over how to handle redactions originating from the host server vs other federating servers, and different server implementations made different choices? Or, maybe it could just be a bug in one or more server implementations? | 21:00:20 |
 eyJhb | Isn't it just because you only really see it when you resync your entire client again? E.g. if you haven't reset you client since before the event, you wouldn't notice | 21:10:51 |
|  d3v0 left the room. | 22:29:27 |
| @fractivore:cyberia.club | In reply to @eyjhb:eyjhb.dk
Isn't it just because you only really see it when you resync your entire client again? E.g. if you haven't reset you client since before the event, you wouldn't notice But if you DO reset your client in the meantime, it's unable to resolve the discrepancy and can't sync the room at all? Do I have that right? So in that case, is it a bug with the client-server API part of the protocol, or just a bug in some clients? | 22:53:41 |
| 16 Apr 2024 |
| Qyriad | In reply to@admin:nixos.org
fixed Still broken for me at least | 00:00:15 |
| eyJhb | In reply to @fractivore:cyberia.club
But if you DO reset your client in the meantime, it's unable to resolve the discrepancy and can't sync the room at all? Do I have that right? So in that case, is it a bug with the client-server API part of the protocol, or just a bug in some clients? No, the events are just redacted. So it can't sync what's not there to sync. :) at least that's my understanding | 09:32:52 |
