[wp-hackers] Future Posting Fix Request

[Doug Stewart]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Robert Deaton wrote:
> Imho, the following things are wrong with some of the suggestions:
> - The one about Akismet... Akismet is a plugin that relys on an
> external service. I'd rather not have anything in the core rely on an
> external service all the time. For example, even the reliance on
> ping-o-matic as the default ping server was a bad thing when it was
> taking 20-80 seconds for ping-o-matic to accept the pings.
> -For search engine spiders, robots.txt, etc., or spammers, they are
> simply too unreliable. A future scheduled cron even may very well be
> triggered by any of them at any time, but we can't rely on only them
> to do the pinging. Short of building some statistic analystics systems
> in with the cron to detect whether or not another hit from a spammer
> or search engine is likely to come within a short period of time after
> the event is supposed to fire, there is no way for us to know which
> sites can handle this kind of behavior or not.
> 

So what you're telling me is that my magical, mystical blogging heat
pump/perpetual motion machine won't work?

Bah.  Maybe I'll write a plugin instead.  *grin*

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

iD8DBQFExQYdN50Q8DVvcvkRAroaAJ9bZScr0QGh+Y8KaxXDSIRcsFfuXgCeKfem
DgpqFm83xbUsrHj+wgH+bRU=
=OxkU
-----END PGP SIGNATURE-----