https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/pageAction

An I2P-Bote plugin tab is a good idea too, but a low priority since Bote isn't very active right now.

Somewhere in the past few releases I broke Android, probably while I was making the window-management less irritating. Find+fix.

The plugin itself supports multiple languages, but the website does not. I should fix that up ASAP.

Work with Mozilla to disable fingerprintable audio API's when privacy.resistFingerprinting=true.

WebRTC can't be disabled on a per-tab basis, so I'm going to add a checkbox(disabled by default) for optionally re-enabling it.

We make a request to proxy.i2p, a sort of "loopback" site, to ensure that the proxy is ready for the browser and provide user feedback. Lintian sees proxy.i2p as a remote site, which it isn't. Given this, the Warning issued by lintian is a false positive. This should be handled somehow.

Not sure if this is a good idea. May want to talk to Simply Secure about it.

TODO

proxy.i2p is a locally hosted tunnel that only your HTTP Proxy tunnel can visit. As such, it's a special case for the extension, since there is no great risk to visiting your own localhost in this way and since the extension needs to use it even if it doesn't know it should be using the I2P context. This concept is being extended for browsing with "pluggable" loopbacks in an experimental standalone http proxy, which provide friendly names for router console applications in the same basic way.

Now that this is getting more and cooler features, I need to go over what all the settings are, how they're configured, which ones are obsolete and which ones needs to be created to fully realize all the cool stuff this plugin can do. This should be done before I even introduce settings for the torrent RPC protocols which makes it another blocker for the next version.

todo

TODO

Work with Mozilla to finish webgl requirements for resistFingerprinting.

Right now the clear data button clears the data for the whole browser. Instead, it should clear as little as is reasonable from the main contextual identity and clear the cookies, cache, etc from the i2pbrowser and routerconsole contextual identities.

It's possible that people will want to run this extension on variant Firefox browsers. There are some where I know it won't work, like Waterfox which only has XUL extensions, and many where it may or may not. It has in the past been used with Firefox ESR, Firefox, I2P Browser, Iceweasel, Icecat, Fennec, and Icecat Mobile at various points. Somehow I need to be able to automatically test for compatibility with each one, especially on mobile devices.

This is super easy to hack on. Maybe too easy to abandon even if IBB is objectively better in most ways except browser updates. Plus, it could be used in a similar way to Tor tabs in Brave or Icecat and can be signed by Mozilla. I need to clearly enumerate the pros and cons of each approach.

Starting from regular browsing, open "Private Browsing with I2P" mode. Also solves my plugin updates without outproxies issue(#4) but maybe creates another one(#6)? Solve #1 first.

Eventually we'll have to have configuration for different RPC endpoints for I2PControl and Bittorrent, from there it's not a stretch to let remote clients be controlled over i2p tunnels as well, but in this case we need to make sure that we require the password to be changed from the default and possibly look into using encrypted leasesets here too.

In order to talk to i2pcontrol I need to set up rules for making a "Native Messaging" connection with an I2P router. In order to do that, I'll need to figure out how to add a native messaging manifest to the resources in the I2P router.

This extension currently Breaks the expected behavior of FoxyProxy by enforcing it's rules over those described by FoxyProxy. This one might be more trouble than it's worth, in fact I think it probably is, but if it isn't, this is a nice-to-have for some of the longtime Foxy users to ease their transition.

When using an I2P Browsing window, requests to the localhost should be dropped entirely without shifting to the localhost identity. Currently, they shift over to localhost browsing, which interrupts the user's browsing process. This does not cause a proxy escape.

Are there any plans to support the Torbrowser?

Do this on the airplane.

There is a chance this extension may be breaking Twitter logins in some circumstances. How is not immediately apparent to me from the information I have, however it's infinitely redirecting people which could either arise from the outproxy configuration, or Twitter sign-on is broken because some aspect of it is being blackholed or redirected mistakenly by the webextension. Or maybe Twitter's wrong, but they have a bigger staff than me so I'll assume I'm wrong first.

Develop a consistent style guide.

Right now history management is from before it used contextual identities, with some hacks on top. It needs to be changed to a better interface, which simply takes a contextual identity and clears history based on that information. This will improve security, reliability, and be useful in non-I2P contexts in the future.

Right now this extension conflicts with other extensions that containerize websites, including extensions that come from Mozilla itself. Co-Exist with these extensions.

I absolutely gutted the strings for the extension recently and haven't made the pages translatable again yet.

I wonder if I understand enough Spanish to write a Spanish translation myself. I will probably give that a shot too.

This is the first plugin that will get it's own container tab and protocol handler in this extension. This will only work with the Java I2P Plugin version of the MuWire application.

I'm definitely going to do snark-RPC, but if I can I'd also like to make XD and BiglyBT configurable options for an i2p-in-private-browsing bittorrent protocol handler.

SOCKS is not used by default and still requires manual configuration. When a user selects SOCKS but leaves host:port undefined, defaults localhost:4446 should be used.

When the proxy isn't ready, but the user enters an I2P browsing tab, provide a descriptive error page to guide the user to a solution, even if that solution is to tell them to wait 2 minutes.

States should be described:

• Router Not Present: There is no indication that I2P is installed on the system. Direct them to an I2P distribution.
• HTTP Proxy Not Ready: The router is present, but the HTTP Proxy is not up yet. Wait 2 minutes, if t>2 minutes, direct them to /i2ptunnel to troubleshoot.

i2psetproxy.js doesn't really tell much about what this plugin does anymore. I2P in Private Browsing is probably better. I don't think I depend too much on this repository being named i2psetproxy.js for like, CI or anything, but if any issues do come up then I guess I'll write about them here as I find and resolve them.

When using AMO, plugins will probably be fetched over clearnet.

There are like a bunch of linter errors for me to clean up. Most of them are pretty boring Javascript-syntax stuff that doesn't make that much difference, but it's a chance to go over the code and tidy it up by definition. I'm partly done, will close this issue when I am completely done on branch lint-roll

I dunno what's up here. This setting is privacy.resistFingerprinting.letterboxing=true or something like that. If seems like the privacy.websites.resistFingerprinting API should enables privacy.resistFingerprinting.

Design webextension experiment.

See also #80 #16 #65 #17

Can I even do that? Without messing with omni.ja or whatever else?

TODO:

Hi. There is C++ correspondence for i2p original java application, called i2pd - see:
https://i2pd.website/
https://github.com/PurpleI2P/i2pd

My question is that: does this extension compatible with i2pd or it is only working with i2p ?

This plugin has to interfere with normal browser operation just a little bit, but it shouldn't ever do it unnecessarily. Setting the home page was a big #fail, we don't do that anymore (in trunk). Besides that, more testing for peaceful co-existence with other plugins and examination of what happens when a proxy.onRequest function does not resolve a proxyInfo object and the browser presumably falls back. I do know that if the proxy is set via network preferences or about:config it will fall back to that proxy, but I want to make sure there are no exceptions to that rule.

The plugin should not interfere with dark mode or themes installed in the browser except when dealing with I2P sites. If dark mode can be detected, providing dark-themed contextual ID tabs becomes a goal.

As titled. This extension should automatically add torrents to snark via the RPC interface.

In certain circumstances, the WebRTC state will default to enabled but forced down the proxy, which is set per-tab. In some of those cases, I2P in Private Browsing, which displays a checkbox to reflect WebRTC enabled/disabled state, will show WebRTC as disabled when it is infact enabled. This doesn't seem to affect WebRTC obedience, so it doesn't introduce a vulnerability, but it does need to be corrected ASAP. Likely solution is to just check WebRTC state at a different point.

I2P integration in Whonix is running into the problem of making the router console available(Which requires either a proxy exception or an extra proxy like Privoxy) without making the whole localhost available. Since that's a problem this can solve, after I deal with the linting stuff I need to get back in touch with them. Right now I'm also (ab)using include-binaries, I'll need to resolve that too.

This can't be done in just this extension, but this extension is probably an important component of a future plan in which this is straightforward. This is the trickiest thing I've tried so far, K, let's define some phases here...

Phase 0: Design

We're pretty different from Tor in the places where Snowflake would really matter, but it's an inspiring effort and a cool product. This process probably won't bear much resemblance to Snowflake when it's all designed, but Snowflake was the original inspiration for the idea.

What we want to do is make it possible for I2P users to easily reseed eachother in a peer-to-peer way when necessary. It must be done no more often than a normal reseed, and it must only ever be client initiated.

This is not a webRTC transport for I2P. That would be an entirely different project. Especially if it were to do something genuinely insane like try to incorporate browser users not otherwise running I2P into the routing process. That would be crazy, right? Right? (It might not actually be that crazy but I have enough to think about right now). This is only for reseeds.

Questions

• Where to get the reseed file? Locally or from a reseed server? Probably a server, and we act as a proxy, but we need to examine advantages and disadvantages of each. Maybe both, server then a local fallback?
• Do we need to geolocate and never fetch a reseed file for a user in a country which is already automatically in hidden mode? Probably yes. Might want to never make them reseed helpers anyway.
• How to distribute the reseed file? If it comes from a server it will be signed by a key we already trust, that's fine, but if it comes from somewhere local we may want to use an interstitial

Components

• Browser Extension - This repo. We use it because we can to some extent assume that people using this extension are also using I2P and can thus provide a reseed from a local source if need be.
• Javascript Import - Placed on web pages, a'la Snowflake and or Flashproxy. Shows a download link that says "Download reseed file over WebRTC," uses a (random?) extension user.
• Native Proxy - Runs locally, obviates the need to download the reseed in a browser by fetching it over WebRTC on behalf of the router. Will start out as a "Bridge" but eventually be incorporated into I2P if successful.
  1. Go version, using pion/webrtc
  2. Java version, using whatever that Guardian Project library is probably

Phase 1: Manual Mode

Components required

• Browser Extension
• Javascript Import

Phase 2: Bridged Prototype

• Native Proxy, Go Version

Phase 3: Router Incorporation

• Native Proxy, Java Version

A larger set of default bookmarks in their own directory would probably be good. Stuff like the forums, zzz's forums, gitlab, stats, identiguy, postman, echobot test, fingerprint test, etc.

Running extension 0.70 with firefox esr 68.6.0, i2p+ and muwire plugin
https://open.lbry.com/@Danrobi:b/bug-extension-0.70-2020-03-24_02.02.27:1