Earlier quoted context omitted.
> No one can say for certain how, and when they delete the data. Even the person from the privacy team said as much. You and I read very different comments. Not being able to tell you, a random HN commented, the exact procedure by which a specific piece of data's lifetime is managed is different than not being able to, in the abstract, describe, monitor, and alert on the intended lifecycle of a piece of data. > I won…
> It's becoming more apparent to me that you, either intentionally or not, aren't clear on what the status quo was, or what this change changed. It's becoming more apparent that the whole conversation kinda derailed from " privacy engineering team " which engineers privacy (whatever that means at Google) does a shitty job to "we should celebrate them for doing just the minimum amount of work for something that has al…
Actually no, it was you who derailed an otherwise unrelated conversation to that topic.
> we should celebrate them for doing just the minimum amount of work for something that has already been possible, if spread across many UIs
The "minumum amount of work possible" was doing nothing. Let's isolate this: is this change a good thing, or a bad thing, in your opinion? That is, all else equal, would you prefer Google provide this specific privacy control, or not?
If not, why not? What is bad about this feature?
If yes, why are you attacking the very people implementing features that you think are good? Isn't it better to support the people doing work you support?