|
|
|
|
|
by sythe2o0
3110 days ago
|
|
None of those are net neutrality, but all of those are things that are prevented by the presence of net neutrality. Net neutrality is currently enforced because ISPs are regulated as "common carriers", meaning they can't intentionally prefer some traffic over other traffic. The vote on Thursday is to reverse this regulation. If ISPs could prefer some traffic over others, they could do any of the things that you suggest, enabling censorship. |
|
>all of those are things that are prevented by the presence of net neutrality.
How is 2)? If you're penalized by total usage [A], irrespective of source or type, that seems pretty neutral. Whether it's a good policy in general is debatable, of course.
(That's another problem with the debate: that "NN violation" is casually equated with "imprudent policy". If an ISP throttles everyone to 1 KB/s, then, yeah, that's a jerk move, but it's definitely content- and source-neutral.)
>If ISPs could prefer some traffic over others, they could let do any of the things that you suggest, enabling censorship.
That doesn't follow. Let's say they lay down some new expensive pipe for some link in their network, on top of what they already have, and then allow anyone to pay for access to the faster pipe. Data continues to get through at the pre-existing speed if you don't pay. How is anyone being censored?
ANd if you find that objectionable, how is that any worse than toll roads or even e.g. convenience stores, where you pay more in order to have a shorter checkout time.
[A] In this context, I have in mind something like "charging more for users who download more than X bytes, weighted by time of usage" or "slightly reallocating the pipe in favor of lighter users at times of peak usage".