In an article Chris sent me a message saying more or less: That is not a tip, tip must be short.
To be honest, I prefer to keep the focus on good articles having a higher minimum requirements and to have a bigger diversity in tips, than to keep the focus on short tips and everything what is longer going to articles.
In other words... With black and white, the grey zone belongs to tip.
And I think many members think like me. But if I am wrong, then I won't say the "have you consider to post this as a tip?" anymore, if it is not clearly 100% a tip.
Members feel free to answer, I will accept the majority.
Edit: Expanding the types with the "HowTo/Walkthrough" and/or "Guideline" (as suggested short ago) would be a nice feature that would cover most of the grey zone and make it easier to classify.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
In this specific case the article (at least according the revision history) never got published...It went from 'pending' to 'closed'...
In any case I would say to notify all those approved an article
1. If already has a spam/plagiarized flag on the article - to let him review it more
2. If approved and later someone flag it as spam/plagiarized
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
How would this work? Would the author be contacting the people who rejected the article (there are lots of people who have the privilege)? A better bet is to raise the issue in the Article Writing forum.
Member Profile - CodeProject[^]
This member posted a joke, that had the exact bearing of a spam, and for that the post and the account removed...
I think that in this case it would be appropriate to reopen the account...