&zzz
+R4SAS
+RN_
+StormyCloud
+T3s|4
+acetone
+mareki2p
+orignal
+postman
+qend-irc2p
Daddy_I2P
Danny
Irc2PGuest93194
NiceBoat
Onn4l7h
Over1
Sisyphus
Sleepy
T3s|4_
Yotsu
Zapek2
aargh3
ahiru
ananas
b3t4f4c3___
duanin2
eyedeekay_
hagen_
marek
marek22k
mfs
n2
not_bob_afk
nyaa2pguy
o3d3_
poriori
profetikla
r00tobo
rapidash
test7363673
u0_a292__
uop23ip
urist_
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