Skip Navigation
Pawb.Social Announcements @pawb.social
Crashdoom (he/him) @pawb.social
PSA

Known Issue: Posts in NSFW Communities

We’ve been made aware that it is no longer possible to identify posts as NSFW in a NSFW community as of Lemmy 0.19.11 (https://github.com/LemmyNet/lemmy-ui/pull/2887), and as a result some posts appear to be not marked as NSFW.

While some apps (Voyager is the only one I have personally verified) do correctly flag the posts in NSFW communities as NSFW by default.

We’ve verified on 0.19.11 Lemmy will blur the image and not tag the post as NSFW, but we haven’t verified behavior from older instances viewing our communities / posts.

Due to the current time as of writing this, I’m not able to investigate further until the morning but I hope this provides some basic information on the situation for now.

8 comments

  • You're welcome for making that clear :P

    . . .anyway, thanks for working on the issue!

    • We've got a fix deployed that'll allow the NSFW box to be toggled again for new and existing posts -- Is there any chance you'd be able to facilitate that on your existing posts? We're hoping that'll alleviate reports and complaints in the interim while we wait for the permanent backend fix x3

      • I tested and yes, I can flag NSFW now. I will update my posts soon

      • As a user level verification, I don't see a checkbox for post https://pawb.social/post/22913626 I'm on the default web interface. The post was marked as NSFW originally by some developer tools trickery.

        • I'm not able to replicate this myself as it's showing on both the Create Post and editing modes. I've cleared the site cache on Cloudflare as it could be it's caching an old version of the UI. I'd also encourage clearing your browser cache / force refreshing.

          • Okay, a hard refresh and now its showing up. (ctrl + shift +r)

    • Just as a hack, when creating a new post, most of the information is passed as parameters in the URL, you can ensure the NSFW flag is set for the front end by ensuring nsfw=true is one of the parameters in the request.

8 comments