slothrop@lemmy.ca to privacy@lemmy.caEnglish · 2 days agoeveryone is someone's bad guylemmy.caimagemessage-square26linkfedilinkarrow-up1533arrow-down16
arrow-up1527arrow-down1imageeveryone is someone's bad guylemmy.caslothrop@lemmy.ca to privacy@lemmy.caEnglish · 2 days agomessage-square26linkfedilink
minus-squareQuacksalber@sh.itjust.workslinkfedilinkarrow-up10·1 day 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