Better keyword monitoring and a failed Friday update

As some of you may have noticed, there was an update. On Friday. Late in the afternoon. Despite knowing the jokes about this, I did it anyway and it failed. Throughout the week there are numerous tiny updates that you'll hardly notice. The bigger updates are usually done in the weekend, and only after they have been running successfully in test for a while. This update was running ok in test, but the test was obviously not complete enough. The decision of how much to test is always hard. No one wants to unnecessarily slow down development.

The update
Well, up until now keywords where matched as whole words. This means there are spaces (or tabs, or new lines) around them. If you entered something between quotes, like "@shadowtrackr.com", this would find Shadowtrackr email addresses in passworddumps. But if you just had a surname (without quotes) this would be missed in passworddumps. The surname would likely be prefixed with a '.' (behind the first name) and postfixed with a '@'. No match. That has changed now. Shadowtrackr matches a word between any non-letter and non-number character now.

In some cases you might want to detect a partial match, like sub in subdomain. On the traps page for your keyword you can check the box "match partial keyword" for this.

What went wrong?
When you have multiple keywords in a trap, they should all occur before a notification is send. With this new algorithm, this went wrong. Any of the keywords now was enough. To make things worse, the update set the default state for "match partial keyword" to on. This resulted in way more notifications than you'd be happy with.

The problem only lasted for about half an hour, but you can get an amazing amount of notifications in that time. I myself got about a thousand of them. My sincere apologies to you all, I'll be more careful with updates.