Live data from Hacker News

I bought netflix.soy

tinyprojects.dev

61–70 of 272 posts

Re: I bought netflix.soy

#61
post #7

I'm from Israel, and this is the first time I've heard about the .קום tld. I've never seen any website that uses it. The author mentioned that creating a new tld costs a minimum of 185k USD. This makes me wonder who would pay this kind of money for this completely useless tld.

.קום is just .com transliterated into Hebrew letters, right?

That actually seems quite useful, if people are typing not realizing the keyboard is set to Hebrew.

Re: I bought netflix.soy

#62
post #7

I'm from Israel, and this is the first time I've heard about the .קום tld. I've never seen any website that uses it. The author mentioned that creating a new tld costs a minimum of 185k USD. This makes me wonder who would pay this kind of money for this completely useless tld.

If they managed it for only $185k I'm impressed, maybe if you did several on the same infrastructure. It's a gold mine offering. There was a long queue of people quite sure that .binglebongle would be the new .com. Sometimes it was a marginally less stupid plan, like we can be a regional alternative - and Russia even has one that's actually making money - it isn't taking over the world, but it's Cyrillic and was neve…

> The obscure brand TLDs are funnier. Not brands you've heard of like google, brands who are their own tiny corner of the non-IT world and figured they ought to have a TLD, so now they do to the tune of maybe six figures a year.

While everyone here has certainly heard of Softbank, I find it amusing that they have their own TLD too (with sites like https://group.softbank/).

Re: I bought netflix.soy

#64
post #10

Earlier quoted context omitted.

Even better yet, it would be interesting if we just abandoned TLDs. There is no reason why http://google/ can't work, really, with a bunch of infrastructure changes.

Infrastructure changes aren't even needed; Google already owns the .google TLD. All they would need to do is attach an A record to the root.

The used to have an A record on some of the other TLDs they own.

I maintain a list at captnemo.in/tld-a-record

Re: I bought netflix.soy

#65

Registering unambiguous trademark domains falls under the category of "play stupid games, win stupid prizes".

Could anything worse than losing out on the registration fees ever actually happen?

Yes. You might have to deal with the hassle and expense of being sued.

There's all downside and no upside to playing this particular stupid game.

Re: I bought netflix.soy

#66

Registering unambiguous trademark domains falls under the category of "play stupid games, win stupid prizes".

Could anything worse than losing out on the registration fees ever actually happen?

If you actually caused say, reputational damage, you could be stuck with a lawsuit for more than just turning over the domain.

Re: I bought netflix.soy

#67
There's a terrible enterprise security product that can be configured by IT to quasi-MITM your company web traffic. Instead of relying on enterprises pushing their own trusted root certs and MITMing the whole session this terrible product redirects all traffic to (and I'm not kidding here) urls like "www.terriblesecuritycompanyname.com/www.originalurl.com" when the user accesses www.originalurl.com.

So this "enterprise security" company encourages end users to put information such as passwords into www.terriblesecuritycompanyname.com/owa.office365.com for example. Of course everyone has SSO enabled for Office 365 but everyone is also used to SSO sometimes breaking and falling back to forms based auth so people have no issue typing their passwords into any page that looks somewhat legit as long as the URL is close to what they expect and has a little lock next to it.

Anyway www.turriblesecuritycompanyname.com is available and I'm waiting for someone nefarious to purchase it and start sending phishing emails with links to www.turriblesecuritycompany.com/owa.office365.com embedded in them.

Re: I bought netflix.soy

#68
post #10

Earlier quoted context omitted.

Even better yet, it would be interesting if we just abandoned TLDs. There is no reason why http://google/ can't work, really, with a bunch of infrastructure changes.

Infrastructure changes aren't even needed; Google already owns the .google TLD. All they would need to do is attach an A record to the root.

ICANN doesn't allow A records on the DNS root on gTLDs. If they did, we already would've.

Re: I bought netflix.soy

#69
post #61
post #7

I'm from Israel, and this is the first time I've heard about the .קום tld. I've never seen any website that uses it. The author mentioned that creating a new tld costs a minimum of 185k USD. This makes me wonder who would pay this kind of money for this completely useless tld.

.קום is just .com transliterated into Hebrew letters, right? That actually seems quite useful, if people are typing not realizing the keyboard is set to Hebrew.

That would only work if the Hebrew keyboard layout they were using had this mapping of letters. Most language layouts for non-Roman scripts don't optimize for phonetically approximating the corresponding English letters (presumably on a QWERTY layout).

It appears that they don't match to the TLD letters here: https://en.wikipedia.org/wiki/Hebrew_keyboard

Re: I bought netflix.soy

#70
post #11

Earlier quoted context omitted.

>their "all-encompassing" TLD package which registers their trademark across all TLD's for a special price That's a thing? What's preventing a predatory registry from being a holdout and demanding exorbitant prices?

That is a thing for at least one Registry that I know of (and worked for), I don't know if Google does the same, but I don't believe there is anything stopping them (please correct me if I'm wrong).

Google does not do the same.
Post reply on HN