Spam Tickets - Begone.
Although it wasn’t a huge problem in the past, recently the Rails Engines issue tracker has been receiving an increasing amount of spam. Today I’ve finally taken some steps to protect the site.
The first, actually taken a few days ago, is that the lifespan of tickets marked as Invalid ends as soon as they are marked so. Changing the status of a ticket to Invalid will forever (well, without DB intervention) prevent any further updates being posted to it. This change was a last-ditch attempt to stem the typical spammer behaviour of finding a ticket and sending continual changes with swathes of spam URLs to particular tickets (I had to actually delete that last one because it was attracting so much spam attention).
The second change to our issue tracker is that is that you now need to log in to create a new ticket . Here are the details:
login: anon password: engines
You can login in here.
I’m not the only one feeling this pain, but I’d rather add this little hurdle and keep the issue tracker clean and focussed than let the spam continue any more.
Unfortunately, this still isn’t good enough; spammers can still flood the comments to their heart’s content. In the future we made augment the issue tracking tools here to cope properly with the ever-present threat of spam; until then, please login in with those credentials, have your browser save them so you never need to remember them again, and do keep reporting issues!