[–] 2 points 11 months ago*

Gatekeeping communities that get like 5 posts a day seems utterly pointless and counterproductive to me.

Edit: sorry, nine posts in one day, one of which was a meme that's still up for some reason. Just goofy.

  • source
  • [–] 12 points 11 months ago (3 children)

    This doesn't really solve the problem. This person used to scramble/delete their own content in the past before they went to delete the entire accounts.

    They're a rather persistent ban evader who can't accept not being welcome in some spaces on the internet. Even before they started deleting accounts they already used multiple accounts to evade bans.

    I'd be happy to hear suggestions for addressing this without essentially banning all new accounts. Preventing new accounts from participating will only result in them aging accounts for a bit before usage and discouraging legitimate new users from participating.

  • source
  • parent
  • context
  • [–] 17 points 11 months ago (4 children)

    One option is to switch to a PieFed instance running V 1.3.6. The devs did something about this for PieFed users that should help.

    v1.3.6
    Stop floods of spammy posts from very new accounts on lemmy.world.
    New accounts (< 24h old) from lemmy.world are now limited to 3 posts in their first day.

    V1.3.3
    Automatically delete posts by very young accounts that self-delete.

    piefed.social and feddit.online are two that are running the latest code. I'm sure there are others.

    Yeah, that person is quite annoying.

  • source
  • [–] [S] 3 points 11 months ago* (last edited 11 months ago)

    They either need to make a rule denying posts about storage server, or start enforcing it fairly.

    If they had a rule like that, I could accept it, as selfhosting to me implies more of running a service on the internet rather than a "simple" or "standard" storage server.

    That would be better but storage is a fundamental part of self-hosting, given that commonly used services need significant storage (e.g.Β Immich) and storage redundancy is vital to the reliability of self-hosting these services. And it's not just storage either. The compute hardware also has a fairy tight connection to what's being self-hosted. E.g. GPU, RAM, have significant bearing on the ability to self-host LLMs. The same is true for network infrastructure.

    Because these topics are interlinked in the context of self-hosting, the knowledge exists in this community members' brains. Trying to separate it means these same people have to figure out another place to gather to talk about that subsection of self-hosting. I'm not aware of such a community and ever since I've been on Lemmy (2023) /c/selfhosted has been the place for it.

  • source
  • parent
  • context
  • [–] 4 points 11 months ago (1 child)

    I had a look at rule 3, it is really vauge, about making it clear that you are self hosting.

    When I look at the modlog screenshot you posted, the rule seems to be applied way to broadly.

    They either need to make a rule denying posts about storage server, or start enforcing it fairly.

    If they had a rule like that, I could accept it, as selfhosting to me implies more of running a service on the internet rather than a "simple" or "standard" storage server.

    I could see the mods being annoyed at seeing the same questions being asked time and time again, especially when the community was created with a different focus in mind.

    But that needs to be communicated clearly and not just randomly enforced.

    TL;DR: Looks like a combo of bad rules, bad communication and too eager mods.

  • source
  • [–] 18 points 11 months ago

    This exact thing has happened to me on c/selfhosted. Made a post asking for help on setting up my storage for a proxmox vm and got a couple helpful replies before the mods removed it, simply because I failed to mention what software I was planning to host in the VM. Pretty silly, and I think it hurts the community by removing those helpful responses.

  • source
  • Torn about this one. The rules do explicitly say about selfhosting, the software specifically. So, yeah against the rules. However, I think that's pretty pedantic when we're talking about an average of 6 posts a day, quite a ways from spam. Storage is a natural issue when it comes to selfhosting, choosing which storage can have large ramifications on how your services run above.

    It'd be nice if they at least removed it with a suggestion, like where to post it instead.

  • source
  • [–] 1 point 1 year ago

    To be fair, you don't need the domain, you could just have them change the host record. But it would sure be safer for the instance if you controlled the entire domain.

  • source
  • view more: β€Ή prev