• yukichigai@kbin.social
    link
    fedilink
    arrow-up
    5
    ·
    1 year ago

    Pretty sure kbin defeds from some of the worst, like exploding heads (though they’ve since imploded) and rammy.

    Also you can always block the entire domain on kbin so you don’t have to deal with those jagoffs at least. Just go to kbin.social/d/<instancedomain.whatever> and you can block all content coming from that domain/instance.

    • DarkThoughts@kbin.social
      link
      fedilink
      arrow-up
      8
      ·
      1 year ago

      It’s not defederated from exploding-heads, hexbear, lemmygrad & others. It doesn’t even ban extremistic magazines & users either.

      And no, you cannot block an entire domain on kbin. Blocking an instance through the interface like this does nothing. The posts & comments from those places will still show up on your feed. You have to block each and every single magazine / community individually. I tried this with the furry instance and lemmy.ml already.

      • Mario_Dies.wav@lemmy.dbzer0.com
        link
        fedilink
        arrow-up
        4
        arrow-down
        1
        ·
        1 year ago

        Oh damn, that explains why 99.999% of advertising bots and spam are coming from kbin. Imagine not defederating from exploding-heads wtf

        Are they at least defederated from that one raging pedo instance?

        • ijeff@lemdro.id
          link
          fedilink
          English
          arrow-up
          3
          ·
          1 year ago

          Oh damn, that explains why 99.999% of advertising bots and spam are coming from kbin. Imagine not defederating from exploding-heads wtf

          The reason is that moderator actions don’t federate over from kbin. It’s being worked on.

          • DarkThoughts@kbin.social
            link
            fedilink
            arrow-up
            2
            ·
            1 year ago

            Not just from kbin but also to kbin. I think it’s a general issue with the protocol, same goes for edits I believe. I’ve seen several posts that allegedly have been removed by moderators on Lemmy, which were still visible on kbin. Same for people who said they allegedly edited their comments (specifically URLs), but they were still the same for me on kbin.

        • DarkThoughts@kbin.social
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          Are they at least defederated from that one raging pedo instance?

          No idea since I have no idea which one you’re talking about.
          Kbin was quick to defederate from nsfwlemmy over the bs pedo claims, if that’s what you mean, but I think that has been reversed already. But 18+ content in general seems to be not really fed into the feeds algorithm, as I almost never see anything.

          • Mario_Dies.wav@lemmy.dbzer0.com
            link
            fedilink
            arrow-up
            2
            ·
            1 year ago

            Naw, this wasn’t just a NSFW one. I was unfortunate enough to see posts and comments from it browsing all when I first joined back in June.

            Burrgit? Burgerrit? Something like that. Afaik, most instances defederated them pretty quickly.

    • CarlsIII@kbin.social
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      Just a warning, blocking instances on kbin leads to an issue where you can’t see any of the comments on your own threads, and your own threads don’t show up in your own feed.

      • yukichigai@kbin.social
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        Oof. Damn. Is there a fix for it in the pipeline? Maybe in the new upgrade ernest is rolling out Soon™?

        I’m not personally affected since I’ve never felt the need to block an entire domain (yet?), but honestly it’s one of kbin’s better features. Be a shame for it to not work fully.

        • CarlsIII@kbin.social
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          If I understand correctly (and I probably don’t,) there is a fix but it hasn’t been implemented yet.