So in summary…
old, last revision really using using privoxy:
- i2p webinterface functional
- i2p eepsites functional
- clearnet broken
- onion functional
current revision without privoxy [1]:
(this at time of writing)
- i2p webinterface functional
- i2p eepsites functional
- clearnet functional
- onion broken
Correct?
[1] privoxy get installed but not configured so effectively doing nothing.
Confirmed. This is true. That is also what I described here:
Tor Browser Customization using user.js (for example for i2pbrowser)
The same in other words:
network.proxy.socks_remote_dns set to true is now hardcoded directly by Tor Browser and it always reverts to Tor Browser default after Tor Browser restart.
i2p inside Whonix-Workstation instructions - both old and new - require network.proxy.socks_remote_dns set to false.
Unless the user re-applies these Tor Browser settings all the time which is very bad usability, I don’t think we currently have a good solution with or without privoxy.