by Berin Szoka & Adam Thierer, Progress Snapshot 5.11 (PDF)
Ten years ago, Nobel Prize-winning economist Milton Friedman lamented the “Business Community’s Suicidal Impulse:” the persistent propensity to persecute one’s competitors through regulation or the threat thereof. Friedman asked: “Is it really in the self-interest of Silicon Valley to set the government on Microsoft?” After yesterday’s FCC vote’s to open a formal “Net Neutrality” rule-making, we must ask whether the high-tech industry—or consumers—will benefit from inviting government regulation of the Internet under the mantra of “neutrality.”
The hatred directed at Microsoft in the 1990s has more recently been focused on the industry that has brought broadband to Americans’ homes (Internet Service Providers) and the company that has done more than any other to make the web useful (Google). Both have been attacked for exercising supposed “gatekeeper” control over the Internet in one fashion or another. They are now turning their guns on each other—the first strikes in what threatens to become an all-out, thermonuclear war in the tech industry over increasingly broad neutrality mandates. Unless we find a way to achieve “Digital Détente,” the consequences of this increasing regulatory brinkmanship will be “mutually assured destruction” (MAD) for industry and consumers.
New Fronts in the Neutrality Wars
The FCC’s proposed rules would apply to all broadband providers, including wireless, but not to Google or many other players operating in other layers of the Net who favor such broadband-specific rules. With this rulemaking looming, AT&T came after Google with letters to the FCC in late September and then another last week accusing the company of violating neutrality principles in their business practices and arguing that any neutrality rules that apply to ISPs should apply equally to Google’s panoply of popular services. In particular, AT&T accused Google of “search engine bias,” suggesting that only government-enforced neutrality mandates could protect consumers from Google’s supposed “monopolist” control.
The promise made yesterday by the FCC—to only apply neutrality principles to the infrastructure layer of the Net—is hollow and will ultimately prove unenforceable. Continue reading →
The Technology Liberation Front is the tech policy blog dedicated to keeping politicians' hands off the 'net and everything else related to technology.
More on the FCC’s e-Government Transparency Efforts: ECFS, RSS, Social Media & Setting Priorities
by Berin Szoka on September 11, 2009 · 12 comments
I vented my frustration earlier today with the FCC’s failure to make comments it receives easily accessible to the public—which means, more than anything, making them full-text searchable. This may seem like Inside Baseball to many, but it’s not. It’s a failure of the democratic process, a waste of taxpayer dollars, and a testimony to the general incompetence of bureaucracies, regardless of who’s running them. It denies the public an easy way to follow what goes on inside Washington, while essentially subsidizing law firms who get to bill clients for having paralegals or junior associates do things that existing web technology makes completely unnecessary—like reading through every comment in a document (at the rate of hundreds of dollars per hour) instead of just looking for keywords in a full-text search.
Later in the day the FCC announced:
I’m thrilled about the RSS feeds, which go a long way in letting all Americans know what the FCC does, supposedly in the “public interest.” Still, I can’t help but note that the FCC waited until after a huge discussion about whether RSS is dead to finally start using RSS in a serious way—fully a decade after the birth of the RSS standard. Better late than never, I suppose.
FCC Connect is also good news: once you have an RSS feed, there’s really no reason not to pipe that feed into as many platforms as possible—which is precisely why RSS isn’t dead, even if most people will never use an RSS reader.
But I’m less thrilled about the crowdsourcing platform. Continue reading →