Just open any post with NSFW picture the preview in the post is not blurred. See this post itself as an example

  • willya@lemmyf.uk
    link
    fedilink
    English
    arrow-up
    14
    ·
    1 year ago

    If you’re opening a nsfw post, wouldn’t you be opening it to see it?

      • willya@lemmyf.uk
        link
        fedilink
        English
        arrow-up
        4
        ·
        edit-2
        1 year ago

        Maybe they really like the build up. “Oooohh am I gonna be naughty still? One more chance.”

        • limerod@reddthat.comOP
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 year ago

          There can be posts which are nsfw which are not porn — gore, other not safe for work ones, etc. Doesn’t mean i would want the preview to be visible.

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

    I’m struggling to understand the problem here. At which point should the content not be blurred then?

    • limerod@reddthat.comOP
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      1
      ·
      1 year ago

      The blurred preview settings should also apply to previews in posts images. Just because I clicked the post doesn’t mean it should unblur previews automatically. Maybe, i didn’t want to see the image and just wanted to check the comments.

  • Mom Nom Mom@nom.mom
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    1 year ago

    I had thought that the way Sync currently behaves was the normal behavior, but after using the pwa (instead of Sync) I can see that it behaves differently between the two.

    The pwa keeps the thumbnail blurred until you click on it - even when you go into the post to read whatever. It makes your request make a lot more sense when you see how the website behaves.

    You guys probably know that I like my screenshots, so here’s my pwa views before clicking the thumbnail and after. (Did you make that feature request?)