[Feature Request]Mark Seeding as Downloading

[noian]

I know that Concast is sandvining torrents, and Deluge has been one of the few softwares able to still upload (although significantly less). Although I'm not a programmer, so I don't know the feasibility of doing this, but would it be possible to add a option to mark all torrents "completed" and seeding as downloading? It would save the time of copying+pasting, then deleting the copy where deluge looks for in order to seed as when your "downloading" a torrent. That is since comcast sandvine decides to not bar you from uploading (as much) when it thinks your still downloading the torrent (ex when your copy isn't complete). I would think it would be easier to implement than some sort of enhanced security feature on trackers and such to simply have the option to continue "downloading" since it would only be on the torrent manager side

I guess from a technical side, It wouldn't actually be downloading, rather deluge notes it is complete, but treats it when its sending data as incomplete (so lying basically) and randomly requests some peice from others that the user already has, and discards the data (requesting less often than uploading, so it pays off). It would sort of mess up share ratios and things, but wouldn't the ability to at least be able to upload with a few minor bits of data discarded be better than not being able to upload at all?

[deadlikeoscar]

That would probably get Deluge banned on every private tracker there is. Also, they already found a way around Comcast. It probably won't take long to trickle down to Deluge.

[noian]

Ehh..I guessed something like that might happen. Worth a shot though for ideas.

Also, I read the so called "fix" on torrentfreak. Didn't impress me much. Might just be my lack of knowledge, but it seems that its merely a "rename" file transfer name or something like that (which I must admit might work for a while) but doesn't seem like a long-lasting fix since it seemed rather easy for comcast to change the settings to re-block the new file "name"

I never got why all of the clients didn't just implement a RST filter, I mean they found the code to do it and it worked, but the argument was that if not everyone had it, it would be useless. If all clients did implement it though, it wouldn't be useless. Auto-update would have spread the fix to a majority of people, and the new fix seems to require a client update as well, so..

At least I can *sometimes* get a total of 30kib/s up from the sum of 3 torrents seeding with deluge, lucky to even get 15b/s on azureus.