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
Chromium uses web search for .internal TLD instead of opening URL
51–60 of 96 posts
Re: Chromium uses web search for .internal TLD instead of opening URL
#52What a bizarre response from Google, a couple hours after this was posted: > @Reporter: As we are not very clear about the issue being faced by you, could you please elaborate on the same by providing detailed manual repro steps to reproduce the issue from our end. > Also requesting you to share the expected, actual behaviours along with screen-cast for better understanding of the issue. > *Note: Requesting you to co…
probably just an ai or unskilled triage tech responding?
Sounds like someone just had a desire to make this pesky bug report go away, requesting detailed version information, detailed steps to reproduce, expected behaviour and a screencast (!), hoping the reporter wouldn't provide them so they have an excuse to close the ticket?
Re: Chromium uses web search for .internal TLD instead of opening URL
#53One of the worst security bugs of browsers is the combined url/search bar. But Google loves it! What about .corp subdomains?
The fact of the matter is most people do not grok addresses, so a dedicated address bar is useless to them. It's bad user interface design that defies what most people can do.
Here's how most people actually use a web browser if they want to go somewhere, say Amazon:
1. Type "amazon".
2. Enter.
3. First result is (probably) amazon.com.
4. Click.
5. ????
6. PROFIT!
In the dark ages this was facilitated by setting the home page to a search engine like Google, changing the address bar to a search bar removes that additional step making it that much easier for the common man.
Is it horrible for security and privacy? Yeah. But you write a web browser for users, not security and privacy nazis.
Re: Chromium uses web search for .internal TLD instead of opening URL
#54Earlier 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.
Most people don't know how to navigate their local file system, let alone the internet.
Re: Chromium uses web search for .internal TLD instead of opening URL
#55Re: Chromium uses web search for .internal TLD instead of opening URL
#56One of the worst security bugs of browsers is the combined url/search bar. But Google loves it! What about .corp subdomains?
No, everyone loves it. By everyone I mean the vast majority of the world. The fact of the matter is most people do not grok addresses, so a dedicated address bar is useless to them. It's bad user interface design that defies what most people can do. Here's how most people actually use a web browser if they want to go somewhere, say Amazon: 1. Type "amazon". 2. Enter. 3. First result is (probably) amazon.com. 4. Click…
Could we please not use such a term for privacy/security conscious people? Maybe it’s because I am German but I feel very uncomfortable being called such.
Re: Chromium uses web search for .internal TLD instead of opening URL
#57Earlier quoted context omitted.
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)
IIRC there is no setting in Firefox to keep the content of the URL bar local.
If you want the content of your URL bar to stay local you should disable suggestions
Re: Chromium uses web search for .internal TLD instead of opening URL
#58As a workaround you can type a trailing slash: example.internal/
Re: Chromium uses web search for .internal TLD instead of opening URL
#59Earlier quoted context omitted.
It's because of the omnibox that people no longer know what an URL is.
You have it backwards: The omnibox (or whatever you want to call it) came about because people don't know what the hell a Universal Resource Locator is. Most people don't know how to navigate their local file system, let alone the internet.
The U stands for "uniform". Which kinda supports your point, actually.
Re: Chromium uses web search for .internal TLD instead of opening URL
#60Having 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
Hanlon's razor is malicious . Assuming malice is the trivial right choice. Assuming stupidity just bc it rhymes, or bc you can feel smart about yourself is stupid .