#i2p-dev (irc2p) | 2.10.0-0

eyedeekay OK everyone it's the 5th, which means that final checkin deadline for 2.10.0 is in about ~4 hours

eyedeekay I am going to be doing checklist.md stuff and trying one last time to get ahold of those 2 reseed operators I pinged last week

zzz ok I think I gave the translators until noon eastern, will pull after that

zzz pls retest the two reseeds, maybe they're fixsed

zzz you have console news for me to push to tx?

eyedeekay Sorry about that I got trapped on an elevator of all stupid things, news is pushed

zzz reading...

zzz couple things

zzz can we just tell people to enable MLKEM in hidden services manager rather than telling them to go to IRC?

zzz and re: Android - I don't think we're going all the way to Java 17 on android, and people don't know what java they have on android anyway

zzz we talked about maybe going up to java 11 which would be a ~2021 phone

dr|z3d re MLKEM, we need to inform people that 768 is the standard option, other options are esoteric.

zzz but java 17? there's no good reason and that would be a 2024 phone

zzz 768 is the only visible option unless configadvanced

dr|z3d sure, but people in advanced mode are going to see 1024 and think "I'll have that, sounds secure"

dr|z3d postman, for example :)

zzz 768 is marked beta, the others are marked experimental

zzz don't think we should put configadvanced-only info into the console news, it would just confuse people

dr|z3d I don't think it hurts to state that 768 is the recommended option, but up to you.

zzz it's the only option for 99% of ppl

dr|z3d I love those stats you pull out of your head to prove a point. :)

zzz not a proof, just an argument

dr|z3d Yeah, an argument built on imaginary stats :)

zzz if I added a ~ would you be happier?

dr|z3d Unless you've got some secret telemetry going on? :)

dr|z3d *** chuckles. ***

zzz your user base is fairly different from ours

dr|z3d valid point

zzz anyway, eyedeekay let me know what you think about those two comments ^^

dr|z3d do we have a draft news link?

zzz in git newsxml

zzz please proofread, you're pretty good at spotting things

dr|z3d yeah, was about to, we do best when we attack the news as a group :)

dr|z3d OK, let's start. This line is a complete waste of space: "I2P 2.10.0 is a maintenance release that includes bug fixes and new features."

dr|z3d Based on what we've just discussed, this is wrong: "In this release post-quantum cryptography is available but disabled by default."

dr|z3d Or maybe not wrong, but less than 100% clear.

dr|z3d It's not disabled, it's just not configured as the default option for new tunnels.

dr|z3d "I2PSnark has been improved by implementing support for datagram-based torrent trackers." - "I2PSnark now supports UDP trackers."

dr|z3d The whole paragraph about async address lookups doesn't communicate much to the average user, just confusing.

dr|z3d "Outside of the I2P router itself, there has been a major update to the Reseed Server."

dr|z3d Not the place for news about reseed servers, and there is no "Reseed Server", there are multiple implementations.

dr|z3d "In one release, at 2.11.0, I2P will require Java 17." - "The next release will require Java 17 or later, both for desktop and Android."

dr|z3d EOT

zzz except the android part almost certainly isn't true

zzz lets not mention android in the console news at all, it's not relevant, and we don't have a plan yet

dr|z3d ok, you know more about that than me, I was just working with the text there.

dr|z3d agreed

zzz agreed re: reseed server

dr|z3d maintenance release needs to die as a description of anything other than out-of-band point releases. we don't do maintenance releases, we do new releases with new features.

zzz yeah PQ is a big deal, it's a disservice to call it a maintainance release, you wanted to call it 3.0

dr|z3d maintenance release is shorthand for "we fixed a bug" or "we're no longer actively innovating".

zzz maybe elevator broke again. take the stairs!

dr|z3d :)

eyedeekay I was looking at something else but the elevator is completely broken now

eyedeekay My plan for Android was indeed Java 17 but if it isn't relevant to the news then it isn't relevant to the news

eyedeekay The rest I'll adjust

eyedeekay I said "come to IRC" to encourage people testing it to interact, I can just say both

zzz ok lets put off the android discussion for now we can debate after the release

eyedeekay Ack will do, I'll just take that line out

eyedeekay About to push revised news

zzz in particular for hidden svc mgr tell them it's a new encryption type so they don't have to hunt for it

eyedeekay Done. New draft is up, took most of the suggested revisions but left the programming interfaces paragraph in

dr|z3d Still this -> I2P 2.10.0 is a maintenance release that includes bug fixes and new features.

dr|z3d the headline feature is PQ encryption support.

eyedeekay Refresh one more time

dr|z3d OK, better. In one release, not great. "In the next release"

zzz according to this, a Java 17 reqmt (Android 14) would strand 70% of the user base - including me. composables.com/android-distribution-chart

dr|z3d Rephrase: "Note: The next release (3.0.0) will require Java 17 or later@.

