It’s the same problem that Amazon has - one size does not fit all in UX, and one decision maker, even if very smart and well-meaning, will sooner or later get himself into a corner and be stuck there.
It’s the same problem that Amazon has - one size does not fit all in UX, and one decision maker, even if very smart and well-meaning, will sooner or later get himself into a corner and be stuck there.
This is a major point though. I spent time at Travelocity, Orbitz, and Expedia. All three companies were (not any more) direct competitors based in far away geographies. Regardless of that I was utterly astonished by how similar the work cultures and technology were. Everything was being run from archaic centralized giant monolithic Java applications using nearly identical technology stacks and it was always an incredibly slow and painful experience to update, extend, or maintain the beast. The business solution was always the same: hire more developers until market conditions present financial barriers.
For emails it is surely worth, but for many other application it might be different.
But think about what it means for a minute! If one figured out protocol evolution or migration might be all it takes to give federated systems prominence.
Can you compare SMTP, NNTP, ActivityPub, XMPP, ATOM, Scuttlebut (SSB), to make your point clearer?
Make the act of sending a message cost the send or money and I think spam goes away and self hosting becomes much simpler.
...and the service itself becomes less useful to everybody who doesn't want to self-host.
If you choose to off-road, you can't really complain about it being bumpy.