i guess at some point they could Introduce timed caching.
Like a Post from lets say 2021 could get removed at a foreign instance till someone wants to access it again on Instance X while its original from Y.
### About Community Tracking and helping #redditmigration to Kbin and the Fediverse. Say hello to the decentralized and open future. To see latest reeddit blackout info, see here: https://reddark.untone.uk/
i guess at some point they could Introduce timed caching.
Like a Post from lets say 2021 could get removed at a foreign instance till someone wants to access it again on Instance X while its original from Y.
This is the solution Usenet uses. I'd expect it to make it's way to the fediverse if it gets big enough.
I'm still learning but share your concern.
I also think there's different dimensions to the growth too. A lemmy server such as programming.dev may have many communities which become popular and it's primary task is to be the home to those communities and federate that out to the wider community.
At the same time it has to pull in any random community that even a single user on that server wants to look at and store it.
The server that is home to programming discussion could buckle under the load of too many posts to /c/funny. It doesn't seem right. They are different responsiblities.
Does lemmy federate images as well or only text? I think it only does text and loads images from the original instance. In that case, its not a lot of storage.