9 ms·
The tracking should ocurr when the user performs the +1. It shouldn't track the way it does, and it certainly shouldn't track HTTPS. It is not even an issue of
by Hrundi 15y ago
The tracking should ocurr when the user performs the +1.
It shouldn't track the way it does, and it certainly shouldn't track HTTPS. It is not even an issue of privacy, it is simple courtesy and common sense.
- adgar 15y agoIf the extension doesn't send the URL to Google anyway, then it can't know how many +1s the page already has (and from whom). That's why it triggers on every page load.
- Hrundi 15y agoBut Google already knows the +1's received by the page, regardless of the visitor's login status. Granted, it doesn't know if the visitor has friends that shared it. It still doesn't excuse them for sending all url's. Facebook received a lot of flack for doing this and I don't see why Google should be excused for this intentional "gaffe".
- tomkarlo 15y agoYou're missing the point - Google knows how many +1s the page received. But the user's browser doesn't, so it can't display the +1 count without contacting the server (and sending the page URL) to find out. I have to wonder if this is an unintended side effect of the recent push to have site move to HTTPS - it used to be that HTTPS requests were mostly unique to a user, but now lots of "regular" pages are being requested using HTTP and if you want to make any kind of extension that return data about pages (+1, anti-phishing, etc) you're probably going to to want to send HTTPS URLS as well.
- Florin_Andrei 15y agoHere's a happy medium: track it "on demand". Let's say, when you hover the mouse over it. Or make the +1 a two-gesture event: click the extension button (which is when "tracking" occurs) which opens a balloon, then click a +1 button within the balloon.