Okay, this is possibly going to be controversial in some quarters, but it has to be said for the good of the Fediverse:

Mastodon.social is not a good way to join Mastodon. If you're already on mastodon.social, you might want to move your account to another server. I've done an article about this topic at:

➡️ https://fedi.tips/its-a-really-bad-idea-to-join-a-big-server

If you want to move your account, there's a complete step-by-step guide to how to do it here:

➡️ https://fedi.tips/transferring-your-mastodon-account-to-another-server

#FediTips #Mastodon #MastodonSocial

Mastodon.social is not a good way to join Mastodon. If you’re already on it, you might want to move your account to a different Mastodon server. | Fedi.Tips – An Unofficial Guide to Mastodon and the Fediverse

An unofficial guide to using Mastodon and the Fediverse

@FediTips With all due respect...

Your main argument seems to be a fear that if offered a lot of money, that someone running a huge instance like mastodon.social will eagerly sell it if a large enough offer comes up.

My question to you is, what constitutes a "large instance"? Is there an exact number and if so, do you believe that all instances should be capped at that number and no longer allowed to accept new users?

Thanks.

@Mrfunkedude

My "main fear" -- as you put it -- is that a mega-instance is poorly moderated (if it's moderated at all) such that my public/remote and public feeds are filled with extremely explicit, full-contact, full penetration homosexual pornography, all emanating from Mastodon dot Social exclusively

Which may not trouble you, but de gustibus non est disputandum, right?

cc @FediTips

@FinchHaven @FediTips
The problem with this is that it seems to assume that smaller instances have better moderation. I think it would be better to say that it's "easier" to moderate a small instance. Some small instances are barely moderated at all.

As for the porn, I've been on .social since 2018 and while I have seen all types of porn and nudity here, if it is covered with a CW then it follows the TOS. If not, what's stopping you from blocking it yourself? (Which I've done as well.)

@Mrfunkedude @FinchHaven @FediTips

Uh bro you don't make sense. "easier" leads to better moderation structurally. To put it another way, it may not be a 1:1 relationship, but it IS a major contributive factor.

> "If not, what's stopping you from blocking it yourself?"

This is absurd and completely ignores the idea of moderation to begin with, which is to minimize bad user experience. Networks are large and filled with lots and lots of people. It's impractical to delegate it to users purely.

Preferably, moderation is robust enough that that is an exceedingly rare situation to be in.

@scien @FinchHaven @FediTips Your assumption is that all smaller instances will put an adequate amount of their time and resources into moderating their instances. While this may be true for a large amount of small instances, (whatever that means) it isn't necessarily true for all small instances. So yes, "bro". It does make sense.

@Mrfunkedude @FinchHaven @FediTips

> Your assumption is that all smaller instances will put an adequate amount of their time and resources into moderating their instances.

There is no such assumption. It's simply more difficult to scrounge up and manage a larger moderation team without having large financial structures to facilitate it. This is a commonly seen dynamic.

I am making no judgement of small instances being "better". Simply that moderation oft scales *poorly*. That's all.