this post was submitted on 10 Jul 2023
259 points (92.7% liked)

Fediverse

28750 readers
37 users here now

A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).

If you wanted to get help with moderating your own community then head over to [email protected]!

Rules

Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy

founded 2 years ago
MODERATORS
ruud
Xylinna
MrCenny
TragicNotCute
automodbeta
woelkchen
259
We have 2-3 months to compile a Threads block list (www.timothychambers.net)
submitted 1 year ago* (last edited 1 year ago) by jocanib to c/fediverse
123 comments fedilink hide all child comments
 

It is expected to be 2-3 months before Threads is ready to federate (see link). There will, inevitably, be five different reactions from instances:

  1. Federate regardless (mostly the toxic instances everyone else blocks)

  2. Federate with extreme caution and good preparation (some instances with the resources and remit from their users)

  3. Defederate (wait and see)

  4. Defederate with the intention of staying defederated

  5. Defederate with all Threads-federated instances too

It's all good. Instances should do what works best for them and people should make their home with the instances that have the moderation policies they want.

In the interests of instances which choose options 2 or 3, perhaps we could start to build a pre-emptive block list for known bad actors on Threads?

I'm not on it but I think a fair few people are? And there are various commentaries which name some of the obvious offenders.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 1 points 1 year ago* (last edited 1 year ago) (1 children)

I'm looking at beehaw communities on both Lemmy.world and Beehaw.org,and they're totally out of sync with each other. There's the rare post from a beehaw user that breaks through somehow - possibly boosted from a kbin or Mastodon instance? - but for the most part, you're getting basically none of the content from those communities.

Because beehaw isn't sending you any updates.

Is it that you're seeing beehaw users who are posting to communities hosted on 3rd party communities? Because that's absolutely possible.

And that's absolutely the issue with federating with sites that continue to federate with instances you've defederated from. You're blocking direct communication in both directions, but there's a lot of indirect communication going on.

Like, this is literally the scenario I described.

[โ€“] Zaktor 1 points 1 year ago

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.