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
2d
OMG what am I even doing This is a huge project it's going to need Jingle and that needs WebRTC and then file transfers and voice messages and oh also localization and sounds and hotkeys and settings and multi-account support and Oh God. even with AI this will take fifteen years why did I get out of bed today and choose this for myself
4
1
4
0
User avatar
plzupgrademe @plzupgrademe@fedi.txw.ca
2d
@fastfinge it is. File Transfers are not so difficult on XMPP, they’re really just HTTPS.

Jingle is a big effort. Be prepared to learn about ICE, DTLS, STUN, TURN et al.
1
0
0
0
2d
@plzupgrademe I think this library has everything I need for Jingle. The same way you did for mac, I'm doing for Windows. So that makes it simpler because I want to just be Windows native whenever possible. So no cross platform worries. github.com/sipsorcery-org/sipsorcery
1
0
1
0

User avatar
plzupgrademe @plzupgrademe@fedi.txw.ca
2d
@fastfinge sadly I wanted to make it a truly modern macOS first class citizen, so the app is using 100% Swift. So not a lot to leverage.
0
0
1
0