# Spoiler on images doesn't effectively protect NSFW images

**URL:** https://meta.discourse.org/t/spoiler-on-images-doesnt-effectively-protect-nsfw-images/24009
**Category:** Feature
**Created:** [Janeiro 14, 2015, 7:46pm UTC](https://meta.discourse.org/t/spoiler-on-images-doesnt-effectively-protect-nsfw-images/24009 "2015-01-14T19:46:32Z")
**Posts on this page:** 12
**Page:** 1

<div class="post-metadata">

### Author: ![Robert\_Lee\_Louviere](https://avatars.discourse-cdn.com/v4/letter/r/ea666f/32.png) [@Robert\_Lee\_Louviere](https://meta.discourse.org/u/Robert_Lee_Louviere)
#### Post date: [Janeiro 14, 2015, 7:46pm UTC](https://meta.discourse.org/t/spoiler-on-images-doesnt-effectively-protect-nsfw-images/24009/1 "2015-01-14T19:46:32Z")

</div>

Someone used a spoiler tag to blur a fun, but NSFW image.

The problem is that the image loads and displays unblurred until the image fully loads.

This kind of defeats the purpose.

Can we either have a NSFW tag that hides before fully working? Or have the spoiler tag hide content completely until after it can apply the blur filter?

---

<div class="post-metadata">

### Author: ![Robert\_Lee\_Louviere](https://avatars.discourse-cdn.com/v4/letter/r/ea666f/32.png) [@Robert\_Lee\_Louviere](https://meta.discourse.org/u/Robert_Lee_Louviere)
#### Post date: [Janeiro 14, 2015, 7:55pm UTC](https://meta.discourse.org/t/spoiler-on-images-doesnt-effectively-protect-nsfw-images/24009/2 "2015-01-14T19:55:48Z")

</div>

Apparently, spoilers also don’t take effect when you click  
the icon to see the post being replied to, and I’m going to guess if it  
was quoted, expanding to see the full quote would have the same issue.

Yup, expanding a quote has the same issue.

---

<div class="post-metadata">

### Author: ![riking](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riking/32/170938_2.png) [@riking](https://meta.discourse.org/u/riking)
#### Post date: [Janeiro 14, 2015, 8:35pm UTC](https://meta.discourse.org/t/spoiler-on-images-doesnt-effectively-protect-nsfw-images/24009/3 "2015-01-14T20:35:32Z")

</div>

Fixing this will require a redesign/rethinking of the way that spoilering images works.

---

<div class="post-metadata">

### Author: ![Robert\_Lee\_Louviere](https://avatars.discourse-cdn.com/v4/letter/r/ea666f/32.png) [@Robert\_Lee\_Louviere](https://meta.discourse.org/u/Robert_Lee_Louviere)
#### Post date: [Janeiro 14, 2015, 9:01pm UTC](https://meta.discourse.org/t/spoiler-on-images-doesnt-effectively-protect-nsfw-images/24009/4 "2015-01-14T21:01:35Z")

</div>

Honestly large enough images with high dpi, will still be recognizable.

Just make them black.

Or aesthetically pleasing color tone that fits with the background tone.

---

<div class="post-metadata">

### Author: ![strager](https://avatars.discourse-cdn.com/v4/letter/s/e99b99/32.png) [@strager](https://meta.discourse.org/u/strager)
#### Post date: [Janeiro 14, 2015, 9:07pm UTC](https://meta.discourse.org/t/spoiler-on-images-doesnt-effectively-protect-nsfw-images/24009/5 "2015-01-14T21:07:58Z")

</div>

Couldn’t you simply div it invisible (actual display=“invisible” rather than “none” as invisible still loads the image) until the image is fully loaded and than change the visibility back on?

---

<div class="post-metadata">

### Author: ![riking](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riking/32/170938_2.png) [@riking](https://meta.discourse.org/u/riking)
#### Post date: [Janeiro 14, 2015, 10:42pm UTC](https://meta.discourse.org/t/spoiler-on-images-doesnt-effectively-protect-nsfw-images/24009/6 "2015-01-14T22:42:06Z")

</div>

Applying a full-black overlay in CSS seems more effective to prevent reflows.

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [Janeiro 14, 2015, 11:06pm UTC](https://meta.discourse.org/t/spoiler-on-images-doesnt-effectively-protect-nsfw-images/24009/7 "2015-01-14T23:06:25Z")

</div>

First, I suggest suspending the user if this is unwanted.

You should be able to override the css to make the images black if this is a regular thing on your site.

---

<div class="post-metadata">

### Author: ![Robert\_Lee\_Louviere](https://avatars.discourse-cdn.com/v4/letter/r/ea666f/32.png) [@Robert\_Lee\_Louviere](https://meta.discourse.org/u/Robert_Lee_Louviere)
#### Post date: [Janeiro 15, 2015, 2:25pm UTC](https://meta.discourse.org/t/spoiler-on-images-doesnt-effectively-protect-nsfw-images/24009/8 "2015-01-15T14:25:27Z")

</div>

I appreciate that thought, but this affects all images.

Imagine if the spoiler image was just a screenshot of an actual spoiler in a game or story.

At 85% scanline loaded, you can pretty much see the picture, and it doesn’t blur until fully loaded.

Thus the whole purpose is rendered ineffective.

Also, replies (the expand to show back and forward) don’t use the spoiler effect at all.

This is a bug that needs to be fixed, regardless of the content that this specific post contains.

---

<div class="post-metadata">

### Author: ![chapel](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chapel/32/122414_2.png) [@chapel](https://meta.discourse.org/u/chapel)
#### Post date: [Janeiro 15, 2015, 2:38pm UTC](https://meta.discourse.org/t/spoiler-on-images-doesnt-effectively-protect-nsfw-images/24009/9 "2015-01-15T14:38:18Z")

</div>

I think spoiler images shouldn’t even be loaded and instead they should have a placeholder which can be clicked to load.

This would be important for actual nsfw images as even if we make them harder to see or blocked entirely the image is still downloaded and if you’re at work it could be tracked on the network.

---

<div class="post-metadata">

### Author: ![Overmind](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/overmind/32/55446_2.png) [@Overmind](https://meta.discourse.org/u/Overmind)
#### Post date: [Janeiro 15, 2015, 2:39pm UTC](https://meta.discourse.org/t/spoiler-on-images-doesnt-effectively-protect-nsfw-images/24009/10 "2015-01-15T14:39:58Z")

</div>

I think spoilers would be more effective if they just hid the image right away and you have to click on the spoiler to view it.

Here is an example:

Text you type:

```
[sp]Testing this for Discourse.org[/sp]

[spoiler=Click Me For Secret]
Test.
[/spoiler]

```

Result:

![](https://global.discourse-cdn.com/meta/original/4X/1/6/9/16911138e2b2780b2d03fbaaac417cb3cc1bddfb.png)  
then:

 ![](https://global.discourse-cdn.com/meta/original/4X/6/4/0/640c623fbdaed6c5169a63d15f7b456086c8a347.png)

---

<div class="post-metadata">

### Author: ![Robert\_Lee\_Louviere](https://avatars.discourse-cdn.com/v4/letter/r/ea666f/32.png) [@Robert\_Lee\_Louviere](https://meta.discourse.org/u/Robert_Lee_Louviere)
#### Post date: [Janeiro 15, 2015, 4:57pm UTC](https://meta.discourse.org/t/spoiler-on-images-doesnt-effectively-protect-nsfw-images/24009/11 "2015-01-15T16:57:22Z")

</div>

I would agree with this one.

Ideally, spoiler images should blur immediately, but a separate NSFW tag for images should act differently and not even load until clicked, possibly with a confirm box.

---

<div class="post-metadata">

### Author: ![lentower](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lentower/32/178287_2.png) [@lentower](https://meta.discourse.org/u/lentower)
#### Post date: [Maio 24, 2022, 5:48pm UTC](https://meta.discourse.org/t/spoiler-on-images-doesnt-effectively-protect-nsfw-images/24009/12 "2022-05-24T17:48:21Z")

</div>

Eu aconselhei um usuário a usar

```plaintext
Ocultar detalhes

```
