If I’m not mistaken, you can see the posts and can even comment, but only people on lemmy.world will see your comment. People from beehaw and other instances won’t see it. That’s because lemmy.world haven’t defederated from beehaw.
You can see which instances are blocked here: https://beehaw.org/instances. It’s in the bottom of the page of every instance home page or just add ‘/instance’ after the instance’s address.
I’m new to this. I have one question. Imagine the following setup:
Instance A federates with instances B and C
Instance B only federates with instance C
Instance C federates with instance A and B
Following scenario:
Someone on instance B posts something and writes a comment to the post
I’m on instance A and I comment on his comment
Now someone from instance C comments on my comment
What does a person from instance B see now? I assume he won’t see my comment as instance B defederated instance A. But he should see the comment from the instance C guy. But how can he see the reply when the original comment is not visible?
Honestly I’m not sure, I’m also quite new to the fediverse. My guess is that being a parent comment, B wouldn’t see it, but if C was the parent and A the child comment, B would see only C.
Someone else explained this pretty well in an answer. If that guy is correct neither users from instance B nor C will see the comment from the A instance user. This is because the post is hosted on instance B. And A-B are not federated (because of the block from B’s side). This causes the comments from A to not be synched with B and therefore also not with C by proxy.
Federation is by definition a union, a mutual agreement. A and B are either federated or they aren’t, there is no “A is federated with B but B is not federated with A”.
So if A and B are federated and B and C are federated but not A and C, and your scenario happens, the person on B sees your comment but the person on C doesn’t see it and can’t reply to it.
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
If I’m not mistaken, you can see the posts and can even comment, but only people on lemmy.world will see your comment. People from beehaw and other instances won’t see it. That’s because lemmy.world haven’t defederated from beehaw.
More info here: https://kbin.social/m/lemmyworld@lemmy.world/t/24341/How-the-beehaw-defederation-affects-us
You can see which instances are blocked here: https://beehaw.org/instances. It’s in the bottom of the page of every instance home page or just add ‘/instance’ after the instance’s address.
That’s actually a really clever approach
I’m new to this. I have one question. Imagine the following setup:
Following scenario:
What does a person from instance B see now? I assume he won’t see my comment as instance B defederated instance A. But he should see the comment from the instance C guy. But how can he see the reply when the original comment is not visible?
Good question!
I think if you do that the little red light would stop blinking and you’d break the internet.
Honestly I’m not sure, I’m also quite new to the fediverse. My guess is that being a parent comment, B wouldn’t see it, but if C was the parent and A the child comment, B would see only C.
Someone else explained this pretty well in an answer. If that guy is correct neither users from instance B nor C will see the comment from the A instance user. This is because the post is hosted on instance B. And A-B are not federated (because of the block from B’s side). This causes the comments from A to not be synched with B and therefore also not with C by proxy.
Federation is by definition a union, a mutual agreement. A and B are either federated or they aren’t, there is no “A is federated with B but B is not federated with A”.
So if A and B are federated and B and C are federated but not A and C, and your scenario happens, the person on B sees your comment but the person on C doesn’t see it and can’t reply to it.
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