This special chapter in my series of essays on Robocars describes a fictional week in the Robocar world, with many created examples of how people might use Robocars and how their lives might change.

If you haven't been following my essay on Robocars, this may be a good alternate entry to it. In a succinct way, it plays out many of the technologies I think are possible, more about the what than the how and why.

For part seven of my series on Robocars, I now consider the adjunct technology I am calling Deliverbots -- namely robot driven trucks and delivery vehicles, with no people inside. These turn out to have special consequences of their own. Read:

Deliverbots

For part six of my series on Robocars, consider:

When can robocars happen?

I discuss what predictions we can make about how long the Robocar future will take. While there are many technological challenges, the biggest barriers may be political, and even harder to predict.

For part five of my series on Robocars, it's time to understand how this is not simply a utopian future. Consider now:

The Downsides of Robocars

Robocars will suggest a great number of possible changes in the way we design and market cars. I now encourage you to read:

Automobile design changes due to Robocars

For part three of my series of Robocars, now consider:

Roadblocks on the way to Robocars

A lot of obstacles must be overcome before Robocars can become reality. Some we can see solutions for, others are as yet unsolved. It's not going to be easy, which is why I believe an Apollo style dedication is necessary.

In part two of my series on Robocars, let me introduce:

The Roadmap to Robocars

My most important essay to date

Today let me introduce a major new series of essays I have produced on "Robocars" -- computer-driven automobiles that can drive people, cargo, and themselves, without aid (or central control) on today's roads.

It began with the DARPA Grand Challenges convincing us that, if we truly want it, we can have robocars soon. And then they'll change the world. I've been blogging on this topic for some time, and as a result have built up what I hope is a worthwhile work of futurism laying out the consequences of, and path to, a robocar world.

In light of my recent studies into transportation energy efficiency I've learned a lot more about the energy budget of the USA and the world.

Sadly, I must report that after our initial success in getting the members of the House to not grant immunity to telcos who participated in the illegal warrentless wiretap program which we at the EFF are suing over, the attempt to join the Senate bill (which grants immunity) to the House bill has, by reports, resulted in a so-called compromise that effectively grants the immunity.

As part of my research into robotic cars, I've been studying the energy efficiency of transit. What I found shocked me, because it turns out that in the USA, our transit systems aren't green at all. Several of the modes, such as buses, as well as the light rail and subway systems of most towns, consume more energy per passenger-mile than cars do, when averaged out. The better cities and the better modes do beat the cars, but only by a little bit. And new generation efficient cars beat the transit almost every time, and electric scooters beat everything hands down.

I want to expand on my proposal to standardize connectivity for devices in hotels. Let's add to that and develop a regimen of having bluetooth keyboards everywhere. Every hotel room should have one (or the hotel should at least have one to loan you at the desk.) They should be in every cafe, on the train and every company meeting room and lobby.

They should be on the street, in kiosks. They should be at the train station. Everybody should have one at their house, for guests. And many other places.

We're moving to smaller and smaller portable devices. Not just keyboard-less iPhones and PDAs -- the new rage is ultra-mobile laptops with reduced size keyboards. We want our devices to be smaller, but there's one thing you can't shrink and keep fully usable, and that's the keyboard. Yes, people get fast on their tiny blackberry keyboards, and yes there have been clever inventions like laser projected keyboards, inflatable keyboards and the much-missed butterfly keyboard, but the small ones just can't cut it.

The small screen we seem to deal with. And via goggles or projection, there are ways to make a large screen on a tiny device if we try hard enough. But solving the typing problem requires some grander change, like perfect speech recognition, or alternate ways of typing.

A subject of debate in environmental circles revolves around whether the successful 70s opposition to nuclear power was a wise idea. At the time, it was never thought of as a choice between nuclear and coal, it was thought of simply as fear of the dangers of nuclear. Unexpectedly, it ended up being a push for coal, which of course kills far more people and emits more radiation than U.S. nuclear plants ever have.

If you run a web site of reasonable popularity, you probably get invitations to sign up for ad networks from time to time. They want you to try them out, and will sometimes talk a great talk about how well they will do.

I always tell them "put your money where your mouth is -- guarantee at least some basic minimum during the trial."

Most of them shut up when I ask for that, indicating they don't really believe their own message. I get enough that I wrote a page outlining what I want, and why I want it -- and why everybody should want it.

Hard disks fail. If you prepared properly, you have a backup, or you swap out disks when they first start reporting problems. If you prepare really well you have offsite backup (which is getting easier and easier to do over the internet.)

One way to protect yourself from disk failures is RAID, especially RAID-5. With RAID, several disks act together as one. The simplest protecting RAID, RAID-1, just has 2 disks which work in parallel, known as mirroring. Everything you write is copied to both. If one fails, you still have the other, with all your data. It's good, but twice as expensive.

RAID-5 is cleverer. It uses 3 or more disks, and uses error correction techniques so that you can store, for example, 2 disks worth of data on 3 disks. So it's only 50% more expensive. RAID-5 can be done with many more disks -- for example with 5 disks you get 4 disks worth of data, and it's only 25% more expensive. However, having 5 disks is beyond most systems and has its own secret risk -- if 2 of the 5 disks fail at once -- and this does happen -- you lose all 4 disks worth of data, not just 2 disks worth. (RAID-6 for really large arrays of disks, survives 2 failures but not 3.)

Now most people who put in RAID do it for more than data protection. After all, good sysadmins are doing regular backups. They do it because with RAID, the computer doesn't even stop when a disk fails. You connect up a new disk live to the computer (which you can do with some systems) and it is recreated from the working disks, and you never miss a beat. This is pretty important with a major server.

But RAID has value to those who are not in the 99.99% uptime community. Those who are not good at doing manual backups, but who want to be protected from the inevitable disk failures. Today it is hard to set up, or expensive, or both. There are some external boxes like the "readynas" that make it reasonably easy for external disks, but they don't have the bandwidth to be your full time disks.

RAID-5 on old IDE systems was hard, they usually could truly talk to only 2 disks at a time. The new SATA bus is much better, as many motherboards have 4 connectors, though soon one will be required by blu-ray drives.

I do enough photography that people ask me for advice on cameras. Some time ago I wrote an article about what lenses should I buy for a Canon DSLR which has turned out to be fairly popular. The thrust of that article, by the way, is to convince you that there is only minimal point in buying a DSLR that can changes lenses and getting only one lens for it, even if you plan to get another lens later (after your camera has depreciated plenty without using its real abilities.)

Recently, I wrote about thedata deposit box, an architecture where applications come to the data rather than copying your personal data to all the applications.

Let me examine some more of the pros and cons of this approach:

Recently we at the EFF have been trying to fight new rulings about the power of U.S. customs. Right now, it's been ruled they can search your laptop, taking a complete copy of your drive, even if they don't have the normally required reasons to suspect you of a crime. The simple fact that you're crossing the border gives them extraordinary power.

We would like to see that changed, but until then what can be done? You can use various software to encrypt your hard drive -- there are free packages like truecrypt, and many laptops come with this as an option -- but most people find having to enter a password every time you boot to be a pain. And customs can threaten to detain you until you give them the password.

There are some tricks you can pull, like having a special inner-drive with a second password that they don't even know to ask about. You can put your most private data there. But again, people don't use systems with complex UIs unless they feel really motivated.

What we need is a system that is effectively transparent most of the time. However, you could take special actions when going through customs or otherwise having your laptop be out of your control.