38
Why can't magazines/communities aggregate content from other instances? (kbin.social)
submitted 3 years ago* (last edited 3 years ago) by to c/fediverse@kbin.social
137 comments fedilink hide all child comments
 

When I look at https://lemmy.ml/c/startrek vs https://kbin.social/m/startrek I see two entirely different lists of posts. Why? It's the same topic, just on different instances. How can we have communities about topics without having them siloed into their own instance-based communities? Is this just related to that 0.18 issue with Lemmy/kbin not talking nicely, or is this how the Fediverse is?

Is it (at least theoretically) possible for me to post an article on https://kbin.social/m/startrek and have it automatically show up on https://lemmy.ml/c/startrek, or are they always going to be two separate communities?

you are viewing a single comment's thread
view the rest of the comments
[–] 17 points 3 years ago (5 children)

You'd probably open yourself up to magazine poisoning that way. Would be easy enough for a troll to spin up a new community or entire new server that helpfully drops spam into magazines with the same name. I think I would prefer users be able to create meta-magazines that will aggregate posts from multiple federated/local sources.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 3 points 3 years ago*

    That's just a moderation tool. A community would simply need the ability to run a whitelist or blacklist of communities to aggregate.

    Frankly, I think a more manual process as an option is better because it would help account for naming variations. It'd also allow a mod team to create a place SPECIFICALLY to aggregate, which strikes me as inherently useful even within an instance.

  • permalink
  • fedilink
  • source
  • parent