Our forums have been experiencing increased levels of members joining the community with the sole intent of building back links and promotion of their signature links. These signature spammers do nothing but clutter our forums with loads of unwanted posts and is something we want to see the end of.
In order to eliminate this, we are going to make a few procedural adjustments. They are as follows:
Signature Links will be no-follow until a member reaches 100 posts- Signatures are not visible to search engines, see updated announcement
- A new infraction has been introduced for individuals who continually post fluff on the forums
The aim here is to weed out signature spammers via our infraction system before the member reaches 100 post and gains any benefit (which is questionable anyway). Over time, this will deter individuals attempting to game the system in the first place...
So what is a fluff post?
A fluff post is a post that doesn’t add any value to the thread. Stuff like ‘nice post’, ‘that’s cool’, ‘that’s helpful’,'thanks for sharing'. Now I’m sure we’ve all made our fair share of fluff posts (myself included) and that’s okay. A fluff post here and there is not a problem, but if the majority of your posts are fluff, you’ll certainly catch our attention. You’ll be warned first, then receive an infraction, then banned if the behavior continues...
How can you help?
We are building a number of internal processes to assist in identifying these signature spammers, but you, members of the community, are best positioned to help us eliminate this frustrating behavior. I ask that if you do see something that feels like signature spamming, please point it out to a forum staff member (via the little orange flag --).
We are hopeful that this will eliminate the problem once and for all without needing to resort to anything drastic and the forums are better for it.



).
. I think this will be helpful. I've noticed this especially in the SEO section. It may even be useful to disable signatures altogether until a certain post count is reached.



This should help the situation tremendously, and I feel this was a move that was most definitely needed. It's good to see action being taken against this. If then more stringent methods are still required, I'm sure the community will be behind you.


Bookmarks