|
I would only be concerned if you get a number of abuse reports. I think you have to remember there are probably a lot of newbies experimenting on how the site works.
Hang on.. I've just spotted a red flag, I wonder what happens when I click it.. Oops wheres the undo button!
modified 8-Apr-15 17:04pm.
|
|
|
|
|
RossMW wrote: Hang on.. I've just spotted a red flag
So it's those bluddy Chinese, again!
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
More likely USA Air Force who have combat training called red flag exercise.
Practicing on CP again... Abuse, Abuse , shoot, shoot, Got that red flag Sir.
|
|
|
|
|
Any community such as this relies on the good sense of its members to avoid "abuse wars", and similar behavior, the problem being the small minority of abusers. The problem with giving everyone the right to report spam/abuse is not the false negatives - most spam that makes it through the automatic filters disappears very quickly - but the false positives. It is these "spam wars" that should be avoided.
What I suggest is that a certain threshold of reports be required before a member is banned. This should work something like this:
- The "abuse report" should be disabled for older messages
This would limit "abuse wars" where someone goes back and tags all of a poster's messages. - The filter should have a time component
There is a difference between someone who posted two abusive messages in the last year, and someone who posted two abusive messages in the last day. - The filter should allow for the number and quality of messages posted
This allows for human error - in both directions. A prolific poster is more likely to be tagged by accident than an occasional poster, and is also more likely to say something to which objection may be taken. - The filter should require reports from more than a small number of people
This would tend to filter out "abuse wars", where a group of friends attempt to get someone banned. - Human judgment should be exercised
This is the most problematic part.
As we are dealing with people's reputations, I feel that a human should review the reports before someone is tarred, feathered, and ridden out of CP on a rail  . This is especially true in borderline cases.
I am aware that "tuning" such a filter would take some time and effort, but I believe that the results would justify the effort.
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
And one more I could think of (I am not sure if this is already in place):
- Reset the abuse votes (and the rep points thereof) after say, 5 days, if the reported message doesn't get the predefined number of abuse votes (so as to get nuked off).
-- EDIT
There's something that is preventing me from starting the list from 6 (the item is appearing as 1). 
You have just been Sharapova'd.
|
|
|
|
|
Agent__007 wrote: Reset the abuse votes (and the rep points thereof) after say, 5 days, if the reported message doesn't get the predefined number of abuse votes
The idea is a nice one, but this would require keeping a log of the time of each abuse vote on a per-message basis (an extra table in the message database), as opposed to keeping a count of the abuse votes (an extra field per message). You would also need a periodic task running that performs the cleanup, reposting of rep points, etc. Building all this mechanism just for a few rep points seems a bit of overkill.
Please note that point (1) on my list ensures that "abuse wars" cannot affect older messages, so the damage to a poster's reputation is minimal in any case.
Banning someone, OTOH, is serious enough to warrant more effort.
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
Daniel Pfeffer wrote: this would require keeping a log of the time of each abuse vote on a per-message basis
Unless it's already in place.
You have just been Sharapova'd.
|
|
|
|
|
Any kind of user moderation is tricky: ultimately there is no safe way to distinguish the serious reports from the abusive ones. We'll have to live with a certain amount of abuse and hope the filters will keep their effects low.
I believe CP does a very decent job at filtering: a single abusive report won't normally* change a lot, and, in most places, when there are multiple reports, some moderator will look into it before taking action.
*: One part of the system where I feel it isn't working all that well is voting on tips and articles: I've been subject to one ab-user who deliberately sought out all of my published tips and articles to downvote them. Since some of them did have no votes at all, they are now filtered out from view for the majority of users who might otherwise have taken advantage of it. On another occasion, I've published a few tips, but within minutes they were hit by some anonymous user in a downvoting spree, resulting in 3 tips that never saw the light of day. I've reported both cases in the support forum, but since there is no official channel for reporting that kind of abuse it went unnoticed.
I realize that my contributions really weren't that important, and the CPians will not suffer for the lack of it. But for me the experience was frustrating, and it discourages me to post further articles. 
GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)
|
|
|
|
|
I'm experimenting with displaying articles using ASP.NET 5, VS15, and EF7.
Keep getting distracted by the content of the CodeProject Articles from 1999 ![Green Alien | [Alien]](https://www.codeproject.com/script/Forums/Images/alien.gif)
|
|
|
|
|
Kind of a cool distraction, I would imagine; memory lane.
|
|
|
|
|
Shhh... I'm trying to write some ODBC 3.5 code... I've had this big damn book since 1999 and it won't read itself...
|
|
|
|
|
Guilty as charged....
Life's like a nose, you've got to get out of it whats in it!
|
|
|
|
|
That's the fault of the algo...... oh look an advert for something I don't need but with a lovely coloured boarder
You cant outrun the world, but there is no harm in getting a head start
Real stupidity beats artificial intelligence every time.
|
|
|
|
|
.. at last.
bridge.net[^].. shall install and report back
|
|
|
|
|
At last? Maybe with a specific focus on "Mobile, Web And Desktop Apps", as bridge.net advertises, but C# to JavaScript converters/compilers have been around for years. ScriptSharp is the oldest I can remember, going back as far as +-2008.
No object is so beautiful that, under certain conditions, it will not look ugly. - Oscar Wilde
|
|
|
|
|
This wasn't good...[^]
What do you get when you cross a joke with a rhetorical question?
The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism.
Do questions with multiple question marks annoy you???
|
|
|
|
|
Too easy!
I could hospitalise myself with chocolate that isn't out of date!
Just bring the truck as close as you can to my door...
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
What a crappy piece of "journalism". Not even a hint as to what made the hot chocolate was toxic after all that time. It reads like, "after 25 years, hot chocolate is an evil menace that should have as all quivering in fear. Yes, it does always pay to read expiry dates, but when it's not glowing green meat, with obvious dangers, just a hint at what is actually wrong would be nice, for any thinking reader.
No object is so beautiful that, under certain conditions, it will not look ugly. - Oscar Wilde
|
|
|
|
|
Brady Kelly wrote: for any thinking reader
These usually don't show up there
|
|
|
|
|
This is why you always need to check the expiration date on everything. Don't assume it's just a guideline or you'll end up in the hospital.
I've worked for the food industry. It's just a guideline. As long as it looks, smells and feels right they'll put any (preferably legal) date on it!
There's even an expiration date on sugar just because it's food and you're required to put expiration dates on food. Sugar doesn't expire...
|
|
|
|
|
There is an expiration date on bottled water
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
It's when the water will have evaporated through the seal on average 
|
|
|
|
|
And salt. My missus pointed out that the salt I was going to put into the salt cellar was expired.
I was in a carelessly foolhardy mood, so I used it anyway.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Quote: expired way back in June 1990.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
Shoot, I was eating 20 year old chocolate, eggs and ham, fruit, etc. in the form of "C" rations when I was but a youngster on my first hunting trip for moose 
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
