undefined> A is either federated with B or it isn’t, there is no “A is federated with B but B is not federated with A”
Maybe I used the word “federated” wrong here. I thought it meant “being linked to another instance”. To give an example of what I meant: the instance “lemmy.world” is linked to the instance “beehaw.org” while the instance “lemmy.world” is blocked on “beehaw.org”.
Yeah, that’s federation. In terms of the principle in government as well as its application in the lemmy protocol.
lemmy.world and beehaw.org are defederated. However, this doesn’t mean that you can’t see beehaw posts as a lemmy.world user, or vice versa. But (let’s say you’re a lemmy.world user) if you comment on a beehaw post, you’re commenting on a replicated version of the post that is hosted on lemmy.world. It is not synced with the original post hosted on beehaw, and you will only be able to see comments from other lemmy.world users and comments from before beehaw defederated.
Thanks that makes sense. I understand that if I’m on a third instance that is federated with both lemmy.world and beehaw.org, and I click on a beehaw.org post then I would not be able to see comments from lemmy.world users. But I would be able to see comments from beehaw.org users and they would see comments from my instance.
Yep the original post on the beehaw instance is like a master record of the post that lives on their server and only their users and users from federated instances can interact with it. Meanwhile the act of a lemmy.world user subscribing to a given beehaw community triggers the lemmy.world instance to archive posts there and create separate self-contained records of them which only lemmy.world users can interact with
undefined> A is either federated with B or it isn’t, there is no “A is federated with B but B is not federated with A”
Maybe I used the word “federated” wrong here. I thought it meant “being linked to another instance”. To give an example of what I meant: the instance “lemmy.world” is linked to the instance “beehaw.org” while the instance “lemmy.world” is blocked on “beehaw.org”.
Yeah, that’s federation. In terms of the principle in government as well as its application in the lemmy protocol.
lemmy.world and beehaw.org are defederated. However, this doesn’t mean that you can’t see beehaw posts as a lemmy.world user, or vice versa. But (let’s say you’re a lemmy.world user) if you comment on a beehaw post, you’re commenting on a replicated version of the post that is hosted on lemmy.world. It is not synced with the original post hosted on beehaw, and you will only be able to see comments from other lemmy.world users and comments from before beehaw defederated.
Thanks that makes sense. I understand that if I’m on a third instance that is federated with both lemmy.world and beehaw.org, and I click on a beehaw.org post then I would not be able to see comments from lemmy.world users. But I would be able to see comments from beehaw.org users and they would see comments from my instance.
Yep the original post on the beehaw instance is like a master record of the post that lives on their server and only their users and users from federated instances can interact with it. Meanwhile the act of a lemmy.world user subscribing to a given beehaw community triggers the lemmy.world instance to archive posts there and create separate self-contained records of them which only lemmy.world users can interact with