Prompt for real email

Virtos,
I'm not sure where you read that about the API method always asking for the 'good' email over the proxy by default. In every case we've tested (and we've done many on subscribers sites), the 'good' email comes up. Can you post a link to where you found that reference?

Not sure why Facebook would default you (or your application) to the proxy. However, they have a lot of 'behind-the-scenes' control over things like that. For instance, with Invitations, they can limit how many your app or your users can send based on history from your site (how new it is, how many invites are sent, how many invites are accepted, etc). It's possible there's a reason they're defaulting it that way.

If you would, please try logging into both this site and the demo site to see if 'we' default to the proxy. About 95% of our FB user's have their real email in our database, so I'm assuming that's not the case. It's always possible this is a recent change we aren't aware of though.

Let us know your results. It's pretty easy for us to update the Facebook button, but we'd prefer not too for multiple reasons.

Thanks!

Well huh. Yup, just tried to log in, and I see the proxy being the default. That's very strange, and I've never seen it before.

Your page (and JFBConnect in general) is using the FBML method. The API should generate the exact same URL that you're sent to when you click the FBML button... so I'm very confused why your site is defaulting to the proxy email.

We'll do some more investigation, but I really can't find any information on this from a pretty extensive search.

What I would recommend trying is to follow our guide to creating a Facebook Application. Only fill out the few fields that we specifically note must be filled out, and temporarily try that secret/api key and application information. See if proxy shows up there or real. If it's the real, try to compare your live application settings with the temporary one and let us know any differences that may be at cause. Hopefully, that will help us get to the bottom of it.

Let me know if you have any other questions or ideas, and we'll definitely keep you posted if we learn anything new.

We still don't have an explanation why your site is treated differently. We'll continue investigating, but there isn't anything we've found yet. Glad you have some solution, even if it's not optimal.

Regarding the Graph API, we already support it in many ways, but not every aspect of it. When JFBConnect retrieves profile information, it's through the Graph API and the Javascript library we load from Facebook is the newest API available (which Facebook recommends). This has been the case since the 3.0 release. With upcoming versions, we'll be adding the ability to easily make each page of your site into a "Facebook Node" through the Graph API by adding specific meta tags to your header.

Finally, for the FBML, we watch this closely, and haven't seen that Facebook will be ditching FBML. It's still the most flexible and configurable way that they recommend to implement the social widgets. However, they don't recommend using the FBML to 'new' developers, and instead recommend the iFrame methods for easier implementation. We don't prefer the iFrame method due to the drawbacks it comes with (no styling capabilities, can't resize, etc).

In general though, if Facebook kicked FBML (or any other feature we use widely) to the curb tomorrow, we'd figure out a way around it by implementing whatever they newly recommend. Facebook is always adding (and removing) features, and we've been able to keep pace so far without too many hiccups along the way.