| 21 May 2025 |
Morgan (@numinit) | When a third party client can't even fix the terrible | 03:06:20 |
Randy Eckenrode | I used a CLI client for a bit (that was written in Go), but it had weird keybindings. | 03:14:53 |
Randy Eckenrode | * I used a terminal client for a bit (that was written in Go), but it had weird keybindings. | 03:15:18 |
Randy Eckenrode | gomuks | 03:15:40 |
Randy Eckenrode | Redacted or Malformed Event | 03:16:46 |
Winter | In reply to @winter:catgirl.cloud if I get one more of these invite spam waves i think i’m just gonna delete my Matrix account i got another. ngl it’s getting tempting | 04:22:16 |
Winter | are there any directions actually being made towards fixing this? i know the “policy servers” are a thing but like… that won’t help w/ this | 04:22:40 |
Winter | can i not just block any and all incoming room invites? | 04:22:51 |
uep | that would be a client feature, or a homeserver feature | 04:49:36 |
uep | so the answer is "it depends", and probably not many do | 04:50:01 |
uep | I do know that one user had a problem, with the #users channel being invite-only, that their homeserver just dropped all invites and they couldn't get it. | 04:50:47 |
uep | * I do know that one user had a problem, with the #users channel being invite-only, that their homeserver just dropped all invites and they couldn't get in, | 04:50:50 |
uep | so it does exist, somewhere. | 04:50:58 |