by ptype on 1/13/21, 10:02 AM with 17 comments
by ignoramous on 1/13/21, 10:54 AM
In a way, the current hysteria is a lesson in the power of defaults [0]. If the default for an app/service was private and secure and later you make the "mistake" of clearly articulating that you're going to be less private... it is going to end up a PR disaster. But... if you confuse masses along the way with large privacy policies (or other such dark patterns), you may get away with it as has happened many times in the past (Windows 10 being a recent example).
That's the reason Facebook and others are opposed to Apple because Apple's stance on being private by default will hurt them: Any data hungry app / service is going to have a hard time if it needs to show notices in plain language asking permissions to harness PII [1].
In a nutshell, what we are seeing with WhatsApp is may be why Google will never default to private with Android. Whilst Google may throw the technological kitchen sink at the privacy problem; at its core, it remains a design problem: How much do you respect your user's Right to Privacy by choosing the right defaults from the get-go, how simple do you design your UX around it?
Despite Apple's own privacy issues, you can't fault them for seeing a pretty good first solution to all of this: A 3-line popup.
by ffpip on 1/13/21, 10:15 AM
by jnord on 1/13/21, 10:05 AM
by protoman3000 on 1/13/21, 11:44 AM
Excuse me if I intentionally misunderstand this, but legal uses every trick in the playbook to get what they want. So, above says that the new policy will not affect how friends and family can't read my messages to other recepients but Facebook might?
by invalidusernam3 on 1/13/21, 1:34 PM
Does anyone have any suggestions or tips on how to migrate data across to another platform? I'm sure most will not be possible, but I would like to at least migrate our images, ideally not manually.
by coffeekitkat on 1/15/21, 3:17 PM
by seebye on 1/13/21, 12:09 PM