Reviews for I2P In Private Browsing
I2P In Private Browsing by idk
Review by Firefox user 12884452
Rated 4 out of 5
by Firefox user 12884452, 5 years agogreat but...when i enable this extension, all my other tabs to other sites are unusable and cant reload. Would be great if someohow this extension sets a container +tab with proxy settings for that tab/container only for i2p? at the moment it looks like when i enable the extension, it basically makes the whole browser {and all tabs as a result} set for i2p via the i2p proxy etc? i initially thought it sets up a container with a tab for i2p only? i didnt have a problem disabling it. i just needed to disable the extension and restart firefox. perhaps the best would be to have two firefox browers and one dedicated with this extension for use for i2p ? but i can seem to be able to install 2 firefox browsers (easily) in linux..unless maybe i use sandboxie or something? thanks in advance for this extension anyway. great work so far,
Developer response
posted 5 years agoAre 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.
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.