Re:Moving the Washington Post to HTTPS
by npongratz on Thursday December 10, 2015 @04:54PM
(#10713777)
Sounds nice in theory, but I'd be concerned about having my reading habits tracked by yet another Central Scrutinizer. I already block ads mainly to avoid creepy and invasive behavior by the ad networks, as well as the malware that seeps through said networks. I am not going to opt-in to mass surveillance.
[ Parent
| on HN ]
Re:Moving the Washington Post to HTTPS
by thetmkay on Thursday December 10, 2015 @05:42PM
(#10714132)
It doesn't have to be.
Assume registration includes specifying a list of "preferred publishers" (like what aggregated news apps ask on sign up in order to curate your feed)
Add a client side tracker (i.e. browser plugin) with the ability to track the page views on each site.
One of three options:
1) no tracking - split the distribution evenly among your preferred sites
2) offline/batch tracking - at the end of the month, submit an aggregated percentage breakdown of your sites
3) online tracking - sent to the server in real time (i.e. Central scrutiniser)
And if you're really particular about tracking, it could just be an API, and you can write to it whatever data you want to share.