2 ms·
Imagine you knew every on-the-clock interaction you had with a colleague was being stored away someplace that an unspecified number of people had access to as "
by ghaff 3y ago
Imagine you knew every on-the-clock interaction you had with a colleague was being stored away someplace that an unspecified number of people had access to as "needed." I'm pretty sure most developers here would object pretty strongly to such an arrangement (and would probably get onto ways to circumvent it).
- Dah00n 3y ago>Imagine you knew every on-the-clock interaction you had with a colleague was being stored away someplace Storing something for two hours is still storing it. The point was why is it bad if it is listen to for X minutes in a month, but okay if it is listen to for X minutes today? I can see no reason at all why two hours is okay if five isn't. I could understand if the argument was that nothing should be stored at all.
- mulmen 3y agoThe issue is the difference between 2 hours on board the airplane and forever with corporate access. > The point was why is it bad if it is listen to for X minutes in a month, but okay if it is listen to for X minutes today? That wasn't the point and the problem is who is listening, why, and what they may do with the information.