List of +1d urls is not available in the API

[GoogleCodeExporter]

The url https://plus.google.com/me/plusones does not have a corresponding API.

I need to get a list of all the links a user has +1d. This would be highly 
helpful as many people use +1 as a bookmark/curating tool. 

This was asked in the Google Group :
https://groups.google.com/forum/#!topic/google-plus-developers/mLlacp_nbps and 
on StackOverflow as well: 
http://stackoverflow.com/questions/6310574/is-it-possible-to-access-a-users-goog
le-1-plus-one-history-via-an-api

Original issue reported on code.google.com by capt.n3m0 on 15 Oct 2011 at 6:02

[GoogleCodeExporter]

Original comment by chirags@google.com on 18 Oct 2011 at 9:46

• Added labels: Component-API, Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Yes, an API is needed for this, but I would also like to simply request that 
Google provide an RSS feed for a user's +1's. Since they are public, this would 
be the easiest way to expose them to the internet in a common format for 
consumption.

Original comment by timrnich...@gmail.com on 7 Nov 2011 at 6:47

[GoogleCodeExporter]

I completely agree, especially for those of us who aren't on Google+ and are 
using +1s to replace the Google Reader sharing functionality. Google have 
always been so open about data, its really disappointing to see this change in 
attitude.

Original comment by michael....@gmail.com on 7 Nov 2011 at 7:00

[GoogleCodeExporter]

+1 from me. This functionality is something which is missing from the current 
API. Especially after the social features of google reader have been removed 
from the frontend application.

Original comment by MightyC...@gmail.com on 20 Nov 2011 at 5:05

[GoogleCodeExporter]

This is a pretty basic feature that I was expecting to have. Please get this 
sorted out asap. Thanks.

Original comment by ssechaud...@googlemail.com on 30 Nov 2011 at 12:30

[GoogleCodeExporter]

Seriously Google+ team, this should be peanuts for you to implement. I used to 
publish my Reader shares on my website, but with the recent migration this is 
not possible anymore unless I scrape my own profile.
Privacy is no issue here because the +1's are public anyway, so just do it!
Thanks.

Original comment by dmonsi...@gmail.com on 30 Nov 2011 at 12:48

[GoogleCodeExporter]

Dear Google. I've always believed in you. Not believing you're evil. But taking 
away our freedom to share our content in the way WE want is a hard blow and i 
REALLY start to wonder where Google is going...

Original comment by raoul.te...@gmail.com on 3 Dec 2011 at 9:37

[GoogleCodeExporter]

This is now open and untouched since 4 months. Can we expect any response or 
workaround/fix? How does google see this req.?

Original comment by MightyC...@gmail.com on 14 Jan 2012 at 8:25

[GoogleCodeExporter]

My use case is perhaps a more complex variant of this, as I'd want a report of 
external +1's which have been made on my own website. Since it's possible to 
let embed +1s for external domains too.

Original comment by mahemoff on 1 Feb 2012 at 9:42

[GoogleCodeExporter]

Dear Google, FYI, I'm moving to another service. Since Eric Schmidt has become 
CEO, it seems like the whole idea of being "open" and focussing on the user is 
no longer a priority. This feature has been in the top list of issues for 
several months now. If we don't even get a reply by any Google employee, it 
looks like you want to keep control of the +1's. This is exactly why I left 
Facebook and other sites, and I was naïve enough to bevlieve Google was 
different.

Sayonara!

Original comment by dmonsi...@gmail.com on 18 Feb 2012 at 2:54

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Thanks but this is not what we are looking for. There are quite a few services 
which parse your public updates to RSS. But what we want is: Our +1 as RSS feed 
- this is something different.

Original comment by dreamfla...@dreamflasher.de on 23 Feb 2012 at 2:36

[GoogleCodeExporter]

yes, this is definitely needed, just like the Reader used to have RSS for 
stared items. 

Original comment by xief...@gmail.com on 24 Mar 2012 at 3:43

[GoogleCodeExporter]

It looks like this link may be a solution:

https://plus.google.com/_/plusone/get?oid=<google-plus-id>

But I cannot understand in which language does it give output. Any ideas? 

Here is the example:

)]}'

