Supporting net neutrality and the Internet Slowdown
Robin Winslow
on 9 September 2014
On 10th September 2014, Canonical are joining in with Internet Slowdown day to support the fight for net neutrality.
Along with Reddit, Tumblr, Boing Boing, Kickstarter and many more sites, we will be sporting banners on our main sites, www.ubuntu.com and www.canonical.com.
Defend net neutrality.
Net neutrality
From Wikipedia:
Net neutrality is the principle that Internet service providers and governments should treat all data on the Internet equally, not discriminating or charging differentially by user, content, site, platform, application, type of attached equipment, and modes of communication.
Internet Slowdown day
#InternetSlowdown day is in protest to the FCC’s plans to allow ISPs in America to offer “paid prioritization” of their traffic to certain companies.
If large companies were allowed to pay ISPs to prioritise their traffic, it would be much harder for competing companies to enter the market, effectively giving large corporations a greater monopoly.
I believe that internet service providers should conform to common carrier laws where the carrier is required to provide service to the general public without discrimination.
If you too support net neutrality, please consider signing the Battle for the net petition.
Also posted on my blog.
Talk to us today
Interested in running Ubuntu in your organisation?
Newsletter signup
Related posts
Building an open source chain of trust: new research uncovers key blockers and ways forward
Canonical is pleased to share its latest research report, “The open source chain of trust.” Based on a survey of 500 DevOps professionals, the report...
Beyond safety and security: Why automotive open source demands dependability
In the traditional automotive world, teams often work in silos: the cybersecurity experts lock down the ports, the quality assurance teams hunt for bugs, and...
DirtyClone Linux kernel local privilege escalation vulnerability fixes available
On June 25, 2026, JFrog published their research into CVE-2026-43503, referring to the vulnerability as DirtyClone. The vulnerability had previously been...