Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Please don't post about US Politics. If you need to do this, try [email protected]
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
The software architect of lemmy is unfortunately doomed. The very concept of how it works means exponential storage and bandwidth needs as it grows in sublemmits and instances. A better design would have been instances being the sublemmits themselves, and leaving it up to the clients to subscribe and aggregate them into a feed. This way scaling is a lot more horizontal, and communities that get too big can scale up individually or purge old data without affecting the rest of the system.
I assume this is a larger theme across the Fediverse?
Could you expand on what causes the massive bandwidth needs? I'm have a vague idea but I'd be very curious to know.
If a user of an instance subscribes to content from another instance, their home instance is pulling, storing and sharing that content. With more and more instances, more time will be spent on sharing that content.
If the design itself is bad, then something will eventually spring up that will replace it. That’s the beauty of nascent platforms; they haven’t completely cornered the market.