Fediverse

287 readers

1 users here now

This magazine is dedicated to discussions on the federated social networking ecosystem, which includes decentralized and open-source social media platforms. Whether you are a user, developer, or simply interested in the concept of decentralized social media, this is the place for you. Here you can share your knowledge, ask questions, and engage in discussions on topics such as the benefits and challenges of decentralized social media, new and existing federated platforms, and more. From the latest developments and trends to ethical considerations and the future of federated social media, this category covers a wide range of topics related to the Fediverse.

founded 2 years ago

Why can't magazines/communities aggregate content from other instances? (kbin.social)

submitted 1 year ago* (last edited 1 year ago) by timbervale@kbin.social to c/fediverse@kbin.social

112 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

[–] briongloid@aussie.zone 19 points 1 year ago* (last edited 1 year ago) (3 children)

I believe that Lemmy should add the ability for an instance to self-aggregate, were an Admin bundles other instances communities into a /g/ grouping.

So instance.tld/g/community could include the whatever communities across the fediverse they felt it should.

Some instances would use it for general aggregation, others would be more strict as a way to merge identical communities.

But as for now, there is no feature set.

[–] Ada@kbin.social 10 points 1 year ago

@briongloid Not admins. Users should be able to do it.

As an admin, there is no way I can be across all of the niche subtleties and naming schemes of communities I'm not involved in. If I have to group them, I'm going to get it wrong.

If it's going to sit anywhere above the individual level, it should be at the community mod level, not the instance admin level. But of course, many community mods aren't going to want to actively point people at other larger communities that overlap with theirs.

@timbervale

[–] I_Miss_Daniel@kbin.social 5 points 1 year ago (1 children)

Maybe if G is common across the Fediverse, it'll help solve the difference in URL formats? (C vs M)

[–] briongloid@aussie.zone 4 points 1 year ago

/c/ & /m/ is the same, /g/ would be a grouping of both.

[–] timbervale@kbin.social 2 points 1 year ago* (last edited 1 year ago) (1 children)

I was thinking more of a situation where we have community registrars, "DNS" like servers, etc. Still a distributed system sharing power, but far more structured than the email analogy that is always used. That said, it appears I had the wrong idea of the goals/functions of federation and the Fediverse in general. Oh well, at least I learned a bit more about it.

[–] briongloid@aussie.zone 1 points 1 year ago

I think indexers are going to be a must, we need central servers to catalog even just all the community addresses for lookup.