9 ms·

Using the signed exchange mechanism means you allow anyone to serve your content. You will no longer know when it has been served and by whom. Instead, Google w

• jimktrains2 8y ago
  Amp does allow Google analytics and other analytics services. Unfortunately, most places don't use server logs for much :(
  • Tepix 8y ago
    Chances are if you don't want Google to serve your content to protect the privacy of your users, you don't want to use Google Analytics either. Btw your account seems rather active for an account with the description "Inactive. Deletion Requested." :-)
    • atoav 8y ago
      Or if you want that stuff to work e.g. in China.
  • tracker1 8y ago
    A bit more on this... there are a LOT of secondary bots out there, either searching for security holes to exploit or otherwise slurping content for reasons other than search. JS based analytics (google or otherwise) is generally a better option for detecting actual usage. Yeah, you lose maybe 2% of actual users. You also lose 99% of the various bots. You still have to filter google's and bing's bots that execute JS though.
• hknd 8y ago
  The caching doesn't necessary need to be by Google. https://blog.cloudflare.com/announcing-amp-real-url/ https://blog.cloudflare.com/announcing-amp-real-url/
  • codedokode 8y ago
    Caching not by Google doesn't give you a priority placement in the search carousel so it is pretty useless.
  • singron 8y ago
    I think that product is still cached by Google. Cloudflare is just providing the cryptography for Web Packaging so that the browser will show the url from the original page instead of the Google cache.
• ihuman 8y ago
  > You will no longer know when it has been served and by whom I'm OK with publishers knowing less about the people seeing their content.
  • jononor 8y ago
    They just have to access the data via Google. Who can cross-link it with all the other data they have. No real privacy gain here.
  • Ajedi32 8y ago
    That statement is also false, because publishers can still track when the page is served via JS.
• zackbloom 8y ago
  The reason it has to be prefetched from not-you is to protect the users privacy. Until they click a link it is not considered acceptable to leak their search to the potential destination. Links have to be fetched from a third-party who the search engine trusts not to share the data, that at the moment is Google but will hopefully expand.
  • Tepix 8y ago
    „Considered acceptable“ by whom? Why should the user‘s privacy be protected toward the content provider instead of the search provider? The search provider already knows more about me.
  • codedokode 8y ago
    Google already can do this by preloading a cached page from its own domain. So this specification is unnecessary. I think the real reason is that Google wants to build a walled garden, but doesn't want the walls to be noticeable. Even with AMP, they display a header that looks like a browser's address bar [1] Also, on that page Google admits that it uses AMP Viewer to collect information about users: > Data collection by Google is governed by Google’s privacy policy. Which is probably their real motication for creating AMP. [1] https://developers.google.com/search/docs/guides/about-amp https://developers.google.com/search/docs/guides/about-amp
    • pvorb 8y ago
      Exactly: Google built a walled garden and now replaces the fence by glass, because people don't like the view from inside their cage. The worst thing is, that it'll get away with it.
    • pxtail 8y ago
      > I think the real reason is that Google wants to build a walled garden Exactly, this is the real reason why this abomination came into existence - all of this is masked as work for greater good all for those poor kids with limited network speed. As end effect everyone will suffer - user will never leave google ecosystem, he will remain on search page without even knowing about it, creator will lose control over his own content