4·
5 days agoGluetun has an example for qbt port forwarding integration on the wiki. I’ve been using this for about a year and some without problem (to my knowledge at least). I’ve seen that gluetun will retry setting the port in qbt for a while to work around the timing issues.
They also mention a bug in qbt when changing the port, which is also covered in the example.
Edit: I see you’re already using the port down script. Not sure what else could be the root cause if you’re running on an up to date container version :/
In theory: Yes, future works are not yet part of the training data.
In practice: It takes months or years for an open source project (or any new technology) to take off and be considered valuable.
The other argument relies on said tech organization doing the right thing, and spending resources on training their own model (years and 100+ million) instead of including the cost of the lawsuit and pending fine in their cost/benefit analysis. I’m not aware that any such tech organization (with the means) exists.