Either use the --proxy
option of yt-dlp, or use torsocks
to transparently torify any application.
0v0
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.
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.
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.
Try perhaps the solution in https://unix.stackexchange.com/questions/648084/docker-interface-tears-down-wifi-internet
Try removing all the superfluous default routes.
I think glider can do this, with -strategy rr
(Round Robin mode). I have not used it in this way myself, so you might need to experiment a little. Proxychains can also do this, but it doesn't present a socks5 interface itself (it uses LD_PRELOAD
, so it won't work everywhere).
Argon2id (cryptsetup default) and Argon2i PBKDFs are not supported (GRUB bug #59409), only PBKDF2 is.
There is this patch, although I have not tested it myself. There is always cryptsetup luksAddKey --pbkdf pbkdf2
.
Options:
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 bytorsocks show
in/etc/ld.so.preload
.