Thanks! It's a delicate balance of fixing the bug, cleaning up the leak, notifying users, and providing accurate guidance.
-
-
Replying to @benhawkes @alexstamos
The notification schedule was coordinated with CloudFlare, there were no surpises about timing of the release.
4 replies 1 retweet 10 likes -
Replying to @benhawkes @alexstamos
We put a huge multi-team effort in to the cleanup at Google in incredibly high pressure and uncertain circumstances.
1 reply 0 retweets 11 likes -
Replying to @benhawkes @alexstamos
Done incorrectly, this cleanup could have seriously damaged legitimate search results. This almost happened.
2 replies 0 retweets 7 likes -
Replying to @benhawkes @alexstamos
It appears some are saying that we should have delayed in favor of a longer cleanup period. On balance, we disagree.
1 reply 0 retweets 11 likes -
Replying to @benhawkes @alexstamos
We were conscious of the fact that many other crawlers are involved too, and that the status of exploitation is unknown.
1 reply 0 retweets 9 likes
To that end, user notification is prioritized - lets get everyone in the affected community working on this together.
-
-
Replying to @benhawkes @alexstamos
We're not perfect, but we're definitely trying hard to do the right thing for users. Always open to new perspectives on this.
2 replies 2 retweets 13 likes -
This Tweet is unavailable.
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.