IRCaBot 2.1.0
GPLv3 © acetone, 2021-2022
#i2p-dev
/2025/11/29
&zzz
+R4SAS
+RN
+Romster
+cumlord
+dr|z3d
+orignal
+postman
+qend-irc2p
+snex
+wodencafe
Arch
Birdy
BubbRubb1
Chrono
Danny
DeltaOreo
Guest99
Irc2PGuest28078
Irc2PGuest63096
Irc2PGuest6790
Irc2PGuest718
Irc2PGuest74254
Irc2PGuest76277
Irc2PGuest88931
Irc2PGuest93934
Irc2PGuest95708
Onn4l7h
Onn4|7h
Over1
Sisyphus
Sleepy
T3s|4_
Teeed
aargh2
ac9f
acetone_
anontor
b3t4f4c3__
b4dab00m
dr4wd3
duanin2
eyedeekay_bnc
gelleger1
leopold
makoto
mareki2p_
matean
n1
n1_
namenick
nilbog
not_bob_afk
poriori_
profetikla
r00tobo
rapidash
shiver_1
solidx66_
thetia
uop23ip
vivid_reader56
w8rabbit
x74a6
anonymousmaybe Hello there
anonymousmaybe Now with PQC connection, cool!
anonymousmaybe Only thing i see it good if the default can be changed is the RAM for wrapper.java by default
anonymousmaybe it would be nice it can be increased to 500mb or so
anonymousmaybe @eyedeekay, will i2p-go be uploaded to I2P repo?
anonymousmaybe If any test needed hit me
anonymousmaybe I hope in i2p-go there wont be any backward compatbility specially for poor encryption routers
anonymousmaybe but i cant connect to i2p-projekt.i2p or stormycloud.i2p/, do they support PQC at the moment?
anonymousmaybe but i believe the issue is that the clients im connected through are not on PQC
anonymousmaybe All are on Encryption Key: ECIES_X25519, No PQC.., probably gonna take time, though i chosed PQC so there shouldnt be any connections
anonymousmaybe oh even my local router is Encryption Key: ECIES_X25519.. dang
eyedeekay Debian repo packaging is likely to be it's own effort, to some extent I may have to do some static compilation things that might not pass muster with official Debian, but I will assess and begin some kind of packaging effort after a usable router can be `go install`'ed
eyedeekay Which I expect to be sometime in January. Really chugging along, going to have exciting stuff to show off in the next day or two
eyedeekay Embeddable by Christmas if I can manage it
dr|z3d anonymousmaybe: there's nothing stopping you editing the wrapper.config file yourself and assigning more RAM to the JVM.
zzz already had 512 on my list, will do it shortly
zzz gitssh down again
eyedeekay What is it showing error wise?
zzz same as usual, immediate sovcket close, no message
eyedeekay Damn, I had hoped that would change after the last reboot
dr|z3d 512's been the default in + for a couple of years, fwiw.
eyedeekay zzz I haven't done anything including a restart, but ssh is working for me from here. I'm going to double-check that the multihome-to-nowhere didn't get restarted somehow but AFAICT you should be able to use it
zzz yeah thanks eyedeekay it worked on the 8th retry (I have a script that retries every 10 minutes)
eyedeekay Hmph. so an ephemeral issue, but not ephemeral enough.