| | 2 | |
| | 3 | == Groups == |
| | 4 | |
| | 5 | * a new level of control for torrents |
| | 6 | * sits between global and per-torrent settings |
| | 7 | * defines bandwidth settings |
| | 8 | * should it also define move completed locations? |
| | 9 | * can a torrent belong to multiple groups? |
| | 10 | |
| | 11 | == Tags == |
| | 12 | |
| | 13 | * tags torrents based on pattern matching |
| | 14 | * can match against tracker or filenames |
| | 15 | * a single torrent can have multiple tags |
| | 16 | * this is going to require a bit of thinking |
| | 17 | * by itself tags just allow easier filtering |
| | 18 | |
| | 19 | == Organiser Plugin == |
| | 20 | |
| | 21 | * tag-based organiser |
| | 22 | * rules are based on tags |
| | 23 | * allows for moving torrents on completion, possibly renaming / restructuring |
| | 24 | * should it handle linking tags <-> groups or should this be done in the core? |
| | 25 | * organiser could simply link a tag to a group to achieve custom move completed paths |
Deluge
