Well mine didn’t update at all until I manually added the servers from amazon it was blocking by default.
So I kind of assume taking them off again is a temporary solution. That said I can’t guarantee they haven’t changed anything since then and I might wake up to a worse fire cube sometime.
Blokada overrides the dns to its own and even then I don’t see how dns is at all relevant because it blocks the update server from being connected with.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !technology@beehaw.org
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Does that help? For me it doesn’t stop anything. It looks like it uses DoH or something to bypass filtering.
Well mine didn’t update at all until I manually added the servers from amazon it was blocking by default.
So I kind of assume taking them off again is a temporary solution. That said I can’t guarantee they haven’t changed anything since then and I might wake up to a worse fire cube sometime.
Blokada overrides the dns to its own and even then I don’t see how dns is at all relevant because it blocks the update server from being connected with.