@eyedeekay
&eche|on
&zzz
+R4SAS
+RN
+RN_
+cumlord
+dr|z3d
+eche|off
+mareki2p
+orignal
+postman
+qend-irc2p
+snex
+wodencafe
Arch
Birdy
BubbRubb1
Chrono2
Daddy
Danny
DeltaOreo
FreefallHeavens
Irc2PGuest10672
Irc2PGuest12486
Irc2PGuest28259
Irc2PGuest34195
Irc2PGuest41303
Irc2PGuest58663
Irc2PGuest73926
Irc2PGuest85653
Irc2PGuest92505
Onn4l7h
Over1
Sisyphus
Sleepy
SlippyJoe_
Teeed
aargh2
ac9f_
acetone_
b3t4f4c3__
bak83_
dr4wd3
duanin2
eyedeekay_bnc
leopold
makoto
nilbog
not_bob_afk
poriori
profetikla
r00tobo
rapidash
shiver_
solidx66
thetia
tr
u5657
uop23ip
w8rabbit
x74a6
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