this post was submitted on 03 Sep 2023
106 points (93.4% liked)

Fuck Cars

9826 readers
135 users here now

This community exists as a sister community/copycat community to the r/fuckcars subreddit.

This community exists for the following reasons:

You can find the Matrix chat room for this community here.

Rules

  1. Be nice to each other. Being aggressive or inflammatory towards other users will get you banned. Name calling or obvious trolling falls under that. Hate cars, hate the system, but not people. While some drivers definitely deserve some hate, most of them didn't choose car-centric life out of free will.

  2. No bigotry or hate. Racism, transphobia, misogyny, ableism, homophobia, chauvinism, fat-shaming, body-shaming, stigmatization of people experiencing homeless or substance users, etc. are not tolerated. Don't use slurs. You can laugh at someone's fragile masculinity without associating it with their body. The correlation between car-culture and body weight is not an excuse for fat-shaming.

  3. Stay on-topic. Submissions should be on-topic to the externalities of car culture in urban development and communities globally. Posting about alternatives to cars and car culture is fine. Don't post literal car fucking.

  4. No traffic violence. Do not post depictions of traffic violence. NSFW or NSFL posts are not allowed. Gawking at crashes is not allowed. Be respectful to people who are a victim of traffic violence or otherwise traumatized by it. News articles about crashes and statistics about traffic violence are allowed. Glorifying traffic violence will get you banned.

  5. No reposts. Before sharing, check if your post isn't a repost. Reposts that add something new are fine. Reposts that are sharing content from somewhere else are fine too.

  6. No misinformation. Masks and vaccines save lives during a pandemic, climate change is real and anthropogenic - and denial of these and other established facts will get you banned. False or highly speculative titles will get your post deleted.

  7. No harassment. Posts that (may) cause harassment, dogpiling or brigading, intentionally or not, will be removed. Please do not post screenshots containing uncensored usernames. Actual harassment, dogpiling or brigading is a bannable offence.

Please report posts and comments that violate our rules.

founded 3 years ago
MODERATORS
 

On Aug. 14, two stalled Cruise vehicles delayed an ambulance from leaving the scene of a crash in which a driver had hit a pedestrian with their car, according to reports from the San Francisco Fire Department. The pedestrian later died of their injuries, which first responders linked to the delay in getting them to the hospital.

“The fact that Cruise autonomous vehicles continue to block ingress and egress to critical 911 calls is unacceptable,” one emergency responder wrote in a report. Cruise spokesperson Tiffany Testo countered that one of the cars cleared the scene and that traffic to the right of it remained unblocked. “The ambulance behind the AV had a clear path to pass the AV as other vehicles, including another ambulance, proceeded to do,” she wrote in a statement to SFGATE.

According to several reports written by first responders, first obtained by Forbes, emergency personnel arrived at Seventh Street and Harrison in SoMa and began treating a “critically injured” pedestrian who had been struck by a car. The patient was quickly loaded into an ambulance, but the ambulance driver was unable to immediately leave the scene, according to two reports written by members of the ambulance team.

Two autonomous Cruise vehicles and an empty San Francisco police vehicle were blocking the only exits from the scene, according to one of the reports, forcing the ambulance to wait while first responders attempted to manually move the Cruise vehicles or locate an officer who could move the police car.

Collectively, these interferences “contributed to a poor patient outcome, delaying the definitive care required in severe trauma cases,” according to one of the reports. The patient reportedly died of their injuries approximately 30 minutes after arriving at San Francisco General Hospital.

SFFD representatives did not immediately respond to SFGATE’s request for comment.

Just days earlier, the California Public Utilities Commission voted to expand driverless ride-hailing services in San Francisco. In public comments sent to the commission ahead of the vote on Aug. 10, scores of residents asked commissioners to limit Cruise and Waymo’s expansion, describing the robotaxis as “death traps” and a menace to disabled people and children.

During an Aug. 7 meeting to discuss safety concerns around autonomous vehicles, San Francisco Fire Department Chief Jeanine Nicholson told the commission that her department had already recorded about 55 reports of driverless cars driving dangerously close to first responders, obstructing travel or blocking stations.

“And you might say well, 55, that’s not a lot. Well, if it’s your family, it’s a lot,” Nicholson said. “And for me, it's not just your family, it’s everybody's family. I'm responsible for everybody in this city. And so if we don't get to one person, that's one person too many that we didn't get to.”

you are viewing a single comment's thread
view the rest of the comments
[–] notatoad 2 points 1 year ago (1 children)

The video captured by Cruise showed that the ambulance parked behind the Cruise and did not attempt to pass the robotaxi in the rightmost unblocked lane.

If there is a lane open, and the ambulance waits behind a parked car for 90 seconds instead of going around in the open lane, is that really the parked car’s fault?

I know blaming the self-driving car is a fun headline, but maybe focus on the vehicle that struck and killed a pedestrian, rather than the one that wasn’t moving

[–] nbafantest 2 points 1 year ago

That doesn't pass my smell test, I'm inclined to trust the paramedic that wrote the report