I’ve noticed in the explosion that we are getting duplicate communities in multiple instances. This is ultimately gonna hinder community growth as eventually communities like ‘cats’ will exist in hundreds of places all with their own micro groups, and some users will end up subscribing to duplicates in their list.

A: could we figure out a system to let our communities know about the duplicates as a sticky so that users can better find each other?

B: I think this is the best solution, could a ‘super community’ method be developed under which communities can join or be parented to under that umbrella and allow us to subscribe to the super community under which the smaller ones nest as subs? This would allow the communities to stay somewhat fractured across multiple instances which can in turn protect a community from going dark if a server dies, while still keeping the broader audience together withing a syndicated feed?

  • aqua_synonym@lemm.ee
    link
    fedilink
    arrow-up
    7
    arrow-down
    1
    ·
    1 year ago

    That’s exactly what I thought of. Here’s my proposal (though I don’t know if this can be implemented in the technology or if it would be compatible with ActivityPub):

    Suppose we have two similar communities (i.e., north.pole and north.star, but they both tackle northness but in different instances). The mod from either communities would send an invite to the other to form a “group” or “federate” or “ally”. Now, if the other mod approves, here’s what happens:

    Whenever you post something in a community that has a group, it would be synced with the communities in other instances that are allied to it, including upvotes, comments, and other metrics. So if I post in north.pole, people in north.star could see my post too because we’re in an “alliance” and vice versa. They can also upvote my post and I can upvote theirs. There would just be a sign (probably a flair-like design) that would tell users in other instances from which instance the post came from.

    With regards to moderation, here’s how: they are basically separate communities with content syncing between them. Suppose a user in north.star posts something offensive and against north.pole community rules. The mods in north.pole can block that post from appearing in the north.pole feed.

    And here’s an unrelated gripe: there should be an instance-standard “ouster poll” for communities that are dead. With what I see right now in the influx of Lemmy users, many communities are dead and users are willing to revive them but they can’t because the moderators of those communities are already inactive and redundancy is a pain in “advertising” membership in Lemmy already. There should be like a poll of interested users where they would agree to “oust” the inactive mod (of course there’s also a qualification for “inactive”) and replace them with probably a democratically “elected” moderator.

    • tetris11@lemmy.ml
      link
      fedilink
      arrow-up
      5
      ·
      edit-2
      1 year ago

      I don’t like the idea of a voting system for mods, as it can be gamed very easily by bot accounts. Democracy is sadly under threat due to AI, and so I think the wall-gardened approach might be necessary: users choose an instance of north that suits them, and if the mod is a dick, then those users let the mods of the other north instances (under that super community) know, and the mods of other instances make the decision.