I think the fingerprinting issue is real, but also addressable. I gave a straw man proposal earlier, in good faith.
-
-
Also hoping it's addressable. Agree that everything we learned from AMP should make its way back into web features for wider availability
1 reply 0 retweets 2 likes -
Replying to @cramforce @lawnsea
We need more than hope. Is there something we can do structurally so Google management and tech leadership prioritizes it?
1 reply 0 retweets 0 likes -
We are prioritizing it. Actual work is happening https://github.com/WICG/feature-policy … https://bugs.chromium.org/p/chromium/issues/detail?id=632361 … (https://docs.google.com/document/d/16VCYGGWau483IMSxODpg5faZny1FJ6vNK2v-BuM5EhU/edit …)
1 reply 0 retweets 1 like -
Replying to @cramforce @lawnsea
Are there enough proposals to deprecate AMP in the medium term?
1 reply 0 retweets 1 like -
Ultimately the fact that Google gets to keep using AMP in the interim means you can take your sweet time on standardizing perfect solutions.
1 reply 0 retweets 0 likes -
It's analogous to a platform supporting proprietary push notifications and raising many "concerns" about supporting SW Push.
1 reply 0 retweets 0 likes -
And this is happening where? You made a similar point about ad networks in AMP. Its just FUD.https://github.com/ampproject/amphtml/tree/master/ads …
1 reply 0 retweets 0 likes -
Replying to @cramforce @lawnsea
Which thing is happening where? And what is FUD?
2 replies 0 retweets 0 likes -
Replying to @wycats @cramforce
fud is an acronym for "fear uncertainty and doubt"
1 reply 0 retweets 1 like
Thanks for the explanation @lawnsea
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
