3 ms·
> is the case against all down to Google's ownership of the project? My main issue is that Google hosts your site and tracks all of your visitors directly, whe
by lucideer 8y ago
> is the case against all down to Google's ownership of the project?
My main issue is that Google hosts your site and tracks all of your visitors directly, whereas you never (directly) see any of those visits. This of course depends on your definition of "ownership of the project" and whether that extends to "ownership of your site and its visitors".
> these seem like issues with Google's cache and hosting, not the spec.
Based on your brief description, these don't sound like they could be issues with the cache or hosting; rather they sound like they're likely with Google's JS implementations of AMP JS libraries.
- ehsankia 8y ago> My main issue is that Google hosts your site and tracks all of your visitors directly Sounds like your problem is specifically with Google's cache. Anyone can host an AMP cache. If you afraid of them tracking visitors, you're free to pay for your own hosting and host your own cache, instead of using their free one.
- wmf 8y agoYou can't really use your own cache; all Google searches only go to the Google AMP cache ("to ensure optimal performance" or whatever).
- throwaway2048 8y agoNot if you want to appear in search results for Google.
- lucideer 8y agoSounds like you don't quite understand how the AMP cache works. Any link source can host an AMP cache—the cache is distributed with each link source choosing which cache (if any) to use. As a website owner, you have no control over which AMP cache is used, or which host tracks your visitors. For Google Search (probably the primary link source on at least the anglophone web), Google hosts your content and tracks your visitors.