Whee! Doing a stunt!

Hello, I blog!

I write with no particular theme in mind, because I am random like that.

06 2012

This is why I love skywatching …

… because you’ll never know what to expect.

Was taking a nice, slow walk back home when suddenly I felt this strange urge to look at the sky. (Usually, I don’t bother since I’m in cloud kuku land when strolling about, and also attempting to dodge cars and all … which I nearly got hit by one actually, but that’s a different story altogether.)

So, I gazed up and saw this magnificent lunar halo smiling down at me.

Lunar Halo, 06 January 2012
Lunar Halo with Orion’s belt 45 degrees to the top right.
Captured on an Canon EOS 450D, F3.5 + 20s shutter speed.

It was quite a massive halo, spanning a large area of the sky. Hurrah for wide-angle lenses. I managed to capture the entire halo along with some surrounding constellations.

The halo had faded considerably by the time I reached home and retrieved my camera, but enjoy what’s left of it. (;

11 2011

Total Lunar Eclipse, 10th December 2011

Hurray for awesomely clear skies, because it allowed me to catch the total lunar eclipse from start to finish.

Managed to catch the first half of the eclipse at Marina Barrage with a bunch of close friends … along with loads of noisy children, other astronomy geeks and surrounded by kites attached with flashing lights which (thankfully) didn’t get in the way of the eclipse viewing.

The second half was caught from home.

Total Lunar Eclipse, 10th December 2011
Click to view original size.

This is possibly the first time lady luck’s on my side, considering my last blotched attempt at eclipse watching no thanks to an overcast sky (which resulted in loads of grainy photos). Today was completely different – witnessing a total lunar eclipse under a clear night sky was an experience on a totally new level.

I’ve collated all the images captured into a composite as you can see above. Click on it to view the composite in its full glory.

Oh yeah, you can find my photo submission on my favourite astronomy site, Spaceweather too.


Prevent automated registrations with JS

After GameMaki (one of my current pet projects) was hit by an onslaught of spam, I spent the last couple of hours thinking about how to prevent automated registrations.

Originally, I attempted a very primitive method, which is to add a hidden field in the registration form which is set to ‘true’ when the form is loaded on a Javascript-enabled browser. When the form is submitted, this hidden field is checked for its value, and it only goes through when the value is ‘true’.

Obviously it hadn’t worked. It was too straightforward, and I’m pretty sure bots are much smarter than that.

So I thought, checking for whether the site was loaded in a standard browser wasn’t good enough. In order for a request to be human-initiated, there has to be some sort of interaction with the website – whether it is a click, scroll or focus.

jQuery slider by TheyMakeApps for form submission.
jQuery slider by TheyMakeApps for form submission.

TheyMakeApps has quite a cool implementation that requires some form of human interaction to successfully submit a form. Instead of a standard ‘click’ to the submit button, their implementation requires the user to drag a slider to an end-point. jQuery is used to detect the position of the slider and the form will submit only when the slider has reached a certain point in the bar.

Quite nifty, but it didn’t feel natural. People are used to hitting ‘tab’ when navigating from one form field to another, before a final ‘tab’ and an ‘enter’ to submit a form.

I didn’t want to yank users out of their comfort zone. So, how do I check for automated registrations without imposing any additional burden to the user? (And quite obviously, CAPTCHAs are out of the question.)

Here’s how I eventually did it. Well, it still involves a hidden field, for sure.

Place a hidden field in your form as follows. This field has a unique ID of ‘botcheck’ with a default value of ‘false’.

<input type="hidden" name="botcheck" id="botcheck" value="false" />

Now, what we need is a bit of Javascript and jQuery.

I have two functions in my Javascript file. The first function, randomString() generates a random string of numbers to populate the hidden field with. The second is the validation function which will be called when the form is submitted. On top of that, we have one global variable to track the value of the generated random string.

// Global variable
var randomstring = "";

// Function to generate a random string
function randomString() {
  var chars = "0123456789ABCDEFGHIJKLMNO
  var string_length = 8;
  for (var i=0; i<string_length; i++) {
    var rnum = Math.floor(Math.random() * chars.length);
    randomstring += chars.substring(rnum,rnum+1);

// Function to verify hidden field value
function doBotCheck() {
  var botcheckfield = $('#botcheck').val();
  if (botcheckfield == randomstring) {
    return true;
  } else {
    alert("Hello, robot!");
    return false;

Note: Credit for the randomString() function goes to MediaCollege.

Now that we have all our Javascript functions ready, let’s add a bit of jQuery magic.

On document load, a random string will be generated. A ‘focus’ event is bound to all my form’s input fields. When this event is triggered, the hidden field is populated with the random string.

I chose the ‘focus’ event as it requires manual user interaction with the form to verify that the user of the form is indeed a human. (Originally, I contemplated using the ‘change’ event but decided against it since the fields can be directly manipulated via a script anyway.)

The use of a random string ensures that the value of the hidden field will not be easy to guess if the spammer wanted to directly manipulate it.

So, we have this.

//Populate hidden field only when user triggers a manual interaction with the form
$(document).ready(function() {
  // Generate a random string

  // Update hidden field on field focus
  $('#MyForm input').live('focus', function() {

Last but not least, remember to call the validation function from your form on submit.

<form id="MyForm" onSubmit="return doBotCheck()" method="POST">

And wa-laaaaah.

Well, this is my method for now. Whether it works, I’ll just have to wait and see. If you see any flaws in my method, don’t hesitate to holler. And if you’ve better ideas on how to solve this problem, feel free to share ’em!

Page 4 of 12First...23456...Last
More Stuff