If you go to a profile on mastodon.social (for example, mine Greg - Mastodon - warning, there’s currently a foodpost on my profile) and there’s a post with a sensitive image recently posted on the profile, or you view a post with a sensitive image by going to e.g. Greg: “AWOOOOOOO” - Mastodon (don’t worry, that post doesn’t actually contain a sensitive image) the image will display without warning the user. This doesn’t appear to be the case on all instances (for example,
awoo.space and oulipo.social seem unaffected) so I’m assuming this is a bug in the current version running on .social, but, maybe some other instance is having this problem too. The content warnings, at least, seem to appear properly in my timeline, and hopefully everyone else’s.
To reproduce, just post an image (that hopefully isn’t actually sensitive) and mark it as sensitive on mastodon.social, or on another instance running the same version.
Update: now that awoo.space is on 1.6.1 this bug is showing up there too. You can see this in action on both my GeorgeAWOOOGreg - Awoo.space and Crom’s (the admin) profiles. Crom, Kobold King - Awoo.space (His second pinned post has a picture that should be hidden.) It looks like this is a bug in this version of Mastodon, and not at all specific to .social.