« home

Kaptcha v2.3 And BuildMonitor v0.7

Jon released Kaptcha 2.3 which includes a patch I submitted about 2 months ago. This patch replaced imaging library with pixels. If you look closely at the new kaptcha image…

you will notice that the water effect (at the centre of the image) is now visible with pixels, whereas it wasn’t at all with imaging library in the original simplecaptcha implementation. I tested various settings of the water effect, and opted to minimise the effect so lowercase letters on a small font size are still easy on human eyes. Another change with 2.3 is the ripple effect on the characters. It’s not too obvious on the above image, but it’s more visible on uppercase letters with larger font size.

All in all, I think Kaptcha is a nice simple library that does the job. I started using it with Blojsom SCode Plugin, and contributed some improvements back to Kaptcha. Another (more popular) java-based captcha library is JCaptcha, which is also used by SCode Plugin. I’m not a big fan of JCaptcha for the simple reason that their generated captchas are hard to read. It’s interesting that similar comments were made on Hudson mailing list.

Now, on to Hudson Build Monitor. I just released BuildMonitor 0.7 last night. This version is compatible with the recently released Firefox 3.0.1, and it includes id-ID l10n as the first translation. Next version will have build executors monitoring. I’ve started working on the UI, but the data feed is yet to be added to Hudson core.

As you can see from the add-on page over at mozilla.org, this add-on still hasn’t received an approval for public access. I understand that the AMO editors (which all/mostly are volunteers) have been working hard with the crazy number of submissions per day since Firefox 3 release, but I believe that the current approval process will keep facing the same problem every time there’s a sudden jump in the number of add-on reviews, unless Mozilla allocates additional editors to help out. This is not a rant or gripe towards the editors, on the contrary, kudos to them for the work that they’ve been doing.

If I can suggest a change to the approval review process, I think it’s better to distribute the review tasks to the submitters by specifying a detailed list of tests that must be done by those submitters, and keep the tasks that the editors must do as minimal as possible. For example, if AMO provided me with 50 things to test, then I would go through the list, record the tests as a video, and put them on youtube. The reviewers can then just review the video, and still perform only the really really necessary checks, like scanning the source code for any obvious security issues.

So, Hudson users, please be patient, you have to keep logging in to add-ons.mozilla.org to download the add-on for now :).

comments

comments powered by Disqus