email_hashes和已弃用的connect.registerUsers [英] email_hashes and deprecated connect.registerUsers

问题描述

Facebook Connect和Facebook应用用户在我们的网站上不重复是非常重要的。所以如果他们已经在我们的网站上有一个帐户，当他们通过FB Connect或者我们的Facebook应用程序连接时，我们想链接而不是创建另一个帐户。我们通常通过匹配电子邮件地址来实现。

It is very important that Facebook Connect and Facebook app users aren't duplicated in our website. So if they already have an account on our website, when they connect through FB Connect or our Facebook app, we want to link rather than create another account. We typically do so by matching email addresses.

所以我很高兴看到一个FQL字段为 email_hashes 用户对象。但是，这并没有返回任何东西。我想我需要使用 connect.registerUsers REST api函数首先向我的用户发送所有的电子邮件散列。没问题，但是这个机制现在已经被淘汰了。

So I was excited to see an FQL field for email_hashes in the user object. However, that doesn't return anything. I think I need to use the connect.registerUsers REST api function to first send facebook all the email hashes for my users. That's fine, but that mechanism is now deprecated.

有没有办法从Facebook用户那里获取电子邮件散列？

Is there a way to get email hashes from Facebook users?

推荐答案

唯一的方法是你详细的，并且记录在 connect.registerUsers 。如果您首先打电话给connect.registerUsers并且有电子邮件匹配，则会填充email_hashes。我不会太担心它被弃用，因为我猜测他们不会删除这个功能，而不用先迁移它的图形API，就像他们在文档页面上所做的那样。

The only way still is as you detailed and as is documented on connect.registerUsers. email_hashes will be populated if you first call connect.registerUsers and there is a email match. I wouldn't be too concerned about it being deprecated as I am guessing they won't remove this functionality without first migrating it the the graph api as they say they will do on the documentation page.

这篇关于email_hashes和已弃用的connect.registerUsers的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！