To support decentralization and spread, should lemmy.world close registration at some point to prevent a performance overload due to too many users? Of course, if registration is disabled, there could be a hint placed somewhere near that from other instances you can interact with content on lemmy.world just like you had registered on it. There could be a link to join-lemmys instance overview.
One of the great things about lemmy.world’s insane user count growth is actual live stress testing of Lemmy software. Instead of having an open question of how Lemmy might scale with large instances, there’s now real world production systems providing that opportunity.
The technical issues will pass, but the notion that merely spreading out the load will alleviate them is probably just treating the symptom than the cause.
I suppose from my PoV I see this as very much live testing in production and have adjusted my expectations around that instead of anticipating a wholly seamless experience.
Lemmy.world - on the way to being the new reddit
Cheered on by its new users.
I think no.
I’m having the same issues with pages not loading as everybody else - but this is a critical moment for Lemmy. A site like this only works if it has a lot of users - the more signups the better.
I understand that new users can sign up for other instances, and still see and interact with lemmy.world content - but I think adding any barrier to entry at all will potentially discourage a huge number of new users. As a rule, new users have no idea how lemmy, federation, instances, etc work - and telling them they can’t sign up and to consider another instance will probably end with a lot of them just giving up and sticking to reddit.
The server issues will pass, but stunting our growth at such a critical stage might not. It’s bad enough that beehaw defederated at a time like this.
I honestly think during the sign up the registration to a server needs to be randomized to spread the load. That and allow the user counts to be global and not just to your instance and you then have user load balancing.
If we could also migrate our data between servers with a backup server option. When lemmy.world goes down, just switch to a different randomized backup server.
The danger in randomizing servers is that some smaller servers not only have less than 99% uptime but are also just run by random regular people who couldn’t handle the increased load and/or have no desire or ability to keep the servers running long term. It could maybe work if the randomization occurs from within a vetted list.
Account migration is a feature that has been noted for the future and would indeed be very important since it would essentially make the entire network bulletproof. Being able to move instances and/or link accounts across multiple instances would create the necessary redundancy and reduce fears of choosing a smaller instance as home.
I couldn’t get anything to load in my phone browser half the time either and my updoots never register. Then I downloaded the jebora app and when it disconnects from the server it flashes at the bottom so you know when it won’t post.
Now I can see everything on the site all the time
What’s to stop .world “defederating” and cutting all the new users off completely.
It’s an odd platform and one that feels like it could all fall apart to someone completely new to it all.
Well Ruud who runs .world also runs Mastodon.world which is a fairly large mastodon instance, so he is somewhat of a known quantity and has experience running large Fediverse servers. His mastodon server has handled a large population and donations happen through Open Collective for transparency as well. He also runs Calckey.world though that is much smaller.
As an immigrant from reddit myself, the multiple instances and where to call my home was the first big hurtle by far. With that, my biggest concern was if the instance I was joining was going to allow me to see everything in the fediverse since instances can be blocked.
Right now I have a kbin and Lemmy account. Because although the Lemmy account I’m on isn’t being blocked by anyone, I’m finding it difficult to find some instances where on kbin the same search yields the results I’m looking for.
I’m in favor of simplifying the signup process with auto-assigning an instance. [Edit: For users coming from https://join-lemmy.org/]
For people who start using the fediverse or lemmy, the concept of federated instances is hard to understand. It also does not matter that much at this part of their journey. How about randomly assigning new users to instances which are open? This could also help with load balancing between instances.
The idea is to make entry as quick and easy as possible. Once users familiarized themselves with content and communities, they can reevaluate their ‘decision’ which instance they want to make their home. At this point, they have a better idea what this is all about.
Choosing an instance right from the start should still be possible, just not be the default mode. Make it a small link at the bottom ‘advanced mode’ or whatever, just don’t scare or burden newcomers with unecessary complexity.
To answer the question directly: I think each instance can make that decision for themselves, and open or close registration accordingly. Both is fine.
Not all instances are going to be equal in terms of things like stability and uptime. It’s going to be unfair and frustrating to users who might randomly end up on a bad instance. It might work if it only chose along the top x instances or something, to ensure a bit of reliability for new users.
It’s going to be unfair and frustrating to users who might randomly end up on a bad instance.
That’s true. On the other hand, we currently entrust this decision to people who know the least.
I think we should weigh the benefits of an uninformed decision against the benefits of making signup easier.
It might work if it only chose along the top x instances or something, to ensure a bit of reliability for new users.
Yes, that sounds like a good idea. Not sure if top x is the right measure, but you’re right reliability should be a criterion.
It makes sense to pause registrations if an instance is actively overloaded, but there’s no reason it can’t keep growing if more hardware is added and the performance issues are resolved.
Some of the issues might be on the software side, so it’ll take some time until it can scale to more hardware resources. But yeah, I agree! What scares me more is the monetization path. Servers can become a really expensive.
With a larger userbase comes more people willing to donate, so it will depend on whether that revenue stream grows faster or slower than the increasing server costs. Mastodon.world has run fine on donations alone but lemmy.world will soon outgrow it so we’re entering uncharted territory for Ruud. Mastodon.social is significantly larger but I believe they also have sponsors and grants to complement the donations.
I get the point, but that limits the users’ right to select which community they want to join. I feel that is more important than preemptive decentralization of content. Hopefully there is a way to migrate communities from one instance to another. Should an instance get too large that would be a good feature to mitigate risk.
I’m not a lemmy.world user (so I have no dog in this debate) but I’m gonna disagree. I’m of the opinion that signups for an instance should stay open as long as the admins can afford/handle the growth. I think it’s unfair to force the admins to keep it open if they aren’t able to handle it which is the crux of what OP is asking.
Besides, it’s not like those users cant just federate with all the communities of lemmy.world they want. And I bet there won’t be a dearth of choices for decent instances if the demand calls for it. Lemmy.ml closed signups despite being the big instance and lemmy.world emerged as an alternative. So why wouldn’t something similar happen if lemmy.world did the same?
