Hello, I blog!

So I purchased the iPhone X (256GB, Silver). Caved in mainly because of the camera specs, and because my old 6S was slowing to a crawl and running out of space (I was previously on 64GB but I take photos like a maniac).

Excited, I was.

My excitement waned significantly when I was setting up the new iPhone on the 23rd February. I’m the type of user who migrates all my data from phone to phone because I am sentimental like that. (I keep WhatsApp chats from as long as 8 years ago.) The iPhone X was a pain to setup, and I lost some notes and all my WhatsApp chats along the way. As it turned out, iTunes backups for WhatsApp chats have ceased to be effective and I had to move my chat backups to iCloud. Luckily, I got everything restored, although it took 3 hours.

My excitement waned further while getting used to the new gestures for the iPhone X. There was no more home button, so I had to get used to multitasking, killing apps and how to take screenshots. (I actually had to Google to figure out how to use the X.)

The excitement returned when it was time to start using the X for photos. I snapped happily for a couple of days.

Until the dreaded green line appeared on the side of my screen on the 25th February.

Green line, still visible as of today.

#LineGate apparently. A quick Google search showed that other iPhone X users have faced this. It’s a thin vertical green line that extends down the height of the screen. Some on the edges, others in the middle of the screen. Mine was on the right edge which thankfully wasn’t too disruptive, but annoying all the same.

Considering this is a phone with a market worth of close to $2000 (Singapore dollars), this was certainly not acceptable. I’ve been lucky so far with my other phones, and #AntennaGate and #BendGate hadn’t happened to me. But it seems like my luck has finally run out.

And here is where my looooooong battle with Apple begins.

Sit back and grab a coffee. Because this is a ridiculously long post.

Just like how Apple is taking ridiculously long to resolve this issue.

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.

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
PQRSTUVWXTZabcdefghiklmnopqrstuvwxyz";
  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
  randomString();

  // Update hidden field on field focus
  $('#MyForm input').live('focus', function() {
    $('#botcheck').val(randomstring);
  });
});

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!