So while there’s more of a push from the top to make mastodon.social the flagship, from the grassroots there’s very much a push against it (I’m loosely a voice in that might self).
That's good. I still think that having the developers pushing or not for an instance makes a different, wasn't Mastodon 40% Mastodon.social at some point?
There is a security issue by allowing automatic federation with any federated instance: an attacker could just create a huge number of communities, with a large number of posts, exhausting the resources of small instances.
That's what I guess it the main reason why it works like it does now: the server only gets the content if someone is interested.
Mastodon was actively pushing to be the default instance.
This criticism was co-joined with the criticism that the Mastodon organisation had set the mastodon.social as the default instance during the signup flow on the apps. While the frustrations are understandable and there are certainly valid criticisms on that decision, crypto spammers do not manually sign up via the official app, making it more of an airing of grievances than actual critique on the spam defense policy by mastodon.social.
Relying on !all to have your newly created community to reach most of the people could work, but using the Scaled sort as it wouldn't have enough subscribers to push it using Hot or Active.
There is only one !newcommunities@lemmy.world, it has 15k subscribers, seems like a pretty good way to promote it.
That's good. I still think that having the developers pushing or not for an instance makes a different, wasn't Mastodon 40% Mastodon.social at some point?