Thanks ruffles! It's actually an incredibly simple function that can be accomplished in just a few lines of code, so no major development time should be required. The only problem is that the Admin on this forum is incredibly bad at coding... But it's no hill for a climber. ;)
> a CAPTCHA on every single page
Some annoyance and wasted time -- but until you get the programming you hope for, a CAPTCHA would be better than what's happening now.
Mainly -- it'd increase the cost to the spam company, maybe enough they'd quit hammering this site.
This site gets hammered because to them, it's wide open to dump crap in, and being cleaned up often so their new crap is kept fresh and floats on top, seen by everyone every time.
Can you make a feature request to the creator of whatever forum software you're using? It sounds like a great idea and they should be able to implement it rather easily since they're the creator of the code. Maybe you could get in touch with them and see if they could add this "limit amount of posts - per user - per minute" feature.
Good Job on all of this Mr.Admin but really I wouldn't mind the MATH captcha on all posts. It only takes a second, no big deal.
I wish I could, but Drupal is a huge project with hundreds of coders who are pretty much uninterested in the needs of individual users.
Hmm, yes and no. The spammers from some flashlight company that want our users to buy their products do want their posts on top so that we click them. But the sort of spammer that posts 50 or 1000 posts at once is doing it to skew the Google search rankings so that when people search for "Coach bags" their site will come out on top because it has more links to it. They don't really expect actual users to click on their links, they just want the Google crawlers to see them.
Isn't this what you want to do? Perhaps you just need to write a "rule"?
http://drupal.org/project/node_limitnumber
-----------------------------------------------------------------------------
Posted by nachenko on April 17, 2008 at 4:21pm
Limit the amount of nodes or comments your users create over a given time period. This module has been rewritten to integrate with Rules. Instead of going to a page to assign limits you now just need to create rules. A default rule has been provided as an example.
When creating your rules there are now many hundreds of ways to implement your limits. Limits can be applied to roles, users, dates, or anything that can be accessed using PHP.
-----------------------------------------------------------------------------
I don't know much about this, just trying to help, but it looks like what you're trying to implement.
Also, i dont know what version you're using...
---------------------------------------------------
Drupal 7
No plans are in place for porting this to Drupal 7. If you need a module like this for Drupal 7 you can try out Node Limit.
-----------------------------------------------------
http://drupal.org/project/node_limit
Posted by davedelong on March 3, 2009 at 2:09am
The Node Limit module allows administrators to restrict the number of nodes of a specific type that roles or users may create. For example, if a site has an "Advertiser" role that can create "advertisement" nodes, then the node limit administrator can restrict all users in that role to a specific number of nodes. He may also restrict users on a per-user basis.
Although other node limitation modules exist (such as create quota (Abandonned), user quota (D6), and node limitnumber(D6)), Node Limit offers features not available in all of those modules, such as:
- Per-role node limits
- Per-user node limits
Per-organic group node limits(Dropped)- Per-time interval node limits
Per-time frame node limits(Dropped)- Per-taxonomy term node limits (Coming soon)
- Any combination of the above
- Drupal 6 & 7 compatibility
- Requires no programming on the part of the administrator
Wow, I'm impressed you found that one. :) I looked for days and finally stumbled across it. But unfortunately it doesn't work. The problem is that it will accept the post but then un-publish it, so if legitimate users post 3 posts in one minute (which some do) their post will be accepted but then immediately un-published. What we need is a method where it checks before accepting the post so that fails at the POST step and the user can simply wait a bit longer and hit SAVE again.
Like i said, im not an expert on it in any way, but it may be possible to set up some type of rules based system. There has to be a way to set it up for newer users, or not have it get applied to users with x amount of posts or something.
I'm very sorry they aren't being more helpful with you. Perhaps you could speak with the designers of the plugin module?
I won't add any more comments to this thread because I really have no experience in the matter and I'm not sure I'm helping :)
You're right, this part is possible. I have thought about doing that, but I don't really want to invest time if we can quickly implement a superior solution.
Thanks a lot for your comments, I do appreciate them.
Mr Admin,
i do believe you want a trigger. Do you know the table the posts get saved to?
Could you please run the command:
show create table tlb_posts and PM me the result? I could try to write a trigger that would do just that - fail the insert command.
edit - You must replace tbl_posts with the correct table name in the command above.
Thanks very much! With this method would it be possible to return the user back to the post editor with a "Please try again in 30 seconds" error message and preserve the form contents?
Have you tried question and answer based CAPTCHAs? The blurry text can be hacked with OCR and the Math is pretty easy for computers. Q and A can be pretty effective because even if humans set up an account they generally might not understand English.
Hmm, not a bad idea. I think I might try that.
Ok, here's a test of the new CAPTCHA.
I already like the new captcha!
Thanks for the link! I am considering using Bad Behavior, which doesn't analyze post content but rather post method and post origin. But it's only a secondary line of defense. The most important will still be our community moderated anti-spam system.
Works... An extra step, but better than Spam...
Should help slow them down at least...
With the trigger in place the database would return the insert error to the forum.
I could not control the message displayed by the forum. You could even get an "internal error", depending on how Drupal handles DB errors (and I'm not an expert in Drupal)