it’s hard to keep track of everything, especially considering upgrades.
In that sense it’s similar to the ‘symlink’ request. That all makes it a 1% feature that has a myriad of scenarios that end up in disaster that has to be dealt with one way or another. Upon upgrade, episode files would be replaced, which would mean we have to tell the torrent client to delete or move the file to the recycle bin.Also, we can’t tell the download client to download directly to the series folder, it would be odd, and the naming/numbering would be off, especially hazardous for series with theXem mappings.Keep track and guard against unintended moves across a network, coz the torrent client wouldn’t be able to seed.(read: telling the download client to look at another location for file, esp when the filename changes). It’s hard to reliabily implement ‘moving’ the seeding files for all torrent clients.The point is that it’s not easy to implement.
Most ppl are concerned about disk space, not disk IO. A SSD has a significant lifespan in terms of writecycles.Īnd btw, if you move it across drives, you have the exact same number of writes as a copy. ‘doubling’ is hardly significant when talking about IO itself. Effectively doubling all disk operation by copying everything then that can significantly reduce the life span of drives, especially if it is a solid state drive
