@RN_
@T3s|4_
@postman
@zzz
%acetone
%mareki2p
+FreefallHeavens
+Gully
+NiceBoat
+Onn4l7h
+Onn4|7h
+Over
+altec
+nyaa2pguy
+poriori
+profetikla
+qend-irc2p
+r00tobo
+uop23ip
+waffles
Arch
Danny
Irc2PGuest16019
Irc2PGuest20377
Irc2PGuest33925
Irc2PGuest48148
Irc2PGuest77921
Liorar_
MatrixBot
Teeed
ahiru
anontor2
cims
floatyfloatilla
mahlay
makoto
n2
nZDoYBkF__
nilbog
noidea
not_bob_afk2
o3d3
orignal
r00tobo[2]
rednode
solidx66
stormycloud[m]
vivid_reader56
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