[["p1c.gpo",[[["1/h1ubcw3nbcrmyw3giptmwtvjhxnqstdighrquftla0wnkhdoa4unci1taov3kg
dlact3chtq/",1,,,"The Ultimate Stock Research Site, Empowering Investors Since 
1995",,1.340057147308808E12,["https://plus.google.com/109854154895681122476","In
vestors Guru Small Cap Stock 
Observer",,"plus.google.com","//images-pos-opensocial.googleusercontent.com/gadg
ets/proxy?url\u003dhttps://plus.google.com/favicon.ico\u0026container\u003dpos\u
0026gadget\u003dhttps://plus.google.com/favicon.ico\u0026rewriteMime\u003dimage/
*\u0026resize_h\u003d16\u0026resize_w\u003d16\u0026fallback_url\u003d//ssl.gstat
ic.com/s2/oz/images/console/url_favicon.png"]
,,,,,[]
,1,"//images-pos-opensocial.googleusercontent.com/gadgets/proxy?url\u003d//lh5.g
oogleusercontent.com/-iGbXtTqkxi8/AAAAAAAAAAI/AAAAAAAAAHc/lLxAeVkzmMk/photo.jpg\
u0026container\u003dpos\u0026gadget\u003d//lh5.googleusercontent.com/-iGbXtTqkxi
8/AAAAAAAAAAI/AAAAAAAAAHc/lLxAeVkzmMk/photo.jpg\u0026rewriteMime\u003dimage/*\u0
026resize_w\u003d45\u0026no_expand\u003d1\u0026fallback_url\u003d//ssl.gstatic.c
om/s2/oz/images/console/default_url.png","//lh5.googleusercontent.com/-iGbXtTqkx
i8/AAAAAAAAAAI/AAAAAAAAAHc/lLxAeVkzmMk/photo.jpg",0,[]
,0,0,,""]
,["1/h1ubcw3nbcrmyw3giptmwtvjhxnqstdighrquftla4v3aidkb4unahloaks3iglmaosn2hts/",
1,,,"The only 24/7 TV channel dedicated to fashion, beauty, glamour and 
style.",,1.34005711585167E12,["https://plus.google.com/116390953644072251178","F
ashionTV",,"plus.google.com","//images-pos-opensocial.googleusercontent.com/gadg
ets/proxy?url\u003dhttps://plus.google.com/favicon.ico\u0026container\u003dpos\u
0026gadget\u003dhttps://plus.google.com/favicon.ico\u0026rewriteMime\u003dimage/
*\u0026resize_h\u003d16\u0026resize_w\u003d16\u0026fallback_url\u003d//ssl.gstat
ic.com/s2/oz/images/console/url_favicon.png"]
,,,,,[]
,1,"//images-pos-opensocial.googleusercontent.com/gadgets/proxy?url\u003d//lh6.g
oogleusercontent.com/-T43bCRf4xtM/AAAAAAAAAAI/AAAAAAAAIQk/E9czp0RmgA4/photo.jpg\
u0026container\u003dpos\u0026gadget\u003d//lh6.googleusercontent.com/-T43bCRf4xt
M/AAAAAAAAAAI/AAAAAAAAIQk/E9czp0RmgA4/photo.jpg\u0026rewriteMime\u003dimage/*\u0
026resize_w\u003d45\u0026no_expand\u003d1\u0026fallback_url\u003d//ssl.gstatic.c
om/s2/oz/images/console/default_url.png","//lh6.googleusercontent.com/-T43bCRf4x
tM/AAAAAAAAAAI/AAAAAAAAIQk/E9czp0RmgA4/photo.jpg",0,[]
,0,0,,""]
,["1/h1ubcw3nbcrmyw3giptmwtvjhxnqstdighrquftla0w3ehtma0s30i1qacsnihltb0t3ahdq/",
1,,,"Издательский дом \"Коммерсантъ\" — 
первое частное независимое журналистское 
предприятие новой 
России",,1.339812998020665E12,["https://plus.google.com/108572000862176982
356","Коммерсантъ",,"plus.google.com","//images-pos-opensocial.google
usercontent.com/gadgets/proxy?url\u003dhttps://plus.google.com/favicon.ico\u0026
container\u003dpos\u0026gadget\u003dhttps://plus.google.com/favicon.ico\u0026rew
riteMime\u003dimage/*\u0026resize_h\u003d16\u0026resize_w\u003d16\u0026fallback_
url\u003d//ssl.gstatic.com/s2/oz/images/console/url_favicon.png"]
,,,,,[]
,1,"//images-pos-opensocial.googleusercontent.com/gadgets/proxy?url\u003d//lh4.g
oogleusercontent.com/--FYZkbXOOUQ/AAAAAAAAAAI/AAAAAAAAABM/vnjty-u1ig0/photo.jpg\
u0026container\u003dpos\u0026gadget\u003d//lh4.googleusercontent.com/--FYZkbXOOU
Q/AAAAAAAAAAI/AAAAAAAAABM/vnjty-u1ig0/photo.jpg\u0026rewriteMime\u003dimage/*\u0
026resize_w\u003d45\u0026no_expand\u003d1\u0026fallback_url\u003d//ssl.gstatic.c
om/s2/oz/images/console/default_url.png","//lh4.googleusercontent.com/--FYZkbXOO
UQ/AAAAAAAAAAI/AAAAAAAAABM/vnjty-u1ig0/photo.jpg",0,[]
,0,0,,""]
]
]
]
]

Original comment by bluesky....@gmail.com on 24 Jun 2012 at 10:06

[GoogleCodeExporter]

No.

Those are the EXTERNAL links which have been plusoned, not internet G+
posts.

That list is what is currently available on the profile page tab.

Original comment by kos...@gmail.com on 24 Jun 2012 at 10:13

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

And even if this would contain the right stuff, something like this (the file 
is some array, prefixed with some closing characters... ) is no good for 
developing with. It would be too 'ramshackle'. I'm afraid Google changed 
strategies, more closed... so I gave up. My 'solution': open a Tumblr account 
(guess Blogger will be closed someday too, as it has too much overlapping 
functionality with Google+) and since I was already using a different front end 
(Feedly) it still is an integrated experience from a 'publishing'/'curator' 
point of view (Google Reader users may like something like: 
http://userscripts.org/scripts/show/18605). The morale of this all: Stop +1'ing 
when you want to reuse your data: you're locking your data into something you 
can't access.

Original comment by ramshack...@gmail.com on 24 Jun 2012 at 11:07

[GoogleCodeExporter]

The format used here is the format with Google have decided to use for the 
clinet rendering of data for all Google Plus pages. 

Go to your stream and view the source. You will see a similar "JSON-like' 
structure. 

Total overkill, if you ask me.  This data format really has nothing to do with 
the API, it all about getting the client browser to do as much of the work as 
possible when presenting the pages. 

Similar to the new "dynamic" Blogger pages. View the source on those pages and 
you'll see little to no HTML at all. It's all rendered via Javascript, making 
those urls utterly usless when it comes to parsing or scraping them.

I used to think Google had some of the smartest people in the world working for 
them. Those days have changed quite considerably. 

All they currently care about is making a succes of "social" in any way they 
can, since Larry offered the bonuses for success in social.

Trouble is, is that they might hire lots of PhDs, who can solve difficult 
problems, but I don't think they have hired enough people who have actually 
used social products online for years and years, like many of us. 

I'm talking 'real' humans. Not propellor heads.  :) 

/rant

Original comment by kos...@gmail.com on 24 Jun 2012 at 11:15

[GoogleCodeExporter]

^ excuse the typos.  Can't edit. 

Original comment by kos...@gmail.com on 24 Jun 2012 at 11:16

[GoogleCodeExporter]

Quite obviously, as comment 9 already says, the API should have a parameter to 
restrict the search to a certain site or domain.
My use case: display on my blog the Android apps to which I gave +1.

Original comment by regis.de...@gmail.com on 4 Jul 2012 at 9:28

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Just found out that Google Takeout offers +1 urls to be downloaded as a 
bookmarks.html file. You can try it out at 
https://www.google.com/takeout/?pli=1#custom:plus_one .

Too bad that the ADD_DATE attribute is blank for all urls. It would have been 
great, esp since the added date is available to everyone via the hidden API 
requests mentioned in comment 14

Original comment by capt.n3m0 on 29 Aug 2012 at 2:00

[GoogleCodeExporter]

@capt.n3m0 thanks for the report — working on it!

Original comment by mess...@google.com on 11 Sep 2012 at 11:25

[GoogleCodeExporter]

@capt.n3mo — can you give your export another try?

Original comment by mess...@google.com on 9 Oct 2012 at 9:17

[GoogleCodeExporter]

Thanks, it works.

Original comment by capt.n3m0 on 10 Oct 2012 at 12:43

[GoogleCodeExporter]

I wrote a parser for the data from 
https://plus.google.com/_/plusone/get?oid=<google-plus-id>, its not pretty but 
it works. 

http://joshuac.net/plusone.php?oid=<google-plus-id>

Original comment by jos...@xybrcode.com on 11 Oct 2012 at 12:55

[GoogleCodeExporter]

@Joshua - Could you perhaps supply the code for that on GitHub or something 
similar? It would be hugely useful as I would like to create an RSS feed of my 
+1s - no other service has worked for me yet, but the data from Google combined 
with your parser is spot on.

Original comment by hlashbro...@gmail.com on 11 Oct 2012 at 1:04

[GoogleCodeExporter]

here ya go, I warn you its very messy

https://github.com/cowboycodur/php-plusone-parser

Original comment by jos...@xybrcode.com on 11 Oct 2012 at 1:29

[GoogleCodeExporter]

Thanks! I see what you mean about it being messy - it seems to do the job well 
though, so let's hope Google doesn't change anything.

Original comment by hlashbro...@gmail.com on 11 Oct 2012 at 1:31

[GoogleCodeExporter]

Original comment by t...@google.com on 7 Dec 2012 at 4:33

[GoogleCodeExporter]

@capt.n3mo, that is also the list of public, external pages that you've clicked 
"+1" on... not the list of G+ posts and comments that you've "+1ed".  See 
comment #15 as well.  

Looks like the answer right now is you can't get that.

Original comment by jan.l.pe...@gmail.com on 1 Feb 2013 at 9:37

[GoogleCodeExporter]

Sorry, I take back my comment.  Looks like issue 89 
(http://code.google.com/p/google-plus-platform/issues/detail?id=89&colspec=ID%20
Type%20Status%20Component%20Owner%20Summary%20Stars) is the one I want.

Original comment by jan.l.pe...@gmail.com on 1 Feb 2013 at 9:43

[GoogleCodeExporter]

I found a workaround using an HTML to RSS service to parse the user's public +1 
page and format it into RSS feed, works great for what I need it for so far. hth

http://blog.electronsmith.com/?p=423

Original comment by haroo...@gmail.com on 1 Feb 2013 at 9:48

[GoogleCodeExporter]

@haroo That's why I made this a while back =) 
http://sourceforge.net/projects/plusonescraper/ (same exact idea, though yours 
may be easier to maintain)

Original comment by michael....@med.einstein.yu.edu on 1 Feb 2013 at 10:27

[GoogleCodeExporter]

I tried to use @Joshua 's parser/scrapper but it didn't work for some reason. 
So I made my own, even messier one.

https://gist.github.com/Naurgul/5605089

Original comment by naurgul on 18 May 2013 at 4:53

[GoogleCodeExporter]

The fact that the Google Plus API does not have any way at all to collect
together all the GOOGLE+ POSTS I have +1d is just nuts.  Also the inability
to post anything or build our own apps or experiences. Not being be to post
(natively) at all is another glaring hole in the API.

Resorting to 'scraping' for our data? In 2012? man...

I'm amazed anyone even bothers to try to build anything useful on this
(so-called) API any more.

All that talk in the beginning of not wanting to p*** off developers when
we were all champing at the bit to build things when G+ launched.  It's
clear that was all to shut us up and stop asking. Due to all that, Google
have completely sullied many developer's desire to care about G+. I just
don't believe anything will happen any more.

A useful, fully-working API for *OUR * data is a pipe dream now.

I suggest moving your resources to App.net.  It's a massively powerful API
with a dedicated, friendly intelligent community (on the whole) - that we
*pay* for. It's also generated more money for me than Google ever did or
could (without resorting to gaming the 'system').

I had no idea I still subscribed to this list.

I'll try leaving it again.

Bye.

Original comment by kos...@gmail.com on 18 May 2013 at 5:05

[GoogleCodeExporter]

Original comment by t...@google.com on 5 Jun 2013 at 1:36

• Added labels: Component-REST-API
• Removed labels: Component-API

[GoogleCodeExporter]

Original comment by t...@google.com on 6 Jun 2014 at 9:37

[GoogleCodeExporter]

Original comment by t...@google.com on 18 Sep 2014 at 2:20