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!
I only have a kbin account,
but I can sub to
/m/memes
/m/memes@lemmy.ml
/m/memes@lemmy.world
/m/memes@anyotherlemmeyinstancethatexists.com
I don’t need accounts on those other lemmy instances, I can sub to them from here.
For example, check out https://kbin.social/m/fediverse@lemmy.ml and you can click subscribe
which is a different instance of the post you made here at https://kbin.social/m/fediverse
You can see that https://lemmy.ml/c/fediverse is the same as https://kbin.social/m/fediverse@lemmy.ml
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
@domainthing 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.
You can also see Lemmy and Kbin users on Mastodon and vice versa. It all runs on the same protocol: ActivityPub. Sort of works like email in that sense.