Flutterby™! : NTSB calls for speed limiters

Next unread comment / Catchup all unread comments User Account Info | Logout | XML/Pilot/etc versions | Long version (with comments) | Weblog archives | Site Map | | Browse Topics

NTSB calls for speed limiters

2023-11-16 21:04:37.057791+01 by Dan Lyke 0 comments

NTSB Calls for Technology to Reduce Speeding in All New Cars. I wrote on Metafilter:

I think that, whatever the privacy issues, we're headed towards a future where we have time and location based mileage taxes, and it makes perfect sense to integrate that with speed limit enforcement, but...

We've been trying to do traffic calming efforts in our neighborhood, and our town's public works department is trying to get out in front of this as well. I've been aware of the fact that "furniture" (sign and light posts, etc) in the "recovery zone" (shoulders and sidewalks) are breakaway, designed to not injure motorists should they swerve into them.

We were recently measuring the geometry of a new roundabout in an other neighborhood to see if it could be applied to our neighborhood, and among the neighbors who stopped to chat and sing the praises was a guy who said "yeah, I got this car cheap because some teenager drove over the roundabout and ripped the oil pan out".

And I am now 1000% behind automated speed enforcement through passive infrastructure. Let's build shit to *seriously* fuck up a car when drivers deviate.

Let's put up bollards to narrow lanes.

The design goal should be that when drivers exhibit unsafe traffic behavior, their cars are destroyed.

So, yes, move forward NTSB, but also work with your local traffic engineers. There's a lot that can be done at the local level in concrete and asphalt as roads are maintained.

[ related topics: Children and growing up Interactive Drama Politics Privacy Invention and Design Current Events Work, productivity and environment Automobiles Graphic Design Government ]

comments in ascending chronological order (reverse):

Add your own comment:

(If anyone ever actually uses Webmention/indie-action to post here, please email me)

Format with:

(You should probably use "Text" mode: URLs will be mostly recognized and linked, _underscore quoted_ text is looked up in a glossary, _underscore quoted_ (http://xyz.pdq) becomes a link, without the link in the parenthesis it becomes a <cite> tag. All <cite>ed text will point to the Flutterby knowledge base. Two enters (ie: a blank line) gets you a new paragraph, special treatment for paragraphs that are manually indented or start with "#" (as in "#include" or "#!/usr/bin/perl"), "/* " or ">" (as in a quoted message) or look like lists, or within a paragraph you can use a number of HTML tags:

p, img, br, hr, a, sub, sup, tt, i, b, h1, h2, h3, h4, h5, h6, cite, em, strong, code, samp, kbd, pre, blockquote, address, ol, dl, ul, dt, dd, li, dir, menu, table, tr, td, th

Comment policy

We will not edit your comments. However, we may delete your comments, or cause them to be hidden behind another link, if we feel they detract from the conversation. Commercial plugs are fine, if they are relevant to the conversation, and if you don't try to pretend to be a consumer. Annoying endorsements will be deleted if you're lucky, if you're not a whole bunch of people smarter and more articulate than you will ridicule you, and we will leave such ridicule in place.

Flutterby™ is a trademark claimed by

Dan Lyke
for the web publications at www.flutterby.com and www.flutterby.net.