We don't have email instances, and email providers similarly block un-desired content, but there's not a big fuss about missing out on specific types of spam. Lol.
Similarly Internet service providers actually also block big blocks of malware providing domains, and accidentally sometimes block some great piracy resources. People who care learn to use a VPN or switch providers. Everyone else doesn't have to think about it.
I'll argue that The Fediverse also carries extremely similar switching cost as an email or Internet provider. For an average user, "Let folks you care to inform know where you moved, and maybe copy over some favorite bookmarks."
Sure, different providers do try to bring different lenses on the same federated content, but most people aren't served well by thinking about it on day one.
I think shifting to the term provider is a lot more honest to the user about what to expect.
Provider has the connotation of being a paid provider for services. While it’s a technically accurate analogy, I prefer the more abstract comparison of considering the fediverse a meeting place rather than a paid service since it’s a mostly volunteer and self hosted network compared to email.
I think instance is okay as a term, but defining it as a provider could be helpful. I don't think the fediverse is that complicated anyway, it could be summarized in a paragraph for a baby
As a term, 'instance' is already baked into code, databases, and APIs.
If I wanted to use an API to block 'lemmy.world', for example, I'd call 'site/block' with the relevant 'instance_id'. That's already 2 different terms for the same thing ('site' and 'instance'), which isn't great, but adding 'provider' into the mix means you're now saying "if you want to block a 'provider', use the 'site' endpoint with the ID for the 'instance'", which is arguably worse.
I wouldn't even mention anything about servers or how it works, since most anyone I would even tell about Lemmy won't understand the technical details, nor would they care. It would only confuse them and push them away.
Just hook them up with an instance they will fit into, and have them use the site. I really think that a lot of the other tech nerds here are overthinking it and trying to get non-tech minded people to switch by giving them technical details that do more harm and cause more confusion than simply having them use the site without knowing jack shit about it other than "it's like Reddit but not shitty."
That's really all you gotta tell most people; "it's like Reddit (or Twitter if you're trying to talk up Mastodon), but not shitty."
I use this approach sometimes and it really works. Provided it's the erm.. simple type of crowd that doesn't ask too many questions lol. They'll wander around and figure it out. If they do, congratulations😂
I agree, let's make it more friendly to people wanting to start a fediverse provider as a business so a big company can't come in and gobble up everyone
Sure, go ahead. Technically it's not 100% correct. I mean lemm.ee wouldn't be your provider, it'd be the people operating the server who provide the service to you... But I think it's close enough. Only issue I can see is the term "provider" usually being used with commercial services. Like a cellphone provider or ISP. So I'm not sure if people start to think this costs $10 a month or something and is run by for-profit businesses... But we also use the word "provider" for free things, so I'm not entirely sure about that. But generally speaking I think we use different terminology because we don't think of the Fediverse as a product.
People can perfectly understand terms like instance or server...if they are explained to them.
They are also accustomed to concepts like social media and social network that can also be used to explain the Fediverse. Each server is its own social media platforms interacting with eachother through a distributed social network.
But, I actually think the Fediverse require an intermediate point between social media and social network, or something above it.
If the Fediverse (including in this case all decentralised protocols like ActivityPub, Zot/Nomad, Diaspora, Ostatus, AT Proto, etc) is a Social network and each particular instance it's own social media platforms that interact within the network, the software they run and the community they form part of within the wider fediverse is an intermediate stage between social medium and social network.
Now, if each server/instance are social media platforms and the software they run are the social network; the protocol or protocol they use is/are a network of networks and the Fediverse a network of networks of networks of social media platforms.