Live data from Hacker News

Kim Dotcom loses new domain in preemptive strike by Gabon government

arstechnica.com

11–20 of 40 posts

Re: Kim Dotcom loses new domain in preemptive strike by Gabon government

#11

Edit: was complaint about misleading title, title is no longer misleading

Why is the title misleading?

> "I have instructed my departments... to immediately suspend the site www.me.ga," said Communication Minister Blaise Louembe, according to the AFP French news agency.

(http://phys.org/news/2012-11-gabon-megaupload-site.html)

> Communication Minister Blaise Louembe, [said] he wanted to "protect intellectual property rights" and "fight cyber crime effectively". "Gabon cannot serve as a platform or screen for committing acts aimed at violating copyrights, nor be used by unscrupulous people,"

Re: Kim Dotcom loses new domain in preemptive strike by Gabon government

#12
post #11

Edit: was complaint about misleading title, title is no longer misleading

Why is the title misleading? > "I have instructed my departments... to immediately suspend the site www.me.ga," said Communication Minister Blaise Louembe, according to the AFP French news agency. ( http://phys.org/news/2012-11-gabon-megaupload-site.html ) > Communication Minister Blaise Louembe, [said] he wanted to "protect intellectual property rights" and "fight cyber crime effectively". "Gabon cannot serve as a p…

I presume that the original title just said "by government."

Re: Kim Dotcom loses new domain in preemptive strike by Gabon government

#13
post #11

Earlier quoted context omitted.

Why is the title misleading? > "I have instructed my departments... to immediately suspend the site www.me.ga," said Communication Minister Blaise Louembe, according to the AFP French news agency. ( http://phys.org/news/2012-11-gabon-megaupload-site.html ) > Communication Minister Blaise Louembe, [said] he wanted to "protect intellectual property rights" and "fight cyber crime effectively". "Gabon cannot serve as a p…

I presume that the original title just said "by government."

Ah, that makes sense.

Re: Kim Dotcom loses new domain in preemptive strike by Gabon government

#18
post #14

That should make anyone think twice about using .ga domains.

The real question is if there is any TLD you don't have to think twice about, and if yes for how much longer..

Is there any TLD more liberal/permissive than .se? I don't think so...

Re: Kim Dotcom loses new domain in preemptive strike by Gabon government

#19

Earlier quoted context omitted.

The real question is if there is any TLD you don't have to think twice about, and if yes for how much longer..

Is there any TLD more liberal/permissive than .se? I don't think so...

.onion but that is more like a pseudo-TLD.

http://en.wikipedia.org/wiki/.onion

Re: Kim Dotcom loses new domain in preemptive strike by Gabon government

#20
post #14

That should make anyone think twice about using .ga domains.

The real question is if there is any TLD you don't have to think twice about, and if yes for how much longer..

It's pretty clear that there are some places to just write off (Libya .ly, io, ga, etc.), and then, if you have anything even vaguely questionable, use a domain name in your country of operation.

If you're operating from NZ, you're already exposed to NZ law. A .co.nz domain name adds no additional risk. You may need to pick your country based on favorable laws -- i.e. don't run a gambling site from the US, and don't be a US citizen. HK is actually one of the better choices. The US is actually good for a lot of things, too.

If you're in the US, .com/.net/.org are all roughly equivalent, although I still think .com is the best overall tradeoff. There are some differences in individual registry ToS, but every one I've read is flexible enough as to be meaningless if they want to do something.

It's probably fair to say the US is the biggest risk for anyone operating in a non-US country except for their own government, so .com is a "safe" backup choice as well.

If you're really worried, the only safe choice is .onion :) Safe from having large numbers of users, too! (you'd be better off at that point distributing some kind of client software, or running multiple pop-up frontends accessing a common API, and then making it easy to move the API around using client-side failover.)

Post reply on HN