4 ms·

Thanks -- We actually maintain an exclude list of OSS ads that you can use with your ad blocker of choice: https://ads-for-open-source.readthedocs.io/en/latest/

Thanks -- We actually maintain an exclude list of OSS ads that you can use with your ad blocker of choice: https://ads-for-open-source.readthedocs.io/en/latest/index.html https://ads-for-open-source.readthedocs.io/en/latest/index.h... Of note, we do run our own javascript client on the pages. Our users can opt into hitting our backend API instead of running JS code, but many just use our client directly. We currently serve the ads on our own domain. We could implement the ability for our publishers to proxy the ad views to our domain (this is generally called "ad cloaking"), but it hasn't felt like the right thing to do. We are also on the Acceptable Ads non-tracking list, so our domains are unblocked for people who choose that in their ad blocker. If we use a publishers domain, they will be unblocked for some period of time, but then their domain gets added to the ad blockers, and we lose this Acceptable Ads traffic.

webmobdev 4y ago
I feel ad proxying and server side rendering would be a better fit for the brand identity you are trying to create. Why does one need javascript to serve some text or image, along side some content? One of the common reasons for blocking ads is they slowdown websites by using more resources and thus also reduce battery life. It also introduces another barrier to trust you more - how do I know that the Javascript code is not doing something unwanted (like browser fingerprinting, introducing some annoying animation etc.) - after all, it would be a pain to keep reviewing your javascript code and would be easier to just block it.
- ericholscher 4y ago
  We do support publishers using an API directly, and running none of our code. Our ad client is also open source, and pretty simple: https://github.com/readthedocs/ethical-ad-client https://github.com/readthedocs/ethical-ad-client -- we have publishers who use a published version with Subresource Integrity, but you can also just host the JS yourself if you want.

webmobdev 4y ago

I feel ad proxying and server side rendering would be a better fit for the brand identity you are trying to create. Why does one need javascript to serve some text or image, along side some content? One of the common reasons for blocking ads is they slowdown websites by using more resources and thus also reduce battery life. It also introduces another barrier to trust you more - how do I know that the Javascript code is not doing something unwanted (like browser fingerprinting, introducing some annoying animation etc.) - after all, it would be a pain to keep reviewing your javascript code and would be easier to just block it.

ericholscher 4y ago
We do support publishers using an API directly, and running none of our code. Our ad client is also open source, and pretty simple: https://github.com/readthedocs/ethical-ad-client https://github.com/readthedocs/ethical-ad-client -- we have publishers who use a published version with Subresource Integrity, but you can also just host the JS yourself if you want.