Facebook Rolls Out New App Authentication Flow That Ups Privacy and Transparency
1–5 of 5 posts
Re: Facebook Rolls Out New App Authentication Flow That Ups Privacy and Transparency
#2Good, but why not make all permissions truly optional?
I think app authors would be a lot more responsive if they saw stack traces from failed attempts to use a declined permission, rather than the silent number of users who never sign up because permissions are overreaching. Throw up a warning when you decline a permission that the app marks as necessary: "This app may crash if you deny this permission."
Re: Facebook Rolls Out New App Authentication Flow That Ups Privacy and Transparency
#3Sorry that I am too bitter, but at this point it is pretty clear that "Facebook" and "Privacy and Transparency" doesn't go very well together
Re: Facebook Rolls Out New App Authentication Flow That Ups Privacy and Transparency
#4Can this flow be used by non-app apps, or whatever we're calling Facebook Connect-type web sites these days?
Re: Facebook Rolls Out New App Authentication Flow That Ups Privacy and Transparency
#5Good, but why not make all permissions truly optional? I think app authors would be a lot more responsive if they saw stack traces from failed attempts to use a declined permission, rather than the silent number of users who never sign up because permissions are overreaching. Throw up a warning when you decline a permission that the app marks as necessary: "This app may crash if you deny this permission."
You could use a tool like Kissmetrics or Mixpanel to track that easily enough -- just fire one event when the permissions dialog is opened, and another if the user accepts the permissions.