[spam-stopper] Akismet and Lyceum

[Shane Bishop]

Being the one who instigated this discussion, I should probably give an 
update, and a bit of clarification for John's sake. I was able to 
hardcode the API key. It actually got sent to the server, and the test 
comment was flagged as spam.
However, when I login and go to manage my blog, there is no Akismet 
section under the comment management, so I can't actually see anything 
that gets flagged as spam. I can flag stuff as spam from the normal 
section, but it is then only accessible by going into the mysql database 
(which is how i verified it was getting tagged in the first place).

For whatever reason, the 'Akismet is not active' warning always shows up 
  on a user's profile page, even after I have set the API Key in that 
account. If I could simply get akismet to use a globally set option, 
that would be the best route I think. Then John could figure out a way 
to set that from the system-plugins interface and we'd be good to roll 
(or bounce, or hop, or whatever we wanted to do). I know, optimally, 
that John wanted to just be able to drop the wordpress plugin into 
either the 'plugins' or the 'systemplugins' and have it work both ways, 
but I'm not sure if that's realistic to expect without any modifications 
to the akismet code.


John Joseph Bachir wrote:
> 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 
> much nicer.
> 
> 
> 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!</>
> 
> John
> ----
> aim/yim/msn/jabber.org: johnjosephbachir
> 713.494.2704
> irc://irc.freenode.net/lyceum
> http://lyceum.ibiblio.org/
> http://blog.johnjosephbachir.org/
> _______________________________________________
> spam-stopper mailing list
> spam-stopper at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/spam-stopper

-- 
Shane Bishop
System Administrator
Trinity Bible College