From: Karl Dahlke <firstname.lastname@example.org>
Subject: js = website
Date: Sun, 17 Jul 2022 03:13:40 -0400 [thread overview]
Message-ID: <email@example.com> (raw)
This feature was suggested by David, along with a rather different paradigm.
You can block js from the top level domains, then turn it on for the sites that need it -
a white list rather than a black list.
You can still use the js toggle command to turn it on or off.
Here is a sample for your config file and yes it works - nasa is one of those sites that has to have js to run.
nojs = .com
nojs = .net
nojs = .gov
js = nasa.gov
reply other threads:[~2022-07-17 7:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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;
as well as URLs for NNTP newsgroup(s).