Look at the very least you should write in the blogpost clearly which parts are generated by LLMs, so your readers can decide whether to trust them.

Idk man, it seems pretty irresponsible to me to write a blogpost with stuff that you got from ChatGPT without understanding it. People will assume that if you wrote a blogpost on this then you know what you’re doing. ChatGPT gets stuff wrong all the time, and we’re talking about firewall configuration here. If it misconfigured some stuff it could leave you and your readers vulnerable to all kinds of shit.

In this case it seems to me that (luckily) there’s just a bunch of redundant routing, but the next time it could be leaking your and your readers’ torrent traffic out of the VPN tunnel, leaving you vulnerable to legal repercussions for piracy.

Please don’t authoritatively post stuff that you got from the automatic bullshit generator without understanding it.

Nice, I recently went through the same struggle of setting up this configuration based on that LinuxServer post. My main nitpick on this is that automating the ip route configuration for the qBittorrent container is a pretty important step which is not explained in the post. Leaving any manual steps in any Docker setup is pretty bad practice.

Since you’re using LinuxServer’s QBT image a good way to do this is to make use of their standard custom init scripts. You can just mount a script with the ip route commands to /custom-cont-init.d/my-routes.sh:ro on the container and it will be run automatically on each startup.

Another nitpick is that the PostDown commands in the wireguard configs are useless since you’re running them in Docker.

I had high hopes when I tried it out but frankly it’s been almost unusable for me. Terrible performance, laggy UI, plenty of bugs, long loading times for songs…

I don’t know if something in my mobile environment was messing with it but I use quite a few indie FOSS apps still in beta and none of them worked as badly as Spotube did. I’d love to go back to it if it improves, but for now it’s just not worth the UX pain.

Edit: forgot to mention. The idea of sourcing tracks from YouTube is cool but causes loads od trouble in practice. I’ve found remixed versions streamed as the original, tracks with the intro from the music video, tracks with sound effects from the music video, and tracks that just cannot be streamed cause they aren’t on YouTube. I know there’s a feature to pick which version to stream, but it’s quite a bit of UX friction and it didn’t work often enough to be a showstopper.