Therac-25 huh? That shit is wild. I can't believe industry would be so irresponsible.
Anyway time to ask my Markov Waifu to make a list of probable military installations to bomb.
@carnage4life Two obvious consequences leap to mind:
1) Reputational risk damage is even easier with faster footguns. (Ask Grammarly about whether another meeting might have been a good idea.)(Though they might have been too all-in on their plans, so it might be a bad example.)
2) Users are about get even more cranky about ongoing churn in features and interfaces. Features appear and then disappear rapidly. Odds of landing in an ephemeral A/B test go up now.
Therac-25 huh? That shit is wild. I can't believe industry would be so irresponsible.
Anyway time to ask my Markov Waifu to make a list of probable military installations to bomb.
@lauren I certainly don't blame the users. But I also don't see what I'd ask Google to do in this particular case. (The behavior strikes me as very similar to many disk systems that leave "deleted" material around. That's a problem that most users just don't understand and I don't expect them to.)
I do expect Google to minimize damage and avoid handing things over lightly. So while this case seems reasonable, I definitely disagree with their responding to administrative warrants recently.
2/2
@lauren
There's a larger issue in that we have complex systems that will react in unpredictable ways that can hurt the broader population. I still don't know how to prepare that larger population of users for things I take for granted as a geek -- besides publicizing explanations like these.
1/2
@lauren Sure -- all fair. I doubt that most folks understand that link exists at all. (I only know because there was a large-scale project that forced me to learn it.)
I agree that the details I understood about video storage all seemed reasonable for exactly the reasons you mention. (TBH, pipelines like the one my team managed didn't have this kind of lag, typically. The long-term storage system had these issues and I didn't work directly on that bit.)
@lauren
Oh, I remember you being there-- which is why I started following you here. Sorry -- that wasn't intended as some kind of "gotcha" comment.
I just wasn't surprised that deletion on a user's behalf would be treated like explicit deletion. I don't know the storage mechanism for Nest video but I would expect it to work like other parts of Google. (It's find if folks disagree. That just didn't surprise me given my experience in video processing.)
@lauren Turns out this is documented: https://policies.google.com/technologies/retention?hl=en-US
"When you delete data in your Google account, we immediately start the process of removing it from the product and our systems.
...
Complete deletion of data from our servers is equally important for users’ peace of mind. This process generally takes around 2 months from the time of deletion."
This aligns with my memories of details I saw while working at YouTube.