-
Notifications
You must be signed in to change notification settings - Fork 529
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add better support for Akismet #83
Comments
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? |
I don't see anywhere in the staticman.yml config to put an Akismet API key. Is there any way to use Akismet when not using the public shared instance? Thanks! |
@deadlydog the Akismet's site and key are configured for Staticman, not for the site, so they are not in staticman.yml. You can set them in config.{ENV}.yml file or using env vars (which are both on where you host Staticman). |
Thanks @PhuNH , I found which environment variables I needed to add here ( I've also modified my # Akismet spam detection.
akismet:
enabled: true
author: "name"
authorEmail: "email"
authorUrl: "url"
content: "message"
type: "comment" I know these fields are documented here, but I'm still not entirely sure what they're for besides the I figured I'd document the process a bit in this thread, as I couldn't find any other documentation for it. Thanks! |
To collaborate with @deadlydog on documenting the process: |
@PhuNH, @deadlydog -- I host Staticman at Heroku. |
@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 |
It can be working around by updating |
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.
The text was updated successfully, but these errors were encountered: