@CogitoErgoBloom be careful, because the spam problem on Lemmy is a bit different from the spam problem on Mastodon (and other microblogging systems).
It is sufficient that the Lemmy user IS NOT SUBSCRIBED to a community to not see the contents of that community.
The Mastodon user, on the other hand, sees the contents of all second-level contacts and everything that is re-shared by first-level contacts.
For this reason, unless an instance is chock full of trolls and shitposters, I don't recommend blocking or muting an entire instance.
@Quilly @lealternative @mobileatom
Here you can find a guide to Lemmy in Italian dedicated to both Reddit refugees, Mastodon or Friendica users, and those entering the fediverse for the first time through Lemmy.
With a good translator it should be clear enough...
@Quilly @lealternative @mobileatom for a user coming from Reddit, Lemmy's interface is much more intuitive, but Kbin wanted to target a different niche.
Unfortunately, there are few instances, but they are almost all for testing, except for the developer's (today it is a bit overloaded).
I can't judge from architecture point of view, but I think Kbin may have some dB boost problem, since Kbin users can also follow other users.
The Kbin instances however are all here: the-federation.info/kbin
But wait – it gets much, much worse
As I was finishing up the above post, I noticed something a little strange in the code – something I'd glossed over earlier. There are a ton of references to what looks to be functions related to Google's #Firestore database.
@CogitoErgoBloom @lealternative @jakob @fishidwardrobe You are right. Blocking an instance is a last resort, but sometimes there's nothing else you can do. After all, if a user remains inside a problematic instance, it means that it too is problematic.