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

141–150 of 301 posts

Re: foo@bar.com

#141

Post by tus88 »

davemtl wrote: post #54
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

Indeed. I've owned `invaliddomain.com` for almost 20 years. You'll be surprised how many use it for testing. One morning I woke up to 30,000 e-mails from Sony Japan with PDFs attached of scanned hand-written part orders. Something similar with Boeing sending me backup notifications. I notified each of these companies about their configuration through their official channels, only to be told "no, it's your server doin…

Why would you tell them and bring an end to the lolz?

Re: foo@bar.com

#142

Post by diamondo25 »

monadic2 wrote: post #113
CydeWeys wrote: post #80

Earlier quoted context omitted.

.app, .dev, .prod, and .zip all had substantial volume of problematic traffic that was discovered during the Controlled Interruption period (which occurs prior to launch and consists of a wildcard DNS entry placed on the entire TLD). You would not believe some of the brokenness that was happening there. .zip may need some explanation -- apparently there are lots of library API calls out there that take a path string…

Ruby's `open` accepts urls. I can't say I've ever used this functionality.

PHP's file_get_contents supports it as well.

Re: foo@bar.com

#143

Post by tingletech »

I worked for Bill Blue at CTS net for about 6 weeks in '94. One of the machines I worked on was named "crash". I asked if that name was not tempting fate.

Bill said it was so that some uucp address would be

   crash!boom
(read "crash bang boom")

Re: foo@bar.com

#144

Post by BiteCode_dev »

Ekaros wrote: post #137
jdxcode wrote: post #130

Earlier quoted context omitted.

if we could go back I wonder if it would be better if we had required a leading dot in domain names ".google.com"

Or if browsers weren't trying to be too smart enough and use the same box for both searching and addresses. Trips me with .py files all time time.

After ".py", use " ?" (the space is important) to force the search in firefox.

Re: foo@bar.com

#146

Post by CydeWeys »

basch wrote: post #138
jdxcode wrote: post #130

Earlier quoted context omitted.

if we could go back I wonder if it would be better if we had required a leading dot in domain names ".google.com"

or go back to left to right reading. http//com.google.www. vs http//com.google.www./file.zip

This is the real answer here. It's widely believed that domains working the opposite way of filesystem hierarchies and even URL paths was a huge design mistake. Think of how many billions of dollars have been lost over the years from account compromises resulting from people not correctly distinguishing yourbank.com/account/foobar from yourbank.com-account.info/foobar.

Re: foo@bar.com

#147

Post by mdaniel »

grishka wrote: post #15

It's behind cloudflare and I was met with a captcha AGAIN. Sigh.

If CF is still using that abomination "hCaptcha", you can get an accessibility cookie for it which doesn't stop the captcha from appearing but does cause it to actually work when you click on the "I am a human" widget, unlike the normal broken flow

Re: foo@bar.com

#149

Post by darkerside »

srtjstjsj wrote: post #115
darkerside wrote: post #17

Earlier quoted context omitted.

Probably not, but it's always nice to follow intended designs, since others will do so as well and this allows systems to evolve in compatible ways. There may be no difference today, but there could be tomorrow. These days invalid TLDs don't really exist. New ones are getting released all the time. The only problem you'd run into is if the system you're using is treating .test differently for some reason, but that's…

.invalid is guaranteed invalid by spec.

Touche

Re: foo@bar.com

#150

Post by BerislavLopac »

davemtl wrote: post #54
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

Indeed. I've owned `invaliddomain.com` for almost 20 years. You'll be surprised how many use it for testing. One morning I woke up to 30,000 e-mails from Sony Japan with PDFs attached of scanned hand-written part orders. Something similar with Boeing sending me backup notifications. I notified each of these companies about their configuration through their official channels, only to be told "no, it's your server doin…

I remember reading - long time ago - a story of a developer who used http://xxx as a placeholder for unknown domains, until at some point the browsers started resolved single-word links into www..com... :-o
Post reply on HN