You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
thanks for this cool repo,
note:
the auto-weighting equation for upload bandwidth repartition is smart, but unfortunately does not take into account partial leecher (people who partially downladed the torrent and ignored some files in their client (frequent in torrent pack), thus they are acually seeder but reported as leecher), which could lead to a massive upload on a small torrent full of only partial leechers, thus leading to a tracker detection and a ban.
For the next version written in Go, I would humbly suggest a per torrent speed selector, which would allow setting those to 0 for upload speed (while keeping them for H&R avoidance).
The text was updated successfully, but these errors were encountered:
I understand your point, but this is a difficult problem to solve, i'll keep it opened as a possible improvement.
But it's unlikely to be implemented any time soon.
thanks for this cool repo,
note:
the auto-weighting equation for upload bandwidth repartition is smart, but unfortunately does not take into account partial leecher (people who partially downladed the torrent and ignored some files in their client (frequent in torrent pack), thus they are acually seeder but reported as leecher), which could lead to a massive upload on a small torrent full of only partial leechers, thus leading to a tracker detection and a ban.
For the next version written in Go, I would humbly suggest a per torrent speed selector, which would allow setting those to 0 for upload speed (while keeping them for H&R avoidance).
The text was updated successfully, but these errors were encountered: