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

[–] gauffke@kbin.social 8 points 1 year ago

Everyone, I want to say a big thank you! The example you gave me really helped me out. For the sake of clarity, I indeed only need 1 account, and I’ll stick to kbin for now.

The things I still keep in mind, and feel free to comment if any of this is wrong or stupid 😅

maybe it’s better having 1 login on 1 smaller and more local instance than a huge one like kbin.social. If I get it right, kbin.social is a great instance to minimise the « entry cost », but the best is to keep instances reasonably small. However, the smaller the instance is, the bigger the risk is that it disappears (together with your account).
on the short term, I will closely follow the developments of those apps!
on the longer term, I’m curious whether there is a benefit to have 1 single account for all fediverse services (like mastodon AND kbin). On the one hand, it makes perfect sense, with « distributed login ». On the other hand, putting all your eggs in 1 basket seems to be , on the client side, the opposite of what we want to do at server at side: spread! In that aspect, profile backups will probably be key!

Thanks again guys!