https://news.ycombinator.com/item?id=32801317
17:07:12 vs 17:10:57
great minds, yada yada ;-)
151–160 of 208 posts
https://news.ycombinator.com/item?id=32801317
17:07:12 vs 17:10:57
great minds, yada yada ;-)
You can also use Unicode ligatures to make URls which look shorter. From that list, you could use http:// ㎝. / - that's U+339D if HN mangles it. I wrote it up at https://shkspr.mobi/blog/2020/08/buying-a-single-character-d...
Interestingly, in my lan: dig ai @ googledns works dig ai @ unbound works (DoT cloudflare behind) dig ai @ dnsmasq NXDOMAIN (openwrt, forwards to unbound) Thus something's up with openwrt (22.03.0 release) dnsmasq, or dnsmasq in general.
https://news.ycombinator.com/item?id=32804868
There's a dnsmasq setting you have to twiddle to make it work.
You can also use Unicode ligatures to make URls which look shorter. From that list, you could use http:// ㎝. / - that's U+339D if HN mangles it. I wrote it up at https://shkspr.mobi/blog/2020/08/buying-a-single-character-d...
Unicode URLs are scary
Shorten URLs using invisible spaces
http://ai is an interesting case. It was there from the early days of the web, back when you could type "ai" into the mozilla url bar and it would take you there. Today firefox "helps" you out and changes what you typed into something else because it knows better than you do what web site you want. It's run by a character named Vince Cate who moved to Anguilla to protest taxes or something. He was from the US and gav…
I genuinely want to know what you think is the percentage of FF users who type "ai" who intend to go to http://ai and not search for "ai" is. Even better if you can estimate that for all possible single words that are also TLDs. And then tell me why users who might actually want the domains can't just disable search from the address bar which is a feature FF has which is exactly tailored for this use case. And then also tell me what is wrong with having to explicitly specify "http:// TLD>" which works even when the search-from-address feature is enabled.
http://ai is an interesting case. It was there from the early days of the web, back when you could type "ai" into the mozilla url bar and it would take you there. Today firefox "helps" you out and changes what you typed into something else because it knows better than you do what web site you want. It's run by a character named Vince Cate who moved to Anguilla to protest taxes or something. He was from the US and gav…
> Today firefox "helps" you out and changes what you typed into something else because it knows better than you do what web site you want. I genuinely want to know what you think is the percentage of FF users who type "ai" who intend to go to http://ai and not search for "ai" is. Even better if you can estimate that for all possible single words that are also TLDs. And then tell me why users who might actually want t…
Earlier quoted context omitted.
> Today firefox "helps" you out and changes what you typed into something else because it knows better than you do what web site you want. I genuinely want to know what you think is the percentage of FF users who type "ai" who intend to go to http://ai and not search for "ai" is. Even better if you can estimate that for all possible single words that are also TLDs. And then tell me why users who might actually want t…
The bigger question is what percentage of users would like a separate search / location field. Merging them created this problem but now that screens are bigger I think we can afford another textbox.
Earlier quoted context omitted.
At Google and many other tech companies, internal machines are configured to have go/ work just like you describe. Looks like someone even made a whole company around it https://www.golinks.com/blog/go-links-history/
A problem with this approach is browsers love to resolve it to http://go.com , so Disney may be getting a feed of what Googlers are interested in.