Erasmus354 wrote:
SoNi67 wrote:Well, true, it might still detect/conter it at some point. I know is not a true VPN, it just "hides" the destination.
But exactly that's why it proves my point that Verizon ACTIVELLY criples our service for their interest. Is not a Netflix issue, is purelly a Verizon choice. Nothing changes in the data path, except the fact that Verizon cannot sniff it like any regular DNS request.
Verizon advertise their speed as being "internet access". If it does a traffic-shaping then is just limited Internet access service.
Their TOS doesn't say nothing about that and frankly I think they are in breach of contract for doing that.
I think you are a bit confused about what is actually happening. I think the road/bridge analogy is the best example that might help you. Verizon is not (at least there is no evidence) actively crippling connections to Netflix. They aren't detecting you connecting to Netflix and then slowing down that connection.
Instead Verizon is simply allowing the connections to Netflix to become overloaded, which in essence slows down the connection for everyone.
OK, so explain how by just changing the DNS the route sudenly becomes less congested???
Like I said, unlocator.com is not a VPN, it just "hides" my request from my ISP provider. My packets still gets from Netflix to me trough Verizon network, including the "bottleneck" that you keep assuming that exist. But, since Verizon cannot **bleep** where they are coming from, it cannot traffic shape them.
The proof is that I get 10x the speed that I get when I use Verizon DNS.
Other DNS providers don't work because they are "transparent", Verizon still can "see" the endpoint.
This is not just "not taking care of upgrading the system", it is activelly throttling my connection.
If you like the examples is the difference between "not repairing holes in the Netflix road" and "sending crews to make the holes in the Netflix road".