A Little Bit.ly Sharia? Tech Business Builds on Libya Domain « Creeping Sharia

A Little Bit.ly Sharia? Tech Business Builds on Libya Domain

By creeping

In other words, as Gawker titled their story: Muammar Qaddafi More or Less Owns Your Links. Astute reporting below from a blog entitled Workbench:

Bit.ly Builds Business on Libya Domain

The URL shortening service Bit.ly just secured $2 million in financing from investors including O’Reilly’s AlphaTech Ventures. Though URL shorteners have been around for years, Bit.ly believes there’s money in offering Twitter-friendly short links along with web analytics to track how the links are used. The company reports that its links were clicked 20 million times last month.

So far, the news coverage I’ve read about Bit.ly has neglected an unusual aspect of the startup: It’s one of the only prominent online ventures using a domain name in the .LY namespace, which is controlled by Libya.

There are two issues that arise from this relationship.

First, of course, is the appearance of an American company doing business with Libya, a country that the U.S. considered a state sponsor of terror from 1979 through 2006. On Dec. 21, 1988, Libyan intelligence agents planted a bomb on Pan Am Flight 103 that blew up 31,000 feet over Lockerbie, Scotland, killing all 259 people onboard.

Bit.ly’s only doing a trivial amount of business with Libya — the domains sell for $75 per year from the registrar Libyan Spider Network — but its use of .LY domain is helping to popularize and legitimize the top-level domain for general use on the Internet. It’s only a matter of time before a reporter decides to ask the families of Lockerbie victims what they think of the arrangement. I can’t imagine that story going well for the company.

Even without that PR hit, there’s another potential concern for Bit.ly and any other venture that builds its business on an .LY domain. These domains are governed by Libyan law, as it states on the Libyan Spider Network site:

Any .LY domain names may be registered, except domains containing obscene and indecent names/phrases, including words of a sexual nature; furthermore domain names may not contain words/phrases or abbreviations insulting religion or politics, or be related to gambling and lottery industry or be contrary to Libyan law or Islamic morality.

So the names must conform to Islamic morality, and it’s possible that the use of the domains could fall under the same rules. What are the odds that some of those 20 million clicks on a Bit.ly-shortened URL end up at sites that would be considered blasphemous or otherwise offensive in an Islamic nation? Bit.ly conveniently provides search pages for such topics as Islam, sharia, gambling and sex, any of which contain links that could spark another controversy.

Bit.ly’s building a business atop a domain that could be taken away at any time, and the company’s only recourse would be to seek redress in the Libyan court system. Take a look at Section 11 of the regulations for .LY owners:

The Arabic language is the language of interpretation, correspondence and the construction of the Regulation or anything related to it. … In case of conflict between the Arabic and the English versions the Arabic version shall prevail.

I hope Bit.ly’s attorneys are brushing up on their Arabic. ~end

it gets to be burdensome because any twitter, facebook or friendfeed user is already catering to Libyan interests by defaulting url shortening to bit.ly. people were shocked when I said social media was biased against Israel. Would this not be the icing on the cake of an unethical culture?

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: