• 0 Posts
  • 13 Comments
Joined 2 years ago
cake
Cake day: June 23rd, 2023

help-circle



  • No, Beehaw users posting in Beehaw communities visible on Lemmy.world. There’s no third party interaction on either of those posts (just the Beehaw OP and Lemmy.world comments). Whether or not Beehaw is doing the convenience of sending updates, their content is accessible through Lemmy.world. It might take some action on a user here to trigger a pull, but it’s entirely possible and you shouldn’t expect defederation to prevent an intrusive instance from continuing to get content if they want it.

    I don’t know for sure there isn’t some pathway through another instance causing this, but in my understanding that’s not how federated communities work. There’s the owner instance that has the true version of the content and distributes it around and then local copies on each other server that feed their updates back to the main instance. You wouldn’t ever take a third party’s version of a community because you couldn’t trust its legitimacy.




  • Defederation is a one-way block of incoming traffic from the blocked instance. I’m on lemmy.world and can still see Beehaw content posted by Beehaw users even though they’ve defederated from lemmy.world, but if I comment on that content it will only be visible to lemmy.world users. Beehaw has protected its communities from lemmy.world commenters, but its content is still accessible by anyone for any purpose. Instances that federate with both sides don’t change this.




  • My expectation is that Threads will be too permissive with rules rather than too strict. They’re pretty happy to have LibsOfTikTok on there so they can make money from the stochastic terrorism. The problem I see is that their size means defederation for insufficient moderation isn’t a real threat, so federating instances are stuck with per-user moderation and will be overwhelmed with Threads trolls.

    I suppose it ends up being “their rules are our rules”, but in a “there are no rules and you’ll accept it” sort of way, rather than “adhere to our community standards or we’ll take away 90% of your users”.


  • Yes, I’m talking about what Threads users may see. It’s not clear how the Threads Algorithm will evaluate and prioritize showing Mastodon toots, but even less clear how it will prioritize message-board-like Lemmy content. It may not ever show them because it’s very possible it will either filter or devalue non-microblogging post types to fit with its native format. Whether or not they technically Federate is only half the question because they have the Algorithm deciding what you actually see.




  • Especially since a federated Mastodon server (since that’s the clearer peer service) means you can actually decide which Threads users you see rather than Trusting the AlgorithmTM. That’s a pretty strong pitch to get people to migrate once they’re sick of their feed just being 85% brands and influencers paying for reach.

    I’m more concerned with the expected lack of Threads moderation making a lot of work for admins who need to continually ban individual Threads users with no hope of the originating instance policing itself.