sent from a disposable whonix qube

    • Multiplexer@discuss.tchncs.de
      link
      fedilink
      arrow-up
      1
      ·
      2 days ago

      Had a look into the ublock settings.
      The one I found seems to be more of a nuke-grade total disabling, as opposed to the fine-grained approach of the noscript extension.

        • Multiplexer@discuss.tchncs.de
          link
          fedilink
          arrow-up
          2
          ·
          1 day ago

          I guess I prefer the Unix philosophy of doing things:
          Have a bunch of combinable small programs each being dedicated to a single function and doing that well instead of large complex monoliths.

          • keiko@fedia.ioOP
            link
            fedilink
            arrow-up
            3
            ·
            1 day ago

            When it comes to browser addons, it is generally recommended to have as few as possible in order to reduce attack surface, since a higher number increases the chance of having one that becomes compromised. It’s especially relevant with browser addons because they tend to have lots of capabilities/permissions and can therefore do lots of damage.

      • rumschlumpel@feddit.org
        link
        fedilink
        arrow-up
        2
        ·
        2 days ago

        UBlock’s approach is that you disable it for every site in the settings and then whitelist per site. Seems sensible enough to me. How does noscript do it?

        • keiko@fedia.ioOP
          link
          fedilink
          arrow-up
          1
          ·
          2 days ago

          That is certainly a valid approach to using ublock origin, but the wiki outlines a few other blocking modes available.