| 15 Apr 2024 |
 @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 |
