@RN_
@StormyCloud
@orignal
@postman
@zzz
%mareki2p
%snex
+FreefallHeavens
+Gully
+Onn4l7h
+Onn4|7h
+Over
+nyaa2pguy
+poriori
+profetikla
+qend-irc2p
+r00tobo
+uop23ip
AlV5tGf7
Arch
Danny
Holmes
Irc2PGuest17692
Irc2PGuest28384
Irc2PGuest32652
Irc2PGuest98066
Liorar_
OfficialCIA
T3s|4
U1F642
acetone_
ahiru
anontor
cims
floatyfloatilla
leopold
mahlay
makoto
n2_
nilbog
not_bob_afk2
pory
r00tobo[2]
rednode
synergy3582
user_
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