@eyedeekay
&eche|on
&zzz
+Irc2PGuest32505
+R4SAS
+RN
+RN_
+acetone
+cumlord
+eche|off
+orignal
+postman
+qend-irc2p
+snex
+weko
+wodencafe
Arch
BubbRubb
Chrono
DeltaOreo
FreefallHeavens
HowardPlayzOfAdmin
Irc2PGuest16211
Irc2PGuest18900
Irc2PGuest62240
Irc2PGuest64908
Irc2PGuest88693
Irc2PGuest98322
Onn4l7h
Sleepy
SlippyJoe_
T3s|4_
Teeed
aargh2
ac9f
b3t4f4c3__
bak83
death
dr4wd3
dr|z3d
duanin2
eyedeekay_bnc
idk_afk
leopold
makoto
nilbog
not_bob_afk
one1
poriori_
profetikla
r00tobo_BNC
rapidash
shiver_sc
solidx66_
thetia
u5657
uop23ip
w8rabbit
x74a6
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