Implement dis button for disqualifying/respecting posts

[GoogleCodeExporter]

Several users are demanding that we implement "the dis button".

No one has specified this feature in detail so I created this bug to track
& document this new feature.

My impression is that users want this feature in order to disqualify
certain posts.  

Some questions:

1) Should everyone have the ability to press dis button?
2) Should editors have a more powerful dis button for moderating?
3) Should non-controversial but otherwise average or bad posts be taken out
of the site if it receives enough dis's?
4) Should it be possible to attach a comment along with a DIS press?

My personal opinion for the above questions would be:

1) Yes
2) No
3) Yes
4) Yes ("saw this here just 2 weeks ago, dupe!", "against our unwritten
posting policy")

I'm quite sure that this feature will require some fine-tuning after roll
out, so perhaps it's better if we just go ahead and implement something
simple at first.

My suggestion would be to just have a threshold of N dis's and any post
that has N or more dis's would be set to unpublished mode (no need to
delete, I guess?).

Dis feedback has to go back to the author who posted the dis post.  How
else are they gonna learn to improve their posts? :)

Dis'd posts might make interesting material for our galas..

Setting priority to high as there seems to be a lot of demand for this feature.

Original issue reported on code.google.com by jjhel...@gmail.com on 26 Apr 2008 at 2:38

[GoogleCodeExporter]

See comments at:

http://www.saasta.fi/saasta/?p=3122

Good ideas & background for this feature.

Original comment by jjhel...@gmail.com on 27 Apr 2008 at 8:49

[GoogleCodeExporter]

Good ideas yeah but I'm not sure how "easy" they are to pull off.

Original comment by mikko.ur...@gmail.com on 12 Aug 2008 at 7:38

[GoogleCodeExporter]

Yeah I agree.  I gave this some thought while the discussion was still 
on-going.  I
couldn't figure out any "easy" ways to do that, even just implementing the 
"hidden
queue" for registered members.

The only way you could make posts invisible from non-registered readers was to 
make
them password protected.  This is clearly not what we want.

If there's no support for this in WordPress, implementing it ourselves would 
break so
many things.  For example, we'd need to ensure those hidden pages don't show up 
on
any tag searches, full text searches, don't end up in RSS feeds etc.  How would
saasta subscribers see those posts in their RSS's, etc..

I'm leaning in the direction of WontFixing this feature.  Spending a lot of 
time on
this feature for only dubious gains would not be the best use of our resoures 
(which
are always spread thin).

Original comment by jjhel...@gmail.com on 12 Aug 2008 at 7:58

[GoogleCodeExporter]

Actually, what if:

1) we add a dis button that works just like "add fave" (also shows # of disses 
etc)
2) whenever a post gets more than N disses, all editors/managers/ceos get 
notified that this might now be 
unworthy saasta
3) any editor can then delete/unpublish the saasta if he/she deems it rubbish 
as well

Original comment by mikko.ur...@gmail.com on 13 Aug 2008 at 6:05

[GoogleCodeExporter]

Tru dat but I wonder if the same couldn't be accomplished with the existing
technology and a few e-mails saying this post is junk.  As I understood the 
general
consensus of our users, we should only delete offensive posts (as opposed to
generally acceptable but poor quality posts).  I haven't seen too many offensive
posts lately and I believe we're at the moment capable of dealing with 
individual
offensive posts.

One of the ideas proposed in the discussion that ensued from post
http://www.saasta.fi/saasta/?p=3122 was that we could quarantine "too 
controversial"
posts into a "subscribers only" queue that would not be publicly visible.  This 
way
the general public would not be offended with such posts but our subscribers 
would
still get a chance to see them.

However, it may well be that such a "controversial queue" might encourage 
people to
post more offensive material as they could lower their own standards knowing 
that
their questionable material would be dealt with by others moderating the site.

Be that as it may be, implementing this queue would be a lot of work.

Original comment by jjhel...@gmail.com on 13 Aug 2008 at 8:14

[GoogleCodeExporter]

Agreed. We could, for example, just instruct people to use the feedback form to 
bitch on posts they find 
inappropriate.

Original comment by mikko.ur...@gmail.com on 14 Aug 2008 at 3:47

[GoogleCodeExporter]

Won't fixing.

Original comment by jjhel...@gmail.com on 14 Aug 2008 at 6:58

• Changed state: WontFix