[Feature Request] Client side file ban list

[MRx]

Hi,

I'm collecting bootlegs and live recordings of several bands. Now i often have the problem i download dupes f.e. less quality, other ripper (files are not having the same hashes somehow), not the biggest problem when it happens the first time. But if you delete those files and don't share them you are able to dl them agian without any problems, only sharing them would protect that.
It would be really nice if i could get those files on some kind of internal ban list because i don't want to dl them again but i don't want them to share either.

I hope you understand what i mean.

[Mickeba (mickeba)]

I want this too, for some reason I keep downloading those files that I have deleted because they had flaws over and over again...

Since I already hashed them once and they are still in my hashdb, why can't dc++ exclude those files from downloads too?

[Jota.Ce (psidtg)]

Or... could DC++ mark those files as "Downloaded in the past" ???

(eMule-ing DC++) xDDDDDDDDDDD (but i hate ed2k)

[Neil Harding (8-launchpad-nharding-co-uk)]

I was thinking of adding database type facility to filelist, where you could add shares that would be marked as external. So you could index files on backup DVDs and when searching it would say File:xxxx is on DVD 320. There would be another tick box, Hide Files In Share, Hide Files on External Storage (name would be different), the files there would not get auto refreshed and would stay in the filelist, to delete files you could have a deleted directory, and move the files there, and then it would say File:xxxx is on C:\Deleted (or wherever you decide to put them).

[poy (poy)]

have a look at the "Queue > Keep finished files in the queue" setting.