Body cameras should encrypt their contents as they capture them.
Records at the station house should be dumps of the encrypted data.
The keys should be stored elsewhere, available by subpoena or warrant.
In addition to making body cam data useless for mass surveillance, wearers can be required to have the camera running all the time - nobody gets to see officers in the bathroom unless they are accused of beating someone up there.
I use it to tell me when the damned Government-required anti-virus scanner starts up in the background.
That's when the time remaining value drops by about half.
I did, when we talked about WhatsApp back in 2014.
Worked and lived in Mountain View in the late 1980's; visited the peninsula many times since then.
Got out when I realized that I would not be able to afford a house unless I hit the startup lottery.
Also, realized I did not want to rear children in either side of Palo Alto (east or west).
Still, having some direct experience of Silicon Valley has been useful ever since; it helped me get every job I've had since that time.
For ages, there have been less problems with malware on Macs than on Windows PCs.
For ages, one main excuse for this has been "more people use Windows, so it's naturally a bigger target". Technical arguments about vulnerability are dismissed by people who make this argument.
OK, so now in Chromebook we have a new malware target which may be both bigger than the Mac market AND theoretically less vulnerable.
This could be amusing...
(See the Criminal Investigation section)
Don't these legislators (or anyone on their staffs) know anything about what they're attempting to restrict?
That's the way we handle information that may end up as evidence in court.
That's the way we should handle police body cam video. ALL OF IT.
... when they start using version-control systems on legislation.
The ability to track who wrote every line of a big law would be a revelation to the public, which is why it will never happen.
Google is no doubt watching this experiment very carefully...
If I were Sergey Brin, Larry Page, or Eric Schmidt, I would be looking into this as a way of taking the drudge work off my desk so I could do more of the fun, world-changing stuff.
If data is on my personal server and the US government wants to see it, they need a warrant.
If it's on a cloud server, they don't.
Two principles to be aware of when you are on a bike in auto traffic:
1. You are in the most danger when auto traffic crosses your path. Intersections are the most obvious example. Especially dangerous are turning lanes and off-ramps when you are going straight - cars that are changing lanes or preparing to turn are looking for other cars, not bicycles.
2. If you hear a siren, get off the road NOW. Cars will be trying to get out of the way of emergency vehicles, and looking to avoid other cars, not bicycles.
I've been a short-distance commuting cyclist since 1994. I've been hit once in traffic - at an off-ramp, by a car that was getting out of the way of a fire truck.
I live in a blessed neighborhood that has both FIOS and Comcast, so I can credibly threaten to switch. I almost went for Comcast recently; they offered me
105 Mb down + basic cable + phone
for the same price as Verizon's
50 Mb down + basic cable + phone
The deal-breaker was Comcast's up speed is 10 or 20 Mb, and Verizon's is 50 Mb. Not in this age of video calling and torrenting, thankyouverymuch.
Comcast's infrastructure is still apparently fundamentally biased toward broadcast. Verizon at least understands communication should be two-way.
is a rack-mounted server, and getting an A/C balance that keeps the servers cool without freezing the humans is a problem.
Honesty is for the most part less profitable than dishonesty. -- Plato