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?

  • VerifiablyMrWonka@kbin.social
    link
    fedilink
    arrow-up
    1
    ·
    2 years ago

    Lemmy is to Reddit as Mastodon is to Twitter.

    The underlying ActivityPub protocol is pretty flexible. A Mastodon user can subscribe to Lemmy communties and a Lemmy user can follow a Mastodon account. Same goes for KBin which has added functionality in that communites (magazines in KBin) can follow hashtags that Mastodon accounts might use, bringing those posts in as additional community content.