Mastodon media storage graph for the past year. I wonder what happened in April and then again in November…
(I’ve still got media going to AWS from when I set up the server myself even though it’s with @mastohost now… because, lazy.)
@aral @mastohost do you know you can periodically prune the image cache without breaking anything? The last release allows to enable it by the administration panel too.
Aral, I have to say… I was not expecting to see you using #AWS!
@RyunoKi @emanuele @aral there is already automated cache cleaning in place. As explained here https://masto.host/re-mastodon-media-storage/ or the numbers would be much higher.
But Aral can use more aggressive limits in the admin interface. For media it’s fine but for content it can lead to unwanted consequences as I mention here https://github.com/mastodon/mastodon/discussions/19260
@RyunoKi @emanuele @aral Still what can actually help is this https://github.com/mastodon/mastodon/pull/21066 because currently there is no way to remove avatars and headers. And everyone that ever federated with a server will have their avatar and header cached forever.
@mastohost Ah, and it looks like that’s closed for now :(
@mastohost Ooh, that’d be interesting to know. But only if it’s no trouble, Hugo and if/when it’s convenient. I know you’ve got your hands full with the influx of new people.
@aral Yep, the other items are automatically cache deleted using `tootctl` with the number of days mentioned on https://masto.host/re-mastodon-media-storage/
But `tootctl` does not allow to clear the Avatars/Headers cache and they are cached indefinitely for everyone that has ever federated with your server.
That's like almost the half of
@aral @mastohost It's also good question from the data protection angle as avatars (profile pictures) can be considered personal data, so a software that (currently) can't delete such is at risk from more than a few regulations. While the problems are limited at the moment, it will likely get more difficult in the future.