

Honestly, I wouldn’t even consider using it unless it were reviewed by a professional cryptographer. There are already battletested options that don’t require a phone number or sharing info with a company. For that, I like XMPP with a client that uses OMEMO for encryption.



To me, open sourcing the code is a move in the right direction but it doesn’t make up for a professional review of your encryption system.
The thing about encryption is that there are many subtle ways to get something wrong, even when just implementing it with a well known and trusted library. I took a deep dive course on Designing Secure Encryption for Practical Use and while I learned a ton from it, the main take away for me was that I shouldn’t do it if its intended for serious use. At least not without expert reviewers.
Regarding XMPP, it’s architecture is like email. Anyone can stand up their own server and your User ID looks like an email address: [email protected]. Like email, you can send messages to anyone on any server if you know their ID. Phone numbers are simply never involved.