Add functionality to flag topics and replies NSFW

[netweb]

WordPress usage is pretty diverse, occasionally support topics and follow up replies can contain NSFW links to the site to aid in troubleshooting.

​The policy on NSFW: ... references to adult content that have not been highlighted as NSFW.

Via Slack discussion ​https://wordpress.slack.com/archives/forums/p1473447594003545

ipstenu [4:59 AM] Maybe someone should open a ticket and suggest we have a moderator way to flag a post NSFW which will change the subject (maybe the URL) and somehow alert folks at the top?

Related: User actions:

• "Flag Author" does not change their bbPress role, they retain the "Participant" role when flagged in this scenario
• "Spam Author"(#1960) will change the users role to "Blocked" and mark all the users topics and replies as spam.
• "Block Author"(#1989) only changes the user role to "Blocked" and not change the status of any topics or replies

[SergeyBiryukov]

Related: #2401

[netweb]

Maybe something along the lines of the recent "Resolved" changes, an icon representing NSFW added to topics see 2018-meta-01.png​ and topic views along with a similar action to the "mark as resolved" and "mark as not a support question" we add "mark as nsfw" see 2018-meta-02.png​

[netweb]

Related: we should investigate doing similar for "Not a support question" at the same time

[Clorith]

I think the simpler, and more user friendly, solution here would be a checkbox "My site or content may be considered Not Safe for Work (NSFW)", kept as postmeta.

If ticked, prefix the post title with [NSFW] (ideally also with the abbr markup so we can write it out in full for those who are unfamiliar with the term).

[valentinbora]

@denisco thanks for the patch. It looks like it contains extraneous diff hunks that don't actually change anything in the code.

It might be due to CR/LF line endings or tabs vs. spaces, so I'd like to encourage you to check that out and redo the patch with only the relevant code changes included.

[denisco]

@valentinbora thank you for the reply.

I uploaded a new patch (2018-2.patch).

[denisco]

About 2018-3.patch: I found ticket #2862, so I converted my code to part of the Support Forums plugin instead of a separate plugin.

[Clorith]

#5167 was marked as a duplicate.

[Clorith]

Completely missed this ticket, despite having commented on it, so I've closed the new on in favor of this existing one.

2018.2.patch​ takes the ideas already covered here of providing a checkbox and prefixing titles, and adds on an administrator interface (taxonomy) to define terms used for mature content that will auto-mark topics as well, since users may forget to do so more often than not, or what's considered mature may differ based on personal views.

The term management is limited to forum key masters, and is per-forum, this allows rosetta sites to add their own local words, instead of us needing to maintain a list that's cumbersome to update.

moderators are also able to post or edit topics that may otherwise have been picked up as NSFW without the automatic checks running, this is to allow them to handle individual false-positive cases without needing to mess with the term list in the backend.

It also makes sure that the robots tag is added for such posts, as we're currently struggling with search engines incorrectly viewing us in part as an adult content provider due to certain keywords ranking highly on our site.

[dd32]

In 9802:

Support Forums: Add the ability to flag topics as NSFW.

This supports both a checkbox, and for matching on a phrase within the title/url/tags.

Props Clorith, denisco.
Fixes #2018.

[dd32]

In 9817:

Support Forums: NSFW: Dont' output the <abbr> in the <title> tag.

See #2018.
Fixes #5194.