I'm still surprised no one has yet figured out a way to store sensitive data about personal interests and preferences on the client-side and let the client itself pull appropriate ads for the user to see. The quality of such a system should be comparable or better to server-side technologies with the right amount of tuning, and much less privacy-invading than existing approaches. Personally I'd love to support more w…
Brave, with the Basic Attention Token (BAT), is building exactly the client-side anonymous contribution + ad-matching system you describe. We will take BAT to other apps after proving the model in Brave. BAT in Brave is opt-in -- each user consents before anything local happens with data or zero-knowledge/blind-token attestations -- and users can get _gratis_ BAT grants right now using the stable desktop browser (thi…
Funding Choices – Google’s new tool for GDPR compliance and content monetization
141–150 of 173 posts
Re: Funding Choices – Google’s new tool for GDPR compliance and content monetization
#142Earlier quoted context omitted.
I'm a big fan of that idea. Imho the beauty of your BAT system (the way it is envisioned) is it's independency from the current model of monetizing the web, which is ads, gradually evolving towards direct transmission between publisher and consumer. Ads in the way they work on the web are just a very inefficient system of transferring this value, and they don't serve the original function of marketing anymore. It tur…
> The system is so inefficient that it finances almost the complete operation of Alphabet/Google. Since Youtube is wildly unprofitable, Alphabet/Google has to be funneling in money generated from other sources. Thus, Youtube is funded by ads, just mostly not from the ads on Youtube.
Re: Funding Choices – Google’s new tool for GDPR compliance and content monetization
#143Earlier quoted context omitted.
Having cleared all cookies recently, I'm re-encountering all these dialogs. They've gotten cagier. Anecdotally, a third of these cookie dialogs are violating those principles, either preselecting all third party advertisers, or claiming all 60+ third parties are necessary for the functionality of the site so Allow or Go Away. Or having only one OK/Agree button. It's not just little guys. Slate.com for example: Slate’…
> claiming all 60+ third parties are necessary for the functionality of the site If you consider financial needs underpinning the site operation, it's technically true - without the 60+ 3rd parties, they could run out of funds to host the site, after which the site would not function at all.
Re: Funding Choices – Google’s new tool for GDPR compliance and content monetization
#144Re: Funding Choices – Google’s new tool for GDPR compliance and content monetization
#145Gotta love their choice of wording, "recover lost revenue from ad blocking users", like blocking ads is equivalent to stealing money from the site owner.
Re: Funding Choices – Google’s new tool for GDPR compliance and content monetization
#146I would be willing to load ads if I didnt have to see them. I’m happy. Content provider gets ad shown so they are happy. Advertiser doesn’t get anything, but I don’t care.
Re: Funding Choices – Google’s new tool for GDPR compliance and content monetization
#147Earlier quoted context omitted.
> The system is so inefficient that it finances almost the complete operation of Alphabet/Google. Since Youtube is wildly unprofitable, Alphabet/Google has to be funneling in money generated from other sources. Thus, Youtube is funded by ads, just mostly not from the ads on Youtube.
It was mentioned in a private email that the only reason YouTube exists is that Google's servers happens to have a lot of free disk space in the days before SSDs.
Re: Funding Choices – Google’s new tool for GDPR compliance and content monetization
#148Earlier quoted context omitted.
It was mentioned in a private email that the only reason YouTube exists is that Google's servers happens to have a lot of free disk space in the days before SSDs.
YouTube was a separate company acquired by Google in 2006: https://en.wikipedia.org/wiki/History_of_YouTube
Re: Funding Choices – Google’s new tool for GDPR compliance and content monetization
#149I'm still surprised no one has yet figured out a way to store sensitive data about personal interests and preferences on the client-side and let the client itself pull appropriate ads for the user to see. The quality of such a system should be comparable or better to server-side technologies with the right amount of tuning, and much less privacy-invading than existing approaches. Personally I'd love to support more w…
Brave, with the Basic Attention Token (BAT), is building exactly the client-side anonymous contribution + ad-matching system you describe. We will take BAT to other apps after proving the model in Brave. BAT in Brave is opt-in -- each user consents before anything local happens with data or zero-knowledge/blind-token attestations -- and users can get _gratis_ BAT grants right now using the stable desktop browser (thi…
Do my ip-address, sites-i-visited, date/time of visit, geo-location ever gets stored in on a server outside (eg outside my phone or my computer I am browsing on)?
Re: Funding Choices – Google’s new tool for GDPR compliance and content monetization
#150I'm still surprised no one has yet figured out a way to store sensitive data about personal interests and preferences on the client-side and let the client itself pull appropriate ads for the user to see. The quality of such a system should be comparable or better to server-side technologies with the right amount of tuning, and much less privacy-invading than existing approaches. Personally I'd love to support more w…
Brave, with the Basic Attention Token (BAT), is building exactly the client-side anonymous contribution + ad-matching system you describe. We will take BAT to other apps after proving the model in Brave. BAT in Brave is opt-in -- each user consents before anything local happens with data or zero-knowledge/blind-token attestations -- and users can get _gratis_ BAT grants right now using the stable desktop browser (thi…