On the one hand Google has optics into problems and means to try to solve. On other is too big to move fast without collateral damage.
-
-
Replying to @mbleigh
Great powers treat collateral damage as something to minimize as close to 0 as possible. Even FB abandoned "break things"
1 reply 0 retweets 0 likes -
Replying to @wycats
I believe Google does try to minimize damage, and has a culture of calling bullshit (internally) on user-hostile decisions.
2 replies 0 retweets 0 likes -
The problem is that Google is *so* big that small mistakes can be amplified into enormous problems.
1 reply 0 retweets 0 likes -
Replying to @mbleigh
I understand that (great power, etc) but I also think the banner and AMP decisions aren't really "small"
2 replies 0 retweets 0 likes -
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
You should reconsider whether those constraints are acceptable if they lead to this solution.
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.