Either use the --proxy
option of yt-dlp, or use torsocks
to transparently torify any application.
Either use the --proxy
option of yt-dlp, or use torsocks
to transparently torify any application.
singlelogin.re still worked for me recently.
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.
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 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).
You should not torrent over the tor network, but you can torrent over the I2P network. qBittorrent even has experimental I2P support built in.
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.
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
.