Ok I see. And the reason for that is because beehaw has defederated my server, but my server has not defederated beehaw, correct?
Kinda confusing, I guess I thought of federation as a bilateral agreement for some reason, but actually each instance unilaterally decides who to federate with, and its not always reciprocal.
Yes. Think of it like blocking someone. beehaw defederated from sh.itjust.works so they can’t see anything from sh.itjust.works. not comments, not threads, not communities. 100% blocked. whereas the reverse isn’t true. you’re not able to get communities or content from beehaw (because they blocked and aren’t sending it to you), but their comments and threads elsewhere in the fediverse are still shared with you. This thread is hosted on lemmy.ml, so everyone federated with lemmy.ml can see it and interact with it; this is why you can see the beehaw user’s comment.
However, since beehaw defederated with sh.itjust.works, your reply remains unseen by them. sh.itjust.works could mutually defederate/block beehaw and you wouldn’t see the comment. but that’s up to your instance whether you wanna do that or not.
Ok thanks for explaining. I don’t see any reason we would defederate beehaw, they only blocked us because trolls were signing up on our server and spamming toxic stuff to their communities. Totally understandable, and hopefully we can reconnect with them once this platform matures a bit.
I know some people on lemmy.world were discussing defederating with beehaw because they were thinking it was annoying/confusing to have beehaw stuff show up even when beehaw defederated with them (and thus results in situations like this).
personally, I’m of the philosophy that it’s good to federate with as many instances as possible. and that’s how kbin has been doing things so far. other instances may wish to intentionally select which instances they federate to craft particular experiences (like what beehaw did). just depends on what you’re after.
Defederation should honestly be saved for the worst of the worst. What beehaw has done just doesn’t really make much sense. They’re intentionally blocking themselves off from the rest of the fedi, and I don’t think it’s because of trolls/spam. It seems like any comments that don’t fit the culture they want are seen as a reason to defederate.
I mean that’s fine for them, they can stay in their bubble, but it means their users could potentially miss on a lot of content as well; it honestly hurts them more than the rest of us. And the longer they stay that way, the more they’ll suffer, unfortunately.
I feel like even though this is all pretty chaotic in the short term, it feels like it could be a pretty good learning experience for the strengths and weaknesses of federating in general
Ok I see. And the reason for that is because beehaw has defederated my server, but my server has not defederated beehaw, correct?
Kinda confusing, I guess I thought of federation as a bilateral agreement for some reason, but actually each instance unilaterally decides who to federate with, and its not always reciprocal.
Yes. Think of it like blocking someone. beehaw defederated from sh.itjust.works so they can’t see anything from sh.itjust.works. not comments, not threads, not communities. 100% blocked. whereas the reverse isn’t true. you’re not able to get communities or content from beehaw (because they blocked and aren’t sending it to you), but their comments and threads elsewhere in the fediverse are still shared with you. This thread is hosted on lemmy.ml, so everyone federated with lemmy.ml can see it and interact with it; this is why you can see the beehaw user’s comment.
However, since beehaw defederated with sh.itjust.works, your reply remains unseen by them. sh.itjust.works could mutually defederate/block beehaw and you wouldn’t see the comment. but that’s up to your instance whether you wanna do that or not.
I love you for explaining this so clearly, I was actually so confused about this I may or may not have misinformed someone else, oops.
Ok thanks for explaining. I don’t see any reason we would defederate beehaw, they only blocked us because trolls were signing up on our server and spamming toxic stuff to their communities. Totally understandable, and hopefully we can reconnect with them once this platform matures a bit.
I know some people on lemmy.world were discussing defederating with beehaw because they were thinking it was annoying/confusing to have beehaw stuff show up even when beehaw defederated with them (and thus results in situations like this).
personally, I’m of the philosophy that it’s good to federate with as many instances as possible. and that’s how kbin has been doing things so far. other instances may wish to intentionally select which instances they federate to craft particular experiences (like what beehaw did). just depends on what you’re after.
Defederation should honestly be saved for the worst of the worst. What beehaw has done just doesn’t really make much sense. They’re intentionally blocking themselves off from the rest of the fedi, and I don’t think it’s because of trolls/spam. It seems like any comments that don’t fit the culture they want are seen as a reason to defederate.
I mean that’s fine for them, they can stay in their bubble, but it means their users could potentially miss on a lot of content as well; it honestly hurts them more than the rest of us. And the longer they stay that way, the more they’ll suffer, unfortunately.
I feel like even though this is all pretty chaotic in the short term, it feels like it could be a pretty good learning experience for the strengths and weaknesses of federating in general