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

[–] FaceDeer@kbin.social 3 points 1 year ago (4 children)

Idk why there are so many general use instances when the threadiverse would be a great place for themed instances to exist.

I would suspect that it's because when these instances were coming online a week or two back there weren't any other instances around, so having them be general-purpose was good. The Threadiverse can't "afford" special-purpose instances until there's already a large number of people around.

[–] timbervale@kbin.social 1 points 1 year ago (3 children)

It also could be that people want their instance to be the instance for that community, or they want to be in control of the community, not someone else. It's also one of the concerns I have about user impersonation (having a @timbervale, a @timbervale, and a @timbervale could lead to a whole bunch of confusion).

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

It doesn't matter if an instance wants their instance to be "the" instance for a community, they don't get to decide that for the whole Fediverse. It's up to the users.

It's also one of the concerns I have about user impersonation

Usernames should be interpreted in the same context as email address. I am FaceDeer@kbin.social, the "@kbin.social" part is as much a part of my username as the "FaceDeer" part.

The UI should probably be displaying it more prominently than it is, that's a bug that Kbin should resolve at some point.

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

You're right, but the current tradition and momentum are towards using short display names; virtually every service that has a public-facing feature uses display names (even most email clients put the first and last name of the users instead of their actual email addresses).

We definitely should be using the full bit on kbin/lemmy, though, as it's so critical to the idea of the Fediverse, you're 100% correct on that.

[–] FaceDeer@kbin.social 2 points 1 year ago

The current tradition may simply have to change when it comes to the Fediverse, because the Fediverse doesn't work that way. It can't work that way because instances are independent of each other. There's no central authority that can decide which one gets to have the "startrek" community name or the "FaceDeer" username.

If you want there to be a central authority to decide that stuff, then you don't want the Fediverse.