Migrating the MKVToolNix bug tracker to GitHub issues
Saturday 24 January 2015 @ 9:57 am

I’ve migrated my previous bug tracker (a Trac installation) to GitHub’s issues. Why? Due to spam.

First things first: what does that mean for my users?

Here’s some background information how I came to this decision:

Over the last couple of months the amount of spam has increased significantly. Even though I required verified user accounts before anyone can open a ticket there were bots that created such accounts automatically, handled the email verification and posted spam tickets afterwards. I had to clean up this mess time and again.

I had been using a Captcha plugin for registration as a countermeasure. Unfortunately that plugin is no longer compatible with the user management plugin (and a plain Trac installation doesn’t have any user registration capabilities on its own, so you have to rely on third-party addons for such tasks).

A second countermeasure I had deployed was administrator approval. Each newly registered account had to be approved by me, and I was getting pretty good at sniffing out obvious spam accounts. However, I sometimes erred, on both sides: spammers were still getting through and posting their crap while legitimate users weren’t allowed to post and complained via private emails. This countermeasure also meant that I received around 50 emails a day about new accounts having been created.

So that’s why I don’t want to host my own bug tracker anymore.


Comments (3) - Posted in Matroska by  

 3 responses to “Migrating the MKVToolNix bug tracker to GitHub issues”