Behind the complaints: Our investigation into the suspicious pressure on Archive.today
adguard-dns.io
Some time ago, we were contacted by a group fighting against online CSAM, demanding that AdGuard DNS blocks the Archive.today website. This was only the beginning of a much larger story…

I feel like more people should know about this, specially the tech-native Lemmy audience that may be using Adguard DNS.

  • pulsewidth@lemmy.worldEnglish
    151·
    4 hours ago

    Your comment makes no sense with respect to this story.

    I don’t use AdguardDNS’s services but they are going above and beyond in their response to this spurious claim, seems very professional to me. If you read the story and weren’t happy with them and it’s boistered your desire to roll completely unfiltered DNS so that you won’t have any CSAM domains blocked, well… weird flex.

    • 1984@lemmy.todayOPEnglish
      10·
      4 hours ago

      I think maybe he just meant that the pressure from organisations to make dns services more censored is a reason to run your own dns service.

      But I agree with you. The solution is not to stop using public dns services, its to bring attention to things like this and not let it happen in the shadows. Adguard were amazing here and wrote a very good blog post to inform the community.

    • Nollij@sopuli.xyzEnglish
      11·
      2 hours ago

      Not OP, but the most obvious and popular alternative to Adguard DNS is a (self-hosted) Pi-hole. That setup is effectively protected from such attacks, in no small part because it’s self-hosted.