this post was submitted on 09 Jun 2023
61 points (98.4% liked)
Asklemmy
43963 readers
1231 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- [email protected]: a community for finding communities
~Icon~ ~by~ ~@Double_[email protected]~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Interesting, do you think this approach will limit how big Lemmy can get? For example, if a server wanted to subscribe to ten communities that are the size of large subreddits, how much data would that be? How much would it cost to maintain a server that could handle that?
Generally speaking, text is cheap to transmit and store. It's images and video that could be a real issue.
But ultimately, content on small instances may end up being somewhat ephemeral. Developers and admins may want to look into ways to earmark significant posts so that they don't end up in the dustbin, but 90%+ of what gets posted to social media isn't actually worth saving long term anyway.
Only text is mirrored, images and video are hosted on the instance where they were posted, so overall it's really cheap to store all of that, and even more so if the load is distributed across many instances.