Live data from Hacker News

Google no longer providing original URL in AMP for image search results

twitter.com

231–240 of 566 posts

Re: Google no longer providing original URL in AMP for image search results

#231

This is so unfriendly to users. I don't understand the push to obscure URLs. They are sometimes hiding the URLs in search results also which is infuriating. One more reason to use DuckDuckGo.

Another thing that is extremely annoying is the hiding of urls in Chrome. Hiding the protocol and the rest of the url besides the domain. When you go to click up in the url/address bar to change a section of the site the protocol re-appears and messes you up. Or when you click in on some mobile and the whole url disappears and you just wanted to change part of the url. Yes Google there are still people that want hack…

Yeah the hiding of the protocol in the URL was a pain to deal with. I updated Chrome today and looks like there's a way to turn this off:

1. Enable chrome://flags/#omnibox-context-menu-show-full-urls

2. Right click the address bar

3. Select 'Always show full URLs'

Instead of seeing: news.ycombinator.com You'll now see: https://news.ycombinator.com

I made a Tell HN post about it: https://news.ycombinator.com/item?id=23322705

Re: Google no longer providing original URL in AMP for image search results

#232

Earlier quoted context omitted.

I've been using DDG as my default search engine for more or less a year now, and tbh I find myself using the !g bang way more often than I'd like. Basically anytime I'm searching for something dev related or anything that's broad enough that without my personal user info it would be hard to return the results I'm looking for. Which is kind of the crux of the issue I believe. For everything that's wrong with Google as…

"YMMV though, maybe I need to step up my searching game to obtain better results using DDG. That's definitely something I should work on." Yeah, I had the same exact feeling a couple of month ago and created this [0]. [0] https://www.runnaroo.com

Looks interesting! I'll give it a look, thank you!

Re: Google no longer providing original URL in AMP for image search results

#233

How does anyone think this is a good idea? It should be clear which news site I am reading when I'm reading an article. Otherwise, how do I know which bias to apply? On iOS, the title bar says "google.com" whether I'm reading an article from CNN.com or WashingtonExaminer.com. Of all the anti-competitive actions google has taken around search results, AMP is by far the worst. I hope they get smacked down for it in the…

>Of all the anti-competitive actions google has taken around search results, AMP is by far the worst. I hope they get smacked down for it in the upcoming anti-trust lawsuit.

This reminds me of the EU Internet Explorer lawsuit, which was peanuts compared to what Google is doing right now. Between Google Search, Chrome, Android, Youtube, Gmail, Google Maps, Google Docs, AMP and likely 5 more things I forgot, they've stealth-grabbed so much of the internet, it's not even funny. At least force them to split off their ad/datahoarding businesses.

Re: Google no longer providing original URL in AMP for image search results

#234
post #152

Earlier quoted context omitted.

https://amp.dev It's supposedly a component framework. supposedly you can build web stuff faster and easier using it. In reality it looks like Google is using it a Trojan horse

It's direction is no-longer owned by Google, but by the OpenJS Foundation, right?

yes. we will also all get a 10% raise and a Tesla with our next paycheck.

Re: Google no longer providing original URL in AMP for image search results

#237

I understand the objections to Google's actions--this is clearly a dick move which is terrible for both users and content creators--but I'm not understanding the AMP hate here. As a user, AMP is great. AMP is a better implementation of the open web than HTML is. It's a (usually) self-contained document that isn't tightly coupled to the server it came from. You can download an AMP document, render it, attach it to an…

The silent down-voters are more likely site owners who feel they are being coerced into using AMP in order to compete in Google's search rankings, or users who feel they are being forced to visit AMP sites (which have various usability or privacy concerns) due to these site owners being coerced. (For what it's worth, I up-voted you).

Sure--but that's the result of society giving too much power to Google, not the result of AMP.

Re: Google no longer providing original URL in AMP for image search results

#238
post #48

This is pretty much what we've been saying would happen since the day AMP was fire presented to the public. I really hope this AMP thing never becomes anything mainstream, it's an atrocious attempt at monopolizing the internet as a whole.

I believe it’s already mainstream :(

I'm seeing AMP in random links non-techy people post all the time, it's depressing and it's become basically 50% of URLs I see posted.

Re: Google no longer providing original URL in AMP for image search results

#239

I have never liked AMP and I really don't like this. I also find myself wondering if this has any security implications. I mean if AMP effectively disguises the original URL could it not be used for phishing? To be clear I know very little about AMP and if this is the case Regardless it just adds complexity and makes it that much harder to teach people what is an acceptable URL when it comes to email links etc...

It uses Signed HTTP Exchanged.

https://blog.amp.dev/2018/05/08/a-first-look-at-using-web-pa...

Re: Google no longer providing original URL in AMP for image search results

#240
post #199

Earlier quoted context omitted.

How does a client-side cert help with authenticating the server? Why wouldn’t a phishing site also ask for the client-side cert if the real site does?

~~It wouldn't work because the phishing site would lack the private key needed to validate your client-side certificate and the TLS connection would not be established. This is assuming that the legitimate website itself signed your certificate signing request (CSR) to create the client-side certificate.~~ Edit: What I posted above is not correct. What I should have said was that the server would validate the client…

A private key is not required to validate certs (private keys are for generating certs). A cert chain back to a trusted root cert is required for validation. A phishing site would just trust all certs.
Post reply on HN