This is possible, after all, legwork.i2p is based on YaCy. I'd recommend taking a look at the YaCy and Tor guide, and use it as a template. Where they create a Tor hidden service, create an I2P server tunnel, and where they proxy YaCy to Privoxy just proxy directly to I2P's HTTP proxy.
0v0
Options:
- Just start it from the terminal with torsocks
- Use application-specific proxy settings
- Since
torsockssimply uses LD_PRELOAD, you could try to make this apply globally by adding the torsocks library to ld.so.preload. Just put the path returned bytorsocks showin/etc/ld.so.preload.
Either use the --proxy option of yt-dlp, or use torsocks to transparently torify any application.
Running nyx just shows some of the circuits (guard, middle, exit) but I seem to have no way of associating those circuits with fetchmail’s traffic. Anyone know how to track which exit node is used for various sessions?
In nyx, on the first page, press e and enable STREAM events. These have the following form:
[stream id] [status] [circuit id] [hostname/ip]:[port] ...
Find the correct stream based on hostname/ip, then you can cross-reference the [circuit id] with the items on the Connections page.
This element is never generated as a candidate in the picker, probably a quirk of this specific site. I just looked at the DOM and saw this related element next to the dark mode button.
Also add acoup.blog##.darkmode-layer to your filters.
You can take the package from the Ubuntu PPA, which is generally updated quickly, and rebuild for Debian using the instructions here.
fn foo(x: i32) {
match x {
const { 3.pow(3) } => println!("three cubed"),
_ => {}
}
}
But it looks like inline_const_pat is still unstable, only inline_const in expression position is now stabilized.
It's because it has to work in pattern contexts as well, which are not expressions.
It looks like the image proxy returns a
Too wideerror for some images, e.g. the one in OPs screenshot