Fediverse

19 readers

2 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

Trying out Lemmy and kbin… And the #fediverse interoperability has lost me 😥 please #help ! (kbin.social)

submitted 1 year ago by gauffke@kbin.social to c/fediverse@kbin.social

19 comments fedilink hide all child comments

Hey All,
I’m an (old 😉) IT guy, very excited by the #fediverse and trying to find my way amongst various services.

As an example, I started gathering topics I like on a Lemmy account. Then, I got tempted to create different accounts on smaller instances and try out kbin.

I’d love that my « subscriptions » follow me, so that I don’t have to scan all my « magazines » and re-register from everywhere.

Can someone kindly help me on how I can achieve that? Apologies if the question is naive, but given the decentralised nature of those services, shouldn’t each user have a « local » trace of what they follow (for example on a local app), no matter the service, so that they get « their view », their « window » on the #fediverse?

Many thanks for the #fedihelp and again my apologies for the probably basic questions!

you are viewing a single comment's thread
view the rest of the comments

[–] CoderKat@kbin.social 4 points 1 year ago

Yeah, the key thing here is that you (and OP) should be only using one account (in both of your cases, your kbin account) on the site your account belongs to (kbin.social). The site takes care of the federation. There's generally nothing you need to do † and you don't even actually need to know how the federation works. Simply treat the @domain thing as part of a magazine's name (eg, it's never just "memes" but "memes@kbin.social").

† The exception is when you're the first person on your instance to subscribe to a sub on another instance. Right now this has a phenomenally bad UX and I'm hoping it will be improved quickly.