People see that they have the highest user count and gravitate towards it. Most people don’t really get how federation works, so they worry about getting “stuck” on an instance with no one to talk to
I think that it was also influenced by it being the developer’s instance (thus kinda had some official-ness to it, combined with the domain name reflecting the name of the service) and people wanting to just give newcomers an easy onboard by directing them straight to a link rather than to join-lemmy where some people get confused about choosing an instance. I had seen it in a few subs on reddit where it was just people putting lemmy.ml rather than join lemmy to give someone alternatives to reddit.
If you imagine you’re targeting reddit users looking for an alternative and you already know that some people get confused by choosing instances, you’re potentially more influenced to just give them a link to one of the instances. Doesn’t really matter where they sign up to an extent since it’s all federated, just need to skip them past the part that might confuse them. Then if you’re doing that, you’re also making it more familiar to things they understand by using a domain that looks official. If you say, “Use Lemmy” and then put “beehaw.org”, some might question why it’s called Lemmy but the website is beehaw. You don’t go to reddit.com but call it Linkit, so it may have seemed better to just use lemmy.ml to tell people to use Lemmy. Of course if you onboard people through join-lemmy then it better contextualizes names of instances that don’t have lemmy in them, but I think people were just trying to find ways to spread the word without potentially confusing people with the federation aspect.
I to thought it wise to pick one with high numbers. It had nothing to do with being afraid of not having people to talk to though, as I understood that we’d all be connected. It was more a fear that an instance with 20 users might get shut down because the owner got bored. In my mind it seems less likely that a popular instance gets shut down.
So what happens to an account if an I stance goes away?
Makes sense. I assume the same applies to communities hosted be said instance. What, however, happens to posts one has made on other communities whos instances are still running? I assume posts made there will still be there, but the usernames will point to dead links?
Is it at all possible to migrate users or communities from one instance to another?
it isnt currently possible to migrate users from an instance to another but there is an issue on github about it so maybe it will get implemented at some point as for posts from a deleted instance im not sure maybe someone else can answer that
This is 100% me, but my understanding is that you can see all community content and interact with everyone regardless of what server you’re on, is that more or less correct? I went with beehaw because it seemed moderately popular (I’d read that servers can disappear, and figure more users=less likely?) and is focused on keeping out assholes, which I am 100% cool with.
As long as the instances who’s content you’re trying to interact with are federating with your instance (beehaw), then you can interact with everyone, yes. It’s important to keep in mind instances can choose to not federate entirely, or selectively block certain instances from interacting with theirs, although this isn’t something you should have to worry about.
A good analogy I’m seeing thrown around is email: everyone has their own email provider - gmail, yahoo, outlook, or a corporate email server, etc - but all of those can send and receive emails from every other one. I have gmail, but I can email you at yahoo, and recieve emails from my friend on hotmail. If gmail starts being shitty and corporate or making decisions I don’t like, I can switch to a different provider, and crucially, gmail doesn’t get to decide how the rest of the email universe behaves.
Lemmy instances are like the email providers, and “sending emails” is like interacting with communites on any instance. If my Lemmy instance starts serving ads or something I can just leave it, and still have access to all the other communites on every other instance.
People see that they have the highest user count and gravitate towards it. Most people don’t really get how federation works, so they worry about getting “stuck” on an instance with no one to talk to
I think that it was also influenced by it being the developer’s instance (thus kinda had some official-ness to it, combined with the domain name reflecting the name of the service) and people wanting to just give newcomers an easy onboard by directing them straight to a link rather than to join-lemmy where some people get confused about choosing an instance. I had seen it in a few subs on reddit where it was just people putting lemmy.ml rather than join lemmy to give someone alternatives to reddit.
If you imagine you’re targeting reddit users looking for an alternative and you already know that some people get confused by choosing instances, you’re potentially more influenced to just give them a link to one of the instances. Doesn’t really matter where they sign up to an extent since it’s all federated, just need to skip them past the part that might confuse them. Then if you’re doing that, you’re also making it more familiar to things they understand by using a domain that looks official. If you say, “Use Lemmy” and then put “beehaw.org”, some might question why it’s called Lemmy but the website is beehaw. You don’t go to reddit.com but call it Linkit, so it may have seemed better to just use lemmy.ml to tell people to use Lemmy. Of course if you onboard people through join-lemmy then it better contextualizes names of instances that don’t have lemmy in them, but I think people were just trying to find ways to spread the word without potentially confusing people with the federation aspect.
I to thought it wise to pick one with high numbers. It had nothing to do with being afraid of not having people to talk to though, as I understood that we’d all be connected. It was more a fear that an instance with 20 users might get shut down because the owner got bored. In my mind it seems less likely that a popular instance gets shut down.
So what happens to an account if an I stance goes away?
it gets deleted and you would need to sign up to another instance
Makes sense. I assume the same applies to communities hosted be said instance. What, however, happens to posts one has made on other communities whos instances are still running? I assume posts made there will still be there, but the usernames will point to dead links?
Is it at all possible to migrate users or communities from one instance to another?
it isnt currently possible to migrate users from an instance to another but there is an issue on github about it so maybe it will get implemented at some point as for posts from a deleted instance im not sure maybe someone else can answer that
This is 100% me, but my understanding is that you can see all community content and interact with everyone regardless of what server you’re on, is that more or less correct? I went with beehaw because it seemed moderately popular (I’d read that servers can disappear, and figure more users=less likely?) and is focused on keeping out assholes, which I am 100% cool with.
As long as the instances who’s content you’re trying to interact with are federating with your instance (beehaw), then you can interact with everyone, yes. It’s important to keep in mind instances can choose to not federate entirely, or selectively block certain instances from interacting with theirs, although this isn’t something you should have to worry about.
A good analogy I’m seeing thrown around is email: everyone has their own email provider - gmail, yahoo, outlook, or a corporate email server, etc - but all of those can send and receive emails from every other one. I have gmail, but I can email you at yahoo, and recieve emails from my friend on hotmail. If gmail starts being shitty and corporate or making decisions I don’t like, I can switch to a different provider, and crucially, gmail doesn’t get to decide how the rest of the email universe behaves.
Lemmy instances are like the email providers, and “sending emails” is like interacting with communites on any instance. If my Lemmy instance starts serving ads or something I can just leave it, and still have access to all the other communites on every other instance.
That’s really helpful, thanks!