Google+ (AKA Google Plus, GPlus, or G+) is both a social content hosting silo operated by Google, similar in many respects to Facebook, and a centralized Google identity service for other Google services like YouTube.
Google has integrated Google+ across many of their services, e.g. even Google's search shows a toolbar for it when signed into Google+.
Google announced they're shutting down consumer version end of August 2019:
- 2018-10-08 : Project Strobe: Protecting your data, improving our third-party APIs, and sunsetting consumer Google+ (archived)
- 1 How to
- 2 Features
- 3 Brainstorming
- 4 Issues
- 5 See Also
How to export your data
Google Takeout lets you download a zip with all of your Google+ posts, comments, pictures, etc. It's not linked directly from anywhere within Google+, and doesn't come up as a first search result for common queries, but works fantastically (if a bit slow).
How to POSSE to
There's currently no good way to automatically POSSE to Google+. Here are the (bad) options:
- Use the Moments API. As far as we know, though, it doesn't actually surface to users yet.
- Apply for the partner-only Pages API. (Requires signing an NDA.) Known Pro uses this.
- Make a business relationship with Google so you can use a private/partner API, like WordPress's Jetpack Publicize. More details. Here's an example: original post, Google+ post.
- Screen-scrape and use the web endpoints as if you were a normal user. NextScripts SNAP does this.
Why POSSE to
There is some evidence that Google+ "+1"s on links affect their search ranking:
- The Moz Blog / : Amazing Correlation Between Google +1s and Higher Search Rankings (http://moz.com/blog/google-plus-correlations)
POSSEing links of your posts to Google+ may help increase +1s on them and thus increase their search ranking.
IndieWeb POSSE Examples
to manually create links to his blog posts on Google+ where he then accepts comments (instead of comments on his own blog).
This isn't a full POSSE implementation (which would be cross-posting the entirety of the contents of your blog posts to G+ posts), but rather just a way to manually share links/summaries of your original posts onto G+, similar to POSSEing articles to Twitter.
Manually POSSEs posts and replies to Google+
- Original post POSSE example (from 2014-05-26) : https://kartikprabhu.com/notes/technologies-ideas-action POSSE copy: https://plus.google.com/+KartikPrabhu/posts/GYxvUCwXC4y
- POSSE of a reply: https://kartikprabhu.com/notes/birth-of-idea-phone POSSE copy: https://plus.google.com/+LeoStein/posts/fBQeHxP8h2R#z135gpcygo2qebcj404chhhyzof0ubprel40k#1417402122646866
Google+ does not have URL permalinks for replies but does have an
id attribute in the
Google+ has a proprietary read API.
Google+ allows you to put a "+1" button on any page that when clicked, does a "+1" (similar to a like) of your page, inside Google+, on the Google+ profile of whoever clicked the button.
Google+ has a proprietary Activities API that is based on (but not actually) ActivityStreams:
How to delete your account
Has anyone deleted their G+ account? What's the process? How long do they hold your data anyway? Etc.
See also: delete your account
Anecdotally there seems to be more interaction on G+ event posts than simple text posts.
If we can figure out a way to automatically create event posts on G+, it might be worth POSSEing indieweb event posts to G+.
It's not obvious how to best publish/POSSE to or comment on G+ in a way that is most easily searchable / findable. Here are some tips:
- only post public posts to G+
Comments on Google+ lack their own permalinks, making it very difficult to reference a part of a conversation on a Google+ post.
It's apparently a "Known feature request that's never made it to the head of the priority queue." according to:
Similarly when asked at the 2013 Google I/O conference, Google+ representatives relayed the same message that it's a known feature request and there are still no plans for it.
Occasional IndieAuth login problems
Ben Roberts had used Google+ for login via IndieAuth primarily until there were intermittent failings due to errors in redirects. For example https://plus.google.com/113259788317081930920/posts redirects to https://plus.google.com/+BenRoberts83/posts but Google will occasionally change/break this routing.