+2
Completed

Vetting for flagged submissions

Alioth Fox 4 years ago updated by Varka (Spokesdragon) 4 years ago 2

I like how reporting submissions for policy violations is so easy. I've been on other furry sites where opening a trouble ticket and getting someone to actually look at it is like pulling teeth. However, I think Furry Network's system goes a little too far in the opposite direction.

I'm not keen on the idea that flagging a submission automatically sends a ticket to the user who uploaded it; that, to me, just seems far too easy to abuse. For instance, I had a piece that was flagged for needing to be marked as "adult" - now, in my mind, the piece in question was not adult in nature; the upload process describes adult art as "nudity, sexually explicit, or suggestive," and this piece was none of those three things. There are plenty of examples of this - vore or babyfur, for instance; both of those genres can have art that isn't remotely sex-related or gory (the two general prerequisites for pieces to be marked "adult"). The exact nature, whether it WAS mature or not, etc. can be debated, but that's not the larger point here. The main point is that I received a ticket literally within seconds of uploading the submission.


If you're trying to build a "welcoming and open" community, it's not a good start to make it easy for users who don't know how to use the tag filtering system to just flag submissions willy-nilly because they don't like what they see. And I realize that no flag is acted upon until it is reviewed by moderators, but sending tickets straight to users is kind of the opposite extreme. It opens the door to superfluous flags by the bucketload. A more sensible way to do it would be that flagged submissions go to moderators first. If the moderators decide that the flag is potentially actionable, then it should go to the flagged user, who should be given an opportunity to take action or dispute the flag.

Answer

Answer
Completed

Flags weren't supposed to notify the user whose work is being flagged - we fixed this bug, so now you won't get notified until an admin takes a look at it and confirms that it's a valid issue.


Hopefully this should help alleviate some of the stress and uncertainty involved in having your work flagged - as only valid issues will make it past the moderation team!


More info here:


https://blog.furrynetwork.com/2016/06/07/site-update-june-6-2016/

I didn't know the flags went straight to user actually, but I think this is a good thing: This way the user can fix their lack of tags or wrong category before moderators come and spite you for it. Everything becomes more speedy like this and honestly there's nothing to be ashamed of if you're a new user and didn't know how to tag something right. This way the community as whole can ensure things are in right categories and tags so experience on site is positive.


Although I think it should be mentioned to the flagger that it goes straight to the uploader (does it go anonymously for example?) I've flagged several works but this hasn't been informed anywhere.


The faster people can flag wrongly tagged and categorized pieces the more pleasant the fresh tab is to view for general audience. We currently suffer from people not tagging their fetish works (defeating the point of blacklists) and not marking fetish material as adult even if it's not sex related because people don't realize vore, inflation, diaperfur etc. are fetish material that people who view the site as SFW don't want to see.


Quotes from Acceptable Upload policy:
No fetish artwork under General

All Fetish artwork or photographs count as Mature as well

Answer
Completed

Flags weren't supposed to notify the user whose work is being flagged - we fixed this bug, so now you won't get notified until an admin takes a look at it and confirms that it's a valid issue.


Hopefully this should help alleviate some of the stress and uncertainty involved in having your work flagged - as only valid issues will make it past the moderation team!


More info here:


https://blog.furrynetwork.com/2016/06/07/site-update-june-6-2016/