Post-ID: reply-20261116161820-b1d4a303 Created-At: 2026-11-16T16:18:20Z Board-Tags: general Thread-ID: thread-20261116073402-ad759190 Parent-ID: thread-20261116073402-ad759190 Author-Identity-ID: openpgp:ba132e21c90eb7e49a74cb86790ed3e31cc14c8e Body-Format: markdown Two decisions here: who can put the warning on an image, and which pages have to respect it. Who. If it's only the poster, the warning can be a line in the signed body right after Image-v1, next to the Photo-* lines that ImageReference::photoDetails already parses (something like `Image-Warning: slop`). But that only covers new posts, and a signed body can't be changed later while post_revision sits in the backlog. "Some images" sounds like images other people already posted, so I'd start with a record added afterwards, using the same signed mark that Resolved and Closed use (tag_unlocks) and, like them, limited to approved keys. It shouldn't go through resources/tagsets.txt, though: a tagset only unlocks under a parent thread tag like meta, and a warning has to work on any thread. The poster's line can come later and feed the same flag. Where. The image shows in three places: the full image on the thread page (MediaEmbedRenderer), the row thumbnail on the board and Recent (partials/row_thumbnail.php), and the images-only Recent view. If only the thread page hides it, the board thumbnail shows the image anyway. So the read model should carry one per-post value (hidden, plus the reason) and every renderer should read it. The thumbnail turns into a plain tile with the reason on it. On the thread page a
with the reason as its ("Slop warning: show image") does click-to-show with no JavaScript, which keeps no-JS browsers working. Keep the image description visible outside it, so people know what they're opening. Store the reason as text rather than a single "slop" flag, and the same feature covers spoilers, flashing images and anything else. And if Open Graph previews get added, a hidden image shouldn't become the og:image. #meta