this post was submitted on 11 Jul 2023
11 points (82.4% liked)

Selfhosted

39257 readers
259 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
11
PiHole and Cookie Warnings (kbin.social)
submitted 1 year ago by LazerFX@kbin.social to c/selfhosted@lemmy.world
11 comments fedilink hide all child comments
 

I'm trying to figure out how to stop having to unblock the pihole, in order to bypass cookie consent alerts. I think this is a devious new attempt by the advertising brigade to ensure that adverts are played, but more and more cookie consent blockers are not working properly if you've got an adblocker, and as I've got one at the network level, this is a real frustration. I've tried a few browser-based bypassers, but that doesn't work for many mobile devices, and sort of defeats the purpose of havign a network-level adblocker...

Has anyone else hit this issue and how have you worked around it?

top 10 comments
sorted by: hot top controversial new old
[–] BitPirate@feddit.de 4 points 1 year ago (1 children)

Cookie banners are usually from the same domain. I doubt you can block them via DNS.

[–] LazerFX@kbin.social 1 points 1 year ago

That's exactly the problem. Parts of the cookie banner are from the same domain, but then other parts are from the advertisers domain. So blocking the advertiser blocks bits of the banner, meaning you cannot click on the banner, because it's just not letting you do so.

[–] nandor@lemmy.world 3 points 1 year ago

I’ve seen it happening over the last few days. The JavaScript used to control the cookie banner appears to be served from a domain that is blocked by my pi-hole, so I can’t click on the buttons to accept or reject cookies

[–] qazwsxedcrfv000@lemmy.unknownsys.com 3 points 1 year ago* (last edited 1 year ago)

Cookies are set via the HTTP headers. And the check is usually done locally by JavaScript. The headers can be stripped away via proxy. But unless you disable JavaScript outright (which will literally break most modern websites), you could hardly avoid those banners.

[–] RoundSparrow@lemmy.ml 3 points 1 year ago

your post got duplicated, this is the 2nd copy

[–] peter@feddit.uk 2 points 1 year ago (1 children)

Try the "I don't care about cookies" extension

[–] ollie@lemmy.world 10 points 1 year ago (3 children)

alternative (superior) open source extension: https://github.com/cavi-au/Consent-O-Matic

[–] LazerFX@kbin.social 1 points 1 year ago

Thanks for the tip. I really loathe having to do tihs as it doesn't help mobile, but at least I can auto-sync across desktop browsers :/

[–] peter@feddit.uk 1 points 1 year ago

Neat, I'll switch to this one

[–] Tippon@lemmy.fmhy.ml 1 points 1 year ago

That looks great, thanks :)

load more comments
view more: next ›