EDIT: This was in response to a member who is no longer active in the forums. I’ll leave it here since it might be relevant to others. The question was “So, in reality a fabEE user will be a ‘ghost’ member because they don’t have an email address?”
Well, they are full members in whatever group you assign them to. The fact that a ‘real’ email address is not automatically associated with the account is only going to matter depending upon the nature of your application. A new fabEE member profile is basically like any other except that all the checkboxes in Personal Settings/Email Settings are unchecked by default. The email address is a placeholder but the user will have a URL, his/her Facebook public profile page.
In the simplest scenario, you might have a interactive site that requires some form of authentication in order to comment on blog entries in member-only templates. fabEE allows site users to only have to remember one set of credentials *and* control how much information is provided to the site. It may be that the user wouldn’t want to provide any email address and in any other scenario would not be able to use your site. If you have an authenticated member that you can identify then you can moderate that member, ban that member, move him/her into another more or less privileged group etc.
It’s not just the UID that is available to view in the member profile; names, profile pics, Facebook friends and some other basic info can be requested and shown. The restriction in the FBConnect Terms of Service is that this data cannot be stored locally for more than 24 hours. So, an FBConnect-enabled application needs to keep requesting that data and checking it against the cached stuff.
I agree that few will voluntarily provide more information after registration (member custom fields) but the same problems clearly exist with all members of every site ever built.
Cheers
Dry