如何发布在谷歌加墙 [英] How to post in google plus wall

查看:146
本文介绍了如何发布在谷歌加墙的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我想分享我的应用程序在谷歌的一些信息加墙。
对于我经历了谷歌,加上API, https://developers.google.com/+/
在这个API,他们都在提如何获得特定用户的访问令牌,但他们没有提到如何在用户的墙后(使用访问令牌)。

I want to share some information in google plus wall from my application. For that I go through the Google plus API, https://developers.google.com/+/ In that API they are mentioning how to get access token of a particular user,but they not mentioned how to post in users wall(using the access token).

推荐答案

那么,Google +不具有墙,它有流。适当的期限可能会帮助你找到更好的搜索结果。无论哪种方式,除非你是一个谷歌的合作伙伴,这个消息并不好:

Well, Google+ doesn't have a "wall," it has "Streams." The proper term might help you find better search results. Either way, unless you're a Google partner, the news isn't good:

的API目前仅限于只读访问。 API网站

请注意:借助Google+ API,目前提供只读的公共访问
  数据。所有API调用要求要么是的OAuth 2.0令牌或一个的API关键

Note: The Google+ API currently provides read-only access to public data. All API calls require either an OAuth 2.0 token or an API key.

由于它是只读的,您将无法更新或通过API发布的任何地方的任何信息 - 你只能用它来拉状轮廓和活动详情基本信息

Because it's read-only, you will not be able to update or post any information anywhere through the API -- you can only use it to pull basic information like profile and activity details.

由于访问API可能会随时间而改变,我会尽量保持这个答案了解最新的关于新闻或改变有关信息的的权限。

Given that access to the API may change over time, I'll try to keep this answer up to date with information about news or changes related to write access.

2015年4月28日 Google+的API域宣布,早在2013年8月,但不知何故,我错过了它的意义至Google+。

2015-04-28: Google+ Domains API was announced way back in August 2013, but somehow I missed its relevance to Google+.

借助Google+域API允许谷歌Apps客户和ISV采取增强Google+的API的功能,来构建可在各种不同的方式被使用的工具和服务。

The Google+ Domains API allows Google Apps customers and ISVs to take advantage of enhanced Google+ APIs to build tools and services that can be used in a variety of ways.

没有,但它的不可以提供的完全的写访问用户的Google+个人资料,但它确实让您欣赏到Google+的API V1小的优势,至少在一个领域。这其中的主要针对移动应用程序开发。

No, it does not provide full write access to a user's Google+ profile, but it does give you minor advantages over the Google+ API v1, at least within a domain. This one's mainly for mobile app developers.

2015年1月21日 :我已经重新许多在这个答案链接的来源和搜索有关消息API的变化,但谷歌一直沉寂。

2015-01-21: I have revisited many of the sources linked in this answer and searched for news regarding API changes, but Google has been quiet.

2014年3月12日 :在Google+上的各种讨论主题有关的写权限(或缺乏):

2014-03-12: Various discussion threads on Google+ about write access (or lack thereof):

  • Discussion thread by Jeff Dwyer
  • In-depth discussion of the topic by Thor Mitchell (the Google+ team member mentioned in Update 6)

2013年12月3日 :从更新1中的问题线程终于得到的 c.google.com/p/google-plus-platform/issues/detail?id=41#c181\">responded~~V来。关于写访问流​​是在使用Google+ 的社区页面开发正在发生间歇性的更多讨论。

2013-12-03: The issue thread from UPDATE 1 has finally been responded to by a Google+ project member. Additional discussion regarding write-access to Streams is taking place intermittently on the Developing with Google+ community page.

2013年7月5日 :命名的开发商的埃里克·乐华已建成一个非官方的JavaScript库,提供读 /编写扩展到了Google+ API。

2013-07-05: A developer named Eric Leroy has built an "unofficial" JavaScript library that provides read/write extension to the Google+ API.


  • XHR哈克= W +(添加/后)

  • via Google+ XHR Hack = w+ (Add/Post)

2013年5月14日 :一个社交媒体管理公司,可以通过尝试成为Google+专页A​​PI合作伙伴获得更多的API访问

2013-05-14: A "social media management company" can gain additional API access by attempting to become a Google+ Pages API Partner.

  • Google+ Pages API Partner Application Form
  • More third party tools to help manage your Google+ page - An announcement from Eduardo Thuler
  • Original Google announcement of third party management tools

下面是从合作伙伴申请表的摘录:

Here's an excerpt from the Partner Application Form:

Google+专页的API允许社交媒体管理公司将Google+页面管理功能集成到他们的工具。访问这个API可以通过一个白名单,并授予权限由公司的基础依赖于适合在公司的合作伙伴与此API。

The Google+ pages API allows social media management companies to add Google+ page management features into their tool. Access to this API is available through a whitelist, and access is granted to partners on a company by company basis dependent on fit with this API.

其他文章解释缺乏一个API写的:

Other articles explaining the lack of a write API:

2013年1月4日 :谷歌刚刚宣布的 Google+的记录。你可以用它来写的时刻(这是默认为私有的),但可以再通过直接共享到您的流和/或您的个人资料被公开。其中的那一刻类型是<一个href=\"https://developers.google.com/+/history/api/moments#commentactivity\"><$c$c>CommentActivity.

2013-01-04: Google just announced Google+ History. You can use it to write "moments" (which are private by default) but can then be made public by sharing them directly to your stream and/or your profile. One of the moment types is CommentActivity.

2012-10-08 :现在有一个的复制错误后只有几个评论,但你可以为未来的更新检查那里。

2012-10-08: There's now a duplicate bug post with only a few comments, but you can check there for future updates as well.

2012-06-25 :我穿过的问题跟踪帖子于Google+写访问。扩展请求状态为新建,重点是中等为6月25日,2012年有很多的评论感兴趣的一些链接。

2012-06-25: I came across the issue tracker post for Google+ Write Access. The enhancement request status is "New" and priority is "Medium" as of June 25th, 2012. There are some links of interest in the comments.

这篇关于如何发布在谷歌加墙的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