Where Am I? NYTimes or Google?
251–260 of 381 posts
Re: Where Am I? NYTimes or Google?
#252Earlier quoted context omitted.
Please provide a link, I could only find this, which suggests Google has reversed course: https://www.techradar.com/uk/news/google-is-phasing-out-thir...
> By undermining the business model of many ad-supported websites, blunt approaches to cookies encourage the use of opaque techniques such as fingerprinting (an invasive workaround to replace cookies), which can actually reduce user privacy and control. https://blog.chromium.org/2020/01/building-more-private-web-... I'm going to copy paste my older comment on this: I find their "removing 3rd party cookies will incent…
Re: Where Am I? NYTimes or Google?
#253IMO the core point of the article is false. > To be blunt, this is a really dangerous pattern: Google serves NYTimes’ controlled content on a Google domain. No, "Google serves NYTimes' controlled content" is an oxymoron. Google controls the content that is served, and that's all your browser is verifying. Google could very well make the NYTimes content on there display something else and your browser wouldn't show a…
With Signed HTTP Exchanges, for Google to modify the content that is served, Google would need access to a private key for a certificate for nytimes.com, no? Either nytimes.com has handed over that key or Google would have to create a key/certificate for nytimes.com. Believing Google would maliciously issue certificates seems a stretch to me. I don't like AMP nor much of how Google has behaved with it ( http://exple.…
No, Signed HTTP exchanges are something that Google dreamed up so people don't have to see their hegemony over the modern web (or as the article you linked calls it, a shakedown). It's not a browser standard so far, because of Apple and Mozilla's resistance.
There are legitimate ways for NYTimes to allow Google to serve content on behalf of them, like so many other CDNs around the world (it usually involves the CDN generating the certificate for your site as well). Why should people create new standards for HTTPS and URLs simply for Google's benefit?
I don't deny that there's a way to make "nytimes.com" work where everything is served by "google.com". What I'm questioning is why we need a completely new web standard for doing so that affects the URL, something that has been standard for decades.
Re: Where Am I? NYTimes or Google?
#254Yes this has been a big issue for a very long time now. Google wants to push a release where it will display the hostname of the amp site even if the content is being served from google.com[1]. Mozilla (and Apple) are strictly against it and thank god for Mozilla. If Google had a bigger market share this would already be something we would have been living with. I'm sure there are better sources for this, but here is…
One should never forget that at a certain point, Google will likely invoke the looser's argument ("protect you from terrorists and pedophiles") to require proof of identity prior to granting access to any resource or service it controls.
Anything that helps them advance in that direction must be fought fiercely.
Re: Where Am I? NYTimes or Google?
#255Re: Where Am I? NYTimes or Google?
#256Re: Where Am I? NYTimes or Google?
#257Earlier quoted context omitted.
I don't get this. Clearly the contents is served by Google, and so they can do whatever they like with it. How is an end user going to know whether the message was signed before it was passed on or not?
That's nonsense. Take a moment to breathe. Think about just typical https, when you request some nytimes.com content that is actually being delivered to you througha bunch of intermediaries. So, by your logic any of those could just change that content. But it turns out, this was a problem solved like 50 years ago. With https, the content is signed by some key that you trust to represent nytimes.com. Sidenote (this i…
Given that HTTP Signed Exchanges are nowhere near a web standard at this point, I think you should tone down your vitriol considerably.
Currently, what the parent commenter is saying is completely valid and true; if you're serving things on your domain and have a cert for it, you can serve " rel="nofollow">https://youdomain.com/, where could be www.nytimes.com, www.google.com, or whatever. HTTP Signed Exchanges proposes a breaking change to this, and therefore is non-intuitive for the vast majority of users.
Re: Where Am I? NYTimes or Google?
#258People have been railing against Google's Amp on HN for years, and I think I finally figured out what it's for. It's Google way of combatting phone apps. If all of the world's information — especially current news and similar information — moves from the open web into apps, then Google can no longer crawl, index, or scrape that information for its own use. The rise of the mobile phone app is a threat to Google on so…
Besides,you dont need the app on your mobile.
Re: Where Am I? NYTimes or Google?
#259Earlier quoted context omitted.
Publishers who use AMP were already allowing Google to track everything through either Analytics or Ads. Likewise, AMP pages are mostly accessed from Google search that's already tracked.
As a user I can choose to block GA, either through URL blocking or through legally mandated cookie choices in some regions (e.g. France). When served from Google I have no choice in the matter.
Re: Where Am I? NYTimes or Google?
#260Earlier quoted context omitted.
The AMP spec REQUIRES you include a Google controlled JavaScript URL with the AMP runtime. So technically the whole signing bit is a little moot, given that the JS could do whatever it wanted.
The same could be said of any CDN hosted javascript library. For example: jquery. There is an open intent to implement support for publishers self-hosting the AMP library as well.