Wow. We didn’t see this one coming, did we?
Actually, we did. But who listens to us? We’re just members of the adult entertainment industry. What could we possibly know about… oh, anything, really, right? ICM Registry has certainly appeared to have come to that conclusion.
Egypt recently demonstrated internet censorship on a national level by simply… cutting access for everyone (except, presumably, top government officials/agencies.) That, in and of itself, should chill the virtual marrow of anyone who believes in the free and reasonably unfettered exchange of information. Of course, so much depends upon the definition of “reasonably” and “unfettered.”
Fortunately, the situation in Egypt, like that in Iran previously, also showed the world that those who truly want to reach the other side of the virtual wall of silence can — with a little help from their social network/microblogging friends.
That’s reassuring… but why should we need that kind of reassurance?
– Darklady
US Gov’t Interest In Domain Name Veto Represents Yet Another PR Nightmare
from the does-no-one-think-about-this-stuff dept
Last week, someone had sent over a document purporting to be from the Commerce Department advocating that ICANN’s new open top level domain plan include a “government veto,” that would let various government agencies seek to block a particular TLD. We didn’t write about it at the time, because I couldn’t confirm that it was real, and the whole thing seemed so ridiculous and short-sighted I didn’t think that it could have really come out of the Commerce Department. Lesson learned: never underestimate the Commerce Department’s ability to make really bad decisions.
It appears that it’s now been confirmed that the Commerce Department really does want veto power for any government over a particular TLD. The reports suggest that there’s concern about TLD’s like “.gay” which some countries may not like, and some of the fear is driven by the .xxx debacle, when ICANN initially approved a .xxx domain, thinking it would be a “redlight district” for porn, but then after public outcry, the US government pressured ICANN to change its mind. This was especially funny because no one seemed sure whether or not .xxx was good or bad for kids. There were some people who thought .xxx would be “good” for kids by creating an area that was easy to rope off and keep kids out of. Others argued that .xxx was bad because it admitted that porn existed (or something like that).
To read more, visit: Techdirt and check for similar articles in the sidebar.


























