Opened 2 years ago
Last modified 23 months ago
#2083 open enhancement
Implement (DHT) search in I2P Snark
| Reported by: | Reportage | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | undecided |
| Component: | apps/i2psnark | Version: | 0.9.32 |
| Keywords: | i2psnark dht search | Cc: | |
| Parent Tickets: | Sensitive: | no |
Description
Currently there is no method for searching the DHT space for torrents.
Implementing a search feature that parses results in I2PSnark, both for
DHT torrents and, optionally, configured trackers with a search facility or
i2p torrent-specific search engines e.g. torrentfind.i2p, would be a useful enhancement.
Subtickets
Change History (1)
comment:1 Changed 23 months ago by
| Component: | unspecified → apps/i2psnark |
|---|---|
| Status: | new → open |
Note: See
TracTickets for help on using
tickets.
Discussed in http://zzz.i2p/topics/831 and also, I believe, in the big Vuze thread http://zzz.i2p/topics/1613
For an in-BT DHT solution, we'd want to implement whatever Vuze (now BiglyBT) does. I believe they have some proprietary and poorly-documented solution, and don't want to propagate it. At least that was the case for the DHT chat, see parg's comments about it in the thread.
For some sort of API use of some external service like torrentfind.i2p (which I'm unfamiliar with), we would need to hear from the op of that service and understand the terms of use and contents of that service.
For any in-i2p search we've considered (not just for torrents), the content is problematic, and we've decided not to do it, it's too much of an ugly mess that we don't want to put into our console. I doubt we'd make a different decision today, but it's worth talking about again, I guess.