So because I have gone temporarily off my rocker, I'm working on an #xmpp client using #dotnet 10 and WPF, with artalk-xmpp for XMPP, libsignal for #OMEMO, and prism for screen reader output where needed. I'm only an evening into it, and I can already tell that OMEMO is going to be the source of complicated, inexplicable, and unreproducible bug reports for decades to come. It's still not as overcomplicated as #matrix, though.
@fastfinge another instance of "there's no good #xmpp client, let's do another one that probably will never be good either"? Gajim and Dino can run on Windows and macOS. Sure, they don't work great and don't feel native, but fixing those issues is probably easier than starting from scratch. Just saying.
@debacle@fastfinge GTK uses AccessKit, a cross-platform accessibility API. There might be issues with it, but fixing those would also bring immediately more benefit to a lot of apps, not only XMPP clients or GTK apps.
@pixelschubsi@debacle Yes, but fixing it is far beyond my skill level. I also do not run or care about Linux until it’s systemic accessibility issues get fixed. I’ll stick to developing for a platform that at least treats me like a second class citizen, rather than a problem it wishes would just go away.
