this post was submitted on 15 Jun 2023
871 points (99.5% liked)

Lemmy.World Announcements

29079 readers
242 users here now

This Community is intended for posts about the Lemmy.world server by the admins.

Follow us for server news 🐘

Outages 🔥

https://status.lemmy.world/

For support with issues at Lemmy.world, go to the Lemmy.world Support community.

Support e-mail

Any support requests are best sent to info@lemmy.world e-mail.

Report contact

Donations 💗

If you would like to make a donation to support the cost of running this platform, please do so at the following donation URLs.

If you can, please use / switch to Ko-Fi, it has the lowest fees for us

Ko-Fi (Donate)

Bunq (Donate)

Open Collective backers and sponsors

Patreon

Join the team

founded 2 years ago
MODERATORS
 

ou might have seen that we've been defederated from beehaw.org. I think there's some necessary context to understand what this means to the users on this instance.

How federation works

The way federation works is that the community on beehaw.org is an organization of posts, and you're subscribed to it despite your account being on lemmy.world. Now someone posts on that community (created on beehaw.org), on which server is that post hosted?

It's hosted on both! It's hosted on any instance that has a subscriber. It's also hosted on lemmy.ml, lemmygrad.ml, etc. Every instance that has a subscriber is going to have a copy of this post. That's why if you host your own instance, you'll often get a ton of text data just in your own server.

And the copies all stay in sync with each other using ActivityPub. So you're reading the post that's host on lemmy.world, and someone with an account on beehaw.org is reading the same post on beehaw.org, and the posts are kept in sync via ActivityPub. Whenever someone posts to that community or comments on a post, that data is shared to all the versions across the fediverse, and these versions are kept in sync. So up until 5 hours ago, they were the same post!

"True"-ness

A key concept that will matter in the next section is the idea of a "true" version. Effectively, one version of these posts is the "true" version, that every other community reflects. The "true" version is the one hosted on the instance that hosts the community. So the "true" version of a beehaw.org community post is the one actually hosted on beehaw.org. We have a copy, but ours is only a copy. If you post to our copy, it updates the "true" version on beehaw.org, and then all the other instances look to the "true" version on beehaw to update themselves.

The same goes for communities hosted on lemmy.world or lemmy.ml. Defederation affects how information is shared between instances. If you keep track of where the "true" version is hosted, it becomes a lot easier to understand what is going on.

How defederation works

Now take that example post from earlier, the one on beehaw.org. The "true" version of the post is on beehaw.org but the post is still hosted on both instances (again, it has a copy hosted on all instances). Let's say someone with an account on beehaw.org comments on that post. That comment is going to be sent to every version of that post via ActivityPub, as the "true" version has been updated. That is, every version EXCEPT lemmy.world and sh.itjust.works. So users on lemmy.world and sh.itjust.works won't get that comment, because we've been defederated from beehaw.org. If we write a comment, it will only be visible from accounts on lemmy.world, because we posted to a copy, but our copy is now out of sync with the "true" version. So we can appear to interact with the post, but those interactions are ONLY visible by other lemmy.world accounts, since our comments aren't send to other versions. As the "true" version is hosted on beehaw, and we no longer get beehaw updates due to defederation, we will not see comments from ANY other community on those posts (including from other defederated instances like sh.itjust.works).

The same goes for posting to beehaw communities. We can still do that. However, the "true" version of those communities are the ones on beehaw, so our posts will not be shared to other instances via ActivityPub. And all of this is true for Beehaw users with our communities. Beehaw users can continue to see and interact with Lemmy.world communities, but those interactions are only visible to other Beehaw users, since the "true" versions of the Lemmy.world communities (the ones sent to/synced with every other instance) is the Lemmy.world one.

Communities on other instances, for example lemmy.ml, are unaffected by this. Lemmy.world and beehaw.org users will still be able to interact with those communities, but posts/comments from lemmy.world users won't be visible to beehaw.org users, as defederation prevents our posts/comments from being sent to the version of these posts hosted on beehaw.org. However, as the "true" version is the one on the third instance, we can still see everything from beehaw.org users. So we see a more filled in version than the beehaw users.

Why can I still see posts/comments from beehaw users?

Until they defederated us, posts/comments were being sent to lemmy.world, so we can see everything from before defederation. After defederation, we are no longer receiving or sending updates. So there are now multiple versions of those posts.

Why can I still interact with beehaw communities?

This won't ever stop. You'll notice that all posts after defederation are only from lemmy.world users. You won't see posts/comments from ANY other instance (including instances that ) on beehaw.org communities.

Those communities will quickly suck for us, as we're only talking to other lemmy.world users. Your posts/comments are not being sent to any other lemmy. I highly recommend just unsubscribing from those communities, since they're pretty pointless for us to be in right now.

Why do I still see comments from beehaw users on lemmy.world communities?

Again, comments from before defederation were still sent to us. After defederation, it will no longer be possible for beehaw users to interact with the "true" version of lemmy.world communities. Their posts/comments are not being sent to any other lemmy. They also aren't getting updates from any other lemmy, as the "true" version of those communities is on our instance.

Why do I see posts/comments from beehaw users on communities outside lemmy.world and beehaw.org?

That's because the "true" version of those posts is outside beehaw. So we get updates from those posts. And lemmy.world didn't defederate beehaw, so posts/comments from beehaw users can still come to versions hosted on lemmy.world.

The reverse is not true. Because beehaw defederate lemmy.world, any post/comment from a lemmy.world users will NOT be sent to the beehaw version of the post.

This seems like it's worse for beehaw users than for us?

Yes. In my opinion, this is an extraordinarily dumb act by the beehaw instance owners. It's worse for beehaw users than for us, and will likely result in many beehaw users leaving that instance. They said in their post that this is a nuke, but I don't think they fully assessed the blast area. Based on their post, I don't think they fully understand what defederation does.

