I’m currently on mastodon.social for my instance, and I was informed the other day that because of poor moderation it’s been permanently defedereated by enough instances to make it an issue for users there to have reach outside of their home instance. Is this true? Should I move to a different mastodon instance? Thank you!

  • SamC@lemmy.nz
    link
    fedilink
    English
    arrow-up
    9
    ·
    edit-2
    1 year ago

    I was on an instance that limited mastodon.social, which means you don’t normally see posts from there, and anyone on there that wants to follow you needs permission. But if you follow people there, their posts will appear normally in your feed.

    Because of its size, I think a lot of instances are hesitant to defederate mastodon.social completely… (but that’s part of the problem with having such a big instance). I think quite a few limit it though. Some instances list all instances they limit/block and might even have a reason why they do it, but some don’t seem to have any info about that at all.

    I moved to an instance where it wasn’t limited. Haven’t noticed a huge difference, either in terms of increased activity or higher levels of abusive posts/bad behaviour.

  • Stefen Auris@pawb.social
    link
    fedilink
    English
    arrow-up
    5
    ·
    edit-2
    1 year ago

    I do know of several instances that throttle or defederate mastodon.social so that part is true. Fortunately migration is fairly straightforward if you’re worried about that though!

    • BoneALisa@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      ·
      1 year ago

      What’s the reason for defederating from them? Aren’t they like the original Masto instance? What kind of moderation issues are going on there?

      • SamC@lemmy.nz
        link
        fedilink
        English
        arrow-up
        7
        ·
        edit-2
        1 year ago

        The reasons I’ve seen given is that it’s a huge instance and at one point only had 1 moderator. So when instance admins complained about a user there, they didn’t always get a response. I think they’ve got more moderators there now, but not sure if it’s solved the problem.

        Some Mastodon admins are very concerned about protecting their users from abuse, and want to limit it as much as possible. And that might be 100% appropriate for their users… people who don’t like it should move to a different instance.

        • BoneALisa@lemmy.world
          link
          fedilink
          English
          arrow-up
          4
          ·
          1 year ago

          Ah, that would make sense. I could definitely see that being annoying, especially considering the sheer number of users on that instance.

      • Ada@lemmy.blahaj.zone
        link
        fedilink
        English
        arrow-up
        6
        ·
        1 year ago

        They’re slow to respond to moderation issues. Which is fine when you’re talking about 1 errant user on a small instance, but it’s not so great when you’re talking about a small but ever present percentage of problem users on a mega instance

    • KNova@links.dartboard.social
      link
      fedilink
      arrow-up
      11
      ·
      1 year ago

      I can help fill in some of the gaps. Mastodon.social is the flagship instance so you get a bunch of people signing up for it, and at times I think some of the reports overwhelm the moderation team. A few weeks ago there was a big issue with spam bots getting through. Some instance owners have a short fuse for this kind of stuff so they opted to defed from it.

      Personally, I’m running a small instance so I did not block it. I follow a lot of accounts from there. The spam bots were annoying though.

    • Joker@beehaw.org
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Spam and bots like other people have said. Then there are the instances that get blocked because of the content and people there. Nazis, racists, trolls, etc. They were coming in from all over during the twitter migration. There was a blocklist on GitHub that was being updated pretty frequently.

  • Spzi@lemmy.click
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    In Lemmy, you can click on Instances (bottom right) to see a list of federated and defederated instances.

    From my point of view (lemmy.click), mastodon.social is federated.

  • BobQuasit@beehaw.org
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 year ago

    Interesting. Is there any instance which specifically will not defederate from any other?

    • Ada@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      6
      ·
      1 year ago

      There are, but they tend to end up being quickly defederated themselves, because they attract bigots who want to share their bigotry without consequence

    • Seedling (she/they)@beehaw.org
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      there are some, but they tend to quickly become spam and nazi instances. I’m guessing even those ones defederate from the instances that only serve malware though

      • Ada@lemmy.blahaj.zone
        link
        fedilink
        English
        arrow-up
        5
        ·
        1 year ago

        There is no instance that is connected to every other instance, and there never will be. Lets say your instance is a free speech instance that doesn’t defederate any other instance. Even then, there are instances that will actively block your instance because they block all instances that are willing to federate with bigots in the name of free speech.