IRCaBot 2.1.0
GPLv3 © acetone, 2021-2022
#i2p-dev
@eyedeekay
&Irc2PGuest88200
&zzz
+R4SAS
+RN
+StormyCloud
+T3s|4
+acetone
+dr|z3d
+eche|off
+hagen
+hk
+mesh
+orignal
+postman
+snex
+weko
+wodencafe
Arch
BubbRubb1
Danny
DeltaOreo
FreeB
FreefallHeavens
Irc2PGuest19848
Irc2PGuest59134
Irc2PGuest85010
Irc2PGuest95057
Leopold_
Onn4l7h
Onn4|7h
Sisyphus
Sleepy
T3s|4_
ardu
b3t4f4c3___
bak83
boonst
carried6590
cumlord
dr4wd3
duck
eyedeekay_bnc
meowking
not_bob_afk
phobos
plap
poriori
profetikla
qend-irc2p
radakayot_
rapidash
segfault
shiver_
solidx66
thetia
u5657
uop23ip
w8rabbit
x74a6
zzz Jetty has now really really EOL'ed Jetty 9.3/9.4, and also 10 and 11. That will push us to 12, meaning Java 17 minimum.
zzz Separately I've also proposed increasing the min Android version, allowing us to use all Java 8 features
zzz eyedeekay, I think I just broke gitea
zzz never mind, it's back
zzz Jetty 10/11 were never in debian; 12 is now in trixie/sid, not in ubuntu yet
zzz if we go to Java 17 we'd have to abandon bionic and focal
dr|z3d less maintenance burden, fine.
dr|z3d focal is came out 5 years ago. safe enough to drop.
dr|z3d nonle is the latest LTS, that's probably a good base for support, whatever Ubuntu's latest LTS version is.
dr|z3d *noble / 24.04
zzz we only drop support if we have to, not because it's old
dr|z3d sure, just suggesting that "official" support for the latest LTS and later re Ubuntu makes for less work.
dr|z3d either way, dropping support for focal and bionic seems like a non-issue.
dr|z3d we probably win a bunch of java optimizations by making 17 min requirement, too, no?
dr|z3d maybe there's some cool new jetty stuff we can also leverage. iirc the rare locked out of console when password issue gets fixed.
zzz sure. they're not even fixing CVEs now
dr|z3d are there any nasty ones that have cropped up recently?
zzz none that affect us
dr|z3d ok, so that buys us some time at least.
zzz bumping to -8 since it's been a couple weeks. One week to tag freeze
zzz next will be -9-rc
eyedeekay I'm going to look at consequences of moving to a new Java for I2P Android but tentative ack re: increasing minSdkVersion
zzz eyedeekay, android would stay at java 8, unless we wanted to go all the way to android R, which I don't think is necessaary
zzz unless we really want to use java 11 features in the router
zzz but I don't think we need to worry about 11 year old phones, we're due for some bump
eyedeekay Right now staying at 8 seems fine IMO, support isn't falling off in Android Studio or anything
eyedeekay I have been bumping the absolute minimum for years to avoid dropping old phones but 11 years is a bit much
snex do we even know how many devices of each type use i2p?
eyedeekay not 'know' no. I know an approximate number of GPlay installs of Java I2P, but they give me round figure, not exact, and it only includes things that are allowed to use their appstore/metrics
eyedeekay Not F-Droid or APK installs
eyedeekay So I see mostly modern phones, mostly in countries where google dominates
eyedeekay All as coarse, graph-style data
eyedeekay The falloff rate leaves a lot to be desired too. Devices probably stay included in the stats longer than they stay in actual use.
IRCaBot New messages won't show without JavaScript.
My JS code is small and simple. Check it at /realtimechat.js and come back with enabled!