Let’s say I’m from instance A and use a community from instance B. Let’s say another user of instance C, that’s not federated with A but is with B, post in B. Can I see that post?
You will not see any content from a defederated instance, even if they were posted to another federated instance.
Hmm… but what if I’m on the federated instance in theory? Assuming I’d see it then sorry I’m still figuring this place out
If the URL actually shows the address of the federated instance, yes - you’ll see the content. In that case you will not be signed in though.
If you visit the federated instance through your home instance, the content will not be visible and you’ll be signed in.
Yess… teach me about the federation… my Lord
Every post and comment is initially hosted on the user’s local instance. From there, it is federated everywhere else. If you’re on lemmy.ml and post on a community in lemmy.world, then if you click the federated link (multicoloured weird shape icon) it will take you to the lemmy.ml version of the post.
Thus, if your instance is not federated with another, you won’t see any posts or comments from users of that instance.
What’s really annoying is that they use a unique ID number for every post and comment - however each instance makes its own. So you can’t just change the URL to be your instance to find a specific post or comment. That only works at the community level, where the link becomes
yourinstance/c/community. What we should have is consistent numbering with the same instance tag, so a lemmy.ml post would belemmy.ml/post/12345, while others would belemmy.world/post/12345.ml. Lemmy is still very much a work in progress.My understanding is that defederation only affects content that’s native to the instance that was defederated. So in your example, users of instance A and instance C would be able to interact on instance C.
If the community is hosted on the defederated instance then I believe you wouldn’t see that post either. I believe the community instance reposts the post so that it can federate to all subscribed instances. And those might only be known to the instance that hosts the community. So everyone goes through it as a proxy.
