IRCaBot 2.1.0
GPLv3 © acetone, 2021-2022
#i2p-dev
/2023/12/04
@eyedeekay
&zzz
+FreefallHeavens
+R4SAS
+RN_
+Romster
+StormyCloud
+cims
+eche|off
+hagen
+nilbog
+nyaa2pguy
+orignal
+postman
+qend-irc2p
+snex
+wodencafe
Arch
Danny
Holmes
Irc2PGuest20264
Irc2PGuest28384
Irc2PGuest34440
Irc2PGuest68355
NiceBoat_
OfficialCIA
Onn4l7h
Onn4|7h
OnyxAcheron
Over1
Sleepy
T3s|4
T3s|4_
U1F642
Wikk_0_
Zapek2
aargh4
ac9f_
acetone_
ahiru
anontor
calamares
dr4wd3
duanin2
eyedeekay_bnc
ice_juice
leopold
mahlay
makoto
marek
mareki2p_
n2__
not_bob_afk
pinotto
poriori
profetikla
r00tobo_BNC
rapidash
test7363673
uop23ip
x74a6
zelgomer
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