• Lka1988@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    3
    ·
    edit-2
    19 hours ago

    Thank you for proving my point:

    every thread the devs get involved with just seems like they’re sniffing their own farts

    Dont get me wrong, I think you guys make a great ROM. However, no advice was requested here, yet you tagged me in multiple consecutive comments chock full of unsolicited advice. Plus, in the first comment, you suggested “RethinkDNS”, which depends on their own DNS servers. How do I know that this service, which I have literally never heard of in my 14 years of fucking with Android devices and ROMs and adblockers until maybe 6 months ago, isn’t just a honeypot? Or will even exist after Trump is done raping the USA? I see they use DNS over HTTPS, but I defer to my previous (rhetorical) question.

    I wouldn’t think a security and privacy-focused ROM should be recommending anything but a locally hosted option. But as others have said, this is your guys’ project and you’re free to implement it how you see fit. And it is a solid ROM. But apparently it’s not for me.

    • GrapheneOS@grapheneos.social
      link
      fedilink
      arrow-up
      3
      ·
      19 hours ago

      @lka1988

      > Plus, in the first comment, you suggested “RethinkDNS”, which depends on their own DNS servers.

      You do not need to use their DNS servers. You can use local filtering and your choice of DNS servers including the network provided ones.

      > I wouldn’t think a security and privacy-focused ROM should be recommending anything but a locally hosted option.

      We’re recommending using local filtering via RethinkDNS, not the RethinkDNS servers. They allow downloading the blocklists locally.

      • GrapheneOS@grapheneos.social
        link
        fedilink
        arrow-up
        2
        ·
        19 hours ago

        @lka1988 We focus our effort on the base OS and areas which are not already covered by high quality open source apps. We don’t need to build our own domain-based filtering and blocklists for it because they already exist.

        We have built-in content filtering in Vanadium based on EasyList + EasyPrivacy. That’s more usable (per-site toggle) and much less limited than what domain-based filtering can do but it’s still limited by needing to permit dual use functionality and is still easily bypassed.