Post #4101875

2026-07-26 01:41 UTC

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.

Replies (4)

@plzupgrademe@fedi.txw.ca 2026-07-26 01:49

@fastfinge@fed.interfree.ca it was an eye opener for me to realize there is an omemo:legacy, and omemo:2 and an omemo:1. I look forward to trying your app.

Open ##4101874
@fastfinge@fed.interfree.ca 2026-07-26 02:05

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

Open ##4102093
@miki@dragonscave.space 2026-07-26 02:26

@fastfinge@fed.interfree.ca 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.

Open ##4102716
@martin@social.mdosch.de 2026-07-26 15:01

@9yyiw179ykv56evd@fed.interfree.ca Maybe checkout #ox (#OpenPGP for #XMPP). It's not as complicated as #OMEMO. it's currently supported by #profanity, #gajim and #GoSendxmpp. #Conversations is currently working on support.

Open ##4114614