Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror

Comment: Re:Slippery slope, blame the driver (Score 1) 360

This isn't a slippery slope.
The driver pushed the gas pedal hard, the car obeyed.
It's the correct response, even if it hypothetically had pedestrian detection.
How is the car to know that the driver wasn't caught in some sort of dangerous carjacking situation that warranted the driver's actions?
Until we get AI that can make decent moral decissions, it should defer to the driver's judgement.

Comment: Re:Another reason my first new car will be a Tesla (Score 2) 360

Why can't all cars be more like a Model S and ship with the most relevant technological developments "out of the box"

Which out-of-the-box Model S are you talking about?
The one without the cruise control, lane assist, self-parking or adaptive suspension options? (which is all of them).

Comment: Re:Defective (Score 1) 360

What is "autonomous movement"? If I put my car in first gear and release all the pedals, it'll start moving forward without me touching any part of the car.
In this particular case we're talking about "autonomous breaking"; a safety feature.
If you make an auto manufacturer 100% liable for any additional safety feature not working 100%, they simply won't implement any additional safety feature at all.

Also, my sig seems to apply to parent's comment.

Comment: Re:What is the difference of these 2 positions? (Score 4, Funny) 144

by mwvdlee (#49773817) Attached to: Apple Design Guru Jony Ive Named Chief Design Officer

Indeed, for Jony Ive is the God of rounded corners.
Nobody can make corners quite as rounded as Him.
He is the Angle and the Radius of corner roundation.
Fear ye square and bevelled, for thou art condemned to the outer corners of the un-Apple.
Praise the Omniroundcornerand's name.

Comment: How could you protect against this? (Score 2) 173

You could encrypt all the data in the database, but that would only protect you from somebody able to access the database but not any of the decryption code (somewhat unlikely).

Assuming full access to the database and code, is there any way to protect against being able to link identification with the rest of the personal information.

I can only come up with the obvious client-side encryption, but will the network as a whole still be able to use the data as it's supposed to (in this case; find adult friends)?

The solution of this problem is trivial and is left as an exercise for the reader.

Working...