No doubt because most large web corporations have completely switched to javascript for their anchors (ie, #) and no longer use HTML spec anchors that actually work. I'm looking at you Microsoft Github.
Chrome deploys deep-linking in latest build despite privacy concerns
21–30 of 159 posts
Re: Chrome deploys deep-linking in latest build despite privacy concerns
#22No doubt because most large web corporations have completely switched to javascript for their anchors (ie, #) and no longer use HTML spec anchors that actually work. I'm looking at you Microsoft Github.
> I'm looking at you Microsoft Github.
Where don't anchors work when javascript is disabled? (With admittedly very brief testing just now, I couldn't find any such cases.)
Re: Chrome deploys deep-linking in latest build despite privacy concerns
#23Imagine telling someone in 2003 or so that the most popular web browser fifteen years later would be made by DoubleClick and imagine what their reaction might be.
Something like "wow, software development will improve so much! You will make a web browser in a double-click."
Re: Chrome deploys deep-linking in latest build despite privacy concerns
#24What? A DNS lookup doesn't include anything but the hostname and anything following a hash is never sent with a request from the browser.
Re: Chrome deploys deep-linking in latest build despite privacy concerns
#25What? A DNS lookup doesn't include anything but the hostname and anything following a hash is never sent with a request from the browser.
Re: Chrome deploys deep-linking in latest build despite privacy concerns
#26As a developer, how do I lend my support to stopping google from trying to steal the web? Something actionable, something specific to my semi-unique position as a developer?
As a first step, at least: Use and contribute to Firefox (or other non-Blink-based browsers, but there aren't many to choose from...), and encourage those you support/influence to do the same.
Re: Chrome deploys deep-linking in latest build despite privacy concerns
#27What? A DNS lookup doesn't include anything but the hostname and anything following a hash is never sent with a request from the browser.
It seems that “privacy researcher at brave” is a job requiring no domain knowledge, only plentiful contact with credulous journalists.
Re: Chrome deploys deep-linking in latest build despite privacy concerns
#28I'm not convinced this is a problem. In terms of ways we leak privacy on the web, this seems very low on the priority list.
Re: Chrome deploys deep-linking in latest build despite privacy concerns
#29Seems like a useful feature to me. You could just train yourself not to click on hyperlinks with the aforementioned tag. And like another comment says, it shouldn't be a privacy issue unless you are running over HTTP, since the resource URLs are encrypted.
Re: Chrome deploys deep-linking in latest build despite privacy concerns
#30Just like everything else. Millions of users won't understand what this is talking about, or care for that matter.