this post was submitted on 15 Jun 2023
136 points (100.0% liked)
Fediverse
12 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
view the rest of the comments
I'm one of those new kids and I'm still struggling to wrap my head around a lot of things. Like I understand the concept of federation, but I can't figure out how to use the tools (if they exist) for distinguishing between local and federated stuff. What makes federated threads show up here on kbin? Are there any that don't? I guess I'm just unclear on the execution in practice.
so you can tell where something is coming from by checking the full @/name. you can see this in the sidebar for magazines, or hovering over someone's name to see for the users. there's userscripts to show it automatically and I think it's planned to have an official option to do so.
By default, we can access every other federated instance. However, it might not show up if someone isn't subscribed to the person or magazine. Threads for magazines should be 100% in sync across instances (though sometimes things are a bit finnicky due to the influx of users).
Content from other instances won't show up here if:
it's not part of what the collective kbinauts have subscribed to (if we subscribe to another instance's magazine, it pulls in that content for everyone here.)
if another instance decides to block or "defederate" with us. as of now I think every instance is federating with kbin.social so this shouldn't be an issue.
if you mark that you don't wish to see federated content. this will only show you stuff from kbin.social.
Not sure if I'll do a good job of answering this, but there are a few ways to discern between local and federated content. First, by how you filter content. e.g. by All or what you've Subscribed to.
Secondly, in two parts:
Next to the title it says where the link first came from, originally. That might be kbin.social, lemmy.world or it might youtube.com. In the latter one, each post in a thread also says who posted it with "[username], 3 hours ago to [thread]" That [thread] indicates the origin in the fideverse of that post. So if someone first posted that youtube link on lemmy.ml and then it was brought over here, that's where you'd find that out.
Note that you might have to hover over it to fully where it came from (that's the case on my desktop). For example, right now I see some post marked "[Username], 1 hour ago to Technology." Hovering over "Technology" reveals that it was @technology meaning that's where it came from.
On sh.itjust.works, there's a way to only see content from that instance. Not sure rn how to replicate that for kbin.social.
What makes federated threads show up here: because you've subscribed to it; because you are viewing m/all, and someone else posted it there. btw, if you want to post something from elsewhere here, you simply copy paste the federated link for it. You'll notice on a kbin article/post, when you click "more" there's the option of either a local link or a fediverse link. Other instances will have that option, which is what you'd want to copy.
Bringing in a url from elsewhere in the fediverse, btw, becomes one way to then be able to subscribe to it here (iirc).
There's a lot of good guidance for understanding kbin and the fediverse. It's just a little scattered everywhere in the many discussions that have been had. Don't be afraid to keep asking for clarifications. Plenty of us are trying to pay forward the help that we've received.
Hope this helps a little