Hacker News new | past | comments | ask | show | jobs | submit login

That's fair, though if you do read said spec sheet, there's a few things you can infer. For one, they give a list of whitelisted AMP component, and none of them allow for arbitrary JS, so that's out.

Furthermore, at the bottom, they specify: > All fetchable attributes like src and href must be static and > All network requests must be proxy-able to ensure that user anonymity is preserved

This implies that anonymity is big focus (so your information will not be leaked), and that things will be fairly static.

Almost all the "speculation" happening goes contrary to that, leading me to believe that no one has actually taken the time to read up, and are just blindly expressing their existing preconceptions and hatred about AMP.




Let's just bet that majority of AMP emails will have a tracker in a form of a personally identifiable resource - image, component, whatever.


Emails have that now, though, with tracking pixels and the like. Google prefetches them all; marketers have no idea if you actually looked at it.


GDPR couldn't be coming any sooner.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: