IRCaBot 2.1.0
GPLv3 © acetone, 2021-2022
#i2p-dev
/2023/12/04
@eyedeekay
+R4SAS
+dr|z3d
+not_bob_afk
+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_
duanin2
eche|off
f00b4r
hababam_
hagen_
leopold
makoto
marek
marek22k
n2
nilbog
noidea
nyaa2pguy
o3d3_
poriori
profetikla
r00tobo
rapidash
solidx66
stormycloud[m]
test7363673
uop23ip
urist_
user_
w8rabbit
zelgomer
zzz
eyedeekay Also runners are back
orignal is there a chance for zzz.i2p back?
eyedeekay Not up to me
orignal ofc this question is not to you
Opicaak eyedeekay, git.idk.i2p returns 502, https returns invalid length, SSL_ERROR_RX_RECORD_TOO_LONG.
dr|z3d now required.
Opicaak https returns invalid length, SSL_ERROR_RX_RECORD_TOO_LONG.
dr|z3d check back soon, he'll have it fixed. it's probably in progress.
dr|z3d in the meantime, github.
zzz eyedeekay, see RN's port81 doc for how to do this correctly
eyedeekay The post says '2 days' I tried to give some warning
eyedeekay But yes I will thanks zzz
eyedeekay Opicaak use https on Wednesday
eyedeekay 502 will be fixed in a sec
eyedeekay Tried to forward the same port as the signal proxy and container stalled
zzz 503 Service Unavailable This I2P website is not configured for SSL.
zzz nice error message but we serve it over http so it's useless
zzz I guess we could spin up a cert if that happens
orignal who uses https in i2p?
zzz one more person soon
orignal the only reason for https is an outproxy
eyedeekay WebSockets, WebRTC, couple dozen other bits of obscura in all major browsers...
zzz i think I can fix the error message, let me try
zzz not so easy, not for this release