this post was submitted on 11 Jul 2023
140 points (100.0% liked)
Fediverse
287 readers
1 users here now
This magazine is dedicated to discussions on the federated social networking ecosystem, which includes decentralized and open-source social media platforms. Whether you are a user, developer, or simply interested in the concept of decentralized social media, this is the place for you. Here you can share your knowledge, ask questions, and engage in discussions on topics such as the benefits and challenges of decentralized social media, new and existing federated platforms, and more. From the latest developments and trends to ethical considerations and the future of federated social media, this category covers a wide range of topics related to the Fediverse.
founded 1 year ago
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
On Mastodon, like kbin and lemmy, locally posted images are hosted locally, and remotely hosted images are cached locally. This can cause a lot of storage. But you can run an automated cron that will clear out cached images older than whatever you want, like a month. Then the local cached storage is at a minimum, and if someone wants to view the image again, it'll get fetched. I don't know if kbin and lemmy have this feature, but they should. It's probably not the locally uploaded images that'll take up a ton of space, it's caching all the remote ones that will.
Note that not all instances do this. Especially not necessarily if they aren't mastodon. My calckey instance for example has it optional and i have it off there. Akkoma i know also can do it optionally.