Visitor Tracking Without Cookies (or How To Abuse HTTP 301s)

Last week I was talking to Alexander Dutton about an idea that we had to implement cookie-like behaviour using browser caching. As I first mentioned last year, new laws are coming into force across Europe that will require websites to ask for your consent before they store cookies on your computer. Regardless of their necessity, these laws are badly-defined and ill thought-out, and there’s been a significant lack of information to support web managers in understanding and implementing the required changes.

British Telecom's implementation of the new cookie laws. Curiously, if you visit their site using the Opera web browser, it assumes that you've given consent, even if you click the button to not do so.
British Telecom’s implementation of the new cookie laws. Curiously, if you visit their site using the Opera web browser, it assumes that you’ve given consent, even if you click the button to not do so.

To illustrate one of the ambiguities in the law, I’ve implemented a tool which tracks site visitors almost as effectively as cookies (or similar technologies such as Flash Objects or Local Storage), but which must necessarily fall into one of the larger grey areas. My tool abuses the way that “permanent” (301) HTTP redirects are cached by web browsers.

[callout][button link=”http://c301.scatmania.org/” align=”right” size=”medium” color=”green”]See Demo Site[/button]You can try out my implementation for yourself. Click on the button to see the sample site, then close down all of your browser windows (or even restart your computer) and come back and try again: the site will recognise you and show you the same random number as it did the first time around, as well as identifying when your first visit was.[/callout]

Here’s how it works, in brief:

  1. A user visits the website.
  2. The website contains a <script> tag, pointing at a URL where the user’s browser will find some Javascript.
  3. The user’s browser requests the Javascript file.
  4. The server generates a random unique identifier for this user.
  5. The server uses a HTTP 301 response to tell the browser “this Javascript can be found at a different web address,” and provides an address that contains the new unique identifier.
  6. The user’s browser requests the new document (e.g. /javascripts/tracking/123456789.js, if the user’s unique ID was 123456789).
  7. The resulting Javascript is generated dynamically to automatically contain the ID in a variable, which can then be used for tracking purposes.
  8. Subsequent requests to the server, even after closing the browser, skip steps 3 through 5, because the user’s browser will cache the 301 and re-use the unique web address associated with that individual user.
How my "301-powered 'cookies'" work.
How my “301-powered ‘cookies'” work.

Compared to conventional cookie-based tracking (e.g. Google Analytics), this approach:

  • Is more-fragile (clearing the cache is a more-common user operation than clearing cookies, and a “force refresh” may, in some browsers, result in a new tracking ID being issued).
  • Is less-blockable using contemporary privacy tools, including the W3C’s proposed one: it won’t be spotted by any cookie-cleaners or privacy filters that I’m aware of: it won’t penetrate incognito mode or other browser “privacy modes”, though.

Moreover, this technique falls into a slight legal grey area. It would certainly be against the spirit of the law to use this technique for tracking purposes (although it would be trivial to implement even an advanced solution which “proxied” requests, using a database to associate conventional cookies with unique IDs, through to Google Analytics or a similar solution). However, it’s hard to legislate against the use of HTTP 301s, which are an even more-fundamental and required part of the web than cookies are. Also, and for the same reasons, it’s significantly harder to detect and block this technique than it is conventional tracking cookies. However, the technique is somewhat brittle and it would be necessary to put up with a reduced “cookie lifespan” if you used it for real.

[callout][button link=”http://c301.scatmania.org/” align=”right” size=”medium” color=”green”]See Demo Site[/button] [button link=”https://gist.github.com/avapoet/5318224″ align=”right” size=”medium” color=”orange”]Download Code[/button] Please try out the demo, or download the source code (Ruby/Sinatra) and see for yourself how this technique works.[/callout]

Note that I am not a lawyer, so I can’t make a statement about the legality (or not) of this approach to tracking. I would suspect that if you were somehow caught doing it without the consent of your users, you’d be just as guilty as if you used a conventional approach. However, it’s certainly a technically-interesting approach that might have applications in areas of legitimate tracking, too.

Update: The demo site is down, but I’ve update the download code link so that it still works.

×

A New Look

Well, it’s been over a year since I last updated the look-and-feel of my blog, so it felt like it was time for a redesign. The last theme was made during a period that I was just recovering from a gloomy patch, and that was reflected the design: full of heavy, dark reds, blacks, and greys, and it’s well-overdue a new look!

The old Scatmania design: very serious-looking, and with dark, moody colours.
The old Scatmania design: very serious-looking, and with dark, moody colours.

I was also keen to update the site to in line with the ideas and technologies that are becoming more commonplace in web design, nowadays… as well as using it as a playground for some of the more-interesting CSS3 features!

This new design has elements in common with the theme before last: a big blue header, an off-white background, and sans-serif faces.
This new design has elements in common with the theme before last: a big blue header, an off-white background, and sans-serif faces.

Key features of the new look include:

  • A theme that uses strong colours in the footer and header, to “frame” the rest of the page content.
  • A responsive design that rescales dynamically all the way from a mobile phone screen through tablets, small 4:3 monitors, and widescreen ratios (try resizing your browser window!).
  • CSS transitions to produce Javascript-less dynamic effects: hover your cursor over the picture of me in the header to make me “hide”.
  • CSS “spriting” to reduce the number of concurrent downloads your browser has to make in order to see the content. All of the social media icons, for example, are one file, split back up again using background positioning. They’re like image maps, but a million times less 1990s.
  • Front page “feature” blocks to direct people to particular (tagged) areas of the site, dynamically-generated (from pre-made templates) based on what’s popular at any given time.
  • A re-arrangement of the controls and sections based on the most-popular use-cases of the site, according to visitor usage trends. For example, search has been made more-prominent, especially on the front page, the “next post”/”previous post” controls have been removed, and the “AddToAny” sharing tool has been tucked away at the very bottom.

[spb_message color=”alert-warning” width=”1/1″ el_position=”first last”]Note that some of these features will only work in modern browsers, so Internet Explorer users might be out of luck![/spb_message]

As always, I’m keen to hear your feedback (yes, even from those of you who subscribe by RSS). So let me know what you think!

× ×

Looking for Wikipedia?

As you may have noticed, the English-speaking Wikipedia is “blacking out” in protest at SOPA/PIPA. This is a very important thing: SOPA/PIPA are potentially extremely dangerous bits of legislation (if you’re looking for a short explanation of why, here’s a great video).

I’m going to assume that you’re aware of the issues and have already taken action appropriate to your place – if you’re in the US, you’ve written to your representatives; if you’re in the rest of the English-speaking world, you’ve donated to the EFF (this issue affects all of us), etc. But if you’re in need of Wikipedia, here’s the simplest way to view it, today:

Accessing Wikipedia during the blackout

  1. Go to the English-language Wikipedia as normal. You’ll see the “SOPA blackout” page after a second or so.
  2. Copy-paste the following code into the address bar of the browser:

javascript:(function()%7Bdocument.getElementById('content').style.display='block';document.getElementById('mw-sopaOverlay').style.display='none'%7D)()

That’s all. You don’t even have to turn off Javascript in your browser, as others are suggesting: just surf away.

If you get sick of copy-pasting on every single Wikipedia page you visit… you can drag this link to your bookmarks toolbar (or right click it and select “add to bookmarks”) and then just click it from your bookmarks whenever you want to remove the blackout.

And if you just came here for the shortcut without making yourself aware of the issues, shame on you.

My Name Is Me

My Name Is Me. I choose to participate on much of the Internet by my full name. I say “full name”, rather than “real name”, because the term “real name” is full of loaded connotations. For example, I (still) periodically have people insist that Dan Q isn’t my real name, because it’s not the name I was born with. It doesn’t matter to them that it’s the name I’m known by to pretty much everybody (except my mother, who still calls me Daniel). It doesn’t matter that it’s the name on my passport or driving license. To them, it’s not “real” because to them, real names are either those acquired by birth or marriage, and somehow nothing else is valid. And that’s without even looking at the number of times I’ve been discriminated against because my name is “too short” for ill-designed computer systems.

That doesn’t bother me. What does bother me is that sites like Facebook and – in the news recently on this very topic – Google+ demand that full “real” names are used on the profiles of their site users. If you don’t use the name that appears on your government-issued documentation (if you have such a thing), then your accounts on these sites are liable to be closed. By the way: the same is theoretically true of your Google Profile, too, so even if you’re not on the Google+ bandwagon and you, say, use a nickname in your Google Profile, your account is still at risk.

Now, I can see the point that these policies are trying to make.  In fact, there was a time that I’d have naively agreed with them. They’re trying to make the Internet a safer, more-accountable place. But in actual fact, there’s a real risk that they’ll make the Internet a lot more-treacherous for some people. I shan’t bother listing folks who are affected, because others have done it far more-thoroughly than I ever could.

But I shall point you in the direction of my.nameis.me, where you can read a little more about these issues. Thanks.

Hash Abnib

When I relaunched Abnib the other week (which I swear I didn’t expect to have to do, until people started complaining that I was going to let it die – this genuinely wasn’t some “marketing” stunt!), I simultaneously brought back Abnib Chat (#abnib), the IRC channel.

I blame Jen for this. She told me that she missed the long-dead #rockmonkey chat room, and wanted it (or something similar) back, so I decided to provide one. Hell; if Jen wanted it, maybe other people wanted it to? And it’s an easy thing to set up, I thought.

Personally, I thought that the chat room would be a flop. I’d give it a go, of course, but I didn’t hold up much hope for its survival. When Abnib first launched, back in 2003, the Abnibbers were all students first and foremost. Now, they’ve all got jobs, and many of those jobs aren’t of a variety compatible with sitting on an IRC channel all day. And at night? We’ve got money, nowadays, and homes, and spice, and all kinds of activities that consume our lives on an evening. Many of us get what our younger student selves would call an “early night” every day of the week, and there’s always so much to do that shooting the breeze over a laborious IRC channel simply isn’t compatible with our lives any more.

Looks like I was right. Here’s the channel activity for the first fortnight of the new Abnib Chat:

#abnib participants in June 2011

Sure, the 1st of the month was busy, but not very busy: in actual fact, many of the people who were “around” were only around briefly, and one of those – Guest1332 – didn’t even identify themselves.

We’ve all got new ways of communicating now. Some folks are using Twitter (I occasionally read the feeds of those who write in a way that I’m permitted to see, but I don’t “tweet” myself). Others use Facebook (for a given definition of “use”, anyway). Others still continue to blog (that’s the medium for me: I think I’m just a little too wordy for anything less). In any case; we’re like Abnib: The Next Generation, and we’ve got reliable transporters and replicators and all kinds of cool shit, and hanging around in an IRC channel just feels kind of… backwards.

Perhaps I’ve been watching too much Star Trek recently.

Anyway – unless people object to that, too (seriously?),  I’ll be turning off Iggy later this month: so if you’ve got something important to say to him, say it soon! I’ll leave the “Chat” button on Abnib because it’s lazier than removing it, and you never know if somebody might find a use for it, but I think it’s time to declare the channel “dead”.

Every Full Moon

This is what happens when you let geeks write your billing software:

I would like to be billed... every full moon. Seriously?

From the website of Andrews & Arnold ISP.

×

Fox News on IPv6

Here’s what Fox News have to say about IPv6:

Web developers have tried to compensate for [the IPv4 address shortage] by creating IPv6 — a system that recognizes six-digit IP addresses rather than four-digit ones.

I can’t even begin to get my head in line with the level of investigative failure that’s behind this sloppy reporting. I’m not even looking at the fact that apparently it’s “web developers” who are responsible for fixing the Internet’s backbone; just the 4/6-digits thing is problematic enough.

Given that Wikipedia can get this right, you’d hope that a news agency could manage. Even the Daily Mail did slightly better (although they did call IPv4 addresses 16-bit and then call them 32-bit in the very next sentence).

Oh; wait: Fox News. Right.

For the benefit of those who genuinely want to know, one of the most significant changes between IPv4 and IPv6 is the change from 32-bit addresses to 128-bit addresses: that’s the difference between about 4 billion addresses and 340 undecillion addresses (that’s 34 followed by thirty-eight zeros). Conversely, adding “two digits” to a four-digit number (assuming we’re talking about decimal numbers), as Fox News suggest, is the difference between a thousand addresses and a hundred thousand. And it’s not web developers who are responsible for it: this change has nothing to do with the web but with the more fundamental architecture of the underlying Internet itself.

New Look, New Protocols

Oh yeah: I changed the look-and-feel of scatmania.org the other week, in case you hadn’t noticed. It’s become a sort-of-traditional January activity for me, these years, to redesign the theme of my blog at this point in the year.

This year’s colours are black, white, greys, and red, and you’ll note also that serifed fonts are centre-stage again, appearing pretty-much-universally throughout the site for the first time since 2004. Yes, I know that it’s heavier and darker than previous versions of the site: but it’s been getting fluffier and lighter year on year for ages, now, and I thought it was time to take a turn. You know: like the economy did.

This new design has elements in common with the theme before last: a big blue header, an off-white background, and sans-serif faces.
This new design has elements in common with the theme before last: a big blue header, an off-white background, and sans-serif faces.

Aside from other cosmetic changes, it’s also now written using several of the new technologies of HTML5 (I may put the shiny new logo on it, at some point). So apologies to those of you running archaic and non-standards-compliant browsers (I’m looking at you, Internet Explorer 6 users) if it doesn’t look quite right, but really: when your browser is more than half as old as the web itself, it’s time to upgrade.

I’ve also got my site running over IPv6 – the next generation Internet protocol – for those of you who care about those sorts of things. If you don’t know why IPv6 is important and “a big thing”, then here’s a simple explanation. Right now you’re probably viewing the IPv4 version: but if you’re using an IPv6-capable Internet connection, you might be viewing the IPv6 version. You’re not missing out, either way: the site looks identical: but this is just my tiny contribution towards building the Internet of tomorrow.

(if you really want to, you can go to ipv6.scatmania.org to see the IPv6 version – but it’ll only work if your Internet Service Provider is on the ball and has set you up with an IPv6 address!)

×

Updating WHOIS Records With Easily

I’ve recently undergone an ordeal with Easily, with whom a number of my domain names are registered, that involved a process so painful and convoluted that I couldn’t help but share it with you. All I wanted to do was to change the WHOIS data on some of my domains, because they were horribly out of date. Here’s the process that seems to be standard at Easily:

  1. I log in to the Easily web site to change my WHOIS information. If this were any of the other domain name registrars I deal with, this would be the only step in the process, but Easily don’t seem to think that their customers want this functionality, and so they don’t provide it.
  2. I use the contact form to send requests that they change the WHOIS information, providing all of the information necessary to facilitate the change.
  3. Easily e-mail me, informing me that requests have to be made by fax or postal mail. Muttering under my breath about this being a little like the dark ages, I send them a letter spelling out my request. The letter also includes three characters from my password, which apparently is all it takes to impress upon them that I am who I claim to be.
  4. Easily e-mail me, thanking me for my fax (it was a letter), and informing me that a change of ownership of a domain requires that a £15 fee is paid. I reply to point out that no change of ownership has occurred; although my name and my address have changed, and I can supply proof of both if required.
  5. Proof of these things isn’t required: my word as a gentleman is good enough, it seems. Easily change the WHOIS information, but mis-spell the name of my street.
  6. I e-mail Easily to inform them of their mistake. Several days later, they e-mail me back to say that they’ve corrected the typo, along with a terse apology.
  7. It turns out that they’ve corrected the typo, but somehow managed to introduce an even more significant one: now the house number is incorrect. I double-check my letter and all of my e-mails so far to ensure that this mistake couldn’t possibly be my fault, and it’s not. I e-mail Easily back and request that they have another go at typing my address correctly).
  8. A week passes. With no response, I wonder if I shall have to write another letter. Don’t forget that this is an Internet-based company selling Internet services. I send another e-mail, asking whether the previous e-mail is going to be handled any time soon.
  9. Easily reply, with no apology this time, stating that the typo has been corrected. I check the WHOIS records: it turns out that they’ve only corrected their (second) typo on one of my domain names, and not on all of them. I write back to ask when they’re planning to correct the others, and list them.

We’re coming up on one month since this ordeal started. For reference, when I used GoDaddy to do the same operation, I had it done within five minutes, and I could do it all online.

Easily have really, really gone down in my estimation.

My Firefox Window

It didn’t occur to me until somebody looked over my shoulder and commented on it, today, that I actually have an at-least slightly unusual layout for my Firefox window. I thought I’d share with you all the thinking behind the particular collection of add-ons and tweaks that go into my day-to-day web browsing:

I’m a big fan of maximising the amount of screen real estate available for browsing, minimising the chrome that surrounds it. That’s why I use the LittleFox theme. It’s not the prettiest theme around, but it’s tiny, simplistic, and works with every version of Firefox I’ve ever thrown it at. It saves space by reducing the size of icons and excess space around tabs and buttons, and it does a great job of it.

To save even more precious vertical space (and because I’m generally running at high screen resolutions, and can spare the horizontal screen space), I combine my menu bar, toolbar, address bar and search boxes into a single toolbar. You can do this by right-clicking on the menu bar and clicking “Customize…” I drop the refresh, stop, and home buttons. I never pressed refresh nor stop anyway, always using the shortcut keys (F5 or CTRL-R, and ESC, respectively), and I my homepage is about:blank. On computers running at lower screen resolutions I’ve previously used the Searchbar Autosizer add-on to tuck-away the search box when I’m not using it, but nowadays I rarely bother.

I frequently find myself with dozens of tabs open, and I loathe it when tabbed applications force me to “scroll” left and right through my tabs (I’d rather my tabs just got narrower and narrower, until only the favicon remains), so I use about:config to change the browser.tabs.tabMinWidth setting to 0, which, after you’ve restarted your browser, changes this behaviour.

In addition to the add-ons that can be seen in my status bar – ColorZilla (in the bottom-left, so not visible in the screenshot above), Adblock Plus, FireGPG, Firebug (and a few extensions), Google Reader Watcher, Greasemonkey, HTML Validator, NoScript (with noscript.firstRunRedirection set to false, to stop it’s nagging), and ShowIP, I use one further add-on to tidy up my “bookmarks toolbar”.

The Status Buttons add-on gives you the capability to drag-drop any other user interface component into the right-hand side of the status bar: I use this to move the entire contents of the Bookmarks Toolbar down into the status bar, tucked out of the way. I remove the titles from most of the bookmarks (I can identify these, my most-frequently-used sites, by their favicons), adding them only where there’d otherwise be ambiguity as to the purpose of the icon.

All of these tweaks give me a huge browsing space that works the way that I want it to. I’m a heavy user of keyboard shortcuts – I pretty much only use the mouse to click hyperlinks and the buttons in the status bar – so this kind of layout suits me very well. One of the great things about Firefox is it’s flexibility: that you can make these kinds of tweaks so easily. And hopefully if you’re a similar kind of power user you’ll take some of these tips and be able to make use of them, too.

×

Internet Explorer 8 More Popular Than 6

Today is a good day for the web. Internet Explorer 8, which actually has reasonably good standards support, is now more widely-used than Internet Explorer 6, which is horrific to code for (Internet Explorer 7 isn’t much better).

It’s always been hard to write good quality web sites that work in Internet Explorer 7 and below: generally, I’ve always taken the approach of writing sites to comply with the standards and then to put in hacks specifically to address the problems introduced by IE6 and IE7. The sooner that we can disregard these browsers, the better.

Despite the stupid marketing campaigns Microsoft’s been pursuing to try to increase adoption of IE8, I’m at least a little thankful that they’re apparently working. I’ll be so glad the next time I can launch a site and not even have to think about using <!–[if IE 6]> conditional comments.

What Not To Do When You Lose Your Mobile

Maybe this is just a pet hate that is exclusively mine, but there’s something that really gets on my nerves and it’s happened under one of the two scenarios below at least three times within the last month. It’s as if the very second you let people loose on social-networking site Facebook they immediately lose all common sense.

Here’s the scenario: you lose or break your mobile phone – I’m sure it’s happened to us all at some point or another – and as if that wasn’t bad enough, you’re stupid enough to not keep a backup of your contacts (virtually every phone can do this now, so there’s no excuse for the vast majority of people). Well, fair enough: like I said, this could happen to anybody, although you’re already due a talking-to by me about keeping your information backed up, and if it’s been stolen I’d quite like to know what information you had about me on there at the time. But in the most part you have my sympathy… so far.

How’re you going to get all those carefully-collected numbers back in your phone? Well, here are two wrong ways to do it. I’ll explain why later:

  1. Send a bulk Facebook message out to everybody you know.
  2. Create a Facebook group.

So why are they wrong?

Bulk Facebook Messages

The first and biggest reason that either of these methods are wrong is pretty fundamental, though: you’ve lost my mobile number, that’s your problem, so why don’t you make some of the effort to fix it. My mobile number is on my Facebook profile. I put it there so that you wouldn’t ever have to e-mail me if you wanted it. It’s there because improving connectivity between and sharing personal information with friends is entirely what Facebook is for. So next time you misplace your address book – which you failed to back up – why don’t you do some of the leg work and actually go to my profile and look it up for yourself.

If you can’t see it on my profile, it’s invariably because I’ve used Facebook’s (now-quite complex and powerfu) privacy tools to hide it from you because I don’t want you to have my mobile number. So there you are. If you’re on my Facebook friends list you should never, ever need to send me a Facebook message to get my mobile number.

Secondly, sending a bulk-Facebook message is wrong because it almost always leads to retards “following suit” like this:

I don’t mind getting James’ new mobile number over a Facebook message. That’s fine. I shan’t be responding, because he ought to be bright enough to get my mobile number for himself, considering it’s only one-click away. But by bulk-sending it to everybody he knows, he’s underestimated the stupidity of his other friends. About 50% of the people he sent it to sent their mobile numbers back to the list by using “Reply All.”

Reply All is the only option available, and so a new Facebook user could conceivably make this mistake. But then a handful of James’ other friends make the same mistake, having seen one of them do it already. Wait, did I miss something? Are these people all patients at some mental hospital that James used to volunteer at, or something?

I don’t know who any of these people are, aside from the fact that they’re James’ other friends. I’m only permitted to read the profile of one of them, and he isn’t sharing his mobile number with me there, so I can only assume that they don’t want me to have their number. But then they’ve just turned around on that idea and given it to me. What?

I’m half-tempted to set up a handful of fake Facebook accounts just so that I can send a message back to each of the idiots like this:

I Need All Your Mobile Numbers

Between You, An Identity Thief, A Stalker, Somebody You’ve Never Met, Their Ex-, Every Man, and His Dog.

I’ve lost my mobile (again!) and can’t be bothered to look up your numbers on your profiles or contact you individually. Please use the “Reply All” form below and tell me and all the other people in the list above exactly how to contact you and harass you whenever we get bored.

Facebook Groups

The other, even more irritating way that people handle this self-inflicted (let’s face it, paper and pen is a backup if there’s no other way) tragedy is by creating a Facebook group exclusively for the purpose of re-harvesting their friend’s numbers. I’m sure you’ve all seen this happen at least once.

And it happens a lot: log in to Facebook and search for “lost mobile” in the Groups list. You won’t ever find out how many idiots do this, because Facebook only lists the first few hundred results. But there are lots. Lots and lots.

The first thing that’s wrong with this approach is an issue which I’m sure I’ll be one of very few people to care about, but it’s not the biggest problem: Facebook “Groups” are, by definition, according to Facebook’s own documentation, collections of “people with similar interests” and “places for discussion.”

I’ve never joined one of these “I’ve lost my mobile!” groups, because:

  • I’ve never lost my mobile.
  • Even if I had, I wouldn’t realy say I have an interest in lost mobiles. I have no intention to discuss what having lost a mobile is like, or even what my friend having lost their mobile is like. And I’m pretty sure that isn’t what they want, either.

Not only is creating a Facebook group a mis-use of the service – this isn’t what groups are for! – but they suffer from all the same problems as Facebook bulk-mailing all your friends (i.e. if they reply, they all see each others’ numbers) but even worse. Most people create these groups but don’t make them “secret,” so anybody can join. Want a few hundred numbers to sell to an SMS-spammer? Just browse Facebook for awhile. Worse still, these groups don’t disappear until (after) every single member has left. So your phone number, which you stupidly put in the group description (if you’re the idiot who lost your phone) or on the wall of the group (if you’re one of their even-bigger-idiot friends), will be visible to pretty much any Facebook user, indefinately. Give yourself a pat on the back. I suggest using an ice pick.

What Little Timmy Should Have Done

Never let it be said that I’m overly negative when I criticise morons. I’m more than happy to educate them and I won’t even demand the right to use a heavy, blunt object to help the knowledge sink in.

Here’s what you should be doing in order to show off your uncommon sense. You can start today!

Back Up Your Mobile Phone

Just stop and think for a moment what your mobile phone is worth. I don’t mean the cost the insurance company will pay when you drop it in a pint of cider a week on Friday, I mean the value of the data inside it. How long would it take you to put all those numbers back in? If you’re a heavier user of the geekier features of modern phones: what about all the photos, e-mails, text messages, music, and the carefully-tweaked settings that make the icons have a purple background and that Crazy Frog video ringtone?

  • Most modern mobiles can be connected to a PC by a cable (which sometimes comes free with the phone) or by Bluetooth, and free software (often from the phone manufacturer’s website) will let you make a backup copy of everything on your device. It’ll take seconds, and doing it as infrequently as four or five times a year will save you a universe of hassle. Just look for a feature that will enable you to read all the data from the screen of your PC if you need to – for example, if your replacement phone isn’t compatible with the data from your broken old handset.
  • Pretty much every mid- or high- end Nokia, Motorola, and Sony Ericsson handset and some LG and Siemens handsets support a technology called SyncML (there are links to lists of compatible phones at the bottom of that page). Using this technology and a free on-line provider like many of these ones, you can back up your entire address book to a safe online repository over the Internet. Sure, if you’re on Pay-As-You-Go you’ll pay a few pence to do an Internet upload, but isn’t it worth it even if you just consider that the price of insuring your data?
  • Even if you’re using an ancient handset, consider keeping a paper backup (little black books are very affordable) or a typed-up list in a spreadsheet (Google Docs provides a free online spreadsheet). Or, if virtually all of your friends are on Facebook or another social networking site that allows the exchange of contact details, encourage them to keep their mobile numbers on their profile; suitably locked down to “friends only” (or even just to specific friends), of course.

What To Do When It All Goes Wrong

Everything goes tits-up from time to time. Suppose you lost your phone in a house fire that destroyed the PC the backups were on, too. Or maybe your phone got stolen and the new “owner” was so malicious he used your SyncML connection (if you’d saved your password on the phone) to overwrite all of your online backups with pictures of Lolcats. Or perhaps you didn’t keep backups at all (so long as you promise to keep backups next time, it’s not so bad – we all have to learn the hard way once, I’m sure, how important backups are). What should you do?

First: take responsibility. There is always something you could have done to keep a better backup. Therefore, it’s your job to do as much of the legwork of getting your numbers back as you can. Don’t make it your friends’ problem. Go through your friends’ Facebook profiles and retreieve as many phone numbers as you can before you start bothering them.

Second: get numbers in a sensible way. If you have a few close circles of friends, it’s pretty trivial nowadays to Bluetooth/MMS/Infared hundreds of contacts from phone-to-phone, and this can be a great way to get yourself re-connected. Call up Barney, and say “Hey, Barney; let me buy you a pint tonight and take a copy of everybody in your address book – I’ve been an idiot and I didn’t keep a backup before I lost my phone the other week.” Barney’ll drink his pint and press some buttons on his phone while saying things like, “Do you know Robin? Marshall? Lily? Have you met Ted?” and these people will magically appear in your address book.

There’s almost certainly be people you can’t re-get the numbers for in this way, but you can still be sensible about it. Send messages individually to those few people and ask for their numbers, but not before double-checking that you actually need them. If you can’t think of a reason you’ll ever call them within the next year, why are you carrying around their number anyway? Unless they’re somebody you’d call “in an emergency” you can always look them up when you need them. That way, you won’t spend you entire time with a number in your phone that could go out of date (people change numbers all the time) and you’d never know until you came to phone them, six years down the line, and you’d have to look them up anyway. Save yourself (and them) the bother and keep them out of your book. It’s a liberating experience to tidy up your contacts list.

And finally: if you get a new mobile number with your new phone, drop a text message to everybody who might want to know it, but make sure you say who you are because you won’t be in their address book with your new number, yet. The number of text messages I’ve got in my life from a number unknown to me that read “Hey there! This is my new number! Bye!” is staggering.

Some people are just too stupid to be allowed mobile phones.

ICANN Invent A Whole Universe Of Mess

In case you hadn’t heard/didn’t care, ICANN have authorised the creation of arbitrary privately-controlled top-level domains. So what does this mean?

Well, the happy hippy theory fun about it all is that suddenly there’s the capacity for pretty much anybody (well, anybody with a particularly deep wallet, and – for now – a demonstrable business plan) to set up their own top-level domain. A top-level domain is the bit at the end of a domain name, like .com, .net, or .org. The idea is that this will increase the number of providers from whom you, as a consumer, can choose to purchase your domain from, as well as giving you more choice – someday, I’ll probably get the opportunity to buy dan.q, for example, or scatman.dan.

Of course, it’ll take a long, long time before people start understanding that these things really are domain names. There’s still a certain stigma attached to not being a .com, because many web users will guess the dot-com domain names first. The success of the “no www.” campaign has been hampered mostly because people do think, in general, that web site addresses have to start with www. and have to end with .com, .co.uk, or another one of a handful of extensions they’re familiar with. If Jo Public sees e.mail written on an advertisement without (or perhaps even with) a http://, www., or both, in front of it, they won’t have a clue that what they’re looking at is a domain name. And how often do you actually use a .biz or a .mobi, and they’ve been around for a while now?

A bigger problem, though, is the capacity for phishing attacks. Apart from their ability to sue my arse off, what’s to stop me becoming the registrar for .microsoft, .paypal, or .natwest. If I sent a large spam attack out suggesting that people get a critical update from https://www.windowsupdate.microsoft/, I’ll bet that at least 50% of the people who click the link will go on to download whatever malware I want them to and become part of my zombie network.

It’ll only take one such event – and perhaps less – for ICANN to start being very, very careful about who it gives top-level domains to. And with all of the applications they could potentially get, they’ll quickly get bogged down in administering the top-level domain system. There’ll be backlogs of months or even years on new top-level domains, a lack of trust of them, and people will still continue to play with .coms for decades to come.

It’ll all work out in the end, I’m sure (although I anticipate a punch-up between ICANN and New.net – which ICANN will win, of course – in the near future). But I’m just not sure we should be letting the unwashed masses loose on their own TLDs quite yet.

Firefox 3 “Download Day”

Download Day 2008

Downloaded your copy of Mozilla Firefox 3 yet to help them make the world record? I’ve been using Firefox 3 since the early betas and I’ve got no qualms about recommending it wholeheartedly. The awsomebar is simply that: awesome, the speed and memory usage have become far better than the previous version, and the care and attention that have gone into the little things – like the fact that it now asks you if you want to save passwords after you’ve seen if they were correct, not before – really do make this the best web browser I’ve ever used.

Go download it already.