zzz we haven't made that decision yet

zzz either

zzz maybe omit the next release number

dr|z3d Sure, "In the next release, Java 17 or later will be required."

dr|z3d with a Note: in front.

zzz nah

dr|z3d well you rephrase it then :P

zzz Important!

zzz <b>Important!</b>

dr|z3d This paragraph I still don't like: "Programming interfaces to the router have also been improved.

dr|z3d I2P now has support for asynchronous address lookups and for DNS-like "Service Records" in LeaseSets.

dr|z3d These will provide useful tools to developers building applications on I2P."

dr|z3d Sure, important! works.

dr|z3d Can we rephrase that paragraph so it makes sense to average user?

zzz actually eyedeekay the service record stuff is only half done

zzz lean agree with drz, not sure API changes belong in console news

zzz maybe replace with hidden mode improvements

eyedeekay ok I'll just pull it

eyedeekay ok

dr|z3d "We've improved the router's Hidden Mode, which should result in less chance of the router running of of RouterInfos." or similar.

dr|z3d *out

dr|z3d "We've made improvements to the router's Hidden Mode, improving RouterInfo retention and overall robustness."

dr|z3d Or something.

eyedeekay OK new version is pushed I think this might be he one

eyedeekay *the one

eyedeekay Pushed

dr|z3d important! -> <b>Important!</b>

dr|z3d Java 17 or later

dr|z3d Otherwise, looks good.

eyedeekay Done

dr|z3d *thumbs up*

zzz ok. what's the translator's deadline eyedeekay ?

eyedeekay The 8th 4PM EST

zzz ok thx

zzz and what's the reseed status?

eyedeekay Cowpat still down

zzz and chaos?

eyedeekay Bigly up

eyedeekay Chaos looks down still

zzz bigly == cowpat

zzz which is it

eyedeekay my bad, cowpat is up, my script just wasn't pointed at the cert

eyedeekay So it thought it was dead

zzz cowpat still hanging from here

zzz chaos is now down completely, before it was hanging

zzz and on IPv6, cowpat is only returning 25 RIs

zzz so I'd say it's more broken than before

eyedeekay 25 is the new minimum value I told parg to set, chaos never got back to me

zzz why 25?

eyedeekay I can see cowpat but not chaos

zzz you see cowpat on ipv4?

eyedeekay Yes on ipv4

zzz how many RIs do you get?

zzz why did you tell him 25? that's too low

zzz ok cowpat works from 2 boxes, not from the third

eyedeekay 25 was low enough to basically never deny a reseed because the server didn't have RIs

eyedeekay Previously was 77 which was too high if we had less than ~400 or so

zzz but we keep reseeding until we have 100

zzz your logic sounds off. Serve however many you have, with a MAX of, say, 77. Why do you implement a MIN?

zzz and why hang if you're under a minimum instead of returning some error?

eyedeekay Pre-dates my maintenance of it but it is/was an anti-scraping thing, to make it so the router never shares some X number of RI's greater than about 1/8 of the total they know about

eyedeekay It does return an error now

eyedeekay I will tweak that minimum up to 51 and plan to move it toward a better strategy after

zzz ok that makes sense

zzz maybe a little more than 51, to account for dups and bans. 60 or so should do it

zzz ok so I'm going to remove cubicchaos and ghativega. I'll check that in with the translations in about an hour, and bump to -10-rc

zzz ^^ orignal

zzz and I'll send out a reseed email so emissary knows

zzz please tell parg to tweak it back up

eyedeekay Will do

zzz news is pushed to tx

zzz I'll holler when I push -10-rc

zzz eyedeekay, you were going to double-check that i2p.i2p docker still worked? or trixie? I forget

eyedeekay Yeah the Docker for i2p.i2p is fine, i2p.www was broken but I fixed it for now

zzz ok thanks

zzz in other news we did get to ~2000 ffs

eyedeekay Excellent, is that on account of the SSU-related fix you told me about?

zzz yeah last release

eyedeekay Cool

zzz I predicted we'd get to 2K ffs and got some scoffs in response

zzz neener neener

zzz -10-rc tagged and pushed

zzz big diff, 14700 lines, but about 5000 lines is bouncycastle

eyedeekay I don't make a habit of betting against things you predict

zzz lol thanks I guess?

zzz reseed email sent to router devs

orignal what?

orignal remove some reseeds?

zzz da

zzz cubicchaos and ghativega

orignal thanks

orignal will do

orignal got your e-mail

orignal what are thier cert filenames?

zzz they might come back if you want to leave the certs for a while

orignal I can always restore from perv release

orignal I don't know which one is ghativega

zzz sec

zzz Reseeder.java: //"https://i2p.ghativega.in/" + ',' + // arnavbhatt288_at_mail.i2p.crt // CA

orignal thanks

zzz np

orignal commited