[spam-stopper] Akismet and Lyceum
John Joseph Bachir
jjb at ibiblio.org
Thu May 11 06:23:06 UTC 2006
Hello all. I just joined this mailing list. I took a look at the archives
and noticed there was discussion earlier this month about how to use
Akismet with Lyceum.
Andrew Ferguson wrote:
> In short, you hard code the API key by changing the host because the API
> key is sent as a sub-domain of the host (fourth level domain name,
> actually). So, all requests should be sent to the host
> aoeu1aoue.rest.akismet.com, where "aoeu1aoue" is your API key.
What do you mean by 'host'? I'm probably missing something obvious here...
I /think/ what Shane was looking for was that he should make an entry in
the options table with option_name 'wordpress_api_key' and option_value
whatever his key is.
BUT hopefully this won't be necessary in the near future, as I hope to
make the interface and functionality for all system-wide plugin settings
Matt Mullenweg said:
> Even if you're a non-profit, send something to the contact form before
> doing this though, as putting too many blogs on a single key without
> pinging us will get you blocked.
What do the Akismet folks see as the most ideal practice for multi-blog
installations in the long term? My impression is that the Akismet
heuristics depend on there being one key per 'person', to determine if
someone is trying to game the system. Would it be impossible to install
one key for a multi-blog system the 'right way'? For example on
deployments with open registration, there may be a few users trying to
game the system amongst the many legitimate users. Are there other options
for differenciating these things, such as url / domain name?
It seems like making the heuristics compatible with single-key multiblog
applications would be desirable eventually. For commercial installs you
guys could charge per head. <kool-aid guy voice>Oh Yeah!</>
More information about the spam-stopper