Meine Soup

After three attempts to implement this feature, we’re finally there. You can now choose to (not) see NSFW (“not safe for work”) content by clicking on the button in the top bar.

On the flip side, you can now also set your whole soup or individual imports and posts to be NSFW.

Please refer to the @didyouknow entries on how this works in detail:

• You need to mark your "adult" content as such
• You can choose (not) to see “adult” material
• Got reported? You can get back on /everyone with just one click
• Only when you’re logged in you’ll be able to see “adult” content on /everyone
• If you mark a post as "NSFW", it will not be exported to facebook

Please note: we’re not interested in making adult content invisible or pester you with silly “age verifications”. The switch to see adult material is in a prominent place, and we make it very clear what you’re currently seeing when surfing Soup. This feature has purely practical reasons: the mobile apps depend on it, users often want to visit Soup in a family/work environment but can’t, and when we try to think about anything that has to do with NSFW content that could finance Soup (such as e.g. ads) we simply need to be able to categorise undesirable material so as to not abandon either the idea or our content policy prematurely.

As you may experience, we implemented this in a human-driven way: there are no bots that deactivate your account, just other users and us. And if your blog is hit with the NSFW status, you can disable it again yourself.

Up until now, we silently disabled blogs with even just one adult picture or text for display on /everyone. From now on, as long as you don’t forget to mark your NSFW material, your blog posts can and will be displayed to non-logged in visitors on /everyone again - and even the rest of it to logged in visitors if they chose to see NSFW content :)

TLDR; if you see adult content anywhere it shouldn’t be, report it via the flag icon (next to repost) and be sure to mark your own material when you create it.

As always, criticism and feedback is welcome. Just reply to this post.

And if you're interested in what we're cooking up next, members of @testkitchen see features long before (but also get hit by bugs harder than) the rest.