&zzz
+R4SAS
+RN_
+T3s|4
+eche|off
+nilbog
+orignal
+postman
+qend-irc2p
+sourceress
Arch
Birdy
Danny
Irc2PGuest30010
Irc2PGuest36077
Irc2PGuest49364
Irc2PGuest51117
Irc2PGuest6564
Irc2PGuest65656
Irc2PGuest67278
Irc2PGuest74235
Irc2PGuest83482
MatrixBot
Onn4l7h
Over
Sleepy
Teeed
Yotsu
__bob_
aargh3
ac9f
acetone_
ahiru
anontor
b3t4f4c3__
cims
dr4wd3_
dr|z3d
duanin2
hababam
hagen_
leopold
makoto
marek
marek22k
n2
noidea
not_bob_afk2
nyaa2pguy
o3d3_
poriori
profetikla
r00tobo
rapidash
solidx66
stormycloud[m]
test7363673
uop23ip
urist_
user_
w8rabbit
zelgomer
eyedeekay
Github's a little behind but a long-term fix for syncing from i2pgit.org/I2P_Developers/ to github.com/i2p should be deployed tomorrow: i2pgit.org/go-i2p/go-github-sync
eyedeekay
So some of those annoying red x's that have been happening since the migration will go away
eyedeekay
And like the other applications that have come as a by-product of migrating to gitea, it's designed to be useful to anybody who has the same problem, not some just-us hackjob
dr|z3d
I keep it simple and sync the other way.
dr|z3d
push to github, sync to gitea.
zzz
TIL sudo journalctl --disk-usage
dr|z3d
I keep my journal trimmed to max 1 day. Keeps it sane.
zzz
found it trying to free up enough space on my chromebook to update it
zzz
all my boxes were using 1 to 4 GB (!)
zzz
in the end I moved and mounted /var on an external drive, then upgraded all the way bionic-focal-jammy-noble, then moved it back
zzz
yup. fixed my fleet