The new auth dialog resolves a number of the fundamental problems described in this article, namely the second step where the user can individually reject exten

The new auth dialog resolves a number of the fundamental problems described in this article, namely the second step where the user can individually reject extended permissions: http://developers.facebook.com/blog/post/578/ http://developers.facebook.com/blog/post/578/ http://developers.facebook.com/docs/opengraph/authentication/ http://developers.facebook.com/docs/opengraph/authentication... I think the post is a bit anachronistic. The dialog box has changed probably ten times since Connect launched, and there was a period where it was a slew of checkboxes to enable/disable ("always been bewildered by the way Facebook implemented Facebook Connect"). In addition, the feature of an off-site app to publish to your stream without asking you has come and gone (remember Beacon?), and has only recently come back with the advent of Timeline and publish_stream permissions. (which, IMHO is just like Beacon, only this time "we're ready for it.") The article does seem to suggest that it has been a longstanding problem however, and that's simply not true - the abilities of what a Facebook-connected app can do, and the UX around it, have changed many times.