Feature Request: If article seen as spam, tell user why

[GoogleCodeExporter]

In relation to issue 41, my post was concidered spam. should the member 
not see why this was concidered spam?

Original issue reported on code.google.com by lsmart...@gmail.com on 18 Aug 2007 at 6:00

[GoogleCodeExporter]

I'd like for a moderator to be able to select a canned reason or write a custom 
one.
Canned responses will include:

 * Post was off-topic
 * Blogspam
 * Foreign Language

Original comment by gavinjo...@gmail.com on 24 Aug 2007 at 9:50

• Added labels: Component-Logic, Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Where would the response be shown at? Once it's delete, you just see a Missing 
Story
page when accessing the story page.

Original comment by james.e....@gmail.com on 3 Oct 2007 at 1:21

[GoogleCodeExporter]

The message could be contained in the email sent to the user.

The story itself is not deleted, it is just marked as spam. We could show it to 
the
submitter and mods, but make it clear that it has been marked as spam and is not
visible to other users.

Original comment by gavinjo...@gmail.com on 3 Oct 2007 at 7:07

[GoogleCodeExporter]

Could also shout on the user's profile.

Original comment by yesthatm...@gmail.com on 3 Dec 2007 at 7:26

[GoogleCodeExporter]

What about an IsSpam page that mods can look at?  I just implemented a way to 
hide
the div of the spam/delete and would like to implement a dropdown like digg 
uses for
the function bury.  In thinking of that all js files should be truncated to 
delete
whitespace for new installs - not good for us devs but good for deploy.

In saving the db, should it track 3-4etc separate fields for Inaccurate / Spam /
Duplicate / Ok this is lame? or should it simply add a Bury count and the last 
one
past the cap sends it out as an email?  I think to compete with digg it needs to
store all 4/# - you'll notice stories buried like one I dealt with a few days 
ago
being inaccurate and stated as such before you can digg it still reachable.  
Report
as Spam and Delete can also be options of this "bury" dropdown.

"Warning: The Content in this Article May be Inaccurate"  Or spam, or lame, etc.
before it hits the deleted point.  Actually I don't think they delete these 
unless
it's really bad.  I can still see the inaccurate post.

http://digg.com/security/Facebook_Voter_Registration_App_Asks_for_SSN_w_o_SSL?t=
11810434#c11814589

I'm working on integrating facebook, don't ask.

Original comment by DustinBr...@gmail.com on 9 Jan 2008 at 6:36