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.
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).
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.
Or, they simply allowed for apps to release on their own schedule, because the OS point version wasn't ready. If they could of announced it all together they would of.
This, however, does nothing to solve update fragmentation. OS updates change the OS, and certain devices simply don't have the memory, or other hardware restrictions, to allow for newer updates. Those did not include app-stuff, the app announcements were just coupled with OS announcement.
Interesting to see articles promoting adding more surveillance cameras for all their flaws (bad angle, resolution trails behind phone cameras, etc). I would focus on acquiring publicly available photo data in real time at dense events and scan them. I.e. crowdsourced surveillance. I'm sure someone is working on that.