Live data from Hacker News

.io considered harmful

beep.blog

151–160 of 254 posts

Re: .io considered harmful

#151
post #106

Earlier quoted context omitted.

"feel free to use it" I feel free with my .co domain and I'm not a citizen of Colombia TYVM.

Good luck with that. What happens when there’s a dispute with a Colombian entity who wants your domain? Who do you think will have the advantage? Would you trust the Colombian registry and courts to favor you?

They could take the dispute to the UN internet court for domain names, whatever it's called. I can't see why that would apply only to the TLDs that existed 20 years ago.

Re: .io considered harmful

#152

This sounds like someone who couldn't buy their desired .io domain and now sounds bitter about it trying to spoil it for everyone.

It's directly at the bottom of the article: it is someone who could and did buy their desired .io domain and now feel guilty about it, having learned new things about why .io domains are the way they are.

Re: .io considered harmful

#153

Earlier quoted context omitted.

The invocation of "colonialism" in tech discussions tends to be a pretty reliable indication that what follows will be gibberish.

I'm just happy they are talking about it all! It's good to learn about things outside your main domain, especially with something like world history/geopolitics. Can you give examples of the gibberish? Genuinely fascinated to know what you are referring to. This kind of stuff in particular can be pretty disheartening to learn about in general, and I find misinformation/pathos around it can often come from resistance…

[deleted]

Re: .io considered harmful

#154
post #138

Earlier quoted context omitted.

I was hoping we could keep our zealousness to tabs vs spaces, 2 vs 3 vs 4 vs 8 indentation levels, etc.

Do you end all your statements in JS with semicolons? What, are you some sort of semicolonialist?

Semicolonizer

Re: .io considered harmful

#155

Earlier quoted context omitted.

I was hoping we could keep our zealousness to tabs vs spaces, 2 vs 3 vs 4 vs 8 indentation levels, etc.

This is a good point you bring up. It is evident that everyone knows the correct level of indentation is a tab character that is four spaces wide; you never use spaces for indentation, only tab characters. Any suitable programming language will immediately recognize a space as a typo and fail compilation.

The correct answer to the "tabs vs spaces" debate is tabs for indentation, spaces for alignment. This allows people to use any tab width they want and it will always look good.

However, in the real world, attempting this won't work because there will be a minimum of 1 person in the team that configures their editor to convert tabs to spaces.

Ideally, that person should have their PRs rejected and be scolded into fixing their editor. But the real result ends up just forcing everyone to use spaces.

Re: .io considered harmful

#156
post #78
post #75

Earlier quoted context omitted.

> just a 'British entrepreneur' who bought the rights to multiple TLDs Not anymore, instead an American private equity firm

Bloody UK government can't hang on to anything

> the United States entered the chat

Re: .io considered harmful

#158
post #48

The article starts with "everything is FACT" then ends with: Every .io domain you buy funds a government committing crimes against humanity. Every .io domain you renew legitimises and reinforces the continued exile of the Chagossians. which is hyperbole at best, and bollocks at worst. .io isn't sold or owned by the british (or US) government Most people don't understand what .io is for, moreover the UK goverment has…

Weird. Also: > And so, Britain traded the land illegally. Whoa, strong claim. Probably backed by facts below? Nope. At the same time, Wikipedia: > In November 1965, the UK purchased the entire Chagos Archipelago from the then self-governing colony of Mauritius for £3 million to create the British Indian Ocean Territory (BIOT). So, they bought it for 3 million pounds. Doesn't seem illegal to me.

Calling the colony self governing to gloss over that this was no legitimate democratic government with actual independence selling it and allowing the expulsion is wildly misleading.

Hence e.g an ICJ decision declaring it illegal in recent years, and a UN resolution declaring it illegal within weeks when it happened in 1965

The "self governing" colony was no more a legitimately truly independent government than the Apartheid bantustans.

Re: .io considered harmful

#159
post #6

Earlier quoted context omitted.

One thing to consider is to have your publicly-visible web sites on vanity domain/domains, but all your server infrastructure on a domain in your local stable ccTLD.

Why does it even matter what domain your servers use internally? Most servers I've ever seen were actually using raw IPs, and the few exceptions used an internal DNS system that couldn't have cared less what the internet thought their domain was.

Personally, I prefer to use the internet as it is and not build up and maintain my own parallell infrastructure.

Re: .io considered harmful

#160
post #128

Earlier quoted context omitted.

> Every .io domain you renew legitimises and reinforces the continued exile of the Chagossians. The history there is unfortunate (although the history lesson itself is welcome), but at the same time this is akin to saying: you should boycott products and services from the UK/US. If you feel that way, you can try to do that, but I get the feeling that purely logistically that would get pretty difficult to do. Looking…

Well, the thought process is that cents from every .io registration go to a private equity firm. And none of that money goes to the people who historically lived there and were displaced. So... that's a pretty shitty thing to support (as someone registering a domain), when the alternative is simply "Pick a different TLD." Tbh, ICANN/IANA should either (a) dissolve the TLD as-is, as there is no independent country it…

The part I fail to follow is that denouncing the occupation of Chagos necessarily means that the two letter abbreviation "IO" becomes off-limits for all use cases.

If ICANN were to actually step in, all they would realistically do (which, logically, should address your concerns) is designate that .io now stands for Input/Output and should be used for tech-related websites (which would merely legitimize how the TLD is currently used anyway).

Post reply on HN