Paul Walker

At the highest level, either the .torrent file or the magnet link metadata needs to be acquired first. This would be an extra step after the current RSS fetch. After...

It's a pretty simple request that I'd estimate at about 10-20 lines of code and documentation. I'd just bang it out myself, but I thought there might be some others...

Well, it sounded interesting so I went ahead and did just that. It's in production right now on my system and working as desired. Have a look.

Certainly, I'll give it a whirl.

When we do this at share_limits.py:187 if group_config["limit_upload_speed"] == 0: group_config["limit_upload_speed"] = -1 ...we lose the ability to do this at share_limits.py:277 self.set_tags_and_limits( torrent=torrent, max_ratio=group_config["max_ratio"], max_seeding_time=group_config["max_seeding_time"], limit_upload_speed=group_config["limit_upload_speed"] if group_config["limit_upload_speed"] else...

The last set of tests were a success, @bobokun. The group upload speed was properly apportioned across the group entries and groups with limit_upload_speed set used that instead (preferred over...

Since each group is evaluated separately, it seems appropriate to have it in the group_config and assigned in update_share_limits_for_group where it is already being assessed.

It is fair to say that you only really need one speed defined in the group config and that it would contain either a limit speed or a group limit...

Yes, that sounds cleaner than maintaining both and trying to keep them meaning what you think they mean as they mutate.

At share_limits.py:193 group_config["limit_upload_speed"] = round(group_config["limit_upload_speed"] / len(torrents)) is getting executed for each torrent rather than once per group, resulting in the wrong values being applied for the 2nd evaluation and...