Gex

joined 2 years ago
[–] [email protected] 4 points 2 years ago

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.

[–] [email protected] 2 points 2 years ago (1 children)

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.

[–] [email protected] 1 points 2 years ago (3 children)

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".

[–] [email protected] 5 points 2 years ago (8 children)

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?

[–] [email protected] 5 points 2 years ago

Hope this idea will succeed!

view more: ‹ prev next ›