~dr|z3d
@RN
@RN_
@StormyCloud
@not_bob_afk
@orignal
@postman
@zzz
%Liorar
%RTP
%cumlord
%snex
+BeepyBee
+H20
+Onn4l7h
+Onn4|7h
+leopold_
+poriori
+profetikla
+qend-irc2p
+r00tobo_BNC
+uop23ip
+xHarr
Arch
BubbRubb
Danny
DeltaOreo
Guest99
Irc2PGuest25224
Irc2PGuest27539
Irc2PGuest4895
Irc2PGuest90985
Irc2PGuest95708
Meow
Over1
Stormycloud_
ac9f
acetone_
anontor
floatyfloatilla
mahlay
makoto
nZDoYBkF
nilbog
ntty
r00tobo[2]
shiver_
simprelay
solidx66
thetia
u5657
vivid_reader56
zer0bitz_
dr|z3d
great stuff, RTP!
dr|z3d
and apologies again for the turbulence. by all accounts I think we're in a good place now, and I've no more plans to hijack the code this dev cycle :)
dr|z3d
!word
H20
scurve — A term historically used to denote leprosy, often associated with social stigma and religious connotations.
RTP
It's all good - I'm just glad I was able to fix it. :) I tried a few different things, and was afraid my router could have been banned for whatever clock randomization or something haha.
dr|z3d
your router will never banned from the network. that's the first thing. other routers in isolation might shun it for a while if it's behaving strangely.
dr|z3d
even if we determine your router is part of a botnet or performing some sort of attack, the best you'll get is a hard ban for java routers. i2pd doesn't implement a blocklist strategy, so you're very unlikely to be banned globally.
RTP
Ahh, okay. Good to know. :)
dr|z3d
if you have ridiculous clock skew, you won't be banned either, not globally, but you may just find your router fails to function correctly until you fix it.
dr|z3d
if you enable global warn level logging on /configlogging, you may get some idea of why your router's not performing as expected, but you'll have to filter/exclude a lot of normal log events.. it's quite noisy at that level, but will give you a good enough idea of what your router's doing.
dr|z3d
in I2P+, you may see your clock skew value in the sidebar turn red if it's potentially problematic (anything over 1s).
RTP
Yeah I wasn't sure if the clock randomization from purposeful hardening might affect it (usually 5min give or take). But just now enabled WARN under logging. THanks again!
RTP
Since I host the same laptop as I do separate router server, I thought maybe it might have related. But I think this was just a temp issue, and looks solved now.
RTP
same hardening set up* (on separate blog router and laptop)
dr|z3d
5m skew isn't great for i2p.
dr|z3d
ideally you want under a ms.
dr|z3d
if you want to prevent skew, just set up a crontab job under your root account > */15 * * * * ntpdate pool.ntp.org
dr|z3d
that's probably preferable to intentionally hijacking your clock to prevent profiling (and arguably just as effective).
dr|z3d
ok, in testing on update.skank.i2p/i2pupdate.zip is a new + dev build will significantly lower ram usage.
dr|z3d
*with
dr|z3d
optimized stat collection to reduce memory footprint. when I've let it soak for a while to ensure it's behaving as expected, I'll push to skank.i2p.
cumlord
I know you didn’t ask for any of this but my tiny dramatic router is still not dead
cumlord
I increased its vm to a ✨massive✨ 128M
dr|z3d
tiny dramatic router not dead? is that a good thing?
cumlord
yes it doesn’t really do anything important but it tries its best
cumlord
no GC problem so far
dr|z3d
and it's running in 100MB?
dr|z3d
didn't you say it's hammering a core?
cumlord
well it was running 104M for about a year like that, just used to torrents occasionally
dr|z3d
ok, well, if you want to continue science, try the latest build on update.skank, the memory footprint is *considerably* reduced.
cumlord
yeah it did yesterday so I gave it a little more rams
dr|z3d
based on what I'm looking at in visualvm here, footprint reduced by 50-60% right now.
cumlord
Amazing I will give it even less 🧪
dr|z3d
!ru
H20
безмозглый (bezmozglyy) — lacking intelligence; brainless.