[wp-hackers] Future Posting Fix Request

Doug Stewart dstewart at atl.lmco.com
Mon Jul 24 13:48:53 GMT 2006

Hash: SHA1

Brian Layman wrote:
>> Its not the blog owner that has to wait, though. It is an unsuspecting
>> end user, who can be hit with 20-60 second wait times. Just search the
>> WP support forums for problems with posting taking a long time.
> Heh - Intercept the robots.txt calls via .htaccess sending the bot over
> to a page that triggers the croned activities while still returning the
> robots.txt info*.  Then no human admin or otherwise has to suffer the
> time lag. The referrer could even be used to ensure that prefered search
> engines (say Alexa which has a speed check) never triggers it.
> Eh... Propably wouldn't be practical but it would put bots into actual
> practical use...
> *now either incorporated into WP or read via IE from robots.txt that
> could still exist in the root web directory. 

I like the thinking, but why not feed Akismet spammers into that tarpit
instead?  I get a nigh-consistent barrage of spammers pinging away at my
comment form, 99.995% of which get caught by Akismet.  Use the spammers
to fire your cron jobs and make 'em wait for the result.

- --
- ----------
Doug Stewart
Senior Systems Administrator/Web Applications Developer
Lockheed Martin Advanced Technology Labs
dstewart at atl.lmco.com
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


More information about the wp-hackers mailing list