"Hidden until clicked" or "click to view" for NSFW Posts



  • The mods don't seem too concerned about NSFW posts around here. I have no problem with nudity, but there's a time and a place.

    And some people just don't want to see it -- for any number of reasons.

    I've messaged the mods about NSFW posts, flagged NSFW posts for review -- nothing. No result. No reply.

    So can I please suggest that the forum implements a "hidden until clicked" feature for posts with nudity?

    Other forums have this. It surprises me that this one doesn't.

    Given that some of the nudity here is arguably in the erotica category (a naked woman on a beach rubbing suntan oil into the buttocks and breasts of another naked woman) ...

    IMAGE AT LINK IS NSFW: https://forum.smithmicro.com/uploads/files/1473019408794-summer-16-01.jpg
    IMAGE AT LINK IS NSFW: https://forum.smithmicro.com/uploads/files/1473350240053-summer-16-01-b.jpg
    IMAGE AT LINK IS NSFW: https://forum.smithmicro.com/uploads/files/1473019431658-summer-16-02.jpg

    ...wouldn't it make sense to make the option of "click to view" available?

    Yes, the entire thread where these pics are eventually got "NSFW" added to the title. Great.

    But if another thread that isn't dedicated to this subject has NSFW material posted in it, it makes that whole thread suddenly NSFW because there's no warning and no choice involved.

    Give forum users some choice, folks.

    Please implement a "click to view" or "hidden until clicked" option.

    Thanks.

    ==========

    • Rules of Conduct. While using the Site you will comply with all applicable laws, rules and regulations. In addition, we expect users of the Site to respect the rights and dignity of others. Your use of the Site is conditioned on your compliance with the rules of conduct set forth in this section; any failure to comply may also result in termination of your access to the Site pursuant to Section 20 below. You agree that you will not:
    • Post, transmit, or otherwise make available, through or in connection with the Site:
      Anything that is or may be... (d) obscene, indecent, pornographic or otherwise objectionable
    • Any unacceptable images including depictions of rape, torture, and sexual, lewd or illegal acts.


  • We are actively looking for a proper solution to this.
    This forum is based on NodeBB platform. I haven't been able to find any useful plugin or a solution to handle NSFW images. Anything working out of the box would speed things up greatly, as it looks to me that R&D required is substantial, so it would take some time to implement such feature.
    We'll keep you updated on the progress.



  • @admin Thanks, I appreciate the reply.

    Too bad that it'll take extensive work to implement something like this. Surprising. It is what it is, I guess.

    I know a lot of the members here like erotic/porn renders -- whatever; it's not the issue. But I had assumed since this is the "Poser community"(and the "Official Poser Forum") with a fairly diverse demographic that people would show a little more discretion and regard for other members of the community. Poor assumption on my part.

    Good luck with any solutions out there.



  • @James_in_3D I had the same feeling. In fact, I don't think I ever posted any nudes to the Reno forum either even though my gallery there has some ( and those were there because I was not getting any response to non-nudes LOL)



  • Alas poor renders ! Culminating point of countless hours of work tweaking morphs and bending limbs without breaking them, in order to bring "customers" a quality free-for-nothing pose set . Only to be singled out by some people who don't wan't to be caught viewing said renders at the wrong place, at the wrong time and with the wrong witnesses.

    Yet there is no more reason for concern, people. To save your eyes and your job the provider of this disturbing imagery has decided to ditch another projected pose set named "car wash" which would certainly have contained more such imagery.

    Get the infamous pose set here before it's too late :

    http://www.sharecg.com/v/86036/browse/11/Poser/MIKI-2-ROXIE-beach-poses-2016



  • @DarthJ A member of the Official Poser Forum posted NSFW erotica in an open thread without an adequate mechanism in the forum to permit warning or choice for others, because no such mechanism currently exists.

    This is the issue.



  • @DarthJ said in "Hidden until clicked" or "click to view" for NSFW Posts:

    Alas poor renders ! Culminating point of countless hours of work tweaking morphs and bending limbs without breaking them, in order to bring "customers" a quality free-for-nothing pose set . Only to be singled out by some people who don't wan't to be caught viewing said renders at the wrong place, at the wrong time and with the wrong witnesses.

    For all the complaints I see here (this forum) and other forums about having barely clad woman pop up without warning, I'd say that "some people" could easily equate to "a lot of people". And it's not to say people never want to see that. I'm a woman. I have no issue seeing other woman. But my developmentally challenged son has some issues. I'd rather have warning so I can choose to view those threads when he's not around. But you would rather use the sex sells mantra than think about those of us who have genuine issues.



  • Half a year ago @nerd3d said in The Infamous Darth J Freebie Thread (NSFW):

    For the time we'll ask you to keep it PG13. We want to add features to handle that better. Lots of stuff we want to add ...

    Good to see this issue brought to the table again and being worked on.
    A NSFW option per image would facilitate publishing images. On a number of occasions I refrained from publishing because of an occasional nipple being visible. The interpretation of what a child of 13 years of age may be upset about and needs parental guidance with will depend on the culture one lives in.



  • @admin said in "Hidden until clicked" or "click to view" for NSFW Posts:

    We are actively looking for a proper solution to this...

    A possible quick-fix:

    https://www.npmjs.com/package/nodebb-plugin-tagstitle

    A plugin that allows for special thread tags, like nsfw, etc.

    https://github.com/psychobunny/nodebb-plugin-spoilers

    A plugin that allows embedded spoiler text. (May be workable for images, you'll have to codemonkey through it to see.)

    Basically, establish a forum rule that threads with NSFW images must be tagged as such and that any NSFW image must be "spoilered", hiding the image unless the user clicks on the spoiler tag to reveal the spoiler. I'm no coder, so I don't know if images get displayed if they're in spoiler tags, but you may be able to figure out if it's a workable solution as a quick-fix until you can come up with something more efficient.

    Note: As this forum primarily revolves around "art", attempting to police what is considered as "acceptable nudity" is fraught with problems regarding various non-local standards if you take any official stance at all. That being said, the most broad interpretation of "unacceptable nudity/sex/violence/taboos" should be adopted in order to avoid controversy/screams/riots/singleton-malcontents. Of course, it's all your call. Enjoy the drama! :)



  • @morkonan , thanks for the research done!!!

    Unfortunately, neither of these plugins seem to be a "proper" plugin.

    https://www.npmjs.com/package/nodebb-plugin-tagstitle

    I'm a bit reserved on this one. Documentation is only in Spanish, parts of code are in Spanish, multiple hardcoded values in Spanish....not to mention code comments. Even if we were happy with the end effect of this plugin, in order to use it we'd need to write a proper configurable plugin without, preferably without hardcoded values and in English.

    https://github.com/psychobunny/nodebb-plugin-spoilers

    Tried it, it doesn't seem to work :<
    There's also a complaint about it messing with email notifications.



  • @admin

    Yeah, sorry about the Spanish issue. I looked around, but it seems there's quite an interest in the nodebb in the Spanish market... which didn't help me any, since I'm A Stoopid American ™ who only understands American English and $... :) (I did successfully make a bowl of oatmeal last night without having to read the instructions, though.)

    Wish I could help more betterer. I'm sure someone, somewhere, will figure it out. The trouble with all these different forum/social-network platforms is that everyone's trying to chase after them and get them to market, but development and lifetime seems to suffer. Then, there's the manager who falls in love with one because it "looks neat" and mandates it, no matter what the web developer has to say on the issue...

    If you're stuck with nodebb, good luck. If not, well... there maybe a few meetings to schedule. :)



  • @morkonan

    https://github.com/psychobunny/nodebb-plugin-spoilers

    I've managed to achieve the same effect using:
    https://github.com/NicolasSiver/nodebb-plugin-ns-embed
    *tech-note: it is a simple regular-expression based string replace mechanism....it is a beauty :)

    I can't say I have much experience using forums. Can anyone point me to a common solution, used on any forum platform, to flag a block of content as nsfw?
    like
    !nsfw....someTextGoesHere.....nsfw!



  • @admin said ..

    I can't say I have much experience using forums. Can anyone point me to a common solution, used on any forum platform, to flag a block of content as nsfw?
    like
    !nsfw....someTextGoesHere.....nsfw!

    Do you mean the command string or just a visible example? For the former, I'd have to hit my keyboard with a hammer and hope for the best.. (ie: I dunno...)

    For the latter, most casual forums handle the issue by "NSFW" being tagged by the user and present in the thread title. (ie: NSFW "Watermelon accident") Threads that are not labeled as NSFW wouldn't generally have NSFW posts and, if an On-Topic NSFW image was posted in a non-labled thread, that thread's title might be edited by the creator or an admin to reflect that.

    But, that's for threads. For individual posts, in my experience, that would only be occasionally encountered by users, embedded NSFW pictures would have a "click to reveal" operator like a spoiler tag. (Generally easily done, I would think, and requires no serious recoding/admin intervention or cookie schemes) In some forums, NSFW picture urls can be shown as hyperlinks, pasted by the poster, to off-site sources, as long as they're labeled as such by the poster, in the body of the post, so individual users can decide for themselves if they wish to view them by clicking an off-site link. (For user-created images, imagehosts are often used for such things. This is a "rules created" sort of protection, not automatic/software dependent.)

    Some forums dedicate a subforum for NSFW posts and lock those subforums based on user status/age/membership/etc or simply rely on the user's choice whether or not to view threads in that forum, for themselves. However, that is likely only for large social forums and a business/commercial forum should never, ever, dedicate that much effort to such things. (Not unless it was in such an industry, at any rate.)

    Some forums/social-media sites hide NSFW or "18+/Adult" images according to selections made by the individual user in their account management options and their session cookie will reflect this. (ie: "Do you wish to be able to view "Adult/18+" content with this account? Yes/No") Images tagged NSFW by posters and tracked by forum software that belong in this category would simply not be displayed and only a "parking/null" image would be revealed to members that didn't have the positive attribute present in their session cookie. This last example is generally considered to be the best choice if the forum software is capable of parsing image posts tagged in this way by posters/admins. It is seamless to users and requires only one user-selection to be made/edited in their membership account. It does, however, rely on uploaders tagging their content and/or admins policing it. (IIRC, Renderosity or DAZ use this system as well as Deviantart.)

    Lastly, generally with art/image forums with large/many such subforums that are "open" to members/nonmembers, forums will include a special disclaimer/age-verification cookie that must be present in order for adult/NSFW images to be displayed. A dialogue popup will ask for verification and birthdate before the image will be displayed and, once acceptable ranges are entered, the cookie will allow display of such images, otherwise only a placeholder image and/or another verification popup will be displayed. This is generally only for sites that dedicate whole webpages for large images and has areas that do not require logins. (ie: Like Deviantart, which does this for non-logged-in users. Otherwise, the selection is made in the user's account window and the user's session cookie will automatically have this attribute, as described above.)

    Note: IMO, you want adequate protections for people's sensibilities with the least obvious impact/visibility. For that reason, either a rules-based, poster-selected, spoilered system for NSFW images or a cookie-selection/image-tag system (If software can handle that with account management/login features.) would probably be the better choice. A spoiler-hidden image post may also have the side-effect benefit of not requiring the so-spoilered NSFW image to be loaded in the first place, speeding up loading/diminishing bandwidth issues for those who don't desire to see such images. (I haven't looked to see if SM actually hosts embedded images. If it does, then you have further issues to consider and may need more protections.)

    For similar sites, subreddits (From "reddit") might hold some clues as images that are NSFW are usually tagged as such and some subreddits may require a disclaimer/popup, IIRC. However, images are not necessarily previewed/thumbnailed and it appears as if this forum software prefers to auto-display/thumbnail/resize embedded images. Other sites like Renderosity/DAZ have forums in addition to their galleries that could host such images, though I think both are fairly strict when it comes to pornographic images (not allowed). Deviantart dedicates entire pages to individual images, but its cookie and account system might be of interest.

    PS - I'll not hog the thread and will let others get a chance to respond for awhile. :)



  • @morkonan
    I need to say first: thank you for this detailed answer!!!

    Do you mean the command string or just a visible example?

    Command string, but an example of any common solution is also helpful.

    In some forums, NSFW picture urls can be shown as hyperlinks, pasted by the poster, to off-site sources, as long as they're labeled as such by the poster, in the body of the post, so individual users can decide for themselves if they wish to view them by clicking an off-site link. (For user-created images, imagehosts are often used for such things. This is a "rules created" sort of protection, not automatic/software dependent.)

    This would be the most simple solution. All NSFW content would be hosted somewhere else and shared using a hyperlink.



  • I found one rather flexible plugin....but, as expected, it also seems to be broken in latest releases :<
    https://github.com/NicolasSiver/nodebb-plugin-ns-spoiler
    If if find time, I may try to fix it.

    PS: though, I need to be careful with this one, as all this flexibility leads into complexity which broke this plugin multiple times already...also, some users reported it eating-up all CPU resources or even taking down the forum app completely.



  • and @morkonan, thanks again for all the options explained.
    We can take many paths from here, ranging from cookie warning, special NSFW tags, NSFW titles, user panel global NSFW settings, NSFW post flags, etc....I'm open to any idea, though I'd prefer not to go for multiple paths but pick the one that gets the job done good enough.

    My opinion is, content-block spoilers-like plugin seems to be a quite flexible solution and at the same time requires the least amount of modifications on app side.
    If there is a general agreement that this will do, I can try to fix nodebb-plugin-ns-spoiler plugin or write a more simple one.

    Reminder: nodebb-plugin-ns-spoiler plugin functionality is inspired by commontalk forum topic:
    https://talk.commonmark.org/t/what-could-a-spoiler-tag-extension-look-like/767
    You can see a demo of it in following video:



  • This plugin still has various issues with loading images and embeded content.



  • To be honest I think that all this is a waste of effort and money. Just make the rules clear that there should not be nude images here and give warnings to those who offend. After the third warning delete the account and bar the user. I'll say this again, I'm not a prude and love seeing the T&A WHEN I WANT TO, but don't need it shoved down my throat by some 13-year-old.



  • @ghostship said in "Hidden until clicked" or "click to view" for NSFW Posts:

    To be honest I think that all this is a waste of effort and money. Just make the rules clear that there should not be nude images here and give warnings to those who offend. After the third warning delete the account and bar the user. I'll say this again, I'm not a prude and love seeing the T&A WHEN I WANT TO, but don't need it shoved down my throat by some 13-year-old.

    I agree with you.

    This "snipe hunt" for a solution via coding is a waste of time and resources and obfuscates the main issue. Respect.

    T&A isn't even the main issue.

    There's a time and a place for T&A, PG13 or R or X.

    A general population forum isn't the place.

    If admin can't code a solution then admin has got to do what Ghostship suggests and do things the old-fashioned way until grown men are capable of not acting like 13 year olds.



  • @James_in_3D said in "Hidden until clicked" or "click to view" for NSFW Posts:
    I've created a plugin for this purpose. It is still in experimental phase and is far from perfect, but tell me if it generally meets your expectations.

    click to show

    click to show

    Edit: an eye icon should be there on creating/editing posts