@eyedeekay
&kytv
&zzz
+R4SAS
+RN
+acetone
+dr|z3d
+hagen
+hk
+lbt
+orignal
+postman
+radakayot
+snex
+wodencafe
Arch
Danny
DeltaOreo
FreeB
FreefallHeavens
Irc2PGuest12735
Irc2PGuest4450
Irc2PGuest47289
Irc2PGuest59134
Irc2PGuest70698
Irc2PGuest87589
Leopold_
Onn4l7h
Onn4|7h
Sisyphus_
Sleepy
SpoofIdentify
T3s|4_
aeiou
ardu
b3t4f4c3___
bak83_
carried6590
cumlord
death
dr4wd3_
eyedeekay_bnc
mareki2p_
not_bob_afk
phil1
poriori
profetik1
qend-irc2p
rapidash
shiver_
solidx66
thetia
u5657
uop23ip
w8rabbit
weko_
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