slothrop@lemmy.ca to privacy@lemmy.caEnglish · 20 days agoeveryone is someone's bad guylemmy.caimagemessage-square26fedilinkarrow-up1546
arrow-up1546imageeveryone is someone's bad guylemmy.caslothrop@lemmy.ca to privacy@lemmy.caEnglish · 20 days agomessage-square26fedilink
minus-squareQuacksalber@sh.itjust.workslinkfedilinkarrow-up10·edit-219 days agoThat’d work too, although I’d implement it the other way around. Define a new http header that indicates what type of content the site you’re visiting is hosting and handle the content blocking client-side based on those headers.
That’d work too, although I’d implement it the other way around. Define a new http header that indicates what type of content the site you’re visiting is hosting and handle the content blocking client-side based on those headers.
👌🏻very elegant