• sab
    link
    fedilink
    14
    edit-2
    1 year ago

    For kbin users to unilaterally block content from threads:

    1. Go to /d/threads.net
    2. Click the block button next to the subscribe one

    The only drawback is that it will only start working after the first piece of content from threads.net has been shared on your instance - for now it returns a 404 not found.

    Edit: Mileage may vary, depending on how Threads solves its fediverse integration.

    • dumples
      link
      fedilink
      21 year ago

      Does anyone know if kbin.social will even federate to begin with?

      • HeartyBeast
        link
        fedilink
        11 year ago

        Since Threads won’t apparently be federating at all, with anyone at launch - no.

    • cutitdown
      link
      fedilink
      21 year ago

      Getting a 404 error, but might just be due to kbin upgrades, etc.

    • static
      link
      fedilink
      2
      edit-2
      1 year ago

      Does /d/ block an instance?

      I think there is a misunderstanding in the kbin community.
      /d/ blocks a domain, A domain is not an instance.
      But i’m not shure what /d/ blocks or not. As far as I know it’s what’s between the bracket’s after a post ()

      • sab
        link
        fedilink
        11 year ago

        You’re right that it’s a bit trickier than I thought. It blocks the shared content: images and other content hosted at lemmy.world can be blocked from https://kbin.social/d/lemmy.world/ , but it will not include links to external sites, nor will it work for text posts. Blocking lemmynsfw.com worked fine for me, but that’s of course because it’s an image-heavy service.

        Whether or not it will work for threads.net off the bat I guess then depends on how Threads interacts with the fediverse; whether it merely shares a link content stored locally, or whether it distributes the content in its entirety.

        I updated my post to clarify!