Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

foo@bar.com

bar.com

Post reply on HN
Print view View original

31–40 of 301 posts

Re: foo@bar.com

#31

Post by CydeWeys »

eli wrote: post #30
CydeWeys wrote: post #14

This guy is really committed to the joke, seeing as how he could easily sell bar.com for millions of dollars. Note also that there is a .bar gTLD, and there is a foo.bar domain as of 2014 (though it doesn't seem to be hosting any content). I run the .foo gTLD, and bar.foo is a real domain (though admittedly not as good as foo.bar). There is no .baz; next round maybe?

I don’t think anyone is paying millions of dollars for domains any more. Maybe low six figures.

Domain names are going for more money than ever before. The record for most expensive sale (publicly known anyway) was hit just last year. 30 million dollars for voice.com: https://domainnamewire.com/2019/06/20/yes-voice-com-is-the-m...

Re: foo@bar.com

#32

Post by owl57 »

CydeWeys wrote: post #27
nebulous1 wrote: post #20

Earlier quoted context omitted.

A lot of people learned this the hard way when Google bought and later enabled permanent HSTS for the .dev domain (prior to actually publicly releasing it) in Chrome, breaking everybody's non https local .dev environments. As mentioned above, it should have been .test

The HSTS preloading fortunately ended up being an unintentional additional type of Controlled Interruption period, which was a good thing in the end. It would've been a lot worse if, one day, your fake domain names are resolving locally, and then literally the next day it's now a real domain name that's resolving remotely, with who knows what result. This at least forced people to address it well in advance of domain…

Sounds like it could be intentional.

— We bought .dev, now what we do with all those people in the wild misusing it?

— Well, most of them misuse it with our browser, let's break at least their hacks early and loudly.

Re: foo@bar.com

#33

Post by AQuantized »

CydeWeys wrote: post #25
Jaruzel wrote: post #19

Earlier quoted context omitted.

bar.foo redirects to careers.google.com. Nice joke. ;)

Yeah, it used to be a programming problem challenge website feeding into recruiting efforts. It was turned down though after living out its useful life and now it's just a redirect.

I believe the actual foobar challenge site is still running.

Re: foo@bar.com

#34

Post by paledot »

ryanbrunner wrote: post #13
darkerside wrote: post #11

Earlier quoted context omitted.

I've typically used example.com for testing, but link says it's just for documentation. Sounds like .test is the sanctioned way. https://en.m.wikipedia.org/wiki/.test

In practice, is there any difference? As long as example.com is guaranteed to be reserved, I don't see any downside in using it. Not using .test was a big problem for tools like Pow a while ago, but that's because they were using .dev, which had no official recognition as being reserved or special-purposed. For e-mail addresses in particular, I could easily see a situation where your domain logic prevents you from us…

Well, example.com resolves, . test doesn't. Depending on your use case, one or the other may be desirable, but if you're setting up a dev environment, .test is your answer.

Re: foo@bar.com

#36

Post by kubanczyk »

ryanbrunner wrote: post #13
darkerside wrote: post #11

Earlier quoted context omitted.

I've typically used example.com for testing, but link says it's just for documentation. Sounds like .test is the sanctioned way. https://en.m.wikipedia.org/wiki/.test

In practice, is there any difference? As long as example.com is guaranteed to be reserved, I don't see any downside in using it. Not using .test was a big problem for tools like Pow a while ago, but that's because they were using .dev, which had no official recognition as being reserved or special-purposed. For e-mail addresses in particular, I could easily see a situation where your domain logic prevents you from us…

> In practice, is there any difference?

RFC 6761 says that there is a difference when I actually resolve these names. The example.com, example.net, etc. will resolve normally to an existent IP. Moreover they resolve the same way on every DNS cache.

The xxx.test will resolve as non-existent by default, unless you configure your own DNS specifically for them.

Re: foo@bar.com

#37

Post by EvanAnderson »

chrismeller wrote: post #4

Something that I’m surprised a lot of devs don’t know; there are official domains you’re supposed to use for documentation, testing, etc. They are specifically reserved by IANA for these purposes. Originally I think it was just example.com, but they now have a list of all them: https://www.iana.org/domains/reserved

You also have Microsoft's list of domains / companies used in their documentation and examples: https://social.technet.microsoft.com/wiki/contents/articles/...

Re: foo@bar.com

#38

Post by CydeWeys »

AQuantized wrote: post #33
CydeWeys wrote: post #25

Earlier quoted context omitted.

Yeah, it used to be a programming problem challenge website feeding into recruiting efforts. It was turned down though after living out its useful life and now it's just a redirect.

I believe the actual foobar challenge site is still running.

You got a link? Because I'm pretty sure it was running on the bar.foo domain.

Re: foo@bar.com

#39

Post by CydeWeys »

owl57 wrote: post #32
CydeWeys wrote: post #27

Earlier quoted context omitted.

The HSTS preloading fortunately ended up being an unintentional additional type of Controlled Interruption period, which was a good thing in the end. It would've been a lot worse if, one day, your fake domain names are resolving locally, and then literally the next day it's now a real domain name that's resolving remotely, with who knows what result. This at least forced people to address it well in advance of domain…

Sounds like it could be intentional. — We bought .dev, now what we do with all those people in the wild misusing it? — Well, most of them misuse it with our browser, let's break at least their hacks early and loudly.

It was unintentional.

Source: The horse's mouth. I'm the guy who came up with the idea of launching .dev and .app as HTTPS-only TLDs, and I'm the one who had them added to the HSTS preload list.

Post reply on HN