NSFW blurred, never unblurred

[xxxserxxx]

NSFW thumbnails are always blurred, and when viewing them, only the blurred image is shown.

On my Piefed account, I have NSFW blurring disabled; I almost always only browse my subscribed feeds and don't subscribe to any NSFW communities, so any NSFW content is usually tongue-in-cheek or if not, I don't care. However, thumbnails are still always blurred by Blorp, and only a blurred version off the image is ever shown if the content is expanded.

Attached is a short video demonstrating this. Note that the unblurred content is briefly flashed during the transition, so Blorp has it; it's just displaying the wrong content.

This is related to neither Piefed nor entirely the NSFW blurring setting. I've tried a Lemmy account (midwest.social) which does have NSFW blurring enabled, and the behavior is the same: thumbnails are blurred, which is correct, but only blurred content is shown.

The content in this video is SFW - the NSFW part is text overlay putting Winney the Pooh content in a NSFW context. The unblurred content flashes by so fast the text is unreadable unless you freeze-frame it, so I figure out is safe to attach.

Android 15, Blorp v1.10.2.

recording_20260120_064556.mp4

[christianjuth]

@xxxserxxx I think I have a fix, but I have to do a bit more testing. If you wanna try the fix on web, you can use the below link:
https://fix-nsfw-blur.blorp-6rm.pages.dev/

[ztar473]

still a problem on link provided and Android app v1.10.2
it also doesn't default to unblurred (on feeds) when activated on account

[sworve]

Encountered this issue with a fresh install of the Android app after creating an account on a piefed instance that defaults new accounts to showing NSFW (the one that recently became popular.)

Steps:

1. Install blorp from Play Store.
2. Login to a fedinsfw account in blorp.
3. Change feed view to Local.

Posts will all be blurred and stay blurred. If you open a specific post, as if to comment, then tap the image, the image in that view will become unblurred, while the full image view that slides open and covers that page will be blurred and cannot be unblurred by tapping.

[christianjuth]

@sworve I'm just now starting to roll out v1.10.3, which I hope fixes this. Could you do me a favor and give it a quick test on web (https://blorpblorp.xyz)? Everything from v1.10.3 is already on web. If it's still broken on web, then I have more work to do.

[sworve]

@christianjuth Tried just now on the site, with Cards view. Tapping the 'NSFW' text in the blurred post area unblurs the post, but tapping the blur area itself either opens the post page or, if you're already on the post page, does nothing at all. So it partially works, though I'm not sure if having to tap the text specifically is intended behavior.

Also as @ztar473 said it doesn't default to not blurring if your account settings on the instance itself are set not to blur (blorpblorp itself does not seem to have any related options to this in either the profile or the app)

[Red-Squid]

App really needs a basic on-off toggle for blurring NSFW, set to ON by default.

This is a normal feature for apps and websites that may have NSFW or NSFL content. I personally ALWAYS turn them off, I NEVER need them. I just don't use services that can display such content when it could become an issue.

The off toggle was one of the first things I looked for while setting up the app for use. I was happy to see that NSFW blurring was being addressed in 1.10.3, but NSFW blurring in 1.10.4 still doesn't work well, despite there now being a button on the blur to view the content.

Please add an option to just toggle it OFF all together. While it not working, those of us who don't need it can just turn it off, and you can then perfect the blur function at your leisure, without further complaint from users.

[christianjuth]

@Red-Squid It sounds like you previously turned on NSFW content on your Lemmy or PieFed account (outside Blorp). Most of the issues with NSFW has been Blorp hiding that content too aggressively, not Blorp showing it when it's not supposed to. That said, I'll see if I can make turning it back off more intuitive.