About Archive Tags RSS Feed


Possibly retiring blogspam.net

2 November 2017 21:50

For the past few years I've hosted a service for spam-testing blog/forum comments, and I think it is on the verge of being retired.

The blogspam.net service presented a simple API for deciding whether an incoming blog/forum comment was SPAM, in real-time. I used it myself for two real reasons:

  • For the Debian Administration website.
    • Which is now retired.
  • For my blog
    • Which still sees a lot of spam comments, but which are easy to deal with because I can execute Lua scripts in my mail-client

As a result of the Debian-Administration server cleanup I'm still in the process of tidying up virtual machines, and servers. It crossed my mind that retiring this spam-service would allow me to free up another host.

Initially the service was coded in Perl using XML/RPC. The current version of the software, version 2, is written as a node.js service, and despite the async-nature of the service it is still too heavy-weight to live on the host which runs most of my other websites.

It was suggested to me that rewriting it in golang might allow it to process more requests, with fewer resources, so I started reimplementing the service in golang at 4AM this morning:

The service does the minimum:

  • Receives incoming HTTP POSTS
  • Decodes the body to a struct
  • Loops over that struct and calls each "plugin" to process it.
    • If any plugin decides this is spam, it returns that result.
  • Otherwise if all plugins have terminated then it decides the result is "OK".

I've ported several plugins, I've got 100% test-coverage of those plugins, and the service seems to be faster than the node.js version - so there is hope.

Of course the real test will be when it is deployed for real. If it holds up for a few days I'll leave it running. Otherwise the retirement notice I placed on the website, which chances are nobody will see, will be true.

The missing feature at the moment is keeping track of the count of spam-comments rejected/accepted on a per-site basis. Losing that information might be a shame, but I think I'm willing to live with it, if the alternative is closing down..



Comments on this entry

icon anarcat at 13:09 on 2 November 2017

I must say that losing blogspam.net would be a great loss. Not many independent providers out there, and even less that are actually free to use (both in the speech and beer sense). Heck it looks like even Mollom is going down...

As for why people didn't see the termination notice, I guess that's because sysadmins rarely visit the site at all... It may help if clients report back that kind of stuff to the admin in the CMS web UI, but I don't exactly how that would work for IkiWiki for example...

And I also don't care about the stats much. I just want a spam filter that works. :)

icon Steve Kemp at 14:54 on 2 November 2017

I can sympathize, but I expect that the pricing is the problem right now. As it is free I have little incentive to keep things going smoothly now that I don't directly benefit as much myself.

As things stand every few weeks I get emails from (indirect) users who say "You said my comment was spam, I hate you!!!11!!".

But yes one of my mistakes, definitely, was not collecting user email-addresses, or setting up keys to access the API - even if freely initially - as things stand I have no way of mass-mailing users either saying "$10/year", "$5/month", or "this site is dying".

In an ideal world I'll cut back the resources required, and keep it going, but even if I do that I suspect there is an end in site.