Live data from Hacker News

The .blog Bait and Switch

chrisschidle.com

111–120 of 186 posts

Re: The .blog Bait and Switch

#111
post #11

This seems to have become the de facto pattern with the new gTLD system. A company swoops in and buys a namespace for $200k (or more if there is a competitive bid), and they effectively turn into the cartel equivalent of the domain squatter. You can register your new gTLD for anywhere between $1 and $100, depending on what I suppose they expect their target demographic to be willing to pay. Dot horse is more expensiv…

I bought Free.TV and it was only $100,000 - per year!

If anyone wants to use it, let me know

Re: The .blog Bait and Switch

#112
post #11

This seems to have become the de facto pattern with the new gTLD system. A company swoops in and buys a namespace for $200k (or more if there is a competitive bid), and they effectively turn into the cartel equivalent of the domain squatter. You can register your new gTLD for anywhere between $1 and $100, depending on what I suppose they expect their target demographic to be willing to pay. Dot horse is more expensiv…

[deleted]

Re: The .blog Bait and Switch

#113
post #102

This seems like it has gotten out of control - it is a basic key/value lookup, and we've created a rent-seeking, global series of registries to further suck good money from people. I worked briefly at a registry - it is money for jam. I don't know if the DNS protocol and all the related ones are fundamentally broken or need fixing, but it seems to me the problem is ICANN and the web that spreads out from under it. Wh…

> except without the rent-seeking/government ownership attached? Because people like money. This TLD business literally invented a new economic activity , and one with great margins. It doesn't really hurt anyone, has little to no cost, and makes a pretty penny. People With Money love stuff like this; if tomorrow they could invent a marketable TLD system for physical addresses, phone numbers or anything else, they'd…

Agreed, I guess the way that works in general is just disappointing in that it doesn't produce anything meaningful or advance anything (to my mind). It's spinning wheels and burning energy for no appreciable reason, to make some people rich.

Re: The .blog Bait and Switch

#114

This seems like it has gotten out of control - it is a basic key/value lookup, and we've created a rent-seeking, global series of registries to further suck good money from people. I worked briefly at a registry - it is money for jam. I don't know if the DNS protocol and all the related ones are fundamentally broken or need fixing, but it seems to me the problem is ICANN and the web that spreads out from under it. Wh…

Legal/Govermental/Regulatory issues, someone has to deal with it. No single organization is going to deal with every country and their various legal issues. Registries and Registrars help abstract a lot of that (ICANN definitely doesn't want to deal with it). I don't disagree with the ease of storing a few million records or more. That is not the real overhead and is in reality only a fraction of whats involved.

Yes the added verification etc on top of the key/value lookup is the meat of it I guess. A complicated problem, I guess it'd be nice to somehow remove the money factor from a critical function of the net.

Re: The .blog Bait and Switch

#115

I fail to understand the purpose of these non-standard TLDs. Nobody is going to remember or type in such a domain, so you stuff is only going to be found by a web search - where a standard domain would be better. So why not just register a .com - which are also cheaper?

Have you ever tried to buy a .com domain dude? There's hardly any useful names left.

That's not true. I just registered a six letter domain a few months ago (minops.com).

There's still plenty of good ones left. I created a program to help me find them: https://github.com/jedberg/wordgen

Re: The .blog Bait and Switch

#116
post #72
post #10

Earlier quoted context omitted.

Browser vendors and OS makers should do an end run around ISPs and ICANN. Just agree between themselves ( what are they like 10? tops) and fork the current registries. Then issue domains themselves. What are the plebs gonna do? Go the the non existent alternative?

The DNS resolver is configurable, not hard coded. Forcing a switch would require OS vendors to ignore the resolver issued via DHCP, which would not work on many corporate networks that block outbound DNS not via their resolver.

Maybe then just prefer if reachable? Soon enough it's the new standard.

Re: The .blog Bait and Switch

#117
post #11

This seems to have become the de facto pattern with the new gTLD system. A company swoops in and buys a namespace for $200k (or more if there is a competitive bid), and they effectively turn into the cartel equivalent of the domain squatter. You can register your new gTLD for anywhere between $1 and $100, depending on what I suppose they expect their target demographic to be willing to pay. Dot horse is more expensiv…

[deleted]

Re: The .blog Bait and Switch

#118
post #116
post #72

Earlier quoted context omitted.

The DNS resolver is configurable, not hard coded. Forcing a switch would require OS vendors to ignore the resolver issued via DHCP, which would not work on many corporate networks that block outbound DNS not via their resolver.

Maybe then just prefer if reachable? Soon enough it's the new standard.

Yes I think any new system would have to see the old one grandfathered (give the current incumbents time to find something useful to do instead of jetting off to conferences all year).

Browsers/OS would be reasonably easy in most circumstances, but there are embedded devices, load-balancing configurations, other esoteric uses for DNS (text records, mail etc) that'd have to be considered as well.

Re: The .blog Bait and Switch

#120
post #70

Earlier quoted context omitted.

I'm glad that someone snagged hoarse.horse and is doing more with it than I would have. not.horse is available, too, if someone wants to tell that joke via a TLD. And of course, bad.horse is exactly what you expect it to be.

Don't forget to traceroute bad.horse.

Hilarious.

Even more geek than setting up joke SSIDs for your neighbours to enjoy.

Post reply on HN