

Not at all, there’s legal risk if you’re hosting your blurays. Cloudflare even explicitly forbids such use. VPN or nothing imo.


Not at all, there’s legal risk if you’re hosting your blurays. Cloudflare even explicitly forbids such use. VPN or nothing imo.


I wanted the same thing with Kubernetes and ended up using FluxCD. Highly recommend it. It basically syncs a git repo to the cluster, so you just push to github or whatever, and it auto applies the changes you pushed. Also, llm models tend to be good at teaching this topic and even writing yaml files for it, so the initial learning curve was not bad actually.
Now I’m exploring doing this even better with this template: https://github.com/onedr0p/cluster-template
The writing has been peeling off of the wall since the channels were sold


There are lots of answers here already so I’ll just comment on the trackers detecting seeding.
Insofar as that’s not directly possible. Torrents are peer to peer, and that’s not some kind of code word. Your client is literally talking to someone else’s client. No server in between the two, no gateway, or anything (meaning one of the two clients need to have a port open too!). So a tracker cannot measure the amount of data flowing between two clients (aka. peers).
So the way trackers know how much you upload is that your client self reports that to the tracker. The tracker has no way to directly check the ground truth, other than relying on what the other client is saying about how much it downloaded from you.
Old or unknown torrent clients may have bugs in them which cause the client to report incorrect data. When a client overreports (reports more than it actually uploads), that breaks the equation that private trackers rely on to make sure there’s enough users on a torrent. So by using an old or unknown client, you might inadvertently damage the functioning of the tracker.


c/lostbots? What is even going on - podcast?


Oh I’m not saying any use of ai is immediately bad, but as a dev I would want the author of the stuff I use to actually understand the whole codebase. I’ll try it out when I get some time to deploy it.


How much of the codebase do you write by hand?


You’re pretty much describing Tailscale with an exit node on the VPS. If the purpose of the VPS is to make their traffic not come from your home, you can omit the VPS entirely as Tailscale only routes through the VPN when reaching services also on the VPN.
Edit: to self host it, look into Headscale, but the default, hosted control server works well too.


Depending on your specs, I don’t think you need to buy hardware. You can scale later if you run out of resources. This is how I’d separate your stuff:
Edit:
Not sure about that, I think it’s more just that they don’t want people streaming terabytes of traffic through their edge.