Documents the long-standing UX regression caused by `tootctl media remove --prune-profiles` (and `--remove-headers`) running on a schedule: cached remote avatars are deleted, but Mastodon does not auto-refetch on profile view, so quiet remote accounts stay broken indefinitely. Article covers: - The mutually-exclusive flag bug (silent skip if combined) - Mastodon's actual avatar-refresh trigger model (Update activities, not profile views) - A `refresh-my-follows.sh` pattern with a defensible WHERE clause (avatar NULL AND avatar_remote_url present) to avoid infinite retry on accounts whose origin has no avatar - Why header_file_name IS NULL is a bad signal (~20% of users legitimately have no custom header) - The cron decision: most admins should drop --prune-profiles |
||
|---|---|---|
| .. | ||
| cloud | ||
| dns-networking | ||
| docker | ||
| monitoring | ||
| reverse-proxy | ||
| security | ||
| services | ||
| storage-backup | ||
| index.md | ||