• 1 Post
  • 22 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle




  • surely I can do that without both of them needing to give me permission via federation?

    So there are whitelist only instances (which honestly is what beehaw should be doing), so if you hosted your own instance, you would need to be whitelisted in order to interact with beehaw communities/users. Otherwise, federation is pretty much a default

    Like if I want to set up my own instance and pull posts from lemmy.world and beehaw.org, surely I can do that without both of them needing to give me permission via federation?

    Ok, so this requires some understanding of the ActivityPub protocol, and my understand of this edge case is admittedly a bit fuzzy. You can still access that information, you could do it right now just by going to https://beehaw.org, and if you have some mechanism to pull that data, you could still get that data if you wanted to. But critically, that wouldn’t use ActivityPub.

    With ActivityPub, your instance would send a request to the community on beehaw to follow the community. The beehaw instance would then send updates to your instance, where they would be stored as a copy. Beehaw keeps the “true” version, as the community is hosted on their instance, but you have your own copy. If beehaw defederates you (or is whitelist only and never federates you), then you can’t send that request (rather, you can send the request, but beehaw won’t listen). So beehaw will not send updates via ActivityPub.


  • sorry, I had to do a lot of editing in order to get it to post this morning.

    Including instances that are also defederated.

    Basically, beehaw has decided we can no longer access the “true” version of communities on beehaw. So the versions hosted here on lemmy.world are still visible to lemmy.world users, but that doesn’t update the “true” version, and also doesn’t update other versions hosted on other defederated instances.

    It will be interesting to check beehaw communities hosted on defederated instances in a few days. Because the version on lemmy.world will be very different from the version on sh.itjust.works which will be different still from the “true” version.


  • You obviously got called out for disregarding the rules of other instances

    I obviously didn’t. I like how you just assuming I’m some internet asshole. All I did was write out an explanation for the users of this instance because there was a lot of confusion about what defederation means. Maybe stop being a jerk and making assumptions?

    I never said beehaw wasn’t allowed to do what they’re doing, of course they are. You’re the one making that assumption. I said that this will result in more damage to beehaw than to lemmy.world, and it will do more damage still to lemmy as a whole.



  • That’s not at all what’s happening though.

    Anyone can create an instance. So using your example, it’s kind of like reddit banning anyone posting from 4chan, but literally anyone could create their own “chan” to post to reddit. If they only whitelisted instances then that would at least make some sense.

    It shouldn’t be beehaw’s job to moderate another instance that just lets everyone in.

    But that’s exactly what they’re trying to do.

    I think the admins of Beehaw think they’ve effectively banned lemmy.world users from their instance, which is largely what they did. And if they chose to do that, then that’s their decision. But they didn’t choose to do that, they did something far more drastic.

    Defederation prevents beehaw users from interacting with lemmy.world users ANYWHERE on lemmy. Effectively, beehaw admins are deciding what their users can see elsewhere on lemmy, which in my view is wrong. Effectively, in order to access most of lemmy, beehaw users will need a second account on another instance. And if you’re going to have a second account, why have the first?

    The problem is that defederation is not an act of moderators. This is an admin level action being used in service of a moderator level problem. This is not how defederation is meant to be used, and given how the admins of that instance describe their reasoning, I don’t think they fully understand the implications of their decision.




  • There’s a lot of instances that could defederate from. 2 is not a huge number so far.

    They defederated from 300 some instances. And it’s kinda ridiculous to use the number of instances instead of the number of users. They defederated from 2 of the top 4 instances in terms of number of users.

    It’s definitely a temporary, broad axe to cutting an apple type solution to their troll problem

    Two things:

    1. It doesn’t actually address their troll problem, since anyone can create a new instance and post to their communities.

    2. It has the knock on affect of their users not being able to interact with a huge chunk of the wider fediverse

    That second point is the main criticism I have for them. I don’t think they fully understood the consequences of their actions. They’re using an extreme admin-level action for community moderation. That’s now how this was intended to be used.

    Why would anyone stay on an instance that can’t interact with a huge chunk of the fediverse? Only the most passionate beehaw-ers will stay there. Most will likely leave to more accessible pastures.


  • They’re trying to intentionally cultivate a culture over there rather than to moderate over an evolving one, and at the moment its too much work for them with the high volume of users.

    Sure, but the way they went about doing it was the wrong way to do it.

    They’ve effectively locked their users into ONLY accessing their walled garden.

    I think what they wanted to do was block lemmy.world and sh.itjust.works users from posting in their communities, which would be possible with a pretty simple bot. Instead, they’re largely preventing their own users from accessing other communities, which based on their post was not their intention. And because of those effects, it’s likely going to result in their users leaving for instances with more access.




  • There’s a positive here:

    Everyone can just leave beehaw. I already saw a few comments from users that left beehaw after the admins there made poor decisions. Unlike reddit where if the admins make horrible decisions you can’t really leave, here the admins are bound similarly to how moderators were on reddit.

    If the mods fuck up too much, people just create their own sub. Seattle had like 4 different subs due to moderator bullshit. Beehaw will probably not survive, and that’s ok. But lemmy as a whole will be perfectly fine!



  • No, this is a bad idea. If an instance defederates, they no longer get the “true” version of posts in other instances.

    This idea of defederation is an extreme step. It really is like a nuke, and it really is supposed to be used in extreme circumstances (for example, a nazi instance should be defederated asap). The issue is that this extreme action is being used incorrectly.

    They’re using extreme actions when a bot could just as easily accomplish the same task without needing to nearly break lemmy. It shows that the admins of that instance really don’t understand what defederation is or what it actually does.