this post was submitted on 23 Jun 2023
188 points (100.0% liked)
Technology
37705 readers
142 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
They desperately need to support horizontal scaling. I'm sure there are enough nerds that could help them out there.
But we already have horizontal scaling in the form of separate instances. We just need to do a better job staying spread out. Making individual instances bigger is not a good thing, it makes everything more centralized.
That’s too complicated for the average user.
Maybe but it's a big point of the Fediverse
I’d hate for this to become an echo chamber of people that understand federated services. That excludes a lot of people that have no interest in it that have valuable input.
tbh I was thinking about this today, and I think there is some merit to having the setup be slightly obtuse so that more of the people on any given thing are the kind of people who think this kind of tech is important, rather than people who don't give a shit about that.
At least, I like when spaces are more densely that kind of person. But other people should have nice things too I guess.
Not really. They're all connected anyways, and if they use an app they'll probably never notice apart from the @instance.com theu have to put at the end of some communities
It doesn't require users to enforce. Individual instances should probably start having caps and close signups/invites occasionally.
I agree. I think one of the easiest ways to encourage users to bring up more instances is to minimize the requirements and steps needed to get a Kbin or lemmy instance running. Its not a very complex process to get an instance running, but it can be difficult to locate the relevant information you might need to spin up an instance without reaching out for support. That could end up putting people off of setting up an instance.
We need user caps on a per-instance basis tbh
If it grows fast and hard it might happen naturally. lemmy.world is suffering already.
Ya I'd much rather lemmy.world set an actual user cap of what they can actually handle ^^
Just accepting users until your system stops working is a bad system.
Is the blocker here that each instance is a single postgres/Lemmy process? I imagine a clustered inplementstion of the Lemmy backend could be used to shard individual communities to dedicated containers when they reach a given size, proxies through a community away load balancer? More to manage but would let instances scale up/down as needed. There are costs associated with this, but those of us who run instances do it because we like playing this game.
Yeah, from what I understand most instances are pretty much the modern day equivalent of a phpBB forum on a server in someone’s bedroom. This situation is basically an invitation for the sort of people who play with Kubernetes for fun, get one of them involved and a lot of these problems will be at least reduced a fair bit.