Dude you're reaching hard. They introduced private routing to offer some degree of IP obfuscation but encourage Orbot Tor routing for maximal obfuscation. You can enforce .onion connections only in-app while having private routing on creating 8 hops (6 Tor and 2 SimpleX) between you and the destination.
You got a better way to obfuscate packet metadata better than padding to a fixed size? Come up with a solution to that and you'll fundamentally change the entire landscape of network level privacy.
The reason Simplex is the gold standard is because each server, in the worst case scenario without VPNs, onion routing or private routing, still only sees one way fixed sized packets, they can't tell if you're talking to one person or in a group chat, not can they tell if the recipient even responds. Stack on multiple layers of network level obfuscation as I've described above and you're left with what is currently the lowest metadata messenger in the space.
If you know of a better messenger please let me know. You mention Session consistently but from my knowledge, Session only obfuscates metadata by two way onion routed connections, much weaker than a well configured SimpleX setup.
Login to reply
Replies (5)
I thought it leaks metadata all over the place?
Just the Bluetooth function, correct me if I'm wrong.
You are so, so stupid. The ideal messaging system is one where you click send qnd the message simply appears in the reciever's inbox without any need for it to travel across connections. Though I'm thinking of upgrading to situation where the other person simply knows what I want to say to them without me having to type it out.
Nice bait.
Whonix doesn't recommend it because it involves six hops over Tor on whonix, but I can't see any other issues with it.