201–210 of 224 posts
Earlier quoted context omitted.
Have you ever met rms? http://www.jwz.org/hacks/why-cooperation-with-rms-is-impossi...
for the uninitiated, you're looking for an audio file at the above link. you need to delete your HN referrer in order to do that because jwz is a "special" kind of adult.
It must have been nice to have been alive in the early internet where barely any domains were taken. On the bright side domains have been less relevant since the rise of accessing sites via search engines and the move to mobile apps whose stores don't suffer from the squatting issues.
This is worse as now you have to compete with ads (potentially from scammers) and SEO. At least with domains, once you register all the major misspellings for a nominal fee, the problem is resolved. With ads, it's an auction so you're constantly paying a protection racket to the search engine to outbid the malicious actors.
Yeah, I can sympathize... I've been using "jest" as my nickname since college years, like 25 years now. Now I'm bothered when someone upgrades @jest in their JavaScript project on GitHub or BitBucket
Earlier quoted context omitted.
No, the page layout is likely designed to be readable on anything that speaks HTTP. Including text-based browsers, mobile devices with low bandwidth and performance, screen readers, etc. All you have to do to get the text width you want is resize your browser window.
None of those things are harmed by putting a maxwidth that limits the line length to something reasonable for the viewport size.
This is the strangest gift I ever saw.
> My husband registered it as a birthday gift back in 1996. This is the strangest gift I ever saw.
A great read. There's something to be said about being early to the party.
This is awesome. I have following 2 domains, which are a popular misspellings :) 1. https://geethub.com/ 2. https://geetlab.com/ Both of them get non-trivial amount of traffic.
Earlier quoted context omitted.
The requesting computer has a bit flip and requests the wrong domain. It even is not stopped by HTTPS depending on where the bit flip happens and how the software is written.
Is there any data to support the hypothesis that this happens often? I've never experienced it without being a human typo. I find it hard to believe in this day and age we have a single service that has high error rates no one notices.
Earlier quoted context omitted.
The requesting computer has a bit flip and requests the wrong domain. It even is not stopped by HTTPS depending on where the bit flip happens and how the software is written.
Is there any data to support the hypothesis that this happens often? I've never experienced it without being a human typo. I find it hard to believe in this day and age we have a single service that has high error rates no one notices.