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
plzupgrademe @plzupgrademe@fedi.txw.ca
2d
@fastfinge 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.
2
0
0
0
User avatar
🇨🇦Samuel Proulx🇨🇦 @fastfinge@interfree.ca
2d
@plzupgrademe Why did you intentionally not do OMEMO:1 in yours? Just curious.
1
0
0
0
User avatar
plzupgrademe @plzupgrademe@fedi.txw.ca
2d
@fastfinge omemo:siacs/axolotl/legacy is widely used so it needs to be supported, omemo:2 is the latest standard and not well adopted, omemo:1 was never well adopted and is replaced by omemo:2

So it’s an ipv4, ipv6, ipv5 situation.
0
0
0
0