&zzz
+FreefallHeavens
+Irc2PGuest61348
+R4SAS
+RN_
+StormyCloud
+T3s|4
+acetone
+eche|off
+mareki2p
+nilbog
+orignal
+postman
+qend-irc2p
+wodencafe
AlaskaBear
Arch
Daddy_I2P
Irc2PGuest23015
Irc2PGuest24082
Irc2PGuest6656
Irc2PGuest77286
MatrixBot
NiceBoat_
Onn4l7h
Onn4|7h
Over1
Romster_
Sisyphus
Sleepy
T3s|4_
U1F642
Zapek
aargh3
ahiru_
ananas
anontor
b3t4f4c3___
cims
dr4wd3_
duanin2
eyedeekay_
hagen_
leopold_
mahlay
makoto
marek
marek22k
n2
noidea
not_bob_afk
nyaa2pguy
o3d3
p2pworm
poriori
profetikla
quack_
r00tobo_BNC
rapidash
rednode
solidx66
stormycloud[m]
sublimia
test7363673
tr
u0_a292_2
uop23ip
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