Eventually the effective dose exceeds the lethal dose

Except that in only a few countries are you able to go that far. Most places require you to stop short of the lethal dose and live in excruciating agony for as long a your systems (and technology) will support you. Have a nice day.

Another facet of this is that the devices can be tracked, whether or not the user is using it or making a call. As long as it is on and available to receive a call (communicating with the base) it can be identified and a coarse location determined. If it were me in the law-enforcement role, the way I would use this is to identify devices in an area of interest (the protest locations) and record the identifiers over a series of days/nights. Eliminating devices which did not appear during a majority of the observed days lets you focus on the core group of people present at the events. (This will include media, people who live/work in the area, police and civil support themselves, etc.) Some careful trimming of the data by time of day will help reduce the "noise". Then you have a subset to focus investigations on. If I were on the other side, I'd make good use of WiFi (fixed and hotspots), VoIP, and "burners" (prepaid phones bought with cash and no ID - don't know if that's possible in all countries). Those are easy protections. Defense can get more technical and fiddle with the device IDs, but that likely crosses a line - and I'd want to be pure as the driven snow if I was at high risk of being arrested at some point.

First off, Congratulations! Including files related to my 4 year old, I've got about 100GB of media. I recommend the 3-2-1 Backup method: 3 copies of the data, on 2 different drives/media, 1 of them off-site. I do this by having a "primary" copy of the data on a machine at home, which I copy to a backup drive periodically. The primary also gets rsync'd nightly to a cheap eeePC with a 1 TB USB drive in a closet at my parents place. All this is running Linux, but you can manage with other OS's. Bonus #1: They get local access to the media via an SMB read-only share. Bonus #2: I gave them a writable share for THEIR data, which is rsync'd nightly to our place as a backup. You can do this with friends, etc. Being on the same ISP helps as the sync traffic can stay in the provider cloud. I've also used Amazon S3 (~US$13/month for 100GB of non-redundant storage) and I still use rsync.net for more limited critical documents (encrypted), though their price doesn't scale well for large, static data sets (they don't charge for bandwidth so relatively small but dynamic data is a good fit).

No, s/he's talking about the ECU dropping the injector dwell to zero because the accessories can be run from the inertia of the car. Engine revs come from the wheels/transmission, not combustion, actually a lot like a hybrid's regenerative brakes. You can actually watch this happen in reverse when you get close to stopping because the revs are too low to sustain drive and the ECU starts fuel flow again, causing a slight blip in RPM as it transitions to idle. (This is also when the transmission disengages.)

Wait a minute, I think I've seen this before...

"The future could see smartphone's containing as much processing power as your current desktop."

"So I'll have to wait 5 minutes before my smartphone has finally booted?"

Yup. Same as it ever was. Next up: Implant boot times.

Some provide a choice: company laptop with maintenance or your own device but you do the maintenance.

I can't wait for this, and the ensuing lawsuits. Am I lawsuit happy? Perhaps, but the first time client PII or similar data is lost through this practice, there will be a lawsuit faster than you can say "failure to perform due diligence".

That said I believe there are "right" ways to do this. Virtual machines, remote desktops, mobile apps, sandboxes, etc. My company has no problem buying an employee a Mac or Linux machine or iPad when the work really requires it. With apologies to MasterCard, for everything else there's VirtualBox.

I say we fix this oversight from 30 YEARS AGO by developing a new addressing scheme, compatible to an extent with the original, that can be overlaid on the network and distributed more evenly around the world. Oh, and make it bigger, too, so we don't revisit this problem for a while. Who's in?

The IntelliDrive program has been working on this for a while, and the OEMs are starting to test this on the road. You can look at some concept videos.

The RF band is around 5.4GHz, allocated specifically for short-range transportation communication.

I don't like the backscatter machines OR the pat-downs, but I saw this and it raised some questions. Now I'm a Schneier fan-boy, and we even work in the same field, but let's take the NY 9/11 attack as a comparison (2819 according to NYMag).

So for the scanner to be deadlier than just that attack, it would have to kill 16 extra people a year for a bit over 176 years. Am I missing something?

For further comparison there's an 9/11-equivalent loss of life on US road every 27 days (using 2008 numbers from the 'pedia.) Maybe it's me, but I don't see it being more deadly than terrorists. That said, I'm not going in them - radiation is cumulative. RF (the MM-wave scanners) is not.

"Eve Tokimatsuri" from Megazone 23 came out in March of 1985. Note this is an Anime OVA, and I suspect influenced the desires of the folks working on Hatsune Miku. My only remaining questions are when the aliens attack our Dyson Sphere-like satellite city, and where to get my Garland prototype.