Arvid Norberg
Arvid Norberg
If you want to detect dishonesty, you could compare the number of bytes uploaded to the number of pieces the peer claims to have. But that's also risky; earlier versions...
I see how this works now. it makes sense
now might be a good time to retry this, on top of latest `RC_2_0`
since some filesystems are case insensitive, libtorrent detects filenames that would collide on such systems and renames the duplicate files or directories. This is a feature that enables Mac and...
By default, both windows and MacOS are case insensitive. I think it's fair to say it's a niche feature. The issues on the opposite side are: 1. increased complexity in...
> Much easier for the end user would be to see a not a warning but an error message when user open a torrent file with case sensitive names and...
do you have a suggestion or vision what a proper solution would look like? For example, if there was a flag where you could disable all (or most) filename renaming),...
detecting whether a filesystem supports case sensitive filenames or not is not the main challenge. The main challenge is to come up with rules and behaviors that are intuitive and...
It seems somewhat reasonable. However, I assume there's not really any privacy expectation when authenticating this way, is that right? It is possible to expose S3 files as just regular...
The github workflow for building and publishing the wheel has not been working for a while. I triggered a build for 2.0.10 here: https://github.com/arvidn/libtorrent/actions/runs/8579717727