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

If the whole point of the algo change is to correct an unfairness by which a strict fee+cart value approach doesn’t reliably reflect the amount of work somebody’s being asked to do, isn’t this exactly the outcome we expect? That the people who were putting more work in now get more money, while the people who were benefiting from sniffing out the “easy” jobs now make something more in line with everybody else’s compensation?

It does seem unsporting on the company’s part to play coy about the details. I wonder what the imperative was there: to avoid squabbling with workers about what “effort” means? To reduce the chances of legal scrutiny in one of the thousands of jurisdictions they operate in? To preserve the flexibility to quietly turn the dial in their own favor in the future?

I’m reminded of how Uber caught flak over surge pricing, and ultimately dealt with that by making pricing completely opaque. Now they still might say “prices are a little higher because of the weather” if they decide to, but normally you don’t even expect to know whether your price for a given ride is based on their estimate of your desperation, their having sized you up as price-insensitive, driver supply, or what…






Apart from the workers and the company there is another important actor here - the clients. I think the point of the algo change was to better serve clients with smaller orders.



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

Search: