User avatar
🇨🇦Samuel Proulx🇨🇦 @fastfinge@interfree.ca
2d
So because I have gone temporarily off my rocker, I'm working on an client using 10 and WPF, with artalk-xmpp for XMPP, libsignal for , 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 , though.
9
5
8
0
User avatar
Debacle @debacle@framapiaf.org
2d
@fastfinge

You might take a look into , a once promising, but later abandoned /#XMPP client by a.k.a. (not on ?):

uwpx.org

github.com/UWPX/UWPX-Client

Maybe you can even take over his work instead of starting from scratch?

IIRC, it does have , but no A/V calls, no message reactions, maybe , not sure.
1
0
0
0
User avatar
🇨🇦Samuel Proulx🇨🇦 @fastfinge@interfree.ca
2d
@debacle Sadly the accessibility infrastructure is poor enough I’d be ripping out and rebuilding it entirely. And it’s not using an up to date library. So I’d also be rewriting the xmpp parts.
0
0
1
0