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?
You can. It took me a day to be subscribed to [email protected], don’t know if it’s how it’s supposed to be. EDIT: okay just checked again, what I said was bullshit. I’m actually still on “subscribe pending” but I can see their threads on my timeline.
That was before beehaw and lemmy.world were defederated.
Wait, are both Lemmy world and Beehaw defederating? I thought it was just beehaw. If Lemmy world defederates, wouldn’t that mean it will no longer see other federated platforms content. That kind of defeats the purpose of the reddit migration in my opinion.
Yeah I don’t understand how it works, but this seems like a really silly time to start splitting off tbh. Which instance are y’all signed up to?
Beehaw’s purpose is to have a place to have certain discussions in an environment that is conducive to those discussions. To build that environment, they have a user application process for new users. That was working well for them. However, lemmy.world allows anyone to sign up without screening. The result was that people were able to bypass Beehaw’s screening process to damage their environment.
To put into perspective, imagine you’re trying to run a support group for civilian refugees of Ukraine. You create an application process to screen out anyone that would like to sabotage that environment. However, the room also has a window to an adjacent room, and that adjacent room is open to the public. Russian military then use access to that room to taunt the people attending the support group with pictures of dead Ukrainians, not only effectively ruining the purpose of the group, but making the group members’ lives worse.
What Beehaw did was concrete up the window until they can figure out how to better protect their group members from people that want to damage their environment.
It seems unrealistic that a team of 4 people are going to be able to screen the potential flood of new users.
Entirely. I have no idea what the solution is. I think what Beehaw is doing is trying to prevent further damage while they come up with solutions that will work when federated with the rest of the instances.
Yeah, you won’t be able to. Basically, lemmy.world won’t be able to see new posts on beehaw, and vice versa.
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.
