Hi Qubes.

I can't change what version of IceCat ParrotOS packages. I'm not in charge of what they do. If you force it to be installed in a lower Firefox version than what I officially support, I am not responsible for the consequences. Firefox plays nice with the sandbox in newer versions. I suggest you update.

Of course it overrides automatic proxy configuration. It's whole job is to override the proxy configuration for the container tab. If you're hell-bent on nonstandard configuration, then this isn't the extension for you.

As I told you on zzz's forum, there is absolutely nothing I can do about CDN's testing for privacy.resistFingerprinting and blocking people who use it. That is Amazon's fault, not mine. The alternative, *disabling* privacy.resistFingerprinting, is much worse. As I said, I won't endanger other users just because you are having issues with a CDN.

I may make an effort to be more compatible with I2P+, but your other three issues are just as ill-concieved and non-actionable as they were on zzz.i2p.

Previous discussion: http://zzz.i2p/topics/3379-i2p-in-private-browsing-firefox-add-on

This is on purpose, it's intentionally recoloring the tabs in order to provide overt visual indication that the proxy is in use and the settings are being applied. I would be open to choosing a different color if the purple is obstructive, or possibly adding an option which disables the dynamic theming, but removing it entirely is not on the table. This is a feature, not a bug.

**Update**
OK I'll fire up a Gnome machine and re-evaluate some of the colors, that's a really widespread configuration as far as Linuxes go. I'm probably going to do a release late this month, perhaps early January, I expect it will be in by then.

Are you reviewing the right extension? There are two versions of this extension, one which is intended only for Android. Since Android is unable to use Container Tabs, the I2P Proxy extension sets the proxy globally and with a separate Firefox is indeed the recommended way to use it. I'd really like to deprecate this version of the extension but until the contextualIdentities API on Android matches the contextualIdentities API on desktop, this second, inferior(Android) extension has to exist. If you have the option, the desktop version is the one which you should be using, and that one is called "I2P in Private Browsing" and is at version "1.26" right now. I don't think there's a way for me to mark the other extension(I2P Proxy for Android and Other Systems) as being installable on Android only, I tried to find one but I don't think it exists.

When I test the release version of the "I2P in Private Browsing" extension the behavior is as you recommend, the "I2P Browser" tab is proxied without any exemptions, dropping localhost addresses, and in the application containers the proxy is applied with a per-app exemption and dropping all non-app localhost addresses. This is exactly as intended as far as I can tell. Moreover my Discord container and my Google containers both work normally, and I don't appear to be using an outproxy to visit the web. I don't know why you would be experience this issue unless you got the Android-only version by accident.

You are the very first user of this extension to ever describe this behavior. The only thing I can think of that could cause it is another extension competing with it to do some function related to closing and re-opening a tab. Could you please describe for me what other extensions you are using, so that I can attempt to reproduce the issue?

That's not good, it means it's probably not playing nice with other containerizing extensions anymore. This is a bug, and I will fix it soon. Very sorry for the inconvenience. https://i2pgit.org/idk/I2P-in-Private-Browsing-Mode-Firefox/-/issues/32

Uninstalling it will undo most of the changes to your browser(But not the containers themselves yet). The settings that it changes can be found by going to the URL `about:config` and searching for `media.peerconnection` and `privacy.resistFingerprinting`. Make sure that `media.peerconnection.enabled=true` and that `privacy.resistFingerprinting=false`, those are the most important. about:config indicates that non-default settings are in use by putting them in bold type-face. Searching may reveal related settings that were also flipped by the extension. Return them to their default state by clicking the "reset" icon, which is the left-pointing curved arrow on the right-hand side of the page.

Edit Reply:
`browser.contentBlocking.category`
`browser.network.cookieBehavior`
`media.peerconnection.enabled`
`media.peerconnection.ice.no_host`
`media.peerconnection.ice.proxy_only_if_behind_proxy`
`privacy.resistFingerprinting`
`privacy.resistFingerprinting.letterboxing`
`privacy.trackingProtection.enabled`
`privacy.userContext.enabled`
`privacy.userContext.ui.enabled`