Explained how it works here https://blog.amp.dev/2018/07/23/privacy-and-user-choice-in-amps-software-architecture/ … We're working on making it work for non-AMP content, toohttps://blog.amp.dev/2019/05/22/privacy-preserving-instant-loading-for-all-web-content/ …
-
-
Lots of folks are happy to retreat into privilege and desktop. OK. But that doesn't make it less of a crisis if we want the web to be meaningful in the lives of most users.
-
Some people are happy to give up. That's fine too. But they shouldn't be policing accurate language or misrepresenting the work we've done in the open and through standards to improve things.
- 6 more replies
New conversation -
-
-
Who is the ‘we’ you’re referring to? If you mean Google, I’d probably agree. If you mean users - that’s a big nope from me. Content is still king - how you get it is up to the content provider. Mechanism shouldn’t matter. Web and native can co-exist. This isn’t a one or the other
-
"we" here is "the web"
End of conversation
New conversation -
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.