Live data from Hacker News

I bought netflix.soy

tinyprojects.dev

101–110 of 272 posts

Re: I bought netflix.soy

#102
post #96

Earlier quoted context omitted.

It depends on which ethical framework you subscribe to, but if I were in your shoes using my ethical framework, it seems like the small cost to me to purchasing an available domain (making the assumption here it's a standard buy and it's not one of those "make an offer for $10k" domains...) to mitigate a lot of potential hurt to other people would make me lean toward just purchasing the domain myself, or at least mak…

Your ethical framework in this case could clash with the arguably broken legal framework that we currently live in. Buying a domain like that could get you into legal trouble once it is found out and people track sensitive traffic funneling to the domain. Even if you aren't doing anything with the information.

This, exactly.

One thing I've learned about "infosec" companies is that their litigiousness is inversely proportional to their actual level of security.

The similar domains I've seen are only $9 though so it's just a matter of time.

Re: I bought netflix.soy

#103

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 "enterpri…

Wow, that sounds awful.

Do you know what they did (assuming not nothing) to have browsers continue to enforce the same-origin policy, and block www.terriblesecuritycompanyname.com/evilhacker.com from accessing cookies that belong to www.terriblesecuritycompanyname.com/owa.office365.com?

Re: I bought netflix.soy

#105

Earlier quoted context omitted.

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

http://cm./ used to resolve

.cm is a ccTLD, not a gTLD. All two-letter TLDs are ccTLDs and all 3+ letter TLDs are gTLDs. Countries have wide latitude to do whatever they want with their ccTLDs.

Re: I bought netflix.soy

#106

Earlier quoted context omitted.

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

Do you remember the details?

Re: I bought netflix.soy

#107
post #17
post #9

If these companies notice, they can file a UDRP ( https://en.wikipedia.org/wiki/Uniform_Domain-Name_Dispute-Re... ) request, on the basis that the domains infringe their trademarks, and were registered and used in "bad faith".

>and were registered and used in "bad faith". How were they registered in bad faith? He's not extorting money from netfilx, nor is he trying to deceive people into thinking he's neflix.

> How were they registered in bad faith?

The article literally says that he only registered it because it clashed with an existing company. He didn't want the domain name for any other purpose.

Re: I bought netflix.soy

#108
post #78

> Truthully, I think its pretty bad that I was able to do this. It is not. The explosion of TLDs is bad. It's simply a racket. But, Google supported it. So if they happen to suffer some of the consequences... so be it.

.sucks is one such example. Everyone feels obliged to buy their own .sucks, lest someone else use it to stand up a hatepage.

A whole bunch of money changes hands, but nobody is better off. gTLDs were a mistake.

Re: I bought netflix.soy

#109
post #97

Earlier quoted context omitted.

http://cm./ used to resolve

https://news.ycombinator.com/item?id=974111 http://to./ used to be a URL shortener. Either the rules on ccTLDs are different, or it's a recentish crackdown.

There are no rules for ccTLDs, which their countries like to claim as sovereign property (see https://meetings.icann.org/en/dublin54/schedule/wed-ccnso-me... and https://gac.icann.org/principles-and-guidelines/public/princ... for some of the views)

Some ccTLDS voluntarily agree to abide by the same rules and operational requirements as the gTLDs - https://www.icann.org/resources/pages/cctld-2012-02-25-en has more details.

This means, for example, than ccTLDs aren’t bound by the findings from SAC053 at https://www.icann.org/en/system/files/files/sac-053-en.pdf which have been included in the gTLD contracts.

Re: I bought netflix.soy

#110
post #80

Earlier quoted context omitted.

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.

I mean technically, maybe, but it's extremely unlikely that they'd sue without sending a C&D first. And given the lack of damage even if they did it'd likely get dismissed quickly with him just giving up the domain. But... INAL and this is not legal advice.

The biggest trouble people get themselves into with this kind of thing is if they, upon being contacted by the company, ask for money instead of immediately offering to transfer the domain to them free of charge. At that point it's trademark cybersquatting and they have your own words in the email as proof.

Speaking from personal experience here: being on the end of any kind of notice with the threat of legal force, even if it's not a lawsuit yet, is the kind of stress you just don't need in your life.

Post reply on HN