Just read a bit of reactions about the #WordPress #ActivityPub plugin and there seems to be a sect of ppl who find it abhorrent that #fediverse posts might federate.
In their opinion, if they post “on Mastodon”, that post shouldn’t leave #mastodon. They think its understandable that a post may leave their own server and federate to other mastodon servers but federating outside of that is unacceptable. (I don’t know how they think about their posts federating to non-mastodon servers, especially non-microblogging servers like Friendica, kbin, etc)
Once again, I think the problem is caused by mastodon. They market mastodon as a Twitter-alternative and hype it as the platform instead of the fediverse. Now these users don’t understand the breadth of the fediverse and are “confused” that their posts could be “leaving” mastodon.
You’re not “on Mastodon”; you’re on the fediverse. Just like someone who runs a blog isn’t on Nginx or Apache, they’re on the web.
@0x1C3B00DA An maybe they even find out may that posts which "leave" an instance are always treated as cached content. Or at least should, most software has it implemented that way.
@linos well, I'd say part of the distributed nature of this platform is that there isn't a central decisionmaker to dictate what instances should do.
Each instance is free to set their policies as they think best for their users.
Some of them might have very good reasons to have different retention policies than simple caching.
@0x1C3B00DA
