0v0

Options:

• Just start it from the terminal with torsocks
• Use application-specific proxy settings
• Since torsocks simply 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 by torsocks show in /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.

singlelogin.re still worked for me recently.

Source

It's the Schmidtstedter Knoten in Erfurt.

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.

https://devblogs.microsoft.com/cppblog/stdany-how-when-and-why/

According to Wikipedia:

In March or April 2023, it dimmed to magnitude 12.3. A similar dimming occurred in the year before the 1946 outburst, indicating that it will likely erupt between April and September 2024.