bilge logo
«  the increasingly incontinent ramblings of a drunken has-been irish punk »
here be tumbleweeds


the other night while i was reloading one of these bilgey pages after fixing a bit of shoddy grammar, i noticed my hit counter had incremented by one.  “that’s a coincidence!” i thought attractively “someone’s visiting the site at exactly the same time i’m updating it”.  so i hit reload again and the counter incremented by one… and again, and it did likewise.

“bollox!” i enthused unenthusiastically and with a dearth of enthusiasm, as i realised that my hit counter was buggered.  it’s supposed to set a cookie when you first visit the site, so that it won’t count page reloads as repeat visits, but it obviously wasnae working.  eventually i worked out that this was because the cookie being set was coming from my ISP’s server and not from my own domain.  seeing as i’ve got safari configured to only accept cookies from the originating domain, it was ignoring the cookie and generating a fresh “hit” every time i visited bilge – sook my stupid brain!

what an arse-wipe! – i had been watching my “viewing figures” incrementing painfully slowly over the past few months until, sometime last week,  i scaled the dizzy heights of the 500th visitor mark.  now i’m left asking myself, “so how many of those 500 odd were real visitors and how many were down to me reloading the pages?”

oh well,  time to make the supreme sacrifice and fall upon my statistical sword.  i’ve fixed my cookies and am now going to reset the bilge counter to zero.  if the bugger ever moves off the starting blocks, at least i’ll know that this time there really is someone out there!

bookmark this bilge:
  • Digg
  • Reddit
  • NewsVine
  • StumbleUpon
  • Ma.gnolia
  • Technorati
  • del.icio.us

leave a reply