@eyedeekay
&eche|on
&zzz
+R4SAS
+RN_
+StormyCloud
+acetone
+cumlord
+dr|z3d
+hagen
+mareki2p
+orignal
+postman
+qend-irc2p
+snex
Arch
Birdy
Danny
FreefallHeavens
Irc2PGuest13449
Irc2PGuest20240
Irc2PGuest57061
Irc2PGuest77260
Irc2PGuest78958
Onn4l7h
Onn4|7h
Over1
RN
Sisyphus
Sleepy
Stormycloud_
T3s|4_
Teeed
aargh2
anontor
b3t4f4c3___
dr4wd3
duanin2
duck
elthommy
gellegery
leopold_
makoto
n1_
nilbog
not_bob_afk2
nyaa2pguy
onon_
poriori_
profetikla
r00tobo_BNC
rapidash
shiver_
solidx66
thetia
u5657
uop23ip
user1
user4
vivid_reader56
w8rabbit
wodencafe2
x74a6
zelgomer
zyx
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