From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Firefox and script block tool/addon
Date: Mon, 17 Feb 2020 12:09:02 -0600 [thread overview]
Message-ID: <4ec72bc3-7581-9d56-4fd4-41f81c241fb4@gmail.com> (raw)
In-Reply-To: <20200217152608.GB3871@inspiron.homenetwork>
Spackman, Chris wrote:
> On 2020/02/17 at 02:31am, Dale wrote:
>> Dale wrote:
>> I been playing with this add-on and watched some videos on it. While
>> it does some things better, it just isn't specific enough for what I
>> need. In some cases, if I blocked scripts with it, some sites
>> wouldn't work at all or caused other issues. In a way it's better than
>> noscript but it still just doesn't go far enough. I wish adblock
>> would list elements the way it used to. That worked great because I
>> could block scripts on a individual basis. Allow the ones I need and
>> block the ones that cause issues.
> I'm really surprised that umatrix (not ublock origin!) can't do what you
> need. As you note, it is much more granular than NoScript. Blocking
> elements at the subdomain level, you'd think, would be granular enough
> for most web pages.
>
> Are you saying you want to additionally allow / block scripts not just
> on a per-subdomain basis but on a per-individual-script basis? I've been
> using things like NoScript and uMatrix for many years, and I don't think
> even I would want to deal with that. How would you know which ones to
> allow? The Reg is showing 7, of which I allow 3. The Guardian has like
> 28, of which I allow 19. It would not be fun to try to go through all of
> those to figure out which ones are absolutely necessary. You'd be
> examining, allowing, and reloading 20 times per site, at first.
>
> Maybe the Tor Browser people would be interested in working on such an
> add on?
>
Yes, blocking on a per script basis is what I need. On one site, I'm
sure it has a couple dozen scripts on it. From what I could see, I
really only need to block 2 maybe 3. The others are needed for certain
things on the page to work. Some are needed to make the page load at all.
The thing about getting it set up, once done, it's done. It may take 30
minutes or a hour but once it is done, it won't require much if any
attention from then on. As I pointed out, I used to do this in
Seamonkey with adblock. It worked well. In some cases, I'd block all
by default and then set exceptions for the ones I need to work.
Whichever is easier.
Maybe one day I'll run up on a add-on that does this. Maybe. ;-)
Dale
:-) :-)
prev parent reply other threads:[~2020-02-17 18:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-25 3:52 [gentoo-user] Firefox and script block tool/addon Dale
2020-01-25 3:55 ` aisha
2020-01-25 4:39 ` Dale
2020-01-25 15:30 ` aisha
2020-01-25 15:09 ` Corpo
2020-01-25 22:54 ` Dale
2020-02-17 8:31 ` Dale
2020-02-17 15:26 ` Spackman, Chris
2020-02-17 18:09 ` Dale [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4ec72bc3-7581-9d56-4fd4-41f81c241fb4@gmail.com \
--to=rdalek1967@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox