Hacker News new | past | comments | ask | show | jobs | submit login

I'm not sure if I fully understand how the RR is calculated. I'm assuming that when a user requests a driver, the app pings 2-4 drivers nearby. If one driver out of the 2-4 pinged accepted, all but one should have their RR lowered, lowering the average RR across all drivers.

Is there a primary potential driver who gets docked in this case or have you guys simply reduced the number of pings to potential drivers per request (i.e. go from making 4 driver requests to 2)?




I'm also confused by this. My guess is either

1) Only one driver is pinged, and they have a narrow window to accept until the offer is removed and given to a different driver.

2) Multiple drivers are pinged. If any one of them accepts, the other drivers are not penalized (but lose the opportunity for accepting this offer). If no drivers accept, all of them are penalized.


Great question. Fundamentally, everyone who is pinged but does not accept gets their reliability rate lowered.

Our new system actually decides how many drivers to send the request to based on their reliability rate. So someone with a 100% reliability rate (or close enough) will be the only person getting a particular request.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: