- monthly subscription or
- one time payment
- cancelable any time
"Tell the chef, the beer is on me."
So, please bear with me, this is not witchcraft, I know it looks intimidating, but just go through it step by step, you can't break anything. If you get stuck, just reload the page and everything will be as it was. Close the Element Inspector with the X in its top right corner.
Also it's obviously very ramshackly.
<ul class="reaction_to">element, and above see that this element encompasses the conversation up to the point of the post of which we're on the page.
<div class="meta">element and the text of the post in the
<div class="content">element. Now in order for the Soup CSS to apply to this HTML (=markup) even after we've ripped it out of this page and put it in our reaction, we need to preserve the whole tree of elements that encompasses these two. The parent node that both have in common is the one that starts with
<div id="post601784690" .... If we look closely, we can see that another element is contained in this node, the
<ul class="actionbar">, which provides the Repost and React to widgets. This we also don't want to quote, so we delete it too.
<div id="post601...element in the Inspector, and choose Copy Outer HTML. (There's still some stuff in there we don't need, but it shouldn't hurt.)
<blockquote>, paste our prepared markup, and write
<blockquote> [HUGE BLOCK OF CODE WE COPIED FROM SOUP] </blockquote> [OUR REACTION]
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:
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 set your soups NSFW status, 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.
"Tell the chef, the beer is on me."
"Basically the price of a night on the town!"
"I'd love to help kickstart continued development! And 0 EUR/month really does make fiscal sense too... maybe I'll even get a shirt?" (there will be limited edition shirts for two and other goodies for each supporter as soon as we sold the 200)