Opened 5 years ago

Last modified 2 years ago

#1357 assigned enhancement

Bote peer management

Reported by: user Owned by: str4d
Priority: minor Milestone:
Component: apps/plugins Version: 0.9.14.1
Keywords: I2P-Bote performance Cc:
Parent Tickets:

Description (last modified by str4d)

old unresponsive peers should be expulsed from the list as the lock up much, while active peers be exchanged between connected peers and also if an unknown peer connects to you, you save his info.

ref: http://forum.i2p/viewtopic.php?t=11477

normal kad is about finding files n downloading a file from a source that we have no influence on whether it goes off or stays on. In Bote we cannot influence the other's behaviour either, but there's a difference: we don't want their files, we want to upload ours, so some better profiling of reliability of kad peers (storage nodes)should take place, this could greatly improve reliability without raising redundancy.
Yet for obvious reasons not exclusively the best performing nodes should be chosen, but alwaays have a small margin of "normal" ones too.
profiling factors could be general reachability/responsiveness, received own mails (so they do not block my dest), and received receipt confirmations (so they do not block/censor the destinataries), automated test mails, overall uptime (time we know the node). Sounds easier than it is, though. If only one of my destinataries is blocked, the mails to others will still arrive and I'll get receipt confs for them and hence a positive evaluation of the storage node, even though it misbehaves. Maybe if another storage node gives me the confirmation and the one in question is closer to the key and does not, then punish strongly - not an immediate ban, but a quite noticeable punishment.

Subtickets (add)

Change History (6)

comment:1 Changed 5 years ago by str4d

  • Description modified (diff)

comment:2 Changed 5 years ago by user

might also be of importance in light of android users.
maybe they'll not be online long in order to save battery or data transfer.
while using those as storage nodes would increase entropy it would also make things much more unreliable and latencies much bigger.

comment:3 Changed 5 years ago by zzz

  • Owner set to HungryHobo
  • Status changed from new to assigned

comment:4 Changed 4 years ago by str4d

  • Keywords performance added; peer management removed
  • Milestone 0.9.18 deleted

comment:5 Changed 2 years ago by zzz

  • Owner changed from HungryHobo to str4d

comment:6 Changed 2 years ago by str4d

Migrated to https://github.com/i2p/i2p.i2p-bote/issues - I will close these tickets as things are resolved rather than right now, but please make future comments on GitHub?.

Note: See TracTickets for help on using tickets.