Reverse-engineering the Google +1 button using Firebug(randomistas.tekeu.com)
randomistas.tekeu.com
Reverse-engineering the Google +1 button using Firebug
http://randomistas.tekeu.com/2011/07/04/reverse-engineering-the-google-1-button-using-firebug/
7 comments
The article did not talk about a click but only about the display. They are only trying to access the displayed click count number directly via PHP.
And not to mention they could change the data it recieves (and how it recieves it) anytime. It would be way easier and more effective just add a click event and with some Ajax save the stadistics on your own database.
Considering this rpc key parameter, I really wonder how long this is going to work and I'd say this is a bug on googles side that it even worked.
I checked their embed page (http://www.google.com/webmasters/+1/button/) and I don't see that it requires any API key what so ever, so I assume this rpc_key thing is something private to the API and fetched as the button-JS communicates with the server.
These keys are probably issued with limited time validity, so possibly the script of the OP has already stopped working (I haven't tried yet).
We DO need a real API for this though - if we webmasters do Google a favor and add the plus one buttons, the least they could do is give us a means of finding out how many time the button has actually been used.
Otherwise, this is a bit one sided: We lend Google space, we do the work of adding the button, but we get nothing in return.
I checked their embed page (http://www.google.com/webmasters/+1/button/) and I don't see that it requires any API key what so ever, so I assume this rpc_key thing is something private to the API and fetched as the button-JS communicates with the server.
These keys are probably issued with limited time validity, so possibly the script of the OP has already stopped working (I haven't tried yet).
We DO need a real API for this though - if we webmasters do Google a favor and add the plus one buttons, the least they could do is give us a means of finding out how many time the button has actually been used.
Otherwise, this is a bit one sided: We lend Google space, we do the work of adding the button, but we get nothing in return.
> Otherwise, this is a bit one sided: We lend Google space, we do the work of adding the button, but we get nothing in return.
You get the whole purpose of the button for you in the first place, users encouraged to share your content.
You get the whole purpose of the button for you in the first place, users encouraged to share your content.
They recently added +1 metrics in Webmaster Tools. Not ideal, but it's better than nothing...
I tried cracking open the button to customize it, but I lack the skills to go all the way. I'd rather lobby Google to make a real API for it anyway.
That's pretty awesome, I wonder if it's rate limited at all?
I think they may have thought people might try this. Very cool though.
I think they may have thought people might try this. Very cool though.
Firebug. I remember using it for the first time - felt like I was born again.
Nice work! Thanks for posting.. I will add this to my Trendn App.
I did this about a day after they officially launched +1 with Ruby for my own app. I scrape probably 2-4000 urls a day, it works fine.
Most badges or like buttons can be reverse engineered like this, it's not too hard.
Most badges or like buttons can be reverse engineered like this, it's not too hard.
And in the response he gets there seem to be a bunch of missing fields (on my machine there's the title and information about my logged in Google Account) and there's also the count of +1s on that page. He seems to be getting a 0 return. Wouldn't be much surprise if this is Google's way of showing that it ignored the request.