Here's an idea I'm not sure would work, but I want to put it out there. Browsing history and/or time spent has to be tracked so the money can be distributed to

Here's an idea I'm not sure would work, but I want to put it out there. Browsing history and/or time spent has to be tracked so the money can be distributed to the right sites. To protect the browsing history: 1) (on the client) Take the domain name (or URL, IP or data point) and add a salt 2) Hash it 3) Add it to a bloom filter (or another type of filter) 4) After enough URLs have been added, submit the filter and salt 5) (on the server) Run the list of participating domains through the filter (take the domain, add salt, hash, and filter) Some thoughts about this type of scheme: No exact history data would be submitted. You may need multiple filters for domain, time spent, type of interaction, etc... The selection of filter and optimal number of domains (or encoding of data points) might be problematic. Submission can be done at any time (no schedule). The loss of a few submissions won't matter (no need for every domain or a complete history.) Submissions can be delayed until there is enough obscuring data, and filters provide plausible deny ability (about browsing history.) Submissions could be made to trusted 3rd parties (browser makers, large company networks, non-profits like the EFF, etc..) and only the results sent to a central authority. Some websites that were not visited will benefit, but the salt will stop gaming of the domains. Running the list of participating domains might be to demanding to be practical. Groups of domains could have their own payment/subscription filter (news domains, GNU endorsed domains, etc...) distributed to the clients like blocklists. The biggest problem: Advertisers and ad networks will fight against loosing personally identifiable information and analytics data.