4 ms·
That's not what net neutrality is about - the author is taking it to the extreme. Not allowing a server on the client side is just reasonable business practice
by jotm 13y ago
That's not what net neutrality is about - the author is taking it to the extreme.
Not allowing a server on the client side is just reasonable business practice, as opposed to shaping or prioritizing traffic to the client according to the source or the client's pay plan.
- diminoten 13y agoNo it's not, that's preference of certain packets over other packets. It is completely and entirely irrelevant what the packets I'm sending and receiving on my network are to be used for - server, or client, according to the principle of net neutrality. If there is a bandwidth problem then we can address that, but as it stands there is simply not a bandwidth problem. Ask how Google or any other company would enforce this. If the answer is packet inspection, then it's probably in violation of the network neutrality principle.
- anu_gupta 13y agoWhy is it a reasonable business practice?
- jotm 13y agoThe way I see it, client Internet connections are for data consumption, i.e. mostly download. Servers, on the other hand, create and provide the content. Kind of like being the manufacturer of a watch and being its end user. The line is getting pretty blurry, but I don't think you can put the two in the same bucket - not yet anyway.