News for hackers. Stuff that matters.
Re:De-Anonymizing Web Browsing Data with Social Networks [pdf] by franze on Tuesday February 07, 2017 @08:30AM (#13589169)
At the launch of G+ I tested a way to assign search terms that people used to get to my page to G+ users - if they clicked on an +1 G+ button (which had some nifty callbacks then). Kinda worked. I could assign the search term to a set of users which I narrowed down with manual review.

Think Google must have been aware of the issue of intermingling Search with Social as a pretty short time later they scrapped the search query referers from (organic) Google Search.

Note: It was just a proof of concept to see if I could. Also: Nobody used G+ anyway.

Re:De-Anonymizing Web Browsing Data with Social Networks [pdf] by aub3bhat on Tuesday February 07, 2017 @09:29AM (#13589554)
Search query referers were dropped due to adoption of HTTPS/TLS. When a url is visited from an HTTPS site the browser does not sends reffer url only the host.

Its still possible to get "aggregate" information about keywords via Google Webmaster tools.

https://webmasters.googleblog.com/2012/03/upcoming-changes-i...

Re:De-Anonymizing Web Browsing Data with Social Networks [pdf] by franze on Tuesday February 07, 2017 @10:03AM (#13589773)
Yeah default-for-logged-in-users-https-with-stripping-part-of-the-referrer started in 2011, besides being a good idea -after the launch of G+ profiles as there was now a public "real name" piece of information that connected search queries to G+ users.

Google Search Console data doesnt let you connect google search queries to sessions.

Re:De-Anonymizing Web Browsing Data with Social Networks [pdf] by travoc on Tuesday February 07, 2017 @12:15PM (#13590818)
Google passing your search queries in the referral URL was always a privacy issue. The TLS/SSL issue was an easy excuse to get rid of it.