357
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 24 Jun 2023
357 points (100.0% liked)
Technology
37728 readers
591 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
Is it just me or does that sound like anything on instances hosted outside of meta's own that can be merely seen from theirs? I'm all for moderation, the stricter moderation against hate-speech is part of why I joined Beehaw. But if I'm reading that right (I hope I'm not), then it seems like they plan to call the shots on other instances as if they have any say in what everyone else does right out of the gate.
Maybe what's meant here is simply defederation of entire instances and banning of problematic users like any other instance does, ok. But it could also mean pressuring admins to enforce Meta's TOS on a case-by-case basis which feels like the start of EEE tactics.
It just means they'll block users who don't abide by local site rules, which is standard practice.
Remote content is viewed locally, via mirroring, so in order for local users to see that remote content it had to be hosted on the local site. If that content does not meet local community standards, it gets removed, and the poster gets blocked.
This absolutely puts pressure on other admins to adhere to Meta's standards, because if they don't then they'll risk being defederate, but that's the whole history and controversy of Fediblock in a nutshell.
Meta won't have control over what users on other instances post. Instead, they'll just have very strong influence over the rules on instances that desperately want to federate with senpai Meta.
Strong echoes of Microsoft's "embrace, extend, and extinguish" strategy...
And really it's nonsense. If we wanted to be on Facebook then we already would be. Meta coming in and telling everyone how to run their instances because a Facebook user might see their content, won't bode well.