Can we get a properly working window.onerror? Currently we either get a very generic Script Error (0 information for debugging) or have to wrap every native method in one with a try/catch. This is more for error log collection and aggregation to understand what's breaking in production.
> Schmidt: Our view of social is a little different than what everyone has been writing. we want our core products to get better from social information.
> We are trying to add a social component [to google's core products] to make them even better.
I don't know how you can compare them. G+ has had a massive support from being tied into every other product, in some cases taking features people already use and making G+ mandatory for continuing to use them. Not to mention getting tied to search such that not having a G+ presence could significantly adversely affect your SEO. Buzz certainly had its problems but it doesn't mean G+ was the right way, or that real names had anything to do with the difference.
It really depends where the crawler is finding these links. I don't think this is a mistake. It's possible that people are adding these links to their site instead of "mailto:" links and crawler is simply indexing them.
It's not the only one overall, but this one likely ranks the highest. It also is bundled with gmail because it links to gmail domain (mail.google.com).
One "restore" preference people have is account migration. Take all your email from one gmail account and import it into another.
Plus your response makes my mind boggle. People consider their gmail way too solid. There's lots of posts online of people who have lost their accounts completely.
