However, a torrent to be duplicate, there must be available another original. That wouldn't be the case here, because the subject is to prevent easy jump-on by members who got the file from other places.

But if these snatchers, who seeded for the torrent I uploaded, used a, for a lack of better term, ghost torrent, a dead torrent which they reseeded or worse a torrent which is not is not from the site, then I feel that is unfair.

There are two additional ways of guarding against this activity; however both have problems.

• Rendering the clip into another format (i.e., mp4 to wmv, etc.)
  Caveat: This will degrade the quality of the clip.

• If the file is an mp4, you can change the extension without rendering it to m4v. This will stop those and their torrent clients who will see it as another format.
  Caveat: It will only slow down those who know it is not.

If your torrent would be a 100% duplicate, I mean with that same hash, than an existing torrent (dead or not), the upload script won't allow the upload. If it is for the same file(s), but got a different has, the system won't recognise and let it pass.

Having someone seed more than 1 GB in an hour requires ~290 KB/s upload rate. That is possible for seedbox owners. They could indeed jump-on a torrent if they have the file from somewhere else, using the re-seed procedure(s).

I think jumping-on an initial seed, while it is seeded, is unfair.

However, jumping-on an abandoned initial seed or an old dead torrent or a reseed requested torrent is welcome.

It is extremely difficult to monitor jump-ons and determine what case it is, because that would require real time surveillance of all torrents, simply next to impossible with reasonable system resources.