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
Pratik Patel @ppatel@mstdn.social
2d
@fastfinge Would you be interested in combining efforts to make a unified client? I'm working with Rust and wxdragon.
1
0
0
0
2d
@ppatel Sadly, i find rust incomprehensible. And i am not willing to just push AI generated code I can’t personally understand and reason about.
2
0
0
0
User avatar
Pratik Patel @ppatel@mstdn.social
2d
@fastfinge I can understand that. I'm far more familiar and comfortable with it. I review everything that goes into my projects. Even though I'm used to Python and like it for some things, I find it unwielding.
1
1
0
0
2d
@ppatel Same. I went with dotnet 10 and C#. Felt like the right tool for xmpp, a protocol developed entirely around xml.
1
0
0
0

User avatar
Pratik Patel @ppatel@mstdn.social
2d
@fastfinge Those are good choices. If I didn't worry about packaging issues or trying to be cross-platform, I'd choose .net and C# too or go to C++ straight.
1
1
0
0
@ppatel I’m hyper focused on windows. So packaging is via msix for the App Store eventually.
0
0
0
0