Slash the Slashes?

Have you looked at a web address lately? Go ahead, look up a few inches and really study the address. Do you understand the information it is trying to communicate? Most people understand that a URL (Uniform Resource Locator) points to a location on the Interwebs (bonus points if you know that DNS (Domain Name Service) ties URLs to static IP addresses (or sockets, if you combine the IP address with the local port number)). It goes from general location to specific location from left-to-right, each location level separated by forward slashes. If you know all that, you're in good shape. Do you know what everything before that means? Many people know that HTTP stands for Hyper-text Transfer Protocol, and that it is the protocol on which the idea of hyperlinks (the colored, underlines parts of the Interwebs) is built on. Some of the real geeks out there might even know that the colon generally means "The following is what we are going to communicate using the previously mentioned protocol." However, I imagine that the vast majority of the Interwebs-using world has no idea why there are two forward slashes after the colon.

It doesn't make sense. After all, anything after the colon is already aprt of the URL, looked up by DNS and matched to an IP address. Where does the colon fit in?

Tim Berners-Lee (or, I should say Sir Tim Berners-Lee), official inventor of the Internet (It wasn't Al Gore, sorry) recently divulged in an interview with the NY Times that the forward slashes are something that he would do away with if he could invent the Internet all over again. He's sorry about the error, and he regrets the amount of trees that died, the amount of finger strain, and the amount of syntax errors induced by the addition of the nearly useless and now ubiquitous forward slashes.

The forward slashes are basically a way of saying "from here on, I will be giving you an address for a file location." Well, duh. That's what the colon after the protocol is telling you. It's obviously redundant. And, considering how many times any web address has ever been typed on a keyboard, that's an insane amount of wasted forward slashes. I don't think anybody's done a study on it yet, but I can give somewhat of a crack at it.

According to Nielsen, Google was getting 5.1 hits per month as of 4/2008. That's 10.2 billion forward slashes just from google alone. Considering that Google had 62% of searches in that month, that means roughly 16.4 billion forward slashes were used on search engines in April of 2008. Now, let's assume we're using UTF-8 encoding (just for kicks and giggles. You're most probably using ISO-8859-1 (Western Languages) but they aren't all that much different). That means there are 8 bits of memory used for every character. That brings our calculation to roughly 131 billion bits of forward slashes used by search engine URLs in April of 2008. That's roughly 15 Gigabytes of forward slashes. Assuming that number stays roughly the same through 2008 (it doesn't, but remember we're just kicking and giggling), that's 180 GB of forward slashes in the year 2008 (1.571 trillion bits). That's just in 2008, and just for search engine URLs. No Facebook or MySpace. That number barely scratches the surface when it comes to forward slash wastefulness. Consider that eastern countries use bigger, more robust (read: memory hogging) character sets, and that every single time someone uses the Internet, two forward slashes are used, and you'll finally start to understand the staggering implications of a simple apology of "Ya, we probably didn't need that." And considering that the syntax is far too ubiquitous to ever be changed, this waste will only proliferate.

So, next time you see those forward slashes adorning your browser's header, think of the trees. Think of your children, and your children's children, who might not have clean air and water due to the sheer waste of energy caused by irresponsible use of the double forward slash. In fact, every time you contribute your forward slashes to the horrid institution of forward slash waste, you kill a puppy 5 generations from now. A puppy dies every time you use the Interwebs.

So, I say "No, we don't forgive you, Sir Tim!" We don't condone the murder of future puppies, and we don't condone people who contribute to that brand of evil.

Just letting you know.


T-Mobile Is Fail

T-Mobile, in all its supreme horribleness, has managed to lose all backed-up data from their customers' Sidekick smartphones. All of it. T-Mo is blaming Microsoft/Danger (the company responsible for the server hardware) for letting the servers fail, but nobody on T-mobile's customer list really cares whose fault it is. Bloggers around the 'sphere have been calling for the fall of cloud-based data storage, due to its obviously unreliable service, and people are now finally listening to the paranoid claims. While I feel for the victims of the T-Mobile Data Loss Tragedy (hitherto called "10/13"), and my heart really does go out to the family and friends of the victims, this is not the time or place to rail against cloud data storage.

Firstly of all, geeks around the Interwebs are still scratching their collective heads. How on digital Earth could a reputable company screw up basic backup practices so flagrantly. Even the smallest IT shop in the tiniest company (protip: not Microdoft/danger) knows that you have bakcups, busckups of backups, and then you have off-site backups of sensitive, mission-critical information (nuclear missile codes is a prime example) just in case of an ICBM strike from North Korea. For many companies, it has become harder to get rid of data than it is to keep it, as many federal law breakers have come to realize. If anything, Microsoft/Danger should have had at least something to show for their presumed basic backup competence. But no, they can't recover a single phone number for a single customer. It's all gone. Do you now realize how insanely ludicrous and suspicious this all is? Some have suggested that there was a corruption in one of the databases that spread silently, so even the backups got infected. That claim still holds no water (it sunk about an hour ago) because they should have had incremental historic backups that should have all the data from before the current database went down. The only plausible theory thus far is that the conglomeration of the Soviets and aliens from Mars hacked into the mainframe a la every episode of 24, and totally uploaded a virus all up in there.

My point is that this is an anomaly. This is by no means a normal data loss situation and should not be treated as the norm. It's very much like saying "My hard drive failed. DOWN WITH LOCAL STORAGE!!" Everything fails. Especially hardware. That's why G-d created automated system backups. If Microsoft/Danger is especially evil when it comes to backing up their customers' data, it's your fault for giving your data to a company with the word "DANGER" in its name. Someone in marketing needs to be fired for that naming fail. But seriously, just because one company is seriously compromised enough that every backup of the data is gone, then that company needs to go away. You can't cry about the failure of the cloud every time there's data loss. There's no such thing as a perfect system (except for mine), and the Interwebs are no different. If  storing your data in the cloud is cheaper, more efficient, and viable from an IT infrastructure standpoint, there's no reason you can't do some proper research and find a company that is reliable enough not totally screw you over.