&zzz
+R4SAS
+RN_
+T3s|4
+eche|off
+nilbog
+orignal
+postman
+qend-irc2p
+sourceress
Arch
Birdy
Danny
Irc2PGuest30010
Irc2PGuest36077
Irc2PGuest49364
Irc2PGuest51117
Irc2PGuest6564
Irc2PGuest65656
Irc2PGuest67278
Irc2PGuest74235
Irc2PGuest83482
MatrixBot
Onn4l7h
Over
Sleepy
Teeed
Yotsu
__bob_
aargh3
ac9f
acetone_
ahiru
anontor
b3t4f4c3__
cims
dr4wd3_
dr|z3d
duanin2
hababam
hagen_
leopold
makoto
marek
marek22k
n2
noidea
not_bob_afk2
nyaa2pguy
o3d3_
poriori
profetikla
r00tobo
rapidash
solidx66
stormycloud[m]
test7363673
uop23ip
urist_
user_
w8rabbit
zelgomer
dr|z3d
re questing, still jetty9.
dr|z3d
re jetty12, fcgi, I think we want that to maintain feature parity with jetty9.
dr|z3d
also, and this one's a bit "out there" as ideas go, and maybe not doable, but an ssl cert for *.i2p that's installed somewhere where only i2p can see it, all websites https by default (sure, overhead), and then we can enable http/2 and http/3.
dr|z3d
we'd effectively be our own cert authority.
eyedeekay
dr|zed I've been talking about that for years, to do it well you end up needing a lot of stuff I barely have time to work on, there is surprisingly enough more than one way to do it but they're all a lot harder than they should be, and on Android it's even worse I haven't found a workaround yet that isn't just "completely disable verification" for mobile, not that I've looked that recently
dr|z3d
yeah, eyedeekay, I suspect it's not as easy as self-nominating yourself as a cert registrar and creating a global cert for i2p, but if it was doable, would be an interesting upgrade.
dr|z3d
with https, enabling http/2 and http/3 is probably not possible, given it's enforced in the browser as far as I'm aware.
dr|z3d
*wuthout
dr|z3d
*without
eyedeekay
yeah it's a big old pain. I have tools to do a lot of what it needs but I have yet to orchestrate them together completely
eyedeekay
That's what the stuff in my go-wbg namespace is for
eyedeekay
cert9util, go-fpw and browser are for that