&zzz
+FreefallHeavens
+R4SAS
+RN
+StormyCloud
+T3s|4
+acetone
+cims
+eche|off
+fa
+mareki2p
+nilbog
+orignal
+postman
+qend-irc2p
+rednode
+snex
+wodencafe
Arch
Danny
Irc2PGuest28384
Irc2PGuest66257
Irc2PGuest75631
Irc2PGuest81267
Onn4l7h
Onn4|7h
Over
ReturningNovice
Sisyphus_
Sleepy
T3s|4_
U1F642
Watson
Zapek
aargh4
ahiru
ananas
anontor
calamares
dr4wd3
dr|z3d
duanin2
i2potus
ice_juice
justaperson
luvme
mahlay
makoto
marek22k
n2_
not_bob_afk
onon_
pinotto
poriori
profetikla
psychopuck
r00tobo
rapidash
test7363673
uop23ip
w8rabbit
x74a6
zelgomer
dr|z3d
Having thought about it, the mod is more consistent with the values displayed in the footer, which are otherwise for all torrents, not just displayed torrents.
eyedeekay
gah gitea still a little bumpy... will be back soon
eyedeekay
Ha, of course it was the script I added to restart it if it went down.
eyedeekay
Showed a bug in onramp(albeit a hard-to-hit one) though so I can fix that
dr|z3d
script?
dr|z3d
why don't you just make it a systemd service?
dr|z3d
I think they provide a demo service file you just need to tweak.
eyedeekay
Right now there's a bug in "go-meta-listener" which is a descendant of "onramp" wherein if one of the listeners inside the metalistener dies, the others will survive it, the practical effect of this on go-gitlooseleaf is that if one of the member listeners dies gitea process lives on
eyedeekay
So I need to make it so if one member listener of the meta-listener(which handles the mirroring) dies then all of it's buddies die too, so the process dies and can be cleaned up
eyedeekay
Or maybe, less likely, I blow away the old listener and recreate it, but I'm not sure how I could trigger that
eyedeekay
The other effect(and actually the intended one) is that the surviving listeners... survive. The Tor HS and the base32+https endpoints lived through it
dr|z3d
I don't think I've ever seen gitea go down tbh.
dr|z3d
maybe I haven't been watching hard enough, though, and systemd is covering it, but it seems pretty robust here.
eyedeekay
It is, but I'm running the nightly so I can test a few features that are going to come out and be relevant to us in the next release
dr|z3d
you and me both :)
dr|z3d
what are you doing with the tor/i2p endpoints? or rather, how are you implementing those?
dr|z3d
now you've said nightly, expect zzz to be holding your feet to the fire when he notices :)
eyedeekay
This is fun actually, I worked with the gitea people on this feature years ago
eyedeekay
So it turns out that you can replace the function that generates the listeners for gitea and replace them with whatever you want
eyedeekay
And you can do it all in separate files to make it impossible to cause a merge conflict
dr|z3d
"this is fun" is about as good a commendation as any. I doubt you were saying that about gitlab :)
eyedeekay
so due to this one quirk about how gitea works I can set up a mostly-CI repository that does this: github.com/go-i2p/go-gitlooseleaf
dr|z3d
looks good
eyedeekay
And automatically builds a gitea that automatically configures itself to work for hidden services, both as an "incoming" server when people need to use it and as an "outgoing" server when it needs to talk to other servers
eyedeekay
That's the "every network" version, then github.com/go-i2p/go-gittisane is the "only I2P" version
eyedeekay
But both mostly just re-use parts of other libraries with a tiny amount of gitea glue in between
eyedeekay
All of which would have been dementedly unreliable with gitlab's mix of go, ruby, and javascript
eyedeekay
I can actually even send and receive federated pull requests now with some limitations
eyedeekay
bunch of assholes poking around looking for hardcoded or mistakenly checked in credentials right now, I'm seeing all 404's but everybody be careful
eyedeekay
Path traversal attempt this, scraper that...
eyedeekay
I assume all this was happening on gitlab, but with completely incomprehensible logs
dr|z3d
sounds like they're presenting the paths you need to proscribe via fail2ban
eyedeekay
Indeed they are
eyedeekay
Besides that, if anybody else is having a hard time keeping up with github notifications because github's homepage is like, 75% noise: i2p.github.io/go-github-dashboard
eyedeekay
It works for any github org or user