@eyedeekay
&Irc2PGuest88200
&zzz
+R4SAS
+RN
+T3s|4
+dr|z3d
+eche|off
+hagen
+mareki2p
+not_bob_afk
+postman
+snex
Arch2
Danny
DeltaOreo
FreefallHeavens
Irc2PGuest59134
Irc2PGuest59581
Irc2PGuest70083
Irc2PGuest96449
Irc2PGuest97049
Onn4l7h
Onn4|7h
SigSegv
Sisyphus
Sleepy
T3s|4_
acetone_
aeiou
ardu
b3t4f4c3___
bak83
boonst
cumlord
death
dr4wd3
duck
eyedeekay_bnc
onon_
orignal_
phobos
pisslord
poriori_
profetikla
qend-irc2p
radakayot_
rapidash
shiver_
solidx66
thetia
u5657
uop23ip
w8rabbit
weko
wodencafe2
x74a6
orignal
zzz, looks like zzz.i2p doesn't like type 12
orignal
or maybe my issue
zzz
orignal, I have an error in the logs, probably my issue, will work on it early this week, thanks for testing
orignal
fine
orignal
let me run local tests
orignal
just finished stuff today
zzz
oh wait, it is your problem ))))))
zzz
you set enc type in key cert to 0, not 255
orignal
at least your keys are fine
orignal
thanks. will fix
orignal
forgot about it
orignal
got it now
orignal
seems working
zzz
super
zzz
I don't allow ElG enctype + PQ sigtype
orignal
huh? isn't it 4?
orignal
I connect as 4
zzz
I mean in the key cert itself
zzz
where it's always been 0 until now
zzz
for destinations
orignal
it's not about this it's becauce crypto key is occupied
zzz
right, but I just have a quick sanity check to prevent 0 enctype + PQ sigtype in destination key certs, that's the error you hit
zzz
actually for router identity key certs also, the proposal says that combination is not allowed
zzz
255 is required
zzz
happy to hear it worked, well done ))
orignal
great
orignal
now it's time to implement my server side with PQ
orignal
but as I said I want to change signature verification first in streaming
orignal
e.g. just ignore it
orignal
I'm wondering what will be LS size with ML-DSA public key, signature and ML-KEM crypto key
zzz
there's a table in the proposal with the size increases listed
orignal
nevermind crypto is 32 bytes
eyedeekay
Flag day for gitlab/gitea in a few hours. Folks can keep using gitlab issues right up until I announce it here later today, our migration tools are excellent and can keep up with your work right up to the last minute.
zzz
I've started working on a complete stat subsystem overhaul to make it simpler and more prometheus-friendly
zzz
and it will make the console graphs much better
zzz
I have the refid migration working, I'll await the gitea migration before putting up an MR or PR or whatever it's called over there
eyedeekay
Thanks, I can handle either way but this is probably easiest
eyedeekay
I'll be sending out password reset emails tomorrow
eyedeekay
Well, tonight likely. But it'll be there in the morning
zzz
please include some migration guidance for us users. is your ssh key changing so we have to muck with our .ssh//config? are MRs and issues coming over or must they be reentered? when is the switchover date/time, both for clearnet and i2p side?
eyedeekay
All your repos, MR's, issues, comments, and public keys will be migrated automatically but the accounts are locked until the passwords are reset
eyedeekay
All you and the other users of the gitlab should have to do is follow a password reset email from idki2p@mail.i2p
eyedeekay
That will happen tomorrow as I said. Hidden service addresses will be migrated to the registered ones today, so you will not need to enter new addresses for the git services in-i2p
zzz
ok, thanks
eyedeekay
Last thing to happen will be the main DNS update and the Let's Encrypt certificate, both happening tomorrow, both should be equally non-interactive for the end users
dr|z3d
zzz: re stats, multiple data points on graphs would be nice, pairs etc.. :)
eyedeekay
Oh also email notifications are getting fixed with this upgrade/migration, and shouldn't break down again afterward
dr|z3d
plenty of stats lend themselves to pairs, which would allow for a more condensed graph view in the console.
dr|z3d
and multiple data points a la stats.i2p where applicable would also be well received, I'm sure.
zzz
yeah I think I see how to get there, not for 2.9 though
zzz
all the required stats and the profile stats have to stay as-is, but the full stats can be greatly simplified
zzz
for the required stats we want to combine in graphs, we can probably do both flavors
dr|z3d
sounds good
dr|z3d
there are probably graphs where it makes sense to do pairs by default, and if one of the two stats is enabled, the complimentary stat is also enabled, to simplify things.
zzz
the idea is to group them and enable as a group
dr|z3d
yeah, sounds good, amounts to about the same thing.
RN
are you suggesting to combine the up/down pairs? like if I graph my eepsite up/down now, or custom tunnel up/down?
RN
been asking about this for a while
RN
iirc the resistance was related to mucking about in some messy code, i guess the promethius stuff got you in there, eh?
RN
:)
zzz
well, I always had resistance to having user-configurable graph combinations because the config UI would be messy
zzz
here, we'd precombine things like in/out bw into one overall stat and graph
zzz
which is how prometheus likes it ("labels")
RN
:)
RN
I'm gonna have to play with that... I think I already grabbed the promethius plugin, just gotta set stuff up as outlined on your blog
RN
but it will be nice to have the in/out all combined
RN
pairwise
RN
:)