Want to get yall’s feedback on community squatting.

There are a good amount of communities with zero posts, comments, etc, as well as some users who have created communities but aren’t trying to grow them or even post to them in any way.

I’d rather have the creators of communities be someone who’s at least contributing to them.

Some options are, occasionally deleting communities with little to no activity, or limiting modship to a small number of communities.

  • liam
    link
    fedilink
    arrow-up
    3
    ·
    5 years ago

    Maybe I’m misunderstanding the tech, but isn’t this irrelevant with federation? If lemmy.ml/c/privacy is squatted, then people will subscribe to (hypothetically) lemmy.privacytools.io/c/privacy.

    Or are you asking with respect to just this instance and not the Lemmy defaults, since you’re administrating this one? In that case, this is a great example of the power of federation. You can pick what you think will keep the instance healthy; I don’t have an opinion.

    • DessalinesOPMA
      link
      fedilink
      arrow-up
      4
      ·
      5 years ago

      You’re correct, but ya this is just w/ respect to this instance. Lots of name squatting going on.

      • AgreeableLandscape
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        5 years ago

        If it’s on an instance by instance basis then it makes sense, but I wouldn’t recommend implementing active community requirements in the web engine itself. For example a dedicated instance for a software project like Blender (they have their own peertube instance so them getting Lemmy isn’t out of the question) might want to reserve admin-only communities for official updates.