是否可以使用应用程序隐藏故事？
Facebook Wall 更新现在为用户提供了“取消标记为热门故事”、“隐藏故事”、“报告故事或垃圾邮件”等下拉菜单。我们可以以编程方式调用这些操作吗？我想知道我们是否可以执行 POST 操作来设置 is_hidden 或与 top_story、reported 等相关的任何属性。我不想允许以编程方式取消订阅。当我们尝试发出这些命令时，我不介意 Facebook 的确认。这个想法是消除用户墙上的垃圾，而不是删除他们实际上可能想看到的任何内容。谢谢！
Facebook Wall updates now have the dropdown for users to "Unmark as a top story", "Hide story", "Report story or spam", etc. Can we invoke these operations programmatically? I'm wondering if we can execute a POST operation to set is_hidden or whatever properties are associated with being a top_story, reported, etc. I don't want to go so far as to allow for programmatic Unsubscribe. And I don't mind a confirmation from Facebook when we try to issue these commands. The idea is to eliminate junk from a user's wall, not to remove anything they actually might want to see. Thanks!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
无法通过 Graph API 报告垃圾邮件。 Facebook 的帖子 API 文档（出现在用户新闻提要上的故事）确实包含删除操作（可用于删除帖子），但它指出：
我相信 Facebook 假设用户会手动隐藏他们不想看到的帖子。由于 Facebook 有某种算法来确定显示哪些帖子，因此他们通过允许第三方应用程序自动删除用户墙上的帖子来降低其性能并没有真正意义（更不用说滥用的可能性）。
Reporting spam is not available through the Graph API. Facebook's API documentation for Posts (the stories that appear on a user's news feed) does include a Delete operation (that can be used to remove posts), but it states:
I believe that Facebook assumes that users will manually hide posts that they do not want to see. Since Facebook has some sort of algorithm to determine which posts are displayed, it does not really make sense for them to degrade its performance by allowing third-party applications to automatically remove posts from users' walls (not to mention the potential for abuse).
目前看来不可能使用 Graph API 在页面墙上“隐藏”或“取消隐藏”帖子。
我们花了一些时间检查这一点，即使查询提要为我们提供了一个字段“is_hidden”，我们也无法发布对此字段的更新...
It doesn't look like it is possible at this time to "hide" or "unhide" a post from a page's wall using Graph API.
We spent some time checking this, even though querying the feed gives us a field "is_hidden", we cannot POST an update to this field...