| 15 Apr 2024 |
 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 |
| eyJhb | E.g. event for channel topic, channel image, etc. | 09:33:14 |
| @fractivore:cyberia.club | I'm just thinking, it can't be intended behavior. Thanks for engaging with me on this line of inquiry. | 18:20:22 |
| @fractivore:cyberia.club | In reply to @qyriad:katesiria.org
Still broken for me at least Even now? What client are you on, by the way? | 18:20:51 |
 Rostby | This might be stupid but I feel like matrix is alot more clunky compared to alternatives | 18:23:57 |
| K900 | It is | 18:24:03 |
 Charles | What alternatives | 18:36:51 |
|  jhuc joined the room. | 19:13:31 |
| 17 Apr 2024 |
|  ahoneybun changed their profile picture. | 15:23:41 |
| K900 changed their display name from K900 ⚡️ to K9Ö0. | 17:16:42 |
| K900 changed their display name from K9Ö0 to K900. | 17:21:53 |
