From: "Clément Lassieur" <clement@lassieur.org>
To: "André Batista" <nandre@riseup.net>
Cc: Marius Bakke <marius@gnu.org>, 68831-done@debbugs.gnu.org
Subject: bug#68831: gnu: torbrowser: noscript gets picked up by icecat
Date: Wed, 31 Jan 2024 16:59:36 +0100 [thread overview]
Message-ID: <87o7d1ebo7.fsf@lassieur.org> (raw)
In-Reply-To: <ZbpjjdGB3bGIhFBt@andel> ("André Batista"'s message of "Wed, 31 Jan 2024 12:13:17 -0300")
On Wed, Jan 31 2024, André Batista wrote:
> Hi Clément,
>
> qua 31 jan 2024 às 03:19:26 (1706681966), clement@lassieur.org enviou:
>> Hello André,
>>
>> I thought about it, and I even started working on a fix. But I stopped
>> working on it because I thought it added too much complexity for too
>> little gain. See:
>>
>> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=68298
>
> Oh, I had missed that, I'm sorry for the noise. I had checked guix-bug
> only before submitting this report.
>
>> The default for Tor Browser and Mullvad Browser is that extensions are
>> not working because tabs are private. Now if a user uses both Icecat
>> and Tor Browser and want a different set of extensions for each of them,
>> they can use 'guix shell', which works perfectly well. (They can also
>> still add extensions to the Firefox profile.) Having 4 versions of each
>> extension seems cumbersome.
>
> I concur to your reasoning, it's easy for users to avoid it if they do
> care. You may close this as wontfix.
Ok! Closing.
prev parent reply other threads:[~2024-01-31 16:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 23:56 bug#68831: gnu: torbrowser: noscript gets picked up by icecat André Batista
2024-01-31 2:19 ` Clément Lassieur
2024-01-31 15:13 ` André Batista
2024-01-31 15:59 ` Clément Lassieur [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o7d1ebo7.fsf@lassieur.org \
--to=clement@lassieur.org \
--cc=68831-done@debbugs.gnu.org \
--cc=marius@gnu.org \
--cc=nandre@riseup.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).