Had to download #WhatsApp the other day and I'm amazed at how it effectively *requires* access to your contacts.
If you try to even send a message, it immediately asks for access to your contacts, and if you say "no" it just stops and you can't send a message. I'm not getting tricked into giving my social graph to #Meta again.
What's crazier is that a friend downloaded it at the same time but *could* send a message without giving access to contacts. Apparently their #iPhone app support this while the #Android app does not.
So my friend could initiate a conversation with me, and I can view and respond. But I can't initiate a conversation with them. (I wonder if this was a requirement of Apple's review?)
Seriously, fuck off with these privacy-invasive designs. There is no valid reason for this.
@develwithoutacause So true! And I'm out of it but I suspect a future job will basically force me to use this again... and I don't know how to have some kind of "shit container"...
@gaufff I wonder if you could have a throw away account on your phone and only share its (empty) contacts? I've never tried something like that, but it might be feasible?
@develwithoutacause Well, could be, but the inconvenience though...
I don't know much about it, but I've heard of OS with "containers" or "profiles", maybe that can allow to get that kind of connectivity without impacting our own real data?
@gaufff Work profile basically does this and isn't *too* inconvenient, but not perfect for sure.
That's very coupled to a single profile though and doesn't really scale well for "Run this one app under this one profile but leave everything else alone."
@develwithoutacause The most frustrating part is that designs like this are framed to the user as if it's good for them.