Add better support for Akismet

I’m currently using the honey pot method but around 3-5 spam comments slip through every day. It’s not the end of the world to close these out, but it does junk up my Pull Request stream.

In the beginning I got a lot more spam when I had a website field in the comment form. Eventually took that out, but whoever trained the bots to constantly hit my site must have adapted. Now I get Markdown links in there with messages almost always phrased in the same way.

I see Akismet is an option but wasn’t sure if that was available to the public instance of Staticman or not. If enabled I could see it pulling out a good bunch of these comments since they seem to follow a common pattern.

If I can get reCAPTCHA working that would probably solve the issue, but having some snags there too.

[eduardoboucas]

Our implementation of Akismet needs some work done. It’s currently set to use whatever key is supplied in the Staticman API, which means one single Akismet account is used to filter spam on all sites. Akismet accounts have usage limits, so I believe it’s disabled completely in the public Staticman instance.

We could take the same approach we used with reCAPTCHA and allow each site to supply their own Akismet API key, now that we support encryption.

@zburgermeiszter is this something you’d like to have a go at?

[PhuNH]

@willymcallister it has to be the URL you use when adding a new site in your Akismet account. You can use the same one as your staticmanUrl, or just the domain name part of it as in the example. Staticman only uses this URL and the API key coming with it to make a call to Akismet, so it can be anything as long as it matches the registered one.