IRCaBot 2.1.0
GPLv3 © acetone, 2021-2022
#i2p-dev
/2025/09/28
@eyedeekay
&eche|on
&zzz
+R4SAS
+RN
+RN_
+StormyCloud
+T3s|4
+acetone
+dr|z3d
+eche|off
+orignal
+postman
+qend-irc2p
+snex
+weko
+wodencafe
Arch
BubbRubb
Chrono
Danny
DeltaOreo
FreefallHeavens
HowardPlayzOfAdmin
Irc2PGuest38175
Irc2PGuest62240
Irc2PGuest64908
Irc2PGuest77933
Irc2PGuest87067
Irc2PGuest88693
Sleepy
SlippyJoe_
T3s|4_
Teeed
aargh2
ac9f
b3t4f4c3__
bak83
cumlord
death
dr4wd3
duanin2
eyedeekay_bnc
idk_afk
leopold
makoto
nilbog
not_bob_afk
poriori_
profetikla
r00tobo_BNC
rapidash
shiver_sc
solidx66_
thetia
u5657
uop23ip
w8rabbit
x74a6
snex nvm got it
StormyCloud Heads up our uplink is doing some emergency repairs and has quoted 12 hours of downtime starting at 11pm CST. Working to activate a backup link but with it being the weekend it’s not looking likely.
StormyCloud My apologies we looking to get a second link to prevent this in the future
eyedeekay Thanks for the report StormyCloud
eyedeekay OK I have a way to repair the broken git repositories that is non-disruptive, but it does take a very long time, couple hours per run. There are six of them to do, all forks of i2p.i2p. That should resolve the PR issues.