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

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/

You can give chisel a try. It tunnels all traffic over http/https, and the client can then create port forwards, just as with ssh, to access other services.

Yes, for example, syncing on a kernel panic could lead to data corruption (which is why we don’t do that). For the same reason REISUB is not recommended anymore: The default advice for a locked-up system should be SysRq B.

https://linux-tc-notes.sourceforge.net/tc/doc/cls_u32.txt:

The base operation of the u32 filter is actually very simple. It extracts a bit field from a 32 bit word in the packet, and if it is equal to a value supplied by you it has a match. The 32 bit word must lie at a 32 bit boundary.

Try perhaps the solution in https://unix.stackexchange.com/questions/648084/docker-interface-tears-down-wifi-internet

Try removing all the superfluous default routes.

You should not torrent over the tor network, but you can torrent over the I2P network. qBittorrent even has experimental I2P support built in.