41–50 of 96 posts
Having trouble not attributing to malice that which is adequately explained by stupidity here... For Home Assistant for instance, the only reasonable option is .internal - its default .local is not the right TLD to use. [1] [1]: https://serverfault.com/a/937808
What if you advertise it on mDNS?
Actually, entering _anything_ that looks like a FQDN should automatically bypass search in any browser. It’s been a long-standing pain of mine that when browsers merged the URL and search fields it became impossible to type “home.lan” (or .local, or .internal) and have it just work without stomping out http:// in front.
The number of times I've typed some internal-only thing or raw IP address into a browser and had it go to a search page instead of the thing I want to talk to, I've lost track of in the past 15 years, and it's too damn high.
Earlier quoted context omitted.
Personally I like them separate. But I’ve been working with folks who are not very computer literate at all and I think I agree with you. If one doesn’t know what a URL is in the first place, how would one distinguish which box to type in?
Having them be the same can make tech support a nightmare trying to figure out whether someone actually successfully entered a URL or if they just googled it :( (I personally love the URL bar & search bar being the same bar)
Earlier quoted context omitted.
Personally I like them separate. But I’ve been working with folks who are not very computer literate at all and I think I agree with you. If one doesn’t know what a URL is in the first place, how would one distinguish which box to type in?
The one that says "Search" in it?
Earlier quoted context omitted.
Personally I like them separate. But I’ve been working with folks who are not very computer literate at all and I think I agree with you. If one doesn’t know what a URL is in the first place, how would one distinguish which box to type in?
It's because of the omnibox that people no longer know what an URL is.
The first thing I do after installing a web browser is disable search for the URL bar.
..maybe I can set up an own mock search service on localhost. Hmph, I will think about it
One of the worst security bugs of browsers is the combined url/search bar. But Google loves it! What about .corp subdomains?
I think it's the autocomplete in particular that leaks a lot of private data. I've rarely had the combined bar do a search when I didn't want it to. But I use firefox and I turned off autocomplete. And I use my own search instance (SearXNG)
That’s the beauty. The whole unified input can be presented as a UX simplicity gain, while this quote points at the actual business value. ;)
One of the worst security bugs of browsers is the combined url/search bar. But Google loves it! What about .corp subdomains?
I think it's the autocomplete in particular that leaks a lot of private data. I've rarely had the combined bar do a search when I didn't want it to. But I use firefox and I turned off autocomplete. And I use my own search instance (SearXNG)