Earlier quoted context omitted.
I used to fly into Pittsburg and take an Uber to my grandparents house 40 miles away. For years I could always get an Uber but then after the pandemic my trip was rejected so frequently that I had to start renting a car. So basically no one wanted the gig and Uber never told me my ride was unreasonable. Something changed in the algorithm to benefit drivers, Uber, or both, at the expense of the customer, and that info…
I’m curious: would you have felt better if Uber had just rejected your ride request upfront (“Sorry, we can’t offer rides that far” or something)? Or is this attitude of “hey, it’s a long shot, but let’s give it a try and see if anybody takes the job” closer to the attitude you’d like to see? If the latter, how would you communicate that to the users? I had an occasion a long time ago where I needed to request an Ube…
A similar (though not a break down in tears situation) - My 300 Mile Lyft Ride From Chicago to Bradford - https://whatever.scalzi.com/2019/07/23/my-300-mile-lyft-ride... ( https://news.ycombinator.com/item?id=20508238 - 186 comments)
The relevant section:
> I considered about it for a minute, and then thought, why the hell not, and scheduled the ride. The worst case scenario in this situation is that no one would take the fare, and I would be no worse off than I already was. After a few seconds, I was matched with a car, and I went out to meet the driver.
> I had a suspicion that the app might not tell the driver exactly where I was going, so when the driver — Victor — pulled up, I double-checked with him.
> “I want to be absolutely clear what you’re getting into,” I told him. “I’m asking you to drive me to Ohio.”
> “The state?” he asked.
> “Yes.”
> He thought about it for a second, consulted his own Lyft app (which hadn’t, in fact, told him the destination, just that it was more than 30 minutes away), and then looked back to me, and sort of shrugged. “I like long trips. This could be fun.” Then he popped the trunk for my luggage.