&zzz
+R4SAS
+Romster_
+Stormycloud
+acetone
+eche|off
+nilbog
+orignal
+postman
+snex
+sourceress
+wodencafe
Arch
Daddy_I2P
Danny
Gully
Irc2PGuest19485
Irc2PGuest31672
Irc2PGuest44504
Irc2PGuest93219
NiceBoat
Onn4l7h
Over
Sisyphus
SlippyJoe
Teeed
Yotsu
Zapek2
aargh3
ahiru_
ananas2_
anontor
b3t4f4c3___
bob___
cims__
duanin2
leopold
makoto
marek
marek22k
n2_
not_bob_afk2
o3d3_
poriori
profetikla
qend-irc2p_
r00tobo_BNC
rapidash
shiver_
solidx66
sublimia
test3847473
uop23ip
urist_
user45
w8rabbit
x74a6
zelgomer
obscuratus
eyedeekay: PeerSelector is a more involved issue than I first appreciated.
obscuratus
I was reviewing the FloodFillPeerSelector class, and I couldn't see anywhere where it understood how to use any other netDb except for the primary floodfill netdb.
obscuratus
On the plus side, things seem to work OK dispite this being somewhat borked.
obscuratus
We may need to pivot to something like relying on trip-wires for RI coming in the Inbound Message Distributor.
obscuratus
As a work-around, on my testing network, it wouldn't be difficult at all to make sure the subDbs are populated exhaustively with every FF RI.
obscuratus
Or, maybe begin testing the nested netdbs without any RI at all, and make sure nothing breaks when we run that way.
obscuratus
I'm almost running that way now, with only the minimum 3 FF in each subdb.
eyedeekay
Thanks for the update, my next move will probably be in the direction of no RI's in subDb's first