Yeah, I’ve tested the app out. But the problem is that people who don’t know any better (which almost none of new people do, me included when I was new) will just use the default. Which is down a lot. This causes two things:
forces lemmy.world to upgrade its hardware all the time
discourages new users from trying Lemmy because it doesn’t work
Getting a list of some instances (that are not as overcrowded) and assigning one at random by default would be the best way to go about it.
I mean, it’s obviously fine for them (the problems will probably get stable after some time and they gain more users in the process), but it’s not good for Lemmy overall and not for new users.
Honestly I think having a default one is necessary for users to put their trust in the service. If there’s no lemmy.world, another server will become the go to (it used to be lemmy.ml before world). People want to have their account on the instance all their friends have it on so that they’d never be alone in losing their account or the service being offline for them. And the bigger the instance, the more trustworthy it seems.
Lemmy.world has also been a tremendous help in debugging performance issues due to necessity.
Honestly I think having a default one is necessary for users to put their trust in the service
As I said:
Getting a list of some instances (that are not as overcrowded) and assigning one at random by default would be the best way to go about it.
People want to have their account on the instance all their friends have it on so that they’d never be alone in losing their account or the service being offline for them
Fediverse drama being what it is, though, that’d probably involve the dev in all sorts of arguments and debates he’d rather not touch with a ten foot pole
Yeah, I’ve tested the app out. But the problem is that people who don’t know any better (which almost none of new people do, me included when I was new) will just use the default. Which is down a lot. This causes two things:
Getting a list of some instances (that are not as overcrowded) and assigning one at random by default would be the best way to go about it.
I’ve been chatting with the lemmy.world admins and specifically asked if pointing at the default was fine.
I mean, it’s obviously fine for them (the problems will probably get stable after some time and they gain more users in the process), but it’s not good for Lemmy overall and not for new users.
Honestly I think having a default one is necessary for users to put their trust in the service. If there’s no lemmy.world, another server will become the go to (it used to be lemmy.ml before world). People want to have their account on the instance all their friends have it on so that they’d never be alone in losing their account or the service being offline for them. And the bigger the instance, the more trustworthy it seems.
Lemmy.world has also been a tremendous help in debugging performance issues due to necessity.
As I said:
That… doesn’t make sense.
Fediverse drama being what it is, though, that’d probably involve the dev in all sorts of arguments and debates he’d rather not touch with a ten foot pole
Possibly, but if you want to get paid more, maybe your app shouldn’t expose “lemmy.world is having issues” as one of the first things new people see.