>>27029"TorX" is a library, not the two proof-of-concept clients, so I'm not going to talk about "we have audio messages, but not voice chat and video chat" those features only exist or don't yet exist in the user interface, which is outside the scope of the library.
TorX, the library, supports P2P and group chats, and supports pushing any type of data, in the form of file transfers and custom protocols, over those connections to groups, individual peers (private messages), and individuals.
Regarding Briar:
So I haven't used Briar (it failed to install on my phone last time I tried), but based on my recollection of reviewing some of the source code and documentation, Briar is designed more with "resilience" in mind than anonymity. It's a P2P encrypted mesh network more than anything else, which is a cool concept aimed at developing countries.
However, they've taken a "kitchen sink" route of feature development, and developed everything in the user-land, so alternative clients (and desktop clients) lag vastly behind their "mobile first" clients. Their code-base is bloated and the underlying protocols are (as far as I can tell) not well separated.
My development method has been a focus on simplicity, separation, and non-redundancy to ensure auditability, both in the proof-of-concept UI layers and the library layer. (do one thing and do it well, at least in the library)
Importantly:
Post too long. Click here to view the full text.