A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community’s icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
A website isn’t a common carrier, you cannot argue that a website isn’t allowed to control who they serve their content to. An ISP is a common carrier because they simply act as a dumb pipe between the provider (websites) and the consumer.
Cloudflare is a tool websites use to exercise that right, necessitated by the ever rising prevalence of bots and DDoS attacks. Your proposed definition of net neutrality would destroy anyone’s ability to deal with these threats.
Can you at least provide examples of legitimate users who are hindered by the use of Cloudflare?
We were talking about network neutrality, not just common carriers (which are only part of the netneutrality problem).
Permission wasn’t the argument. When a website violates netneutrality principles, it’s not a problem of acting outside of authority. They are of course permitted to push access inequality assuming we are talking about the private sector where the contract permits it.
One man’s freedom is another man’s oppression.
It is /not/ necessary to use a tool as crude and reckless as Cloudflare to defend from attacks with disregard to collateral damage. There are many tools in the toolbox for that and CF is a poor choice favored by lazy admins.
Only if you neglect to see admins who have found better ways to counter threats that do not make the security problem someone elses.
That was enumerated in a list in the linked article you replied to.