- cross-posted to:
- technology@lemmy.world
- privacy@lemmy.world
- cross-posted to:
- technology@lemmy.world
- privacy@lemmy.world
Last year, I outlined the specific requirements that an app needs to have in order for me to consider it a Signal competitor.
Afterwards, I had several people ask me what I think of a Signal fork called Session. My answer then is the same thing I’ll say today:
Don’t use Session.
You must log in or register to comment.
It would be nice to read the basic points of your statement, then if someone wants to go in detail, there’s the link to your article.
it’s not my article.
Ops. However a small TL;DR would be useful instead of just copying/pasting links.
Thanks for the notice!
Regular Signal for lyfe.
Use simplex.
I weren’t even aware it was a Signal fork! What kept me away was their heavy integration of the Oxen crypto token (now apparently replaced with their own “Session token” instead). Anything that deep into web3 is a red flag to me, but the security flaws discussed in the above blog post look white hot.
Strong agree. Session is not security focused it’s marketing focused. Last I checked they still use central servers for file uploads.
Cliff notes: end to end encryption is borked.
So borked in fact that the author’s fursona face-palmed in response.
