I noticed that when I attempt to subscribe to beehaw subs, it seems to be stuck on pending. This has been the case for a couple hours now. Is this expected behavior? I think I read somewhere that beehaw was defederating. Perhaps this is the reason it’s not working?
Except I can see a new post from Beehaw. I’m having a conversation with somebody on a Beehaw community right now.
It seems the catch here may be that they are a Mastodon user. I guess Beehaw is still federated with their instance and so are we, so I can still see their content as if it were from Beehaw and we can comment to each other there!? But I guess if any Beehaw users join in, I’ll not be able to see their comments and they’ll not be able to see mine?
It’s quite odd, interesting and confusing.
Oh my! I can imagine this will hurt bees more than the rest of us, because they will read discussions with some comments missing just because the commenter happened to be from lemmy.world or other blocked instances.
Yeah, seems like that’ll be the case 😲. This explains it quite well: https://lemmy.world/post/149743
yes. so from beehaw’s perspective they have no access to lemmyworld communities (like how lemmyworld lacks beehaw communities). On other instances, like kbin magazines, beehaw users will be unable to see lemmyworld comments, and thus be “missing” comments and posts. so beehaw is definitely “hurt” more by this in terms of their content accessibility.
however, beehaw sees this as a positive and a benefit, not as a negative, because they don’t want to see lemmyworld content.
That’s their right. Not every instance have to be interconnected to everything.
If only that were the case. the trouble is, for users on lemmy.world, if they look at commuties, 4 of the top 9 they can “subscribe” to are Beehaw communities.
They can even access and post on those communities, unaware that they have been put in a wee walled garden by beehaw…
Unfortunately the only solution to that at this time would be lemmy.world clicking the defederate with beehaw button
yeah, how lemmy.world decides to respond is up to them. defederating would also mean not seeing beehaw comments outside of beehaw (and similarly hiding all of the non-beehaw replies to those beehaw comments).
as a lemmyworld user, you are not getting updates from beehaw. they blocked you. beehaw people should not be seeing your posts at all.
Isn’t it also the case that each instance gets updates from all others? So in this case, lemmy.world’s access to beehaw communities might lack [email protected] activity and beehaw’s access lacks [email protected] activity?
But I also believe lemmy.world can see old beehaw stuff from before the defed, so that could play a role. I’m really just trying to wrap my head around all the network effects and repercussions, its confusing as hell.
I’ve seen conflicting info on this. It seems to be the case that beehaw’s communities are hosted by beehaw as the “true version” which is synced with everyone else. In this regard, lemmyworld is blocked as beehaw will not send the “true version” of the community to lemmyworld. As for whether lemmyworld can get the “true version” from another instance? I don’t know. Lemmyworld does have the beehaw content before they were blocked, which they can still see and engage with. However those interactions are not sent to beehaw, which is where other instances are syncing with. Whether or not lemmyworld can indirectly participate in beehaw communities via other instances is unclear to me but I’m guessing the answer is no.
This is correct. Lemmyworld still has a copy of all the beehaw stuff from before the block/defederation. However, I believe it’s the case that if lemmyworld users try to comment on it, those comments will not be sent to us here on kbin (since we get our copy of beehaw communities from beehaw).
notably: lemmyworld users can see beehaw user posts on kbin magazines.