IRCaBot 2.1.0
GPLv3 © acetone, 2021-2022
#saltr
/2024/10/17
orignal waht's up to spike of Chinesse routers?
dr|z3d not seeing that here.
dr|z3d actually, not seeing on 2/3 routers checked, see a spike on 1.
dr|z3d ~95% of them are X tier.
dr|z3d and mostly 0.9.58
dr|z3d ~10% ff
orignal but we have 0.9.59 min
zzz 0.9.58 spike ~15 hours ago; overall netdb spike ~4 hours ago
zzz there was a smaller 0.9.58 spike 4 days ago
zzz and a part. tunnel spike 4 days ago
dr|z3d min version is only for building our local tunnels, no, orignal?
dr|z3d min version doesn't prevent older routers from appearing in the netdb.
RTP Odd message on duckduckgo.i2p for me: ""We have detected that you have connected over Tor.
RTP There appears to be an issue with the Tor Exit Node you are currently using.
RTP Please recreate your Tor circuit or restart your Tor browser in order to fix this.
RTP Alternatively, DuckDuckGo is available on Tor via our Onion URL.
RTP If this persists, please email us." I wonder if this relates to some kind of mitm detection or just random.
dr|z3d works for me, RTP.
dr|z3d probably a temp glitch in the matrix.
RTP Ah okay thanks - I was going to email them, but must be matrix glitch as stated. ;)
orignal dr|z3d it prevents being floodfill
orignal e.g. I don't consider a router as FF if below 0.9.59
orignal zzz Vort sees the same
dr|z3d RTP: if it happens in future, you can always try mojeek.i2p which iirc also allows you to specify ddg as your search engine
dr|z3d (as a temporary workaround until ddg is functional again)
RTP good idea
zzz 0/17 22:33:48.159 WARN [P reader 1/4] oodfillDatabaseStoreMessageJob: (dbid: Main NetDB) Unknown peer sent bad data key: 2RRYXk4DLmwmsCwDaFcN1u88XPStZiIAi3eNGFMGyJI= replyreq? false: Invalid store attempt of RI 2RRYXk4DLmwmsCwDaFcN1u88XPStZiIAi3eNGFMGyJI= - Bad family INVALID_SIG [Hash: 2RRYXk4DLmwmsCwDaFcN1u88XPStZiIAi3eNGFMGyJI=]
orignal when?
zzz now
orignal do you see timesmap?
orignal if I give you router.info can you verify using your tools?
zzz I'm adding logging and restarting to investigate further. One router is fine, the other was complaining
orignal all i2pd pass it
orignal do you need router.info?
zzz may be a caching issue for me? will investigate and have more info tomorrow
zzz no need for RI, thanks, I can get it from the router that's happy
orignal anyway
orignal how it looks like on the source
zzz will research and rep[ort tomorrow
orignal thanks
orignal also as long as Java routers keeps updating I see more and more transit