(page 4) 50 comments
sorted by: hot top controversial new old
[–] thesanewriter@vlemmy.net 13 points 1 year ago* (last edited 1 year ago) (1 children)

I think this entire issue is showing a critical issue with Lemmy's maturity, which is honestly the number one thing blocking people from sites like Reddit from joining. All of Lemmy's tools for dealing with moderation are currently a bit underdeveloped. From the Admin tools of an instance to the moderator tools for each community, there just isn't very much granularity. That means right now Lemmy can't handle large communities, and with one as large as lemmy.world some trolls filter in. Even worse, right now if a lemmy.world user goes and posts a homophobic rant on a queer instance, like Blahaj, and people proceeded to report it, those reports would only go to Blahaj when they should probably go to both Blahaj and lemmy.world, meaning that those toxic users are only banned within the instance they offended in and can retreat to the refuge of their main instance, and proceed to attack other communities. One of the issues is less so with the tooling and moreso with just how fast Lemmy has grown, for example beehaw has 5 admins but over 12 thousand users, plus the users from the other communities they are still federating with. That means that every admin is managing thousands of people, which is not sustainable. Until these critical issues with the tooling are solved, Lemmy is going to be staunched in its growth, and we are going to end up with instances defederating to try and take control.

Edit: The report thing might be incorrect, and if so I apologize for not verifying that information before spreading it.

load more comments (1 replies)
[–] rarkgrames@lemmy.world 13 points 1 year ago (2 children)

So maybe this is a silly question and I don’t understand things completely but does this mean as a lemmy.world member I should unsubscribe from beehaw communities and find similar communities elsewhere?

[–] Spzi@lemmy.click 12 points 1 year ago

Yes, I think that's what they tried to explain. If you do not unsubscribe from a community on an instance which has defederated your instance, you will only ever meet lemmys from your home instance in this community. This probably gets stale rather quickly, hence the recommendation to unsubscribe.

If you want to interact with lemmys from other instances, unsubscribe from communities from instances which defederated your instance.

load more comments (1 replies)
[–] stylishboar@lemmy.world 12 points 1 year ago (1 children)

Thank you for this explanation; it’s super helpful. Regardless of our views on this decision, I think it’s important to remember why we’re here in the first place. This decision does seem drastic, but I don’t think hoping that beehaw “dies off” is the right mindset. I’m sure Reddit is sitting on the sidelines waiting for something like this to happen, so we should be doing whatever we can to keep the momentum we’ve gained in the past few days and ensure the fediverse doesn’t implode.

load more comments (1 replies)
[–] sisyphean@programming.dev 12 points 1 year ago (1 children)

The more I think about it, the more it seems that the appropriate response is mutual defederation. It will cause a lot of unnecessary confusion if lemmy.world and the other affected instances don’t do that.

load more comments (1 replies)
[–] Kissaki@feddit.de 12 points 1 year ago (1 children)
load more comments (1 replies)
[–] Anon2971@kbin.social 11 points 1 year ago* (last edited 1 year ago) (9 children)

This is a really good explanation for how defederation works.

I understand your point that Beehaw defederating from two subs for moderation and user management seems like an extreme reaction. But it's one I kind of expected from them given Beehaw's philosophies as as an instance.

Their detailed posts about what Beehaw is always made it very clear to me they think carefully about how they run their space and the users they want to grant access to. They really prioritise making their instance a safe space for well-meaning discussion through their vetted registrations.

I'm not an admin. I'm not an experienced Lemmy user. I'm not someone who has had experience moderating and being an admin on several communities before. They have and I've also seen activity on the Lemmy repo from them showing they have dev experience too.

As you pointed out, the entire site of 12k users is currently managed by 4 people who seem to have quite a lot of experience managing communities. That's a big workload. I've been using both Beehaw and Kbin since Reddit's awful API changes to see how both places grow and so far I've found Beehaw to be a very enjoyable experience with a pretty high engagement rate. I usually get hella upvotes and replies to anything I say. It does feel like a pretty active, close-knit place of well-meaning people even at this early stage. I think they're running Beehaw pretty well so far. Kbin is very solid too, but Beehaw I've found tends to have a deeper level of engagement and longer, more in-depth post styles that I prefer.

I know any instances with open registration could hop in and contribute to Beehaw, so this issue they have of not being able to vet and control users isn't unique to those two instances. But given so far the place to me as a user still feels the same as when I joined a few days ago more or less, I'm going to take them at their word that they're getting an influx of activity that isn't a particularly good fit for Beehaw for now. There's a lot of instances that could defederate from. 2 is not a huge number so far. Plus they did explicitly say at the end this is not a permanent decision, they may very well change their minds later on.

So personally, I respect and understand Beehaw's decision at this moment. Lets give things time and see how things develop. It's definitely a temporary, broad axe to cutting an apple type solution to their troll problem - which may very well continue as Lemmy gets more popularity as a platform overall - but I think they want to be specific about who they pull into their moderation team to ensure the vibe of Beehaw is maintained. Lets give it some time to see what happens.

load more comments (9 replies)
[–] hackbyte@friendica.utzer.de 11 points 1 year ago (48 children)

@AgentGoldfish Hrm .. the actual dumb thing is not getting defederated but owerwhelming other instances moderation team because of the lack of moderation on _your_ site.

load more comments (48 replies)
[–] jinarched@lemm.ee 11 points 1 year ago

I'm very grateful for this post. Thank you very much.

[–] Speckle@lemmy.world 11 points 1 year ago

Thanks for posting this, it made it a lot clearer for me and answered why I could still see the Beehaw communities I'd subscribed to

load more comments
view more: ‹ prev next ›