This will be largely alleviated with managed or hosted services. For example, a lot of corporations used to run mail services on-prem but no longer need to do this, they've moved on to purchasing it directly from a provider like Microsoft or Google Workspace.
Also, this largely reflects the idea behind Discord and Slack - hosted services will be the dominant players once the ecosystem evolves.
also, I'll repeat my new business model Twitter should adopt -- take the underlying protocol (ActivityPub), white-label their services and sell them to orgs who want Twitter on their own domain (also allowing for control over the username namespace like email / @[email protected]). I've been pitching this idea for years and no one's ever given a serious critique of the idea. A global unified namespace like the one Twitter uses is problematic (squatting/trademark disputes, etc) and awful.
It would dilute the Twitter brand and divide internal resources. That's the main critique I can think of. Would never happen while Twitter was a publicly traded corporation. Under private ownership, it very well might happen.
I think the Fediverse idea is great, but people are dumb. @somebody is about as far as most people can handle. @[email protected] is confusing, and nobody will understand. Imagine having to explain bang paths to Fred in accounting so he can send an electronic mail.
Never underestimate how obtuse the average computer user is. They can be taught, but it takes many, many years before it becomes common enough that people grok it without trouble.
(I like your idea, btw.)
But what I was doing was comparing Fedi @[email protected] to old-school bang paths. It's unlikely to take off among the masses until significant time passes. Heck, even email addresses baffle enough people to make me doubt whether all of this Internet stuff was worth the trouble.
ah, the modern take on "AOL Keyword:" from the late 90s.
I started with the simple "managed" hosting, now I am hearing things up to do custom hosting and the whitelabel.
Same issue with Discord, it's a centralized service where you and your content are at the mercy of the owner of the service, which I think is one of the big things that federated alternatives (like Matrix) are meant to solve, so any single entity can't unilaterally revoke your participation in the entire network.
Being able to switch what provider hosts your social media without losing your network is valuable (and has pro-social effects) without needing to self-host.
> That's how we've ended up with email being as difficult as it is to self-host.
I'm not sure what you mean, what's the "that", what do you think led to the situation where email is hard to self-host?
Even if hard to self-host, email succeeds in avoiding vendor lock-in if you have your own domain. Which most people don't, because of cost and because _that_ can be hard to manage for a normal person. But if fediverse succeeds at giving a typical person the lack of vendor lock-in that email-with-your-own-custom-domain does, I'd consider that a success on the criteria of what federation is meant to achieve.
I was referring to spam filtering, where all the big hosts know to allow each other through, but make it very difficult for smaller hosts to participate by being tight lipped about their filtering criteria and making others have to jump through lots of hoops to not be treated as spam. Which, when considering the high cost of being spam filtered (eg. if you're a business) ends up making it very hard to practically self-host.
Similarly, I wouldn't think fediverse would have succeeded in the goals of federation with large centralized hosting providers. Since upon reaching critical mass, they could easily enact similar policies in the name of preventing spam or for 'safety'. The content would be going through their network and would be stored on their hardware, so they would use the same logic current social media uses to justify their right to moderate without oversight.
EDIT: I've said before, the PBLLC should be working with the W3C, IETF, or other open bodies, and they've always had a seat at the table (https://www.w3.org/Consortium/join).
Yep. Self-hosting something like Plex (please consider Jellyfin instead) or a social Fediverse server shouldn't be any more difficult or less secure than installing an app on your phone. I think projects like Sandstorm, yunohost, Cloudron, etc have the right idea, but they're still way too complicated for the average person to get up and running. I've been chewing on this problem for about a year, and I believe it's solvable with technologies that are currently available. This is the focus of my current main side project.
Imagine a popular but controversial blogger deplatforming attempt, followed by his 300k subscribers getting an 'Your contact has just uploaded their first video on NextTube' notification in five minutes. You don't need many platforms when platform understands they only have power to de-content themselves.
You also no longer need those rows of social icons since you only need to subscribe to a creator once.
Content should reside in P2P/DHT mesh and platforms would only present, curate, decorate and discover it. But it should also be discoverable via PKI+DHT.
I think there's an interesting case to be looked at with Discord. Not that discord itself is decentralized, but the surprising amount of vibrant and active communities in the form of Discord servers. If the client-side barrier can be sufficiently lowered, I'm sure many communities like that have at least one or two people knowledgeable enough to set up an instance or two
When payment runs out, it emails you a download link to export your data which you can take to another provider, or just start paying again and it starts working again.
I'd send a few bucks to such a site, sure.
If your community is "people I'm interested in talking to" then they don't need A) or B, and there are so many of those on the Fediverse that congrats, C) is solved.
The fact of the matter is the Fediverse (and even just Mastodon) is that 1) is not the current reality (plenty of medium and small-ish instances), and 2) does not have to be, and indeed is not the reality, and even if it were, A and C still need not apply.
I sometimes fear people jump into the Fedi but, understandably, aren't versed on how discoverability works, thinks there's no-one interesting there, and leaves. Whether setting up your own instance or using a tiny existing one, you can browse the user directories and posts from other, larger instances, and find interesting souls to connect with, without having to make an account there.
Most importantly one can search tags used in posts and profiles which relate to your interests. Any good / mature client (or the web UI) lets you search for tags and pin them as their own timelines - so a rolling conversation about your fav topics, across all instances that you federate with.
I can count on one hand the number of people I know that fit (what I think is) the criteria for the Fediverse:
I think this leaves two possibilities: I'd love to see Fediverse “platforms” succeed, but I'm not sure how they can since the network effect is what is needed.