John Federico ☑︎ (@gadgetboy@gadgetboy.social)
gadgetboy.social
Attached: 1 image I figured this would happen. In just over 48 hours, I’ve already exceeded my Media Storage limit on my masto.host “Moon” plan. I’m going to see if I can purge the cache more frequently. Otherwise, I’m going to have to upgrade. #mastodon #fediverse #hosting

I set up a personal instance using https://masto.host. It’s a small operation that I believe is run by one person. Hugo has been great about responding to my questions.

My instance has only been up for about 3 days and I’ve exceeded my Media Storage limit twice. The first time, I upgraded to the “Planet” plan which has the added bonus of being more responsive.

This time, I’ve tried setting my Media Retention Period to 3 days and am hoping that’s sufficient.

Do you have any other optimization tips to share? Unfortunately (but also, fortunately), it’s a managed service, so I’m limited to only what is available in the Mastodon web interface.

  • Mayana@sub.wetshaving.socialEnglish
    1·
    2 years ago

    It may help you some to block media from bot instances, such as BotsIn.space. Of course, that may be inconvenient if you or your users follow bots that post images.

    You could also import one of the blocklists from Oliphant or another collection. Of course, their purpose is mainly to avoid bigotry and harassment, but depending on how many of them you’re federated with, it may have a slight affect on space used as well.

    Of course, none of these are even slightly as effective as deleting media server-side, but that’s something the Masto.host owner would have to help you with, here.