▲ | johnisgood a day ago | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Differences between Cwtch, and SimpleX? Which are you leaning towards to and why? According to https://github.com/simplex-chat/simplexmq/blob/stable/protoc...: > identify that and when a user is using SimpleX. Does this apply to Cwtch? Also, is it not possible to obfsucate this traffic? Tor with obfs4? Related: #1 - https://security.stackexchange.com/questions/241730/traffic-... #2 - https://github.com/simplex-chat/simplex-chat/issues/4300 #3 - https://github.com/tst-race/race-docs/blob/main/race-channel... | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
▲ | heavyset_go a day ago | parent [-] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> Which are you leaning towards to and why? Heavily sandboxed SimpleX that's firewalled to block any non-Tor traffic. Chose this one because it allows for offline message sending/receiving, despite privacy implications, and because it has clients people will actually use. Cwtch doesn't let you send messages when the recipient is offline by virtue of how it works, which is more secure, but inconvenient. When evaluating Cwtch, I think I read somewhere it might send identifying metadata to your recipient, or something similar, but I might just be making that up. I'll have to look up what I was reading. > > identify that and when a user is using SimpleX. > Does this apply to Cwtch? With Cwtch you're running two hidden services, one on either end of the chat, and that happens over Tor with no middleman service, so no. A passive network observer can tell when you're connecting to Tor, but you can attempt to obfuscate that with transports. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|