Well, for one, like the guy says below, it was often said to people as a means to explain how federation works, which immediately failed by way of people not thinking about or knowing how email works, either.

For another, my emails look like emails everywhere, both on source and destination. I don't have a different character limit or feature set about what I can slap into my emails depending on what client I'm using, and I'm reasonably sure my email looks the same on the other end, no mater what client the recipient is using.

So the back end may work like email (not really, but it may approximate it), but the front end sure as hell doesn't, so the explanation is more confusing than anything else.

Also, not the part of Mastodon specifically that people didn't understand, they just tried to log in, were presented with a thousand instances, told choosing which one to use was super important but also that it didn't matter and they should keep changing instances later, but also that migrating instances was not an easy process, but don't worry, it's just like email.

It was a hilarious endless loop of a conversation, like a Monty Python sketch. Or seeing people try to tell normies to use Linux.

For another, my emails look like emails everywhere, both on source and destination. I don't have a different character limit or feature set about what I can slap into my emails depending on what client I'm using, and I'm reasonably sure my email looks the same on the other end, no mater what client the recipient is using.

This is mostly the case now due to centralized email by a few providers and bountiful bandwidth, but it was certainly not the case 20+ years ago.

Also, not the part of Mastodon specifically that people didn't understand, they just tried to log in, were presented with a thousand instances, told choosing which one to use was super important but also that it didn't matter and they should keep changing instances later, but also that migrating instances was not an easy process, but don't worry, it's just like email.

People used to do the same with email before google and microsoft dominated email. It's just that in most cases, your ISP provided you with an email when you first signed up. Switching email provider currently is way more onerous than switching mastodon or lemmy providers. If each ISP nowadays hosten their own say, friendica server and provided you with a login immediately, it would have a similar effect of solving this difficulty of choosing.

Well, it does if the person on the receiving end gets nothing useful from it. That's my point, the confusion around Masto specifically wasn't "why do people with different handles get to talk to each other?" That's something that enthusiasts and developers care about and users don't even notice.

The question that was being asked was "why do I need to pick an instance at all and what does it affect?" and that didn't even BEGIN to explain the mess of themed instances, personal instances, effects of instance population on post distribution, manual blocks and defederations, what things did and did not make the leap cross-instance and the whole bunch of other details that matter.

A much better answer was "it doesn't matter, just sign in to mastodon.social and call it a day", but people used to be reticent to argue for centralization, because... decentralization!, so...

Ultimately the answer to that problem ended up going to Bluesky, which I think was very much a problem with both the design and the community at Masto. I actually think the Lemmy/MBin/Fedia Reddit-like corner of federated services is much more workable than a Twitter substitute. And it doesn't even need a bad email analogy to kinda just work, either.