Opened 5 years ago
Closed 5 years ago
#1280 closed enhancement (fixed)
i2psnark DHT: Store seed/leech status
| Reported by: | zzz | Owned by: | zzz |
|---|---|---|---|
| Priority: | minor | Milestone: | 0.9.14 |
| Component: | apps/i2psnark | Version: | 0.9.12 |
| Keywords: | Cc: | ||
| Parent Tickets: |
Description
http://zzz.i2p/topics/1613 comment 4:
It would be good to store the seeding/leeching state of a peer when announcing, and allow get_peers to specify whether the caller is a seed/leech itself (and return the peers' seed/leech states too). There is little point in returning seeding peers to a peer that is a seed itself (as per normal tracker announces).
Subtickets
Change History (3)
comment:1 Changed 5 years ago by zzz
comment:2 Changed 5 years ago by zzz
seed=1/0 added to DHT announce in 9ac66debb8c9186d443c2549502d7b255e24ab4a i2p.i2p.zzz.test2 to be propped for 0.9.14. This provides compatibility for other clients supporting this standard.
Ignored on receive, for now (not stored). Still not clear if it's worth it.
comment:3 Changed 5 years ago by zzz
- Milestone changed from 0.9.16 to 0.9.14
- Resolution set to fixed
- Status changed from new to closed
above propped in 0.9.13-2.
See zzz.i2p thread for additional info on why Vuze does this.
'noseed' sent and seed/leech status stored in DHTTracker in 0.9.13-3
See comment 11 in link above for more info. Libtorrent supports this also so it's an unofficial standard.
But I don't see how this saves much bandwidth. Seeds don't have any use for other seeds, but they don't have any use for non-seeds either. An i2psnark seeder never initiates a connection.
So the dht tracker will just respond with a bunch of non-seeds. No better, unless the number of non-seeds is less than the max number of peers to send.