Can we get a consensus on whether our community should de-federate with servers that host loli? I personally think we should block them, and if that ends up not being the consensus here then I’ll probably sign up on another server. I hope we can all agree to set that boundary though because I like it here and it seems otherwise pretty cool.

  • Cracks_InTheWalls@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    23
    arrow-down
    2
    ·
    1 year ago

    I too would like the ability to block at the instance level as a user. Haven’t come across loli, but @lemmynsfw.com does show up quite a bit when looking at All.

    I have no problem at all with other sh.it.heads wanting to look at/interact with nsfw stuff from that instance, but I’m personally not interested. Given this, defederation seems extreme, but blocking on a community-by-community basis is time consuming and, as others have said, necessitates seeing the content to some degree (pretty sure you can choose whether stuff is blurred or not in your feed via the settings). I’d rather key ‘@lemmynsfw.com’ into a block list once, and go back to what I’m doing.

    • Aurix@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      2
      ·
      1 year ago

      No, wrong approach because it blocks users simply interacting. What is needed is a solution for the All feed.

      • Cracks_InTheWalls@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        9
        arrow-down
        1
        ·
        edit-2
        1 year ago

        Perhaps I explained it poorly (or just have some fundamental misunderstanding - both are equally likely), but this is more the ability to personally block posts from all communities hosted on a given instance by defining the block at the instance level, not comments from users from instances I blocked posts on, nor posts that those users make on communities in whitelisted instances. Users should be blocked on an individual basis, for sure. If it gets to the point that too many people here have to do this for users from one specific instance, that’s when defederation should be on the table IMO.

        This way, if it’s able to be done, I block @lemmynsfw.com and

        -I don’t see anything from c/[any]@lemmynsfw.com.
        -I do see a reply from user [x]@lemmynsfw.com on comments/posts I made in communities on other instances.
        -I do see a post from user [x]@lemmynsfw.com on c/[any]@sh.itjust.works

        If this can be done, I’m perfectly happy the leave All the way it is otherwise. But there could be other ways to address this, and I’m super open to hearing better approaches.

        • Pyr_Pressure@lemmy.ca
          link
          fedilink
          English
          arrow-up
          3
          ·
          1 year ago

          I agree, right now Lemmy and kbin and others are still growing, so instances right now with a dozen communities may have a hundred in a few months/years and if you don’t want to see nsfw content you would potentially have to individually block hundreds of communities from @lemmtnsfw.com to keep it from your all feed.

          It may be somewhat feasible now but the problem will only get worse going forward when you should be able to choose to “defederate” yourself from communities you know hold no value to you personally instead of relying on your whole instance to defederate itself from those communities when other users may not want to.