30 comments

[ 2.2 ms ] story [ 37.5 ms ] thread
> Human teleoperation naturally comes with on-the-job surveillance and micromanagement.

> This technology allows employees to be easily slotted in and out of different jobs with very little friction, which destroys their bargaining power.

> AI permanently blacklists employees from every minimum-wage job just for being late a few times

> This can easily lead to a race to the bottom where companies no longer have to providing fulfilling, dignified jobs.

If I were stuck in this hell, I would gladly assist any superintelligent AI taking a swipe at the humans who put me in it.

Isn't this just the "reverse centaur" again, but this time framed as something ostensibly desirable?
[author]

FYI, I don't think this is desirable. See the section of the post starting with "Is it a good thing? I think mostly no..."

The author uses a strange definition of teleoperation.

Following GPS directions is no different than assembling an Ikea furniture by following the instructions. So I guess Ikea been teleoperating millions of humans for decades?

It's something that you'd pause and think about if you were trying to build a sensible argument for a thoughtful audience. But the online attention economy now runs on AI op-eds and in a world of overabundance, the winning strategy is to produce outrageous takes at the highest possible speed.
I think it has to do with the feedback loop. Ikea doesn't know what you're doing and can't adjust and adapt to provide you with new instructions if you take a wrong turn.
A lot of people are doing my this already. There are also companies that build AI platforms for contractors to move them around to fill in gaps.
I'm surprised the author is not panicking about the existence of customer support for decades.

This completely confused and misses the point of teleoperation vs following instructions/rules/protocols. Who set the GPS navigation destination?

Any sort of rule following is teleoperation by this definition then ⇒ the whole world is teleoperated.

Hospitals introduced intubation checklists to make sure protocols are followed and patients don't die. How about coding guidelines?

Interesting idea, but I couldn't get past this:

>Which is why I'm heartened to see a lot of support, including from the CEOs of Anthropic and OpenAI, for managing the pace at which these systems become increasingly capable.

This poor guy actually believes the PR, that the frontier model CEOs want to slow things down (and not just setup regulatory-enforced moats around their empires).

See also: "meat proxy", "reverse centaur"
Sounds basically like the plot of the first Dystopia in Marshall Brain’s manna

https://web.archive.org/web/20260725174355/https://marshallb...

https://news.ycombinator.com/item?id=41743688

I use this reference all the time because it’s literally and I do mean literally the state of a significant portion of retail workers

This is how target workers live

Can you elaborate? How do Target workers live?
So I was at target and I just stopped one of the employees and asked them hey does this reflect how your day-to-day job is and they said yes directly.

They have this gun that’s made by I think zebra, and it basically tells them what to do all day every day for every minute and interacting with a human supervisor is by exception

I think Amazon is actually a better example here because warehouse workers have been living this way for I guess decades now with their per item countdown timers that they have to physically you know achieve or they get downgraded or whatever

This is an academic resource that says similar: https://onlinelibrary.wiley.com/doi/10.1111/bjir.70051?utm_s...

Wow, thanks for linking this. I must have read it in the distant past but it seems more relevant than ever these days.
One has to wonder if we're seeing something like this with Mitch McConnell. It sure looks creepy.
One of the upshots of "pacing the frontier" is that we are all going to have to accept that compute will be a regulated, restricted resource. This includes both "how-much" restrictions (high-performance computers just won't be available to the public) and "what-kind" restrictions (software and hardware features will enforce policies on what software you may run, much like a game console or iPhone).

Back in the 2000s, one of my favorite programmers from the Before Times—Fabrice Bellard—came up with an algorithm for computing digits of pi that was so much better than the state of the art, he beat with a $3000 PC the record for speed of pi calculation, which had been established with a supercomputer.

Some bright spark—maybe they'll have Claude assist, maybe it'll trigger Claude's safety locks, I dunno—is going to derive a way to do transformer or other frontier AI inference in a really efficient manner on consumer hardware, making local models practical to run on the PCs people have today and nearly, if not actually, competitive with today's frontier models. "There is another theory which states that this has already happened"—perhaps several times already, and we just need a few more goes of the cycle. I find that for supposedly a crowd of the smartest dudes in the room, people in the Valley like to do things the stupid way around, by sheer fucking brute force: scale up massively, burn billions and trillions of VCbux on capex, aggressively conserve developer effort at the expense of everybody's CPU time and storage capacity—yours, your cloud provider's, your customers'... So I suspect, but at this time cannot prove, that there's a whole lot of headroom for optimization of AI inference, which has the potential to put some truly powerful models in the hands of ordinary people.

And that's very dangerous, because so much for pacing the frontier! If Joe Schmoe can build a mini-AI lab in his mancave, he can then gain access to a model that gives him all the big scary things Dario and Sam are worried about: instructions on how to build bombs or bioweapons, child porn generation, human sacrifice, cats living with dogs, mass hysteria! If you're concerned about an AI-mediated workplace panopticon, Joe Schmoe could, in principle, build one of those for his auto body shop with a local model. The only way to stop Joe from doing so is to stop Joe from acquiring the equipment it would take to run such a model.

Pacing the frontier is at least as much about pacing what you can compute as it is about what goes on in billion-dollar data centers. Any argument for limiting AI growth and development—and admittedly, there are some strong ones—is an argument against general purpose computing. So if we're really going to regulate AI, bend over for the laws that mandate OS/firmware/hardware-enforced restrictions on what binaries your computer may run. And so long open source. Oh well, those laws were coming anyway; that's what the age verification thing is all about. Society has determined that people can't be trusted with computers.

I don’t buy it. Your premise suggests new inference would make SoTA models performant on hardware that we already have in our hands. To prevent us from running local models, we would literally be forced to turn over existing hardware with such capabilities, prevented from building such machines without a suitable license, and so on. That sounds a lot like attempts at gun confiscation, and the result being that only criminals have weapons. This is not the way.
I believe that models on the level of the frontier if not now, then ~6-12 months ago, may well run on a box you can get at Best Buy. And that yes, this along with age verification and the copyright lobby will add to the push to restrict the hardware people are able to procure and operate. It will be difficult to confiscate old PCs, but a "Cash for Clunkers" style program can get lots of them off the market. And, by law and by convention, the modern internet will just refuse to talk to them.
It's interesting how a more sophisticated term can either highlight (or obscure) the anxiety (or glibness) behind its tongue-in-cheek alternatives.
I'm building this since 2022. It's not a new concept, but it is a new control plane and interesting things to solve.

Human + AI economies is the phrase I've been using. Maybe HAI Economies might be better.

Interesting term that is in context of AI - "teleoperation". Sends a chill thinking about that world. But also the inevitability of a plausible future.
> The classic picture of AIs doing things in the world is robots, but I think a more realistic picture of the near future is computers telling people what to do.

As a purely qualitative description, this does not strike me as anything particularly new. Machines had been doing something like this long before the computer age. For example, as early as the late Middle Ages, mechanical wheel-driven clocks with striking mechanisms were used to call people to prayer.

Any process in which a person reacts to a machine can be characterised in this way. Every till that calculates how much one has to pay, every traffic light, every other machine-generated signal. When a warning light comes on in the car, we are prompted to do something: release the handbrake properly, fasten our seatbelt, visit a garage, ...

We are already so deeply embedded in such cycles that AI seems to be merely a new variation on them than a fundamental change.

The deep sense of unease regarding AI does not stem from a machine telling us what to do, but from the risk of losing control over the situation as a whole.

(comment deleted)
> If you had an expert looking over your shoulder and telling you what to do, I expect most of you could do most of the work of an electrician … In fact, that's the bulk of how electricians learn their trade: through apprenticeship. People wearing glasses with built-in cameras, connected to today's strongest AIs could already do a lot with a bit of scaffolding.

Apprentices have their work directly checked by the person supervising them, who is also ultimately personally responsible for the results.

I am a programmer but also like to work with my hands—I’ve done some amount of "real" electrical, plumbing, carpentry, light construction, mechanical, and landscaping work. To me, this line of thinking overall falls into a category of "things computer programmers believe about other kinds of jobs," that I see fairly often on HN. It’s key to the whole argument here but kind of papered over with an unvalidated assumption it’d probably already work with today’s AI.

Anyone who has followed a DIY YouTube video more than a few times has encountered situations where having muscle memory and proprioceptive experience with actually manipulating the tools and objects you’re working with would significantly reduce the chance you mess it up. How tight is too tight? Am I going to shear this bolt head off? Is this saw blade getting dull and going to hurt me? Even the best guides and teachers don’t cover the combinatoric ways things can frequently go wrong–it’s accumulated knowledge in the heads and hands of people who don’t blog about it so it can be slurped into training data.

I think there’s an enormous chasm between "can AI provide reasonably correct guidance for an inexperienced person along a happy path to accomplish basic physical tasks" and "I no longer need to hire an electrician because AI guides me through every step."

Avoiding this is part of why I think working on robotics is important. I don't want humans stuck being hands for an AI that doesn't have them.