10k, which is around 25% of the whole Lemmy: https://fedidb.org/software/lemmy
It's reasonable. Could be better, but could be worse (Gmail is probably much more prevalent in emails)
Blaze
joined 10 months ago
Host your own instance and that would be the case
I kind of noticed that it's a bit slower if the ping is high (another continent)
On which continent are you located?
(mastodon.social is also about ~25% of masto)
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.
https://fediversereport.com/defederation/
Lemmy's community seems to be aware of the issue, and hopefully it will resolve over time.
For small instances, admins can use tools like https://github.com/Fmstrat/lcs to subscribe to most of the active communities.
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.
This is fixed in version 0.19.3, hopefully your instance will update soon
In this context it's just faster to type, and not really ambiguous.
I’d fear instead that centralisation is pretty sticky without some massive failure and wouldn’t expect much movement in the proportion of users on lemmy.world.
It happened in August during the long DDoS attacks on LW.
I guess here it's less prevalent because the site is still accessible, and most of the users don't really follow closely the Lemmy versions.
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.