Exactly. What happens when a far-right troll like libsoftiktok sics thousands of rabid followers on a fediverse account? I get the feeling our small, volunteer group of moderators just don’t have the resources to cover that kind of brigading.
Also, I don’t think moderation can even stop brigading or the downvotes to hell avalanche. It could only stop thread and comment creation on just your one community/magazine on your instance.
Nothing could stop a bad faith actor from finding my comments on a different instance and harassing or brigading me there if that instance federated with Threads, even if my instance defederate from Threads.
Well, at least downvotes isn’t going to be much of a problem, as threads users will only be capable of upcoming stuff they see here. They don’t have a downvote button. :)
They will be able to send swarms of trolls to harass. If Threads does even federate, I suspect even admins who didn’t sign the fedipact will defederate quite fast.
The way the Fediverse is designed you need to actively seek out content. It’s not going to be all that easy being a troll from threads attacking content on the Fediverse.
What I could imagine is that bigots might seek out LGTBQIA+ hashtags (along with hashtags related to other culture war dimensions), and find content from the Fediverse that way,
Then again, if that proves to be a problem, sites like Blahaj will probably be pretty darn quick to defederate. And this type of content, even when posted by kbin or Lemmy.world users or whatever, will probably often take place in communities hosted by instances like blahaj. So the thread trolls would find themselves isolated from the discussion pretty fast.
On the other hand, there’s a bunch of queer people who use threads. If all servers immediately defederate from it, these people will never get to have a glimpse into the fediverse. They could benefit a lot from joining a different platform, but if we focus only on the bigots we’ll end up never reaching them.
The same logic of course applies to other communities affected by the anti woke culture war bullshit, I’m just too lazy to come up with a more original example. :)
That’s different though - it’s going here and actively creating a user and settling. Interactions with Mastodon users are mostly limited to special interest groups and microblogs I feel, even though we’re all in the same network.
So we have the problem of protecting the vulnerable on our instances, while inviting the vulnerable from their instances.
I wonder if we could create Ambassador instances, where you have an account that basically posts to two instances: one that federates to Threads, and one that federates to the rest of the Fediverse.
Exactly. What happens when a far-right troll like libsoftiktok sics thousands of rabid followers on a fediverse account? I get the feeling our small, volunteer group of moderators just don’t have the resources to cover that kind of brigading.
Also, I don’t think moderation can even stop brigading or the downvotes to hell avalanche. It could only stop thread and comment creation on just your one community/magazine on your instance.
Nothing could stop a bad faith actor from finding my comments on a different instance and harassing or brigading me there if that instance federated with Threads, even if my instance defederate from Threads.
This Fediverse stuff is… complex.
Well, at least downvotes isn’t going to be much of a problem, as threads users will only be capable of upcoming stuff they see here. They don’t have a downvote button. :)
They will be able to send swarms of trolls to harass. If Threads does even federate, I suspect even admins who didn’t sign the fedipact will defederate quite fast.
The way the Fediverse is designed you need to actively seek out content. It’s not going to be all that easy being a troll from threads attacking content on the Fediverse.
What I could imagine is that bigots might seek out LGTBQIA+ hashtags (along with hashtags related to other culture war dimensions), and find content from the Fediverse that way,
Then again, if that proves to be a problem, sites like Blahaj will probably be pretty darn quick to defederate. And this type of content, even when posted by kbin or Lemmy.world users or whatever, will probably often take place in communities hosted by instances like blahaj. So the thread trolls would find themselves isolated from the discussion pretty fast.
On the other hand, there’s a bunch of queer people who use threads. If all servers immediately defederate from it, these people will never get to have a glimpse into the fediverse. They could benefit a lot from joining a different platform, but if we focus only on the bigots we’ll end up never reaching them.
The same logic of course applies to other communities affected by the anti woke culture war bullshit, I’m just too lazy to come up with a more original example. :)
I don’t know, a lot of us found our way here from Reddit and Twitter without being federated.
That’s different though - it’s going here and actively creating a user and settling. Interactions with Mastodon users are mostly limited to special interest groups and microblogs I feel, even though we’re all in the same network.
So we have the problem of protecting the vulnerable on our instances, while inviting the vulnerable from their instances.
I wonder if we could create Ambassador instances, where you have an account that basically posts to two instances: one that federates to Threads, and one that federates to the rest of the Fediverse.
For what it’s worth, LibsOfTikTok’s already getting slapped by Threads’s moderation.
Nope, she has repeatedly had posts reinstated after being initially flagged for hate speech, including that one. Meta knows their audience.
Ah, damn. Should’ve figured it was too good to be true if she was posting it.