this post was submitted on 12 Jun 2023
2 points (100.0% liked)

Fediverse

3 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
 
you are viewing a single comment's thread
view the rest of the comments
[โ€“] speck@kbin.social 0 points 1 year ago (1 children)

The part I'm getting tripped up revolves around accessing the content in another part of the fediverse. e.g., if I go to a lemmy instnace, it will ask for a log-in specfic to it (i.e. it doesn't recognize my kbin log-in). So what's the mechanism by which travel between platforms happens? If I understood correctly, some stuff will show up here that's been 'retweeted'. But what if I'm searching for content that lives in Lemmy or Mastodon instances?

Am I sort of making sense?

[โ€“] WorriedGnome@kbin.social 1 points 1 year ago

You are making sense, just remember your login does not travel between kbin and lemmy. When you are on kbin, you can search for communities on the server you joined or across the fediverse. The way to do that is community@instance.name

For example, say if I found out the beehaw.org server had an awesome gaming community, well I can just type gaming@beehaw.org into the search box and then subscribe to it. It will then federated into the server (the server will start pulling in new posts - but not old posts) that means others can now see it too. That's why if you see the message that it's not fully federated and you might see more on the original instance.

Your login is just a place to reside but with the fediverse, you can pull in content to view. Which helps as you don't need multiple log ins for multiple services. I've seen a few people ask about people with the same username as theirs on other instances and that will happen but remember that your username is like email. You have username@instance.name, so whilst someone might share the same username, they'll never be on the same instance. That's how you tell others apart.

Hopefully that helps make sense!