Instance A does not federate with Instance B. But B federates with A. What does it mean to a user?
Instance A does not federate with Instance B. But B federates with A. What does it mean to a user?
I've tried searching for other posts that ask a similar question, but I couldn't fine one that could fully make me understand what it would mean in this scenario.
So far from my understanding is that if I browse All, the instance I'm on won't show anything at all from the instances that it blocked. But manually doing the workaround would still show me the community and whatever posts that got federated in my instance. Is my understanding correct?
The other topic of federation that I'm interested to understand as a user are below.
The example: fedia.io states in their federation list that it does not federate with ani.social. But ani.social states they federate with fedia.io.
I can go to say !anime@ani.social just fine via fedia.io, although there is some posts that doesn't show. Is this one of the result of this situation?
Additionally, today I did basically try to subscribe to all the same communities/magazines on my lemmy.world (I'm considering to abandon this account), fedia.io and kbin.earth accounts.
Other than the situation above happened to some communities where some post doesn't sync, I've also found some communities that's just inaccessible from either 3 instances.
Is that another result of not being federated?
Thanks in advanced.
It means both instances will see old posts from before one of them defederated.
Now that A is de-federated from B, they both won't see new posts or comments from eachother. In the case of fedia and ani.social, you won't get any new posts from any of their communities or users. If you post on anime@ani.social from fedia, nobody will see that post outside of fedia users, because ani.social isn't seeing it and passing it around to the rest of the fediverse.
You hav basically the right idea, everything stops syncing when one defederates.
Yup. Since fedia.io was federating with ani.social for awhile you've got a "local copy" of ani.social's communities on fedia.io from back when it federated.
So when you post on those communities it's all happening only on fedia.io and you see posts/comments on that community from other fedia.io users. But, for example, I can't see what fedia.io local copy of anime@ani.social looks like from my instance, because my "local copy" is still federating with the actual instance anime community is hosted on (i see new posts and my posts/comments get sent first to ani.social's original community and federates to rest of instances from there).
Thanks. That's a slight shame. I've only been trying out lemmy / threadiverse for just a few days (second attempt. first attempt was back on reddit APIcalypse) and for now I'm liking mbin a bit more than lemmy. fedia.io being the biggest instance, so that's why I registered there first. next biggest mbin instance is a bit less stable.
I suppose it's still early days for me so I can afford to jump around for now to see what instance sticks, and I guess the software as well.
Hmm, I see. This is interesting. It gives me the feeling that I either would "have to" have a generalist account on the least defederated instance to have as wide a net (kind of my early times on reddit), or I would have specialized accounts to specific topics in multiple instances.
is there any particular reason ani.social is defederated? just curious
Sorry, I wouldn't know. I'm new and slowly dipping into lemmy and eventually other parts of fediverse. I'm curious too, but idk if I should ask fedia.io's admin about it.
The lemmy devs added it to some big block list with verifiable lies as the justification (some same lolicon epidemic). Haven't checked to see if it's still there, but it's a pretty good red flag to watch for bad instances imo.
Probably boils down to Western chauvinism over anime.
Instance A defederating B or vice versa is the same result. Any posts on any inaccessible remote communities will remain and act like local only communities, specific to your instance.