@eyedeekay
&zzz
+R4SAS
+RN
+T3s|4
+dr|z3d
+hagen
+hk
+mareki2p
+orignal
+postman
+radakayot
+snex
+wodencafe
Arch
Danny
DeltaOreo
FreefallHeavens
Irc2PGuest12735
Irc2PGuest28644
Irc2PGuest4450
Irc2PGuest59134
Irc2PGuest87589
Onn4l7h
Onn4|7h
SigSegv
Sisyphus
Sleepy
T3s|4_
Teeed
acetone_
aeiou
ardu
b3t4f4c3__
carried6590
cumlord
death
dr4wd3_
eyedeekay_bnc
not_bob_afk
onon_
plap
poriori_
profetik1
qend-irc2p
rapidash
shiver_
solidx66
thetia
u5657
w8rabbit
weko_
x74a6
dr|z3d
you want grafana, RN.
eyedeekay
All right to make it official I now request that any interactions with i2pgit.org wait until tomorrow after the DNS switch is flipped
eyedeekay
git.idk.i2p is up, as requested, no https required on the I2P side. If you *want* https for some reason(there is less reason to need it with gitea-over-i2p than with gitlab) then this destination: 57z3ffssd34lztr2dgkddqd36sdn73luzrkgkvuh7wjfxxy7tqea.b32.i2p is preferred
eyedeekay
Ah, looks like we're in-net only until 12 hours from now, I managed to mess up let's encrypt
eyedeekay
I may hit a quota with the email servers if everybody resets all at once, if it doesn't succeed immediately try again later
zzz
ok site looks good, requested and got reset email, but it's now 503
zzz
the ssl b32 is up
zzz
ok I did the recovery with the ssl b32 and I'm in that way
eyedeekay
Oh right it's to do with the nginx thing, sorry about that I literally just did that 5 minutes ago
eyedeekay
So I'm keeping gitlab up for another day while I deal with this DNS mess I created so people can see their issues and MR's, to do this I disabled the equivalent configs on the gitea side, I'll have it back up in 5
zzz
ok
zzz
looks like all the issues came over, renumbered and with you as author of every one and every comment
zzz
however none of the MRs came over
eyedeekay
Yeah I've got another script to run for that but there was no way to do them without first establishing the fork relationships, which required reaching into the sql DB because there is not gitea API function for that, understandably
eyedeekay
I did that right becore I made something of a mess of the DNS
zzz
if it's too hard just tell me and I'll redo them
eyedeekay
No, not too hard, but feel free to re-create any that you need
zzz
seems like gitssh worked for a pull, didn't complain about any key change
eyedeekay
re: me as author of all comments I can go in and change that retroactively to reflect the actual account owners but only for folks with accounts on the gitea
zzz
re: MRs, let's not both do the work. pick one
zzz
ok the http site is back
eyedeekay
hm, mine complained, let me check and make sure the other dest is down
zzz
that's what I was asking about yesterday, don't think you answered
eyedeekay
Thought you meant something else, I've got a bunch of stuff in my client config for telling SSH to turn destinations into host:port pairs and such
eyedeekay
I am pretty sure it's going to squawk
zzz
is the old gitssl still up or not?
eyedeekay
ssl is no longer available on git.idk.i2p if that's what you mean
zzz
I'm sorry I mean gitssh for push/pull
eyedeekay
The old one was up, I turned it off, only the new one is up now
zzz
ok I'll retest
zzz
yeah it complained
zzz
back to https, any reason you put it on a separate b32?
eyedeekay
TBH it's just a lot less headache
eyedeekay
I could copy the ssh host keys and restart the server, but ssh might complain about that also...
eyedeekay
I updated the forum post with an updated version of the password reset email I sent, has some more information on the topic
eyedeekay
I actually haven't been to bed yet tonight though so I'm going to catch some... you's... after I've answered any remaining questions
zzz
think thats it, good job, good riddance to gitlab
eyedeekay
Yeah might be good for some folks but it was a time sink for me, I can do better with something simpler like gitea
zzz
and for later today:
zzz
reminder: Proposal 169 2nd review today 7 PM UTC #ls2
eyedeekay
Thanks, I didn't remember, I'll be back before then
orignal
l5exwwo2ev2jmz64ku6al4vgsmmamxpk4bczsdkt5u45nizh3fia.b32.i2p should be able to handle ML-DSA-44
zzz
I added a section on LS2 key preference to the common structures spec. The info was in the original LS2 proposal but it didn't get put in the spec at the time
zzz
Still working on a ratchet handshake retransmission section for the ratchet spec, should be done by end of the week
zzz
not sure if anything I checkin today will make it from gitea to github to the website
orignal
do we have a meeting today?
zzz
so github and/or website might be behind for a couple days, don't know
zzz
<zzz> reminder: Proposal 169 2nd review today 7 PM UTC #ls2
orignal
looks like I was kicked out a usual
zzz
also in /topic
zzz
7:22, just a few lines above ^^^^
zzz
also announced in #saltr and #ls2
orignal
yes, I see
zzz
and that's the last one scheduled, 6 reviews in two months, not bad
orignal
I don't know my may/june schedule will know next week
zzz
ok, so we won't schedule a 3rd PQ review today, probably won't need to do it soon anyway
orignal
agree, we need more time to work
zzz
da
orignal
when is the next secheduled release? mid june?
zzz
Mon. June 3
orignal
thanks
zzz
I'm going to get back to my 3 year old UDP tracker proposal 160, rewrite it for datagram2
zzz
then schedule a review, maybe in a couple months. you probably don't care about it ))
zzz
will try to get postman and bigly involved
zzz
eyedeekay, another issue, when you return
dr|z3d
congratulations on your migration, eyedeekay.
dr|z3d
also props to StormyCloud for the hosting.
dr|z3d
you may want to set the default page to explosre instead of the gitea advert.
dr|z3d
*explore
zzz
yeah a custom home page like we had in gitlab
dr|z3d
pages load about 10* faster on gitea. gitlab really is a bit of a hog.
zzz
zowie the 3 year old UDP tracker proposal needs a lot of work ((
eyedeekay
OK I'm back. I got custom homepage so far, that's no big deal I can do that this evening, what else?
dr|z3d
you might want to enable the more heavy duty search, otherwise it just uses git grep.
dr|z3d
I *think* it indexes every time gitea's restarted when you enable, but let me know if you find other methods to trigger a reindex.
zzz
eyedeekay, failed to push (permissions?) to any repo, either my acct or the main one
zzz
I also changed .git/config from i2p-hackers to I2P_Developers, which you didn't mention, but I guess only applies to me, didn't help
eyedeekay
OK, probably a permissions thing, I'll figure it out now
zzz
reminder: review in 5 minutes in #ls2
orignal
zzz, qend-irc2p has a request about SAM
orignal
is there a way to forward peer's LS info to client?
orignal
not only address but trasient encryprion/signing keys
zzz
no, nothing in the spec about that
orignal
I know
orignal
but we might add one
StormyCloud
<3 everyone glad the migration went smooth