News for hackers. Stuff that matters.
Re:[email protected] by BerislavLopac on Sunday September 27, 2020 @02:20PM (#24608880)
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.<word>.com... :-o
Re:[email protected] by bigiain on Sunday September 27, 2020 @10:56PM (#24612523)
Back in the days before I'd ever heard of multicast DNS or zeroconf networking, I had a local dns server set up with all our subdomain.ourdomain.com duplicated as subdomain.ourdomain.local and pointing to our local dev/staging versions of our websites. It worked wonderfully, until I think MacOS 10.2 arrived (so, like 20 years ago almost) which had mDNS support for the first time and "broke" it all on me...

I switched to using subdomain.ourdomain.staging instead and got on with life. I wonder if anyone's gonna have to deal with the fallout of that decision when someone oneway pays ICANN enough money to own the .staging TLD?

(I wonder how much "interesting" stuff would land in your mail/web/ssh/whatever log files, if you registered .staging and .dev and just logged everything that came past (or intentionally/actively honey potted everything there?)

Re:[email protected] by marcthe12 on Monday September 28, 2020 @07:22AM (#24615432)
Use Lan. Reserved so no issues
Re:[email protected] by xmprt on Monday September 28, 2020 @12:09AM (#24612867)
I was about 5 seconds away from clicking this link on my work laptop until I realized what it would redirect to. For others like me, it's very NSFW
Re:[email protected] by BerislavLopac on Monday September 28, 2020 @03:38AM (#24614007)
It doesn't seem that the browsers still to the expansion things; I've tried it, and am just getting the "We’re having trouble finding that site." error message, or similar. But for some time that expansion was real.