But then you would need to first download the file, know the location of the downloaded file, do the comparison and when that files download another torrent which then will hopefully work.

That might be quite some overhead and might confuse users as they thought ted they downloaded an episode but ted threw it away and couldn't find a good other torrent. I think it would be better if we could "see" in advance if a torrent is good or not. Which might be impossible btw

I think you are missing the point.

1. You do not know that TED has downloaded the file untill TED has verified that it is not a fake.

2. You would normally have to reset TED and hope, or find a torrent manuallt. Either way, the overhead will be the same only now you wasted your time too.

3. TED can remember hashes that it verified as fake. Then it can avoid re-ownloading the same file. This reduces the hoping/guessing and would allow you to come home and find a file that can be played immediately.

4. There would be no additional downloads or installs. Under Linux, you can add imagemagic or ffmpeg as a dependancy. Or, as with windows, you can bundle ffmpeg into the TED release if need be. Maby ffmpeg can be ported to java, if it has not already been?

My point is, we can detect this so we should.
Imagemagic is, as far as I can tell redistributeable, bith as a whole or in parts.

I don't follow you here. Ted doesn't download the file, ted just downloads the torrent of the file and passes it to your favorite bittorrent client. That client will download the file for you. So once ted has downloaded the torrent it loses control over the rest of the process.


True, but at least you then know what is going on. That was the point I was trying to make. If you want to redownload the file it should be made very clear to the user that ted has done so.


And my point is that it is not so easy to detect this. You've to know where your client downloads the episode. You can not delete that file as it is under the control of the client which has locked the file. You've to set up a monitoring system which constantly checks if a file is already downloaded and if so that it will perform the procedure as described by you.

I was implying that you'd ofcource keep track of the file via the download folder of your client. I also assumed that the client was capable of moving finished torrents to a "done"-folder to distinguish them from stuff being downloaded.
Torrents moved to done are not locked by for example uTorrent.
It opens the file, reads what it needs for a buffer to seed, then closes it again.

I never said that part would be simple, but doable.

Implementing it in uTorrent won't work as TED needs to redo the effort anyway.

Maybe its doable but it'd end up looking and working like a dogs breakfast.

And, IMHO, probably not very robust.

Bringing this back from the dead because it's got unbearable again lately. The thing is, the fakes I'm getting ALWAYS include a file called HDTV.nfo so if there's a way to check the files they're easy to exclude. Problem is that once they hit a torrent app it's too late, Ted has advanced the schedule and I come home from work to have to go manually set it back