Comment on Switching to more privacy friendly alternatives
kpw@kbin.social 11 months agoYes, the XSF has a very high bar what a standard is and what not, so the many protocol extensions are labeled experimental. However that doesn't mean implementations are "incomplete" or "insecure". OMEMO has good support nowadays and the implementation in Conversations has been independently audited.
LWD@lemm.ee 11 months ago
The Conversations Independent audit casually mentions forward secrecy was broken, and that the documentation itself was out of date… And that was at the time the audit was released. The website doesn’t mention if Conversations took these recommendations into account, either.
And that’s just if we assume users only want to use one device at a time, and they won’t touch a desktop.
It’s been 8 years, how regularly should I check back to see if OMEMO is accepted as a standard?
kpw@kbin.social 11 months ago
How regularly should I check if Signal has become an interoperable internet standard?
LWD@lemm.ee 11 months ago
Privacy does not necessarily mean interoperability. XMPP is trapped in the past because it cannot roll out changes, including privacy enhancements that Signal has delivered
kpw@kbin.social 11 months ago
Sorry but I've been burned by WhatsApp before. Not wasting time on moving my contacts to another walled garden again. XMPP is actively developed and has most privacy features Signal does + most providers don't require a phone number and let you connect over Tor. Doing things properly and in an interoperable way takes more time but is absolutely worth it: https://snikket.org/blog/products-vs-protocols/