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 Ive been playing with The Dotnet ecosystem recently, and I have to say I'm impressed. As long as you.re willing to write a common core and per-platform UIs, it's the framework to go with. It's the only way I know of to get native UIs on every platform without cross-language pain.
@miki Yup. Though in this particular case I can't be cross platform, because I need to use windows encryption primitives to safely store OMEMO keys and usernames and passwords and things.
@fastfinge@miki@plzupgrademe short question: why not participate in gajim development and help improving it rather than reinviting the wheel once again?
That approach would help the ecosystem way more than starting yet another client and abandoning it half way through. Just my two cents.
@Monal@miki@plzupgrademe If you want to be both cross platform and accessible, WX is literally your only practical option. QT5 has come a long way, but there are still lots and lots of issues you’d have to work around. GTK is right out.
