3 ms·
Properly configured Tor connections look like regular HTTPS connections on port 443 otherwise most who need it couldn't use it without getting thrown into "re-e
by krisives 9y ago
Properly configured Tor connections look like regular HTTPS connections on port 443 otherwise most who need it couldn't use it without getting thrown into "re-education camps"
Also I'm not talking about using Tor to connect to "regular HTTPS" sites like Amazon or Netflix where they see you as some special citizen of the Internet (one they don't like) I'm talking about things like Hidden Services where there is no external gap between networks being exploited.
- n4r9 9y agoI wonder if one or both of us is missing the point here. The concern is that ISPs will throttle all traffic which they don't recognise as being served from a big-name domain (Netflix, Amazon, Facebook...). In such a situation, if I use an ordinary https connection to watch my favourite Netflix shows, then they won't throttle me. But if I do anything through Tor, then they will.
- krisives 9y agoMy point is that on a network with onion routing you have nothing to block. You are mixing the two networks that's a separate issue.
- n4r9 9y agoBased on this and your other comments, it sounds like you're suggesting running the entire Internet on a cryptographic protocol like onion-routing. Am I right? This still isn't a practical solution to the problem at hand. Most people want to watch a lot of streamed video, which isn't doable over a Tor-like network in the foreseeable future. Also, it would be impossible to get the support of the internet giants, without which I don't know how you could do this. They've invested a lot into being able to see and analyse almost everyone that's using their service.