Opened 12 years ago

Closed 12 years ago

#2633 closed Enhancement (invalid)

Hashcheck database feature for collectors

Reported by: bussdriver Owned by:
Priority: Normal Milestone: None Set
Component: Transmission Version: 1.76+
Severity: Normal Keywords: hash
Cc:

Description

How about maintaining a database of hashes (copy existing code) to search when adding new torrents to avoid duplicate downloads EXCEPT unlike your current opened-torrent database, this would consist of torrents NOT loaded into transmission.

This would lower resource use; only when new torrents are added would the DB need to be accessed and there wouldn't have to be a whole paused torrent record in memory and cluttering the GUI.

Optionally, removing a torrent file could get its hash added to the known torrent database.

This is just a simple leverage of existing features; it has some use in terms of collecting some stuff; possibly some future use for importing lists of BAD torrents (in which case this db would get huge and need to be file based like a berkley db hash) and possibly could be used as part of a ban policy (not that those work.)

More useful would be HASHING individual files in the torrents instead of just the whole torrent. This would be much more useful in collecting/consolidating things- then you'd also have to resolve collisions with the user: a link/alias in the download, copy the duplicate file, re-download, or just skip duplicates (because the duplicate may not exist any longer but the hash is still maintained.)

For a shared transmission "server" something to limit how different people are downloading duplicate torrents (which is handled now) or slightly different torrents (which is not handled now.)

Change History (1)

comment:1 Changed 12 years ago by charles

  • Resolution set to invalid
  • Status changed from new to closed

There's a lot I don't like about this ticket.

Mostly this seems like the kind of feature that a server farm might want -- I can't think of any plausible use case for end users to need this kind of functionality. It doesn't belong in the end-user application, but rather a plugin for libtransmission. And that moves us from the end-user realm ot the commercial realm, so that's not a feature that's going to happen for free, even outside of the official releases.

Also you can't hash individual files because BitTorrent? doesn't work like that. You'd have to compare the checksums of every piece in the file.

Note: See TracTickets for help on using tickets.