What if we upgraded GoToSocial to the 0.22 RC, because we're liking downtime lately?
Compiled, pushed to Luggage, time to make a database backup, and upgrade. See you in - probably - a couple of hours I guess.
~35 minutes was it or so? I expected slower. Not complaining, though.
Now lets configure some media & old remote status expiry to cut down on database & storage size!
Nevermind. I thought I saw a GtS federation bug, but no. Just normal errors, business as usual.
timestamp="15/06/2026 20:16:38.893" func=media.PruneRemote level=INFO msg="prune DRY RUN"
timestamp="15/06/2026 20:16:38.893" func=cleaner.(*Media).LogPruneUnused level=INFO msg=start
timestamp="15/06/2026 20:18:44.994" func=cleaner.(*Media).LogPruneUnused level=INFO msg="pruned: 292"
timestamp="15/06/2026 20:18:44.994" func=cleaner.(*Media).LogUncacheRemote level=INFO msg="start older than: Jun 8 2026 20:16:38"
timestamp="15/06/2026 20:18:51.191" func=cleaner.(*Media).LogUncacheRemote level=INFO msg="uncached: 4724"
Hm. Maybe I should set 6 month?
Hrm, same numbers. I guess I gave the CLI param wrong or something. Oh well. Will try again after bedtime stories.
