|
Couldn't you just sort of put a timer on it?
My first thought at reporting a question unclear or incomplete isn't to remove it, it's more off a message to the user that he/she needs to explain more.
(the fact that the question gets removed after x such reports is one of the reason's I rarely use that option)
We are here to help people, in my mind helping them express themselves and teaching them to ask a question in such manner that they will get an answer can be just as valuable as answering the question itself.
I know it's naive off me to think that every user can be thought or is willing to learn but I think if we give up entirely we lost a important part somewhere.
My suggestion would be more in the lines off:
- The report as unclear sends a mail to the user informing him that one or more people have marked his / her question as unclear and asking him / her to update the question with more information. (no idea if this happens right now or not? )
- After x amount of such reports the question becomes hidden for everyone except the OP (and maybe a dedicated group off members to help the OP in clarifying the question, they would need a list of such questions tho, something like the moderation queue I guess)
- After x amount of such reports and y amount of time if the question hasn't been updated, the question gets removed.
- Anyone wanting to help the OP in teaching how to ask a good question can do so in comments.
- If an actual answer (not a comment) has been posted to the question the question can no longer be removed (maybe just closed or something like that? )
I do see one problem with this and that the system can be "played" unless you can somehow determine if the edit is an actual edit or just a space added to prevent removal.
This is of course not something you can implement overnight, well maybe you can but please remember then it's 'desktop' with a 's', and make sure there is enough coffee 
Tom
modified 27-Apr-15 15:52pm.
|
|
|
|
|
Seeing the recent spam attack, I'd be willing to volunteer to serve as a protector.
I usually have time in the weekends to help with the attacks, seeing as in the weekends things usually go slower and I don't know how many protectors there are at the moment but dealing with this attack seems they have their hands full.
I don't mind sacrificing the odd hour or 2 on the weekends to help keep things clean.
As always it is up to you
On a side note: in a attempt to help clean things up in QA I went to delete the spam but couldn't (only report) I seem to remember I could delete questions at one point in time, did this change? (just asking to confirm I haven't lost my mind and am remembering things that never where  )
Tom
|
|
|
|
|
Tom Deketelaere wrote: I seem to remember I could delete questions at one point in time, did this change?
Yes, this did change: due to abuse of this function, it was made Protector-only (also see the Privileges tab on the profile page).
The quick red ProgramFOX jumps right over the Lazy<Dog>.
|
|
|
|
|
|
For me Sunday is NOT weekend so I could help protectors too without ruining it - so put me on the list too, if you need more...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
You can add another volunteer to the list.
|
|
|
|
|
Same with me.
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???
|
|
|
|
|
I hate to say it, but...I think we need to consider adding Captcha to QA posts.
One spammer with over 300 posts in two minutes? We can't fight that by hand - the DB caching is against us because even the deleted posts are still showing up as the whole of teh first coupel of pages of QA presently.
Anyone else think this might help?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
It will help against the bots, but probably will render QA unfriendly...
It is a very hard decision - but I would like to go on the other way...give some smart tool to the protectors...like close all post of a member, and the member, who got 3(?) messages in the QA reported as spam by any protector...also some kind of forced cache refresh...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Headshot on QA Moderation queue posts as well as well as message - over 82,000 posts in there at the moment, and that's just not practical to clear manually; not at a page-refresh per individual item of spam.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
82000 spams are rare, but CAPTCHA is there to stay...It is a really hard decision to make (fortunately not to us to do so)...Maybe it's time to wake Chris...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
I sent him an email asking for assistance a while ago. Poor bugger...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
OriginalGriff wrote: Poor bugger...
Yeah - strat your week like that is bad enough, but the weekend! It's just cruel...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
What's wrong with limiting posts (number) from new accounts - or sending all posts from brand new accounts to moderation?
Peter Wasser
"The whole problem with the world is that fools and fanatics are always so certain of themselves, and wiser people so full of doubts." - Bertrand Russell
|
|
|
|
|
pwasser wrote: or sending all posts from brand new accounts to moderation?
Because at the moment there are 82,000 posts in moderation from spambots, and you wouldn't be able to see any "genuine questions" for an hour or so if you started deleting the garbage this instant! 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
On consideration I can't see a huge objection to Captcha's but for those who do there may be other ways. I still think rules can be applied to posts to get rid of most of the spam - especially the robot generated stuff. Just another suggestion and I reiterate Captcha's are certainly one way.
Peter Wasser
"The whole problem with the world is that fools and fanatics are always so certain of themselves, and wiser people so full of doubts." - Bertrand Russell
|
|
|
|
|
pwasser wrote: What's wrong with limiting posts (number) from new accounts
The question would be by which rule the amount of allowed posts would increase. If it's just a matter of how many days old an account is, the spammers could just "plan ahead".
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
|
|
|
|
|
I responded to OG. I agree with your point but it is not an insurmountable issue IMHO.
Peter Wasser
"The whole problem with the world is that fools and fanatics are always so certain of themselves, and wiser people so full of doubts." - Bertrand Russell
|
|
|
|
|
Sascha Lefévre wrote: spammers could just "plan ahead".
Which is what they have done; see my comment in the spam forum.
|
|
|
|
|
How about adding time break between posts.So that when a new member posts a question he/she will allow to post the next question only after a specific time break(like 10minutes or something).I think if member is a spammer he/she will be reported within that time.
|
|
|
|
|
I was thinking - maybe the CAPTCHA should sit on the login page, so you can't fake a login from code...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
When was the last time you logged in? For me, it's about once a year, when the CP cookie expires.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Of course for me and you, but if you try to login with new accounts (and a lot of them) on the same machine and you have CAPTCHA, you have trouble...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Seems I've missed the party. 
Anyway, my opinions.
It's not unreasonable to have a captcha on account creation, anything more get obnoxious.
Having a limit on one message per minute is not unreasonable. Any further messages will end up in the moderation queue automatically.
And have a maximum of five messages in the moderation queue allowed before blocking new messages.
|
|
|
|
|
How about a simple programming CAPTCHA, something like:
Predict the output:
integer i = 0, j = 0;
j = ++i;
Print (i);
OR just give them a simple syntax error to fix (except that would be related to a specific language).
I think everyone will be able to answer such simple ones. And it will keep those "Packers and Movers", "Streaming Movies", "Baba", etc., spammers away.
Just my 2 cents...
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
