Twitter’s best-in-class censorship reveals weaknesses in centralized corporate communication channels

Twitter made some waves this week when it announced a new feature — granular country-by-country censorship of Tweets. It was probably a tactical misstep to make this announcement in the wake of the anti-SOPA blackout protests, and initial reactions ran accordingly hot, but cooler heads have since, for the most part, prevailed. The reality is that Twitter has "boots on the ground" in a number of countries that have different speech laws than we do, and as long as it must comply with those laws to avoid endangering its employees, the best course is to make that compliance as transparent and non-disruptive as possible. Local blocks are better for the greater Twitter ecosystem, and direct attention to the bad laws that deserve the blame.

So, yes, Twitter’s style of censorship is "best-in-class", and its continuing defense of freedom of expression also grants it some benefit of the doubt when implementing this sort of policy. Given the background facts of the situation — a centralized architecture run by a global corporate entity, Twitter has done as well as anybody could reasonably expect.

In other words, as my friend Asheesh has explained, we each have a "risk profile" that shapes the actions we choose to take. Your risk profile probably allows speaking in ways that are illegal in, say, Thailand or Germany. But when you use Twitter, you’re required to adhere to their risk profile. Twitter’s historically been very good about managing its risk profile to interfere only minimally with speech concerns, but it is bound to observe at least some minimum as befits a responsible global corporate entity. Where there are conflicts between the risk profile of the users and the risk profile of the service, the service takes priority.

(It’s worth noting that these mismatched risk profiles can cut both ways, too: people who were using MegaUpload for the legitimate storage and distribution of personal files may have been very conservative about what they were uploading, but were tied up with MegaUpload’s relatively permissive risk profile.)

Those background facts, though, the ones that dictate the shape of risk that the operators of a communication channel are willing to take, don’t have to look like Twitter’s. While we the users have overwhelmingly opted for services that are centralized and run by global corporations, there are other models available. Services that follow these other models, like Status.Net — which powers Identi.ca — or Thimbl for example, are not operated by large groups that have to worry about liability in different parts of the world. Increasingly, too, using these services doesn’t require a tradeoff in functionality or performance.

There are certainly people who still have problems with the sort of censorship that Twitter has admitted to participating in, but that blame is misplaced. Twitter is just being transparent about the requirements of operating a centralized corporate communication channel. Anger about these issues should be channeled in one or both of two directions: reducing the risks corporations undertake operating in foreign markets by improving the laws in those countries, or choosing models that aren’t bound to the same risks.

I prefer the latter. John Gilmore famously said in 1993 that the Internet views censorship as damage and route around it. That’s still true. But corporations don’t have the same attributes. We can try to reduce the effect of censorship in the world by changing laws and governments to cut the problem off at its source, which is a noble goal. But we can also design and use services that are decentralized in function and control, and so take advantage of the fundamental censorship-busting quality of the Internet.

One Trackback

  • […] a reality which every law-abiding corporate entity has to face.  As Free Culture activist Parker Higgins points out, this is a problem with all centralized corporations.  That is why decentralized web […]

Post a Comment

Your email is never published nor shared. Required fields are marked *

*
*

You may use these HTML tags and attributes <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>