对“电子邮件哈希”的提议/不同看法联系问题 [英] A proposal/different take on the "Email Hashes" contacts issue

问题描述

你好，

我第一次尝试使用Windows Live Connect API，它实际上比我想象的要容易....似乎每个人都被卡住的地方（即"电子邮件哈希"问题和MS政策，其中电子邮件地址不会被给予
）。

I've tried using the Windows Live Connect API for the first time, and it's actually easier than I thought it would be....to the point where it seems everyone gets stuck (i.e. the "email hashes" issue and the MS policy where email addresses won't be given out).

现在，我尽管谷歌和雅虎实施了联系人列表检索，但我不会抱怨这个问题。  我实际上理解并且可以接受与保护电子邮件地址相关联的论点以及可能使用访问令牌发送的无限电子邮件以及更改"默认"电子邮件。联系人供稿网址中的电子邮件。  我不同意，但我至少可以接受它。

Now, I'm not going to complain about the issue, despite Google's and Yahoo's implementation of contact list retrieval.  I actually understand and can accept the argument associated with protecting email addresses and the endless emails that could potentially be sent using the access token and the changing of the "default" email in the contact feed URL.  I don't agree with it, but I can at least accept it.

然而，我想知道的是，如果有替代方案或是否会有一个类似于Twitter的OAuth协议的实现和联系人列表的检索。  具体来说，Twitter允许通过其开发者API为经过身份验证的用户发送直接
消息：

What I am wondering, however, is if there is an alternative or if there is ever going to be one similar to Twitter's implementation of the OAuth protocol and retrieval of contact lists.  Specifically, what Twitter allows for is the sending of a direct message for authenticated users via its developer API:

https://dev.twitter.com/docs/api/1/post/direct_messages/new

允许站点发送一个以管道分隔的ID列表到Live oAuth服务器以及至少纯文本格式的消息（理想情况下，支持HTML电子邮件但我认为我们大多数人都会选择纯文本格式现在）将确保
电子邮件隐藏在视图中，同时仍然允许我们大多数人正在寻找我们最终想要的电子邮件地址（即向某人发送电子邮件）。  您还可以通过某种方式跟踪哪些用户发送了哪些邮件，从而
跟踪任何潜在滥用者，但我怀疑oAuth应用程序的百分比很高。

Allowing a site to send say a pipe-delimited list of IDs to a Live oAuth server along with a message in at least plain text format (ideally, HTML emails would be supported but I think most of us would settle for plain text for now) would ensure that the emails are hidden from view while still allowing most of us who are looking for the email addresses that which we ultimately want (i.e. to send an email to someone).  You'd also have a means of being able to track which users send which messages and thus track any potential abusers, although I doubt there would be a high percentage with an oAuth application.

如果适当的范围（称之为wl），在帖子正文中发布http://outh.live.com/send-message/（任意URL）的帖子请求会有效。 send_email）被最终用户接受：

A post request to say http://oauth.live.com/send-message/ (arbitrary URL) with something like this in the body of the post would work, provided the appropriate scope (call it wl.send_email) was accepted by the end user:

access_token = ACCESS_TOKEN& ids = 123 | 456 | 789& message =你好，％20how％20％是你％？

access_token=ACCESS_TOKEN&ids=123|456|789&message=Hello,%20how%20%are%you?

是否有可能实现这样的事情？  可能不符合我列出的规格，但可以实现通用目的。

Is it possible that something like this can be implemented?  Maybe not with the specs I laid out, but something that accomplishes the general purpose.

推荐答案

谢谢建议。我们实际上
在之前的版本中实现了类似的功能 并且同时给出了由于某些限制以及实际保护这些API免遭滥用的成本而导致采用率不足，我们没有继续使用此功能。 

Thanks for the suggestion. We actually implemented similar functionality in a previous release  and given both the lack of adoption due to certain limitations and the costs of actually protecting these APIs from abuse, we did not move forward with this functionality. 

这篇关于对“电子邮件哈希”的提议/不同看法联系问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！