They are closing all issues citing piracy https://github.com/yt-dlp/yt-dlp/issues?q=is%3Aissue+piracy+is%3Aclosed

It used to work last year 😀 . The debian yt-dlp version: stable@2023.03.04 is giving a different error

ERROR: [Einthusan] 9r1H: 9r1H: Failed to parse JSON (caused by JSONDecodeError("Expecting value in '': line 1 column 1 (char 0)")); please report this issue on https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using yt-dlp -U

this update broke my installation :(. I have not updated it in a while. Now I have to rollback until I fix this. Hope the backup will work. EDIT: It was the reverse proxy. Check the developer notes before updating.

Thanks for the nice writeup. Can you explain why you have these rules.

PostUp = iptables -t nat -A PREROUTING -p tcp -i eth0 '!' --dport 22 -j DNAT --to-destination 10.0.0.2; iptables -t nat -A POSTROUTING -o eth0 -j SNAT --to-source SERVER-IP PostUp = iptables -t nat -A PREROUTING -p udp -i eth0 '!' --dport 55107 -j DNAT --to-destination 10.0.0.2;

What happens if you remove it ?

Immich having accounts+SSO is the single best feature IMO. Thanks for your thoughts on the topic.

Why do people repair their polish ??

@torvalds@social.kernel.org

I see the option now, Thanks 😄

Thank you! I am making a comment so I can find this thread later.

Yeah all Indians are vegetarians and look exactly like this /s

Should replace it with a markdown editor

Now I have to self host mastodon to join the party 🥳