We had an issue today in which it seemed like we were getting flooded with posts from a new member. I found the current settings were either too drastic (unfederate community, block user) or weren’t available (those in title), so I settled on temporarily restricting posts to mods only, plus adding a warning message for other posters, which unfortunately was again on the drastic side. (that message now appears all over the place)

Had a good look through codeberg issues but couldn’t find that the title ideaas had been suggested before. So to be clear, would it be possible to add in community settings:

  1. Limit posts per user per day to X.

  2. Checkbox option to require posters to be on a whitelist, incidentally helping prevent spam.

Thanks for any consideration!

  • CerebralHawks@lemmy.dbzer0.comEnglish
    2·
    1 day ago

    Slow mode would be useful for some communities, but we also don’t want to scare people off, or get people posting from multiple accounts.

    (I don’t speak for PieFed. I’m just a user. On Lemmy, not PieFed, though I do have an account on a PieFed-powered instance.)

    So I’m all for that being an option for community moderators/admins.

    The whitelist thing is good too, if you want to create a read-only board where only certain people can post (others can maybe comment). The nice thing about the Fediverse is, if you limit people to post, someone can just make the same community somewhere else, and the users can decide which one they want. Like, I’m still getting the hang of Lemmy/PieFed. As I said, I have an account on each. db0 for Lemmy. But if I look for a community, and db0 has one, .world has one, and sh.itjustworks has one (using them because I like their name), I’m not necessarily gonna pick the one on my instance (though, maybe I should?). I’m gonna go where the conversation is because I don’t want to shout into the void. So that’s usually gonna be .world. But if .world and db0 ever have beef, I would wish I’d put more effort into the db0 comms. Or hedge my bets and make an account on .world. I dunno. I do like that we have choices though.

    • Skavau@piefed.social
      English
      2·
      1 day ago

      The threadiverse isn’t at an activity level right now where most large communities even would feel the need to make use of these things. But these tools really should be made at some point if users do increase. I’d imagine communities that want to use a posting slow mode for users would have a specific mission in mind, and would be unlikely to be more generalist or popular communities.

    • JohnnyEnzyme@piefed.socialOPEnglish
      2·
      1 day ago

      Excellent list, Skavau. Your point 5 is like a more articulate version of my p1.

      I also restated my p2 to be a little more clear & useful, above.

      • Skavau@piefed.social
        English
        2·
        1 day ago

        I don’t think your whitelist idea was in mine though. Might be an idea to codeberg that.

        • JohnnyEnzyme@piefed.socialOPEnglish
          1·
          21 hours ago

          No, it wasn’t. And my pt1 had similarities with your p5, but wasn’t entirely the same thing.

          TBH, I have pretty much zero experience with GitHub / Codeberg. Is it enough that I’m posting this here, or would I be expected to add something over there? (it seems like codeberg is more for the dev, or people who directly work with the dev)

          • Skavau@piefed.social
            English
            2·
            21 hours ago

            If you want rimu to see it, it’s advised to post it so it doesn’t get forgotten.