If you have an overall 2-3% failure rate, I am not sure you are doing it right 🤷♂️
If you have an overall 2-3% failure rate, I am not sure you are doing it right 🤷♂️
Brave search got an option for that.
If qBittorrent is not complaining about file errors you are in fact still seeding the original file. Especially on Linux file systems a file keeps being referenced as long as at least one application is still accessing it, regardless if you delete, rename or alter it. Once you close qBittorrent the ‘old’ file will be dropped though.
And at that point it won’t be seeded anymore as it does not match the checksums that are stored in the .torrent file or were retrieved via a magnet link. If the client is not broken it should not be possible to seed corrupted or altered files.
Well, how about having a local API and have no calls at all to your cloud infrastructure? Probably too easy and you cannot lock people into your ecosystem.
Until it gets through, there’s nothing preventing them from doing it times and times again.