Uber wants to turn its drivers into a sensor grid for self-driving companies

Original Article ↗ Hacker News Discussion ↗

Acronym and framing confusion

  • Many readers misread “AV” (autonomous vehicles) as audio‑visual, antivirus, adult video, etc., underscoring how important explicit “self‑driving” wording is.
  • The submitter notes “self-driving” didn’t fit the HN title limit, hence the abbreviation.

Timing and feasibility of Uber’s sensor‑grid idea

  • Multiple commenters say Uber is ~6–10 years late; major AV firms already have large proprietary datasets and mature programs.
  • Practical questions raised: who pays for and installs expensive sensors (e.g., lidar) on mostly privately owned or rental vehicles?

Is data really the bottleneck? Real vs synthetic

  • Uber’s “data is the bottleneck” claim is heavily disputed.
  • Some argue leaders like Waymo rely heavily on simulation and “world models,” using targeted real‑world data plus massive synthetic mileage, not brute‑force data collection.
  • Tesla is cited as evidence that “billions of miles” alone don’t yield full autonomy.
  • Others counter that you still need “boots on the ground” to detect environmental changes (new signs, lane paint), edge cases, and to validate simulations; mapping data from governments may be incomplete or stale.

Labor, unions, and automation

  • One thread explores drivers unknowingly training their replacements and lacking awareness of unions or collective bargaining.
  • Views diverge:
    • Some see AVs as overhyped and far from deployment, akin to flying cars.
    • Others who’ve used Waymo claim AV tech is “basically here” and likely to scale over the next 10–20 years.
  • Broader concerns emerge about automation reducing labor demand, depressing birth rates, and contributing to a long‑run population and social crisis; others argue population decline or steady state could be workable.

Business model, incentives, and driver compensation

  • Several note that a highly successful single AV platform is an existential threat to Uber’s current model.
  • One analysis suggests the real near‑term product is “shadow mode”: running AV models against recorded Uber trips, not turning cars into full sensor platforms.
  • Commenters question whether drivers will be informed or compensated for data collection, given Uber’s history of extracting value from its network.

Cost, economics, and alternatives

  • Debate on whether AV fleets are truly cheaper than human drivers once R&D, remote ops, maintenance depots, and social costs (displaced labor, potential UBI) are included.
  • Suggestions that rideshare/taxi work functions as a de facto jobs program; others argue public transit infrastructure would be a better employment target.

Privacy, mapping, and prior attempts

  • Tesla is cited as already doing extensive vehicle‑based data collection, raising privacy and ownership concerns.
  • A prior startup (Nexar) trying similar dashcam‑based mapping is mentioned as not clearly successful.
  • Comparisons drawn to other “unpaid sensor grids” like location‑based games used for mapping and robotics.

Societal and urban impacts

  • Some see ubiquitous AVs and automation as part of a broader “dark” societal trajectory.
  • A closing comment notes Uber’s negative impact on NYC’s character and pricing, with traditional car services still cheaper in some cases.