@eyedeekay
&zzz
+R4SAS
+RN
+RN_
+Stormycloud
+T3s|4
+acetone
+anonymousmaybe
+dr|z3d
+eche|off
+hagen
+hk
+mareki2p
+orignal
+postman
+qend-irc2p
+snex
+weko
+wodencafe
Arch
BubbRubb
Danny
DeltaOreo
FreefallHeavens
HowardPlayzOfAdmin
Irc2PGuest57893
Irc2PGuest82088
Irc2PGuest85022
Irc2PGuest86602
Leopold_
Onn4l7h
Onn4|7h
SigSegv
Sleepy
T3s|4_
Teeed
aargh
ardu
b3t4f4c3__
bak83
cumlord
death
dr4wd3
duanin2
eyedeekay_bnc
idontpee
nnm_
not_bob_afk
ohThuku1
onon_
profetikla
r00tobo_BNC
rapidash
rascal
shiver_
solidx66
thetia
u5657
uop23ip
w8rabbit
wew-
x74a6
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