I’m new to the fediverse, and so far, I have been seeing some situations from lemmy instances rejecting users to defederating from others, but I ask myself: what can be done if trolls or bots come from self-hosted single-user instances?

  • Jamie@jamie.moe
    link
    fedilink
    arrow-up
    5
    ·
    1 year ago

    I don’t usually make a habit of being an ass, but I am extra careful about what I say because I choose to self host. Since any instance admin that decides not to take a liking to me could take one look at my instance and defederate me without a second thought. If anything, self-hosting makes you more vulnerable than just normally ban evading on an open instance.

  • Gsus4@lemmy.one
    link
    fedilink
    arrow-up
    4
    ·
    1 year ago

    They get defederated wherever they get consistently banned…and then they can federate with their friends and make their community of shit and yell at each other or something.

      • Gsus4@lemmy.one
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        Well, if we had a DDOS-like barrage of troll instances, probably a solution would be to institute a “pending federation request” for any new communities.

        • llama@midwest.social
          link
          fedilink
          arrow-up
          0
          arrow-down
          2
          ·
          1 year ago

          This should be the default in the next Lemmy version because otherwise it’s only going to get easier for people to launch new instances and it’s going to get too overwhelming

      • tinwhiskers@kbin.social
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        I believe there is a whitelist mode, that isn’t currently enabled but in that mode new instances are defederated by default. That would be a pain to administer for all the small instances joining, so they may set some size rules to apply for federation (??). I imagine this is inevitable if automated instance spamming becomes a problem, unless some type of RBL comes in vogue for managing federation first. It may become impossible to manage manually.

        • russjr08@outpost.zeuslink.net
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          E: oh the white list thing may only be relevant to kbin federation, as that was the topic I saw it in. Sometimes I forget where I am :-/

          No, you were correct - Lemmy’s admin settings has an Allowed Instances setting, which acts as an allowlist for federation. If you put an instance (or more, separated by ,'s) then your instance will only federate with the ones specified in that list.

  • Rylo@lem.rylo.dev
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    Instance admins can blacklist & whitelist other instances from federating with theirs. If you have a lot of bot spam originating from a particular server, you can just add them to the blacklist to prevent them from interacting with yours.

  • delcake@lemmy.songsforno.one
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    I agree with Jamie. While it is certainly possible for a bad actor to spin up burner instances for the purposes of evading defederation, that’s a disproportionate amount of effort compared to just creating a new account somewhere that already exists.

    Will we see it happen? Probably. But it honestly seems easier to deal with than if those bad actors were to hide themselves in established instances.

  • MeowdyPardner@kbin.social
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    Assuming you can block a top level domain and have it apply to all subdomains, doing so would force the troll to pay for another domain to get around the block. That could add up to quite the expense.