passwords-webextension VS I2P-in-Private-Browsing-Mode-Firefox

This is browser storage, and has nothing to do with I2P. I can't help you if you're using a misconfigured browser. If you are concerned about managing browser storage, I have half a dozen applications which can help you do this in a modern, portable, routine and secure way. I suggest using this one. Alternatively, This one. If you insist on doing it yourself, enjoy all the reading.

The Firefox extension depends on the presence of the I2P router, it does not include an I2P router itself. That information is the top line of the extension website. It is also available in the description on the Mozilla Addons Page. The extension won't work without a running I2P router. Installing it without an I2P router is pointless.

I am almost fully convinced that understanding this question better is the most important thing I can do for I2P, because answering it in in various forms has been my primary occupation for nearly five years now and I feel like I've barely scratched the surface. I did eventually run out of links though. As u/DivaExchange and u/psychonaut3333 pointed out, there is a learning process here and I would add that I don't believe it has a clear end. We're just a network, you can do almost any network thing with I2P. If we don't clearly cover your use case, talk to us about it.

I'm looking for people interested in helping me out, and there's space for non-coders too! I've started translating it in earnest, I need people to translate the extension and report untranslated parts. Android hackers who want to help me get it ported to Firefox for Android can help me figure out how to make containers work. Please get in touch with me on gitlab or github if you're interested in contributing(Gitlab preferred). Chromium hackers can help port features to the Chrome Version.

What everybody else has said is true, no, you can't tell Firefox's HTTPS enforcement padlock "you're using I2P, don't worry about HTTPS." But you CAN write your own padlock on the opposite side of the panel and use it to display equivalent messaging for equivalent I2P scenarios. Which, hopefully surprising less people by the day, I've already done: https://github.com/eyedeekay/I2P-in-Private-Browsing-Mode-Firefox/blob/master/i2p-https.png

You have two options: If Transmission has SOCKS support you may be able to configure it with an I2P SOCKS proxy, or you can use "I2PSnark-RPC" to turn i2psnark into a transmission-rpc API service, and connect a transmission client to it. You can get i2psnark-rpc from zzz's stats.i2p plugin archive or from my clearnet mirror.

Lots. One very important one is that they leave media.peerconnection in a non-proxy-obedient state. Mozilla provides an API for configuring this behavior, which I use here: https://github.com/eyedeekay/I2P-in-Private-Browsing-Mode-Firefox/blob/master/privacy.js, or you can see https://i2pgit.org/i2p-hackers/i2p.firefox for our preferred set of hardening tactics for general users. As you can see, the modifications are pretty extensive.

Firefox-based is much better than Chromium-based in the majority of ways. https://eyedeekay.github.io/I2P-in-Private-Browsing-Mode-Firefox/, https://eyedeekay.github.io/I2P-Configuration-For-Chromium/ and it is very easy to tell the difference between Chromium's and Firefox. If you are using Chromium, you are more unique to more people.