noinput.net | plug it in

Tampabay: Driver goes 3 miles with lodged body

ST. PETERSBURG - A 93-year-old motorist struck and killed a pedestrian Wednesday evening, then drove about 3 miles with the body lodged in the windshield until he was stopped at a Sunshine Skyway tollbooth.

The driver told officers he thought the body had fallen from the sky, said St. Petersburg police Officer Mike Jockers.

“He had no idea he had been involved in an accident,” Jockers said. “He doesn’t totally understand what happened.”

The crash occurred about 8:30 p.m. when the 52-year-old pedestrian attempted to cross 34th Street S from east to west near 46th Avenue S, witnesses told police.

The pedestrian made it across two of the southbound lanes before he was hit by a 2002 Chevy Malibu, which was traveling about 45 mph, police said.

The impact severed the pedestrian’s lower right leg, which remained in the street. His head and arms went through the windshield, while the rest of his body flipped up onto the roof of the car, Jockers said.

“The driver continued southbound, as the eyewitness said, like nothing happened,” Jockers said.

As the car approached the toll plaza, the toll taker thought it was a prank, until he saw the blood.

When the driver stopped, the body fell into the car, Jockers said.

A veteran traffic investigator, Jockers said it was one of the most gruesome scenes he has worked.

Neither the name of the driver nor the name of the victim was released Wednesday.

I’m sorry, why are they driving at 93? It’s called public transportation with a double senior-citizen’s discount..

What does a Sumo Wrestler post on his blog site?

ANYTHING he damn-well wants to! - translations here

So back from the weekend, and a good one at that. Friday night headed out to Nirvana Lounge in Beverly Hills, awesome hangout spot with the homies. Black Lable most all night, Sanjay took care of us for the VIP room at Habbibi’s in Westwood, alwasy a good time. Photo shoot with Lynda on saturday (pics coming soon), and a whole lot of cleaning and disinfecting the apartment yesterday. The kitchen was pretty intense. After that headed to Pasadena for a 25th anniversary dinner for one of my good friends Christina. I have to say, what better way to spend an evening then with a group of Syrian people. More food then you could imagine, open bar & loud music. Ahh yes, and back to work today.

In honor of the horrid los of the Chargers yesterday to Philly (freaking terrible ending to that game), I was a bit afraid to jump on and check my Fantasy Standings today. I swear, im so SOL this year in my FF roster. But one thing that gave me a bit of silver lining for checking was how mah man Donavan McNabb helped with his insane 54 passes 35 completions in yesterdays game. The man was on fire. Sadily tho, im still bottom of the roster in my league.

Ehh, go figure.

After a much debated decision it’s been decided that the time to register Quick Time Pro has come. Have to say, I think it’s worth the $30, personally. Just the ease of editing MOV files, doinga quick full screen on a video and the export functions make it worth the time alone. Plus you get to watch cool-ass Sigur Ros video in all their Cinema Glory.

Yea mang.

Wired News: Sue Companies, Not Coders

So I was doing my normal 5:45pm last-sip of the latte news-feed jive and came accross this article by Bruce Schneier on Wired. Really good article and I can totally agree with his points. Give it a quick read if your interested in this stuff like me. Taken from expierence where I have been threateded with a lawsuit in the past because a client didn’t like the way i setup a securley-modded out of the box software app, something like this hit’s home.

At a security conference last week, Howard Schmidt, the former White House cybersecurity adviser, took the bold step of arguing that software developers should be held personally accountable for the security of the code they write.

He’s on the right track, but he’s made a dangerous mistake. It’s the software manufacturers that should be held liable, not the individual programmers. Getting this one right will result in more-secure software for everyone; getting it wrong will simply result in a lot of messy lawsuits.

To understand the difference, it’s necessary to understand the basic economic incentives of companies, and how businesses are affected by liabilities. In a capitalist society, businesses are profit-making ventures, and they make decisions based on both short- and long-term profitability. They try to balance the costs of more-secure software — extra developers, fewer features, longer time to market — against the costs of insecure software: expense to patch, occasional bad press, potential loss of sales.

My GOD yes.. Coming from the expierence of attempting to run your own business for 4 years, this is the damned truth..

The result is what you see all around you: lousy software. Companies find that it’s cheaper to weather the occasional press storm, spend money on PR campaigns touting good security, and fix public problems after the fact than to design security right from the beginning.

The problem with this analysis is that most of the costs of insecure software fall on the users. In economics, this is known as an externality: an effect of a decision not borne by the decision maker.

Normally, you would expect users to respond by favoring secure products over insecure products — after all, they’re making their own buying decisions based on the same capitalist model. But that’s not generally possible. In some cases, software monopolies limit the available product choice; in other cases, the “lock-in effect” created by proprietary file formats or existing infrastructure or compatibility requirements makes it harder to switch; and in still other cases, none of the competing companies have made security a differentiating characteristic. In all cases, it’s hard for an average buyer to distinguish a truly secure product from an insecure product with a “boy, are we secure” marketing campaign.

The end result is that insecure software is common. But because users, not software manufacturers, pay the price, nothing improves. Making software manufacturers liable fixes this externality.

Sandeep, this one is for you buddy:

This guy created an excel doc using vbscript to simulate a synth. Be sure to turn your security level on your excel settings to “Low” for it to work, but in any case this is pretty slick. Now if you could just adjust the Hertz and Start mapping it to a beat machine we’d be in business.

Now to test this in Open Office 2.0 will be the deciding factor

Haha, saw this joke over at FoO’s site this morning and had to share:

I recall my first time with a condom, I was 16 or so. I went in to buy a package of condoms. There was a beautiful woman behind the counter, and she could see that I was new at it. She handed me the package and asked, if I knew how to wear one.

I honestly answered, “No.” So she unwrapped the package, took one out and slipped over her thumb.

She cautioned me to make sure it was on tight and secure. I apparently still looked confused. So she looked all around the store. It was empty. “Just a minute,” she said, and walked to the door, and locked it.

Taking my hand, she led me into the back room, unbuttoned her blouse and removed it. She unhooked her bra and laid it aside. “Do these excite you?”, she asked.

Well, I was so dumb-struck that all I could do was nod my head. She then said, it was time to slip the condom on. As I was slipping it on, she dropped her skirt, removed her panties and lay down on a desk.

“Well, come on”, she said, “We don’t have much time.”

So I climbed on her. It was so wonderful, that unfortunately, I could no longer hold back and POW, I was done within a few minutes.

She looked at me with a frown. “Did you put that condom on?”

I said, “I sure did,” and held up my thumb to show her.

hat tip -> ben