Colorado Legalizes Another Vice: Texting While Driving
Distracted driving laws and the crusade against distractions in the car have a history that goes back many years. Generally, the trend has been to try to ban each new distraction that comes along, and to seek to place the blame on device makers and automakers for not figuring out how to reliably disable those devices. There was even a ruling in California that made it illegal for a driver to use a mapping app. But now, the state of Colorado has done something unexpected, and perhaps even… reasonable.
The state has made it legal to text while behind the wheel, unless it’s done in a “careless or imprudent manner.” While the new law does give a reprieve to those who use their phones in a safe manner (e.g., while at red light, or stopped in traffic), it also significantly increases the penalties for those who run afoul of the “carelessness” provision. As we’ve written before, there are many potential distractions inside a vehicle, and eliminating them all would be impractical, if not impossible. So this new law puts the focus on the dangerous behavior instead of the potential distraction itself, holding the driver responsible for unsafe actions.
Before now, any text messaging or manual data entry by a motorist was prohibited. “The simple fact is that if you are texting while driving but not being careless, it’s no longer illegal,” said Tim Lane at the Colorado District Attorneys’ Council.
While the change does appear to have support among law enforcement, it is still understandably controversial.
“The focus of the law isn’t for people who are stopped at stop lights or pulled over on the road texting,” said Mike Phibbs, the legislative chair for the Colorado Association of Chiefs of Police. “I think it’s actually helped clarify the issue and targets what’s really causing the problem.”
But officials acknowledge that it is now harder to issue citations to drivers for texting while driving — and that the law opens the door to more legal challenges in court.
There is a reasonable concern that having what amounts to a conditional ban will embolden people to push the limits of what is acceptable behavior, or just make it more likely that people won’t worry as much about texting while driving, since it is now “legal.” However, the hope is that the severity of the penalties for the illegal behavior — even for first time offenders — will make drivers more cautious in how they use their phones. Either way, it’s good to see a focus on actual bad behavior, rather than a broad ban on activity that might be bad, depending on circumstances.
New FIRST WORD
Because I am the firstiest wordiest!
Re:
This should be fixed now. The Insider Chat was confusing FireFox's "Readability" JavaScript code, which was deciding that the chat content, not the post itself, was the main content of the page.
Re:
There is something going on with the font sizes on mobile, especially with respect to the headlines. We’ll get that sorted out. I’m not sure what you’re seeing with the left margin. I do see a margin on my phone. But I’ll play with it a little. Both the headlines and the department are serif. That hasn’t changed from the previous design.
Re: Re: Re: Re:
Hey Gwiz,
The variable width preference does work on article pages as well as the front page. I'm not saying you're not seeing a problem, but the two page types use the same CSS for managing the content width, and variable width on article pages works for me on multiple devices and browsers. So, if you are seeing variable width on the front page, but fixed on article pages, something odd is going on. I'd recommend clearing out your techdirt.com cookies and shift-reloading to be sure you have the latest CSS.
Re:
They did modify the email. We would have appreciated it if they modified it (much) less.
Re: Comment notify checkbox & preview
Fixed.
Expanded format
There's a way to do this using a preference setting here: https://www.techdirt.com/preferences.php
Set "Page Width" to variable.
Re: "Just go to your preferences page...."
The preferences page is here: https://www.techdirt.com/preferences.php And yes, you can set an "expand all" cookie there.
Re: Is this... new?
I've been using TLS to read Techdirt for over an year. My browser shows it's currently using a Cloudflare certificate. So what's really changed?
While we've "supported" HTTPS/SSL/TLS for a while now, it's only since June that we've defaulted to it and made sure all Techdirt resources are served over a secure connection. But the news here is Namecheap coming on board as a sponsor of that move.
Re: I'll argue the other side
We don't have a built-in spellchecker in the comment form. It's your browser. Right-click the underlined word and "Add to Dictionary".
Re: Techdirt Mods... Please answer
Sorry. It appears that some time during the night, one of our 3rd-party spam filters started getting very aggressive. We're working to get that resolved.
Re: Re: Re: reporting
My point? You said that Techdirt is "not real code" because it's Wordpress. It's not. Never was. I thought that, you being a genius and all, it might satisfy your intellectual curiosity to know something about the actual origins of the code. So my point was to add a spark to your already brilliant light. But, um, never mind.
Re: reporting
Nothing has changed and your votes are being registered. If you vote on a comment and you're not signed in, then you reload the page, of course the button doesn't stick. You're not signed in. We can't assume you're the same person. The behavior you're seeing is expected, correct, and has been exactly the same since the day we launched comment ratings. Feel free to vote as often as you'd like.
Just in case you're interested, Techdirt is not on Wordpress (though perhaps it will be someday). It is run on custom code loosely based on the old slashcode, which we ditched almost a decade ago.
Links for those pages...
preferences: http://www.techdirt.com/preferences.php
account: http://www.techdirt.com/myaccount.php
Or you could go to the preferences page (signed out) or account page (signed in) and set the preference to disable the bar.
This is the new version of Wibiya's toolbar, which we're trying out with the hope that our readers will find it more useful than the old one. One thing the old one had, which the new is missing, was a button to collapse the bar. We've already contacted Wibiya about it -- we think there should be a way to collapse the bar, without completely disabling it.
Re: Typo
Fixed. Thanks.
Re:
I kinda like it too. Will keep it in mind for the next site redesign.
Re: You've got time
Should say November. Fix should appear momentarily.
Re: Re: Unrelated
After some investigation, it appears that the problem comes from a combination of the HTTPS Everywhere Firefox extension and the implementation of the Facebook Like button in the Wibiya toolbar (at the bottom of the page). The other Like button we include below the text of each post doesn't appear to have the same problem. We've removed the Like button from the toolbar and reported the problem to Wibiya.
Re: Unrelated
Yeah, we read our posts. Haven't seen this problem though.
However, we have received a few messages in the past 12 hours about the issue. We're looking into it, but it appears to be related to a Firefox extension called HTTPS Everywhere. For some reason, that extension and the Like button appear to not be playing well together. We don't have any more details than that, yet. But we'll let you know when we do.