I understand that (great power, etc) but I also think the banner and AMP decisions aren't really "small"
-
-
Replying to @wycats
AMP w/ http://google.com URLs is fixed now, right? Isn't it now http://cdn.ampproject.org ? That's an example of mistake, ack, fix.
1 reply 0 retweets 0 likes -
Replying to @mbleigh
Only after outrage from people outside the usual source (the verge!) and a narrow fix that addresses the most egregious issue
1 reply 0 retweets 0 likes -
-
Replying to @wycats
Erg, that's a bummer.
@pbakaus do you know what's up with AMP still being on http://google.com ?2 replies 0 retweets 0 likes -
.. Better idea that works and fulfills the needs (privacy, performance, origin model).
2 replies 0 retweets 1 like -
Performance constraint: "must load fast when coming from http://google.com search result page" is really not about the web.
1 reply 0 retweets 1 like -
I'm frustrated at the mental gymnastics you guys are doing to convince yourself and others that this has anything to do with the web.
2 replies 1 retweet 4 likes -
I'm frustrated about the constant destructive criticism. I believe we're helping the web. I invite you to work with us and do better.
2 replies 0 retweets 0 likes -
I don't feel it has been either constant nor destructive. And I'm hardly the only one. At least I'm being concrete.
2 replies 0 retweets 1 like
As a non-google employee, I have no interest in working for free on AMP, just as I won't work on Facebook Instant.
-
-
This is just reality, not destructive. I'm interested in helping find better solutions, but not improving today's AMP.
1 reply 0 retweets 0 likes -
That's OK. If we can work out a much better solution than AMP, I'm cool with it.
0 replies 0 retweets 0 likes
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.