colluding_sites_attack VS Onion-in-Container-Browsing-Mode-Firefox

A lot of that I already know how to do, but I am hesitant to encourage potentially harmful Tor behavior. In particular, the Tor isolation expectations would end up being different, you would end up with 2 cookiestores and one circuit(I think). When I'm more sure it is safe to do so and that I can set those expectations correctly, I'll add: https://github.com/eyedeekay/Onion-in-Container-Browsing-Mode-Firefox and start distributing it in the Add-On store. WebIRC is almost all the way ready, too. WebTorrent is still down the line because I've not had time to work out all the stuff with negotiating between browsers with STUN and TURN and whatnot, and making all that work inside of I2P has been a little confusing, and it sometimes seems like it must be pointless and I'm clearly missing something because your I2P address is... just your I2P address, there is never going to be any NAT traversal or anything like that. The logical thing is that I just don't need a lot of it, and I've not quite figured out what parts yet. TLS certificates are just more elaboration in the wrapper-launcher parts. Update itself via Bittorrent is tricky not because I don't know how to do it but because I don't know how to reconcile all the potential ways I could do it yet.

I haven't released it to the general public yet primarily because I want to respect TPO/Mozilla's schedule with FuSiOn, but the solution to deal with the cross-network colluding sites attack and while also having a mixed browser already has a proof-of-concept here: https://github.com/eyedeekay/Onion-in-Container-Browsing-Mode-Firefox. It's not as well maintained as my other plugin because I'm watching and waiting with regard to Mozilla/FuSiOn, but what the ideal solution will look like will have the two browser extensions, working in tandem, and the underlying Firefox configuration defaulting to the Tor client. I2P traffic gets sent to the I2P container and the proxy settings are applied per-container, .onion traffic goes to the Tor container and the proxy settings are applied per-container and the container looks like a different Tor client, both extensions drop requests across containers, global(The Tor proxy) handles traffic to non-hidden services. At least, that's the broad strokes of the proxy configuration.