Honestly, this suggests to me that the ability to defederate might be a bug rather than an issue.
If my instance doesn’t talk to the instance at foobar.example, I might be unable to see (parts of) relevant discussions. This is worse for a microblog like Mastodon than it is in the threadiverse but it’s still something to keep in mind even over here. And most non-enthusiasts don’t want to have to do that.
Email is an example of a successful federated platform and it barely has defederation support. But in general all mail servers can talk to all other mail servers as long as they provide the right look-at-me-I’m-legitimate signaling. That makes email easy to use for regular people no matter if they use Gmail or their cousin’s self-hosted mail server.
Perhaps that is how at least the non-threaded fediverse should work… However, that would also mean that some instance hosting heinous shit would keep being visible to everyone. It’s a tricky problem.
Kichae@lemmy.ca 4 weeks ago
Couldn’t disagree more.
The simple fact of the matter is, the fediverse is local. Everything you interact with is locally hosted on whichever website you’re using. That means, if I’m running Mastodon or Lemmy on my website, I’m platforming everyone who has contact with my website.
And I’m not going to want to platform a lot of people. I’m not going to want to pay to host their posts. I’m not going to want to deal with dealing with other websites who refuse to moderate their instance, and who refuse to take out their trash. Suggesting that people should be forced to is how you ensure that people don’t run ActivityPub enabled websites at all, and you reduce the fediverse to a semi-centralized family of, like, 5 big websites.