[Feature request]Origin isolation #1302
Description
Hear me out, the way I see it i2p could become gain a lot more traction for privacy and anonymity if it had stream isolation on both sides.
Now i2p+ as I understand it has destination isolation but it could reach even greater hights in my opinion if it had origin isolation as well. Look at it this way, rather then creating a different http/https proxy bound to a different port for each origin, while still possible isn't as versatile as origin isolation. Assume a family router with i2p where everyone connects to, everyone would receive a different IP address no matter which device they used even when they visited the same websites, or even better (and the reason I thought about it) the i2p community isn't a stranger to QubesOS I am sure, assume you could connect multiple virtual machines to the same router and acquire a different IP address in any use case possible would limit the identity exposure to almost 0%. At the end of the day origin isolation + destination isolation would make wonders.
I assume I am not the first to think about this and that is also why I though about bringing this up since I couldn't find any discussions on this topic, the only reason that I would assume this has not been implemented yet is to keep the general population from dragging down the network by trafficking everything through i2p. What are your thoughts? I think I can definitely achieve this just about transparently with a few firewall rules in an hour or two at most to pass every test and avoid any leaks but I think this could find a place in the i2p+ source code for sure, if anyone has made a java plugin for this I'd love to see it, the only thing I fear is yet again that this feature could become too popular in too many wrong hands and exhaust the network as I could almost expect someone to prepackage this into a router and sell it.