Either use the --proxy option of yt-dlp, or use torsocks to transparently torify any application.

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.

You can take the package from the Ubuntu PPA, which is generally updated quickly, and rebuild for Debian using the instructions here.

Edit i2psnark.upbw.max in i2psnark.config (this can be in a number of locations based on install type and platform - just search for it).

Or you can remove the maxlength and size attributes from the text input, it will save just fine.

Try removing all the superfluous default routes.

Could you run sudo lshw -C network and post the output for the wireless interface?

We have those on I2P already, see tracker2.postman.i2p for example.

Have you tried running tcpdump / wireshark on another device in the network when this happened?

I'm not on NixOS, but I have a decent working knowledge of Tor.

Not quite clear on what you're trying to do, are you trying to run a relay, or just connecting to the Tor network and pointing your browser to the socks proxy?

Arti (the official Tor implementation in Rust) is not a complete replacement for the Tor C implementation yet. Hidden service support is disabled by default (due to the lack of a security feature that could allow guard discovery attacks), and bridges don't work either. If you don't understand Tor very well stick with the old router.

I occasionally experience the same thing. When this happens, it appears the jwt token is not sent with the initial request (thus appearing to be logged out), but it is sent with api requests on the same page (unread_count, list, etc.), so the cookie is not lost (document.cookie also shows it). Sometimes refreshing again fixes it, but I haven't yet found a good workaround. I'll experiment a bit next time it happens.

But you can do this.