~dr|z3d
@RN
@RN_
@StormyCloud
@T3s|4
@T3s|4_
@orignal
@postman
@zzz
%Liorar
%acetone
+FreefallHeavens
+Onn4l7h
+Sh0ck
+bak83_
+bpb
+leopold
+r00tobo_BNC
+uop23ip
+xHarr
Arch
BubbRubb
Danny
DeltaOreo
H20
Irc2PGuest16752
Irc2PGuest33667
Irc2PGuest97218
Maylay
Meow
ac9f_
anontor
b4dab00m
eyedeekay_
halloy13412
john231
makoto
nZDoYBkF
nilbog-
not_bob_afk
ntty
poriori_
profetik1
r00tobo[2]
shiver_
simprelay
solidx66
thetia
tr
u5657
vivid_reader56
zer0bitz
T3s|4
o/ dr|z3d - Minor annoyance, but I'd like to understand why this occurring. 1. I pulled, and am running Revision: 2f5112d8 (Build date: 2025-10-09 06:26:44 UTC) from skank.i2p. 2. Yet router 'Update Status' continues to 'inform' me 'Unsigned i2p+ router update available Oct 9, 6:27 AM'. Why is the router NOT checking what version is already running?
T3s|4
same result after hard refresh
dr|z3d
not sure what your update issue is, T3s|4, but the latest build will have the same commit hash as the prior build, but once it's installed, assuming it's installed via the console, you shouldn't see additional notifications for updates.
T3s|4
dr|z3d: perhaps that is *it*. I never 'install' via the console. I snag an update from skank, then cut/paste i2pupdate.zip into ~/.i2p, then run `~/i2p/i2prouter restart`. It is reproducible ;)
dr|z3d
you could always try the graceful_update script to achieve the same, that will pull updates manually but update via console. and it's been fixed recently.
dr|z3d
at least I *think* it should update the last updated key in router.config
dr|z3d
just run ./graceful_update from your i2p/ dir for arguments, or ./graceful_update dev to pull the latest dev build, there's a new one up.
T3s|4
perhaps, but skank is much faster than console, especially when there are 3+ daily build updates
dr|z3d
graceful_update doesn't download via the console per se, it uses eepget/wget or curl, and you can pull via i2p or tor.
dr|z3d
it'll schedule a graceful restart once download, hence the name :)
dr|z3d
whether it resolves your notification issue is yet to be determined.
T3s|4
k, I always use tor from skank, ^cut/paste and then hard restart
dr|z3d
well, if you absolutely must have correct sidebar notifications, don't! use the console updater, set it to download and verify, at least then you can install whenever you're ready.
dr|z3d
you can configure the checks for 4h intervals.
dr|z3d
and you can always run a manual check if an update's been downloaded and is waiting for a manual restart and it will notify you of any more recent updates.
dr|z3d
shouldn't be *that* slow, anyways, you've already got pack200 magic on the dev branch :)
T3s|4
been at 4h for ages...This is not about an inability for me to receive, install, or re-start the most recent build. This is about redundant 'update available notifications' after I have already been running the latest build
dr|z3d
sure, like I said, you want those to go away, you'll probably need to update in-console.
dr|z3d
or you could just remove the update section from the sidebar entirely.
T3s|4
why are skank direct dev update d/ls behaving differently, post re-start?
dr|z3d
(you'll still see notifications on /configupdate for updates you've already installed, but hey. you pays your money...
dr|z3d
in console updates update the lastupdated timestamp in router.config, manual updates don't.
T3s|4
ah, so ^there is the answer - thanks :)
dr|z3d
your orignal question was flawed in various ways. :)
dr|z3d
you're not actually pulling from skank.i2p, you'
dr|z3d
re pulling from the .onion site..
dr|z3d
and there was no hint that you were doing that manually, either :) but hey, we got there eventually.
T3s|4
ah, didn't realize they are not the same 'service' from the same skank server...and yes, I always click on the tor link manually :)
dr|z3d
same server, different endpoints. eekmit....onion != skank.i2p
dr|z3d
also, worth mentioning, T3s|4, updates in-console you may find to be significantly faster.
xHarr
for anyone following the tracker2 excessive seeder reporting discussed here 2 days ago, I've finally gotten around to making the ticket.
T3s|4
dr|z3d: fwiw; I rarely see a skank tor update take more than 90 s to complete, while I often also see numerous 'console' updates either hang as non-complete, and /or require 5+ m to complete. <<= Why I prefer skank
dr|z3d
well, give it another try. you may be pleasantly surprised :)
T3s|4
You mean something has changed in the past few hours? Been seeing what I ^explained for years ;)
T3s|4
I run tor as a daemon, if that matters
dr|z3d
yeah, last few hours. check it. :)
T3s|4
will do, thanks
T3s|4
dr|z3d: last console update took about 2 m with no hangs; now on 0e7445de (Build date: 2025-10-09 13:05:54 UTC) :)
dr|z3d
*thumbs up*
waffles
have you guys heard of securonis
waffles
im seeing i2p more and more in the news lately
waffles
its some debian trixie based distro that has onion routing for all traffic and an i2p router with preconfigured browser built in
dr|z3d
new one on me, waffles