3 ms·

>we proactively rolled out an opt-in for this on our Android client a few weeks ago and are rolling out the opt-in for this in 2.0.6 of our iOS Client, pending

>we proactively rolled out an opt-in for this on our Android client a few weeks ago and are rolling out the opt-in for this in 2.0.6 of our iOS Client, pending App Store approval. "Proactively?" How do you get into the Social Networking business and not see this issue coming before the first line of code is written? [re: hashing] >This is a good alternative solution which we'll look into. Thanks for the idea. Again, no. That no competent system design talent/time was dedicated to this process is a damning critique of your organization's ability to be trusted to safeguard user data.

rhizome 15y ago
I think the simplest explanation is that he's playing dumb.
- rmc 15y ago
  He almost certainly is either playing dumb or is dumb. If you're not dumb, you have to play dumb, because otherwise you'll be crucified.
  - eob 15y ago
    Playing dumb. Hashing the information is such an obvious choice, there's really no plausible explanation for the developers to have not to consider it. They probably just figured "everyone else is doing this so what's the harm?"
    - rhizome 15y ago
      It's been a long time since Plaxo.
joering2 15y ago
> "Proactively?" How do you get [...] was about to say exact the same. the only thing I can add here is that if this wouldnt make headline, noone would have thought of opt outs.
smacktoward 15y ago
> How do you get into the Social Networking business and not see this issue coming before the first line of code is written? "It is difficult to get a man to understand something, when his salary depends upon his not understanding it." -- Upton Sinclair (http://en.wikiquote.org/wiki/Upton_Sinclair http://en.wikiquote.org/wiki/Upton_Sinclair)