Nemeski@lemm.ee to Technology@lemmy.worldEnglish · 1 month agoManifest V2 phase-out beginsblog.chromium.orgexternal-linkmessage-square54fedilinkarrow-up10arrow-down10
arrow-up10arrow-down1external-linkManifest V2 phase-out beginsblog.chromium.orgNemeski@lemm.ee to Technology@lemmy.worldEnglish · 1 month agomessage-square54fedilink
minus-squaresealhaslupus@lemmy.worldlinkfedilinkEnglisharrow-up0·1 month agofor those who come and read through these comments, on top of considering not using a chromium-based browser, you could also: configure your own DNS resolver e.g. NextDNS go further and use a fork of firefox e.g. librewolf
minus-squaresverit@lemmy.mllinkfedilinkEnglisharrow-up0·1 month agoUnfortunately DNS blocking is not nearly as powerful as an adblock extension which can manipulate the DOM and CSS directly.
minus-squaresealhaslupus@lemmy.worldlinkfedilinkEnglisharrow-up0·1 month agothis is true. however it can filter calls to ad services and block them at the dns level before they’re loaded in the browser
minus-squareAProfessional@lemmy.worldlinkfedilinkEnglisharrow-up0·1 month agoSites are going to move ads to shared domains, now that chrome users are stuck.
for those who come and read through these comments, on top of considering not using a chromium-based browser, you could also:
Unfortunately DNS blocking is not nearly as powerful as an adblock extension which can manipulate the DOM and CSS directly.
this is true. however it can filter calls to ad services and block them at the dns level before they’re loaded in the browser
Sites are going to move ads to shared domains, now that chrome users are stuck.