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.
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.
the Oxen crypto token
Oxen is the company behind Session, for anybody unfamiliar. They were a crypto company that made (well, cloned) a messaging app to promote this token.
And Oxen itself was a clone of Monero.
