This case illustrates some issues at hand. For one thing, it shows how software of a single engineer at Google can have quite far reaching privacy consequences. Google likes to build things that are scalable and which will have enormous impact; an erronous piece of code in such a system may have similarly big impact. Furthermore, the case shows that sometimes it needs authorities pressuring Google to actually make Google reexamine their approaches. Last not least, from what we can see, Google tries to make the case really transparent and public once it found out about their error. Looking at the blog post, I could imagine that Google upon finding out really wanted to make sure that there was no hiding of this, and this may be the important line between corrupt (intentionally bad) or merely flawed (unintentially bad) handling of data.
Google adds, “This incident highlights just how publicly accessible open, non-password-protected WiFi networks are today.”
>> More posts