~dr|z3d
@RN
@StormyCloud
@T3s|4
@orignal
@postman
@zzz
%Liorar
%acetone
%cumlord
%snex
+Onn4l7h
+Onn4|7h
+Sh0ck
+bpb
+profetikla
+qend-irc2p
+r00tobo
+waffles
Arch
BubbRubb1
Danny
DeltaOreo
H20
Irc2PGuest11613
Irc2PGuest43985
Irc2PGuest44009
Irc2PGuest63096
Irc2PGuest74254
Irc2PGuest8482
Irc2PGuest95708
Meow
Over1
ac9f
anontor
dollarthief
floatyfloatilla
halloy13412
leopold
mahlay
makoto
n1
nZDoYBkF__
nilbog
not_bob_afk
onon_1
poriori_
shaye
shiver_
simprelay
solidx66_
thetia
u5657
uop23ip_
vivid_reader56
zer0bitz
dr|z3d
we got a bad gateway issue on git, eyedeekay
RN
dr|z3d, the .org and .i2p seem to load for me, is there something I might not be seeing?
dr|z3d
RN: probably a transient issue.
dr|z3d
I say probably a transient issue, seeing 502 again.
eyedeekay
Alas it's the same deadlock as before, resolves in about 10 min, happens when certain resources that cause gitea to call out to git are accessed simultaneously AFAICT but it's still very weird, going to pull the trigger on some changes that should help today but delayed so I could make sure my backups were adequate
zzz
orignal, re: i2cp pubkeys as promised -
zzz
the first time we get a LS, we do a private-to-public and compare to the LS pubkey to verify the client side knows what it's doing
zzz
for type 5 LS, we always decrypt the LS and store it
zzz
every time we get a LS, we verify the priv keys didn't change, and error out if they did