Re:A Statement on Recent Events Between Signal and the Anti-...
by smokey_circles on Tuesday February 09, 2021 @09:51AM
(#26078117)
Reading the config in the TLS repo, it seems to me that the censorship is at the domain level.
So I guess they're trying to pop up as many endpoints as possible to circumvent that.
I don't know the details about the network block though, so I might be mistaken. But the nginx config in that repo is purely a TLS proxy. Nothing magical happening there at all, just an entrance node to the main signal network
I don't understand. How would you circumvent censorship of the protocol without obfuscating the protocol?
It seems to me that signal has never claimed to be able to hide that it was being used... until now?
But thanks for posting the thing from Moxie, it does sound quite reasonable.
What would be useful to me and presumably other HN readers is a clear summary of the tech involved, readable by an audience who is technical but not security/circumention experts. Like, the people complaining could be spending time on that, to educate users and developers, instead of doing... whatever they are doing. That seems to have turned into a much less interesting argument about etiquette or something.