I bought netflix.soy
231–240 of 272 posts
Re: I bought netflix.soy
#232Earlier quoted context omitted.
The validity of this effect has been called into question, but for a long time, this was the "standard response" to situations like this: https://en.wikipedia.org/wiki/Bystander_effect
Yeah the Kitty Genovese (sp) story is an example right? Wasn’t that proven to be a myth or something?
Re: I bought netflix.soy
#233Interestingly, I recently saw a couple a couple of google.* domains available on Google Domains, including some reasonable-sounding ones: IIRC, google.tech (edit: google.page), google.business, and google.camp. Tried to purchase them but they instantly became unavailable the moment I tried to do so. The cynic in me thinks that Google has a special check for those and renews it themselves if someone tries… More genera…
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.
Re: I bought netflix.soy
#234Earlier quoted context omitted.
What happens if I have a computer on my network named ai? Wouldn't it cause a conflict? I called my FreeNAS box freenas because I didn't feel very creative, and I can browse to it as http://freenas or http://freenas./ but if they took a domain of 'freenas' suddenly that means I have to do extra work and rename my stuff. Doesn't seem fair!
You should have used a reserved TLD like `.local'. If you set it as the local domain name `ai' and `ai.local' would work. `ai.' would not work, as the dot at the end tells it to look at the top level. (like the slash at the beginning of an absolute path)
Re: I bought netflix.soy
#235"Did you know it costs a minimum of $185,000 to create your own domain name ending? For that kind of money, I think ICANN, the registries and registrar sites have a massive responsibility to ensure that this never happens." No they don't. The same problem exists with subdomains, for example some users may visit "netflix.trustworthy-sounding-domain.com" and not notice the issue. Meanwhile, using a weird TLD can raise…
netflix.trustworthy-sounding-domain.com isn't really the same though. If I own netflix.trustworthy-sounding-domain.com, I can create facebook.trustworthy-sounding-domain.com, google.trustworthy-sounding-domain.com, etc simply by creating new DNS records. No one but myself is involved, or even know they exist (unless I put links to them somewhere public). On the other hand, someone owns and operates .soy, and has to a…
So they send people emails with URLs like "netflix.user-support.com" where "user-support.com" is owned by the malicious actor. This is extremely common.
I honestly don't see any other problem. How else would you get people to visit "netflix.soy", if not by the same mechanism? It doesn't matter who controls which part of the domain, users are either going to notice the odd parts of the domain, or they are not. The fact that one is a TLD and the other isn't doesn't really make a difference, at least for uncommon TLDs.
> On the other hand, someone owns and operates .soy, and has to actually approve new domains getting created. Part of that process could be a step that automatically screens for scammy looking registrations.
Yes, but that wouldn't do anything to solve the problem. It would only make things more expensive. I honestly don't see the issue with anybody owning "netflix.soy" unless they're malicious, but in that case owning "netflix.anything-else.com" would be just as bad, if not worse. Since we can't really prevent the latter case, preventing the former case is moot.
Re: I bought netflix.soy
#236Re: I bought netflix.soy
#237Earlier quoted context omitted.
Yeah the Kitty Genovese (sp) story is an example right? Wasn’t that proven to be a myth or something?
Yes, just like Stockholm Syndrome, it was made up to cover up a bungled police response. Neither one is a real thing.
Re: I bought netflix.soy
#238Earlier quoted context omitted.
Yes, just like Stockholm Syndrome, it was made up to cover up a bungled police response. Neither one is a real thing.
Source? https://en.wikipedia.org/wiki/Stockholm_syndrome#FBI_Law_Enf... says it's rare but FBI seems to be saying it is a real thing.
Here is the backstory of how it was created: https://twitter.com/sezmohammed/status/1252500993972948992
Re: I bought netflix.soy
#239Earlier quoted context omitted.
UDRP typically rules in favor of the holder of the unambiguous trademark in these kinds of cases. As an example, "Exxon Mobil" refers unambiguously to a single entity only, and has no other possible uses, so anyone registering exxonmobil.{anything} would lose if the company came after them. No one else has any right to that trademark, and ICANN enforces trademark rights on domains. If the trademark already existed wh…
What about .sucks? Couldn’t one claim free speech? https://www.forbes.com/sites/rogerkay/2015/06/29/saga-of-suc...
You can see every domain with SUCKS in it filed against and the outcome. 66 Granted (complainant won). 35 Denied. 4 Split.
My favorite domain filed against from the list: guinness-beer-really-really-sucks.com also against the guy who got the anti cyber squatting legislation created by pointing disney typos to porn.
Re: I bought netflix.soy
#240Registering 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?
Also if you lose one case, you are likely to have that used against you in the future (pattern of behavior). So any subsequent defense may be weaker in a system that already strongly favors TM holders.