On the surface, user email sharing is just another extended permission that application users will be able to allow (or not) during the authorization process. For the user, this means that the process will flow similar to other application requests that they can accept or reject during authorization.

Here’s how it looks if the developer chooses to make email sharing optional:

And if the application requires your email address:

Given that Facebook wants to make full transition from application-to-user notifications to direct-to-user email communication, they plan to promote the change extensively.

As an application user, you’ll start to see dialog boxes at the top of every application canvas page you visit. You’ll see these for the next three months, or through three independent sessions with a single application.

You’ll probably get pretty familiar with dialogs that look similar to this:

/>

What it Means

/>

For developers, the big email push by Facebook is huge in terms of connecting directly with their application users, something that most have only been able to do indirectly up until now. Essentially Facebook will no longer serve as the middleman between you and your users.

For sites that leverage Facebook Connect as an alternative login, it’s also an important development that will help you store new member email addresses, or the proxied Facebook email address, for future contact.

As for Facebook application users, some of you might not relish the idea of sharing your email address, but Facebook has built-in a number of safe guards should you not only wish to reject sharing your email or do so anonymously. They’re also holding developers to the CAN-SPAM Act and requiring that they pledge not to sell your info to third-parties.

Tags: facebook, facebook application, facebook notifications, social media

Read the rest!!

Read More »