Pretty compelling example of digital labor issues (both subtle and explicit) related to AI. Surely letting Google shape our questions and provide all the answers won’t be an issue?

Digital labor is, imo, the fundamental problem with AI, and I think this story shows why: It’s not just the AI use here that’s exploitative, it’s kind of everything.

Uh, no.

Check this guy out:

He compared the current era of AI to the Tower of Babel, saying society must “avoid the ‘Babel syndrome,’” which he defines as “the idolatry of profit that sacrifices the weak, a uniformity that neutralizes differences, and the pretense that a single language — even a digital one — can translate everything, including the mystery of the person, into data and performance.”

Very glad for 404 Media’s podcast, because I somehow missed when they published this horrifying story.

Kentucky primaries for the 2026 elections take place a week from today, so it’s not surprising that we’ve been getting some political mail over the past couple of weeks. Today, though, something came in the mail that really took me aback. David Kloiber’s campaign sent us something that was clearly more than a regular mailer, since it came in a letter-style envelope and was addressed to both me and my spouse.

It’s digital labor all the way down. What a depressing read.

This is a good example of how thorny the AI problem is, and why I strongly prefer a digital labor critique to a copyright critique. Yes, I’m mad that Meta trained their models on my work, but I don’t think the answer is to strengthen Elsevier or Cengage’s copyright claims.

You don’t have to spend long on my blog to figure out that I default to being grumpy about generative AI, but if I’ve made one exception to that rule, it’s for Kagi Translate, which I’ve found to be a genuinely helpful machine translation tool—and to have some neat features that I haven’t found in its Google or DeepL equivalents.

It took me back a little bit tonight, then, when Kagi Translate straight up hallucinated something on me, in a way that I imagine wouldn’t be out of place for a more mainstream LLM (which I’ve never really used). Earlier today, while working on a paper for an upcoming conference, I was consulting a Jacques Ellul book I was about to cite, and I wanted to make sure that “genetic engineering” would be an accurate translation for his phrase « intervention génétique » (which could obviously also be rendered “genetic intervention,” but I’ve never heard that phrase in my life, so I’d prefer to go with a more well-known phrase if it’s accurate).

Two grumps (and, to be clear, I’m grumpy at my employer, not the student reporter):

1. the framing here is, as usual, “how to use” whether than “should we use”

2. “misinformation” is centered as the (implicitly sole) problem with generative AI, not digital labor or any of the deeper issues

So Doctorow already said this in the essay I linked to this morning, but it’s very striking how much this leak highlights Anthropic’s willingness to use our creative labor while simultaneously cracking down on any effort for others to do the same to them.

Didn’t expect from the headline that this would turn into an essay on copyright, but I’m glad it did:

Expanding copyright will gain little for creative workers, except for a new reason to be angry about how our audiences experience our work. Expanding labor rights will gain much, for every worker, including our audiences. It’s an idea that our bosses – and AI hucksters – hate with every fiber of their beings.

Last Thursday, I listened to a recent episode of The Vergecast during my morning bike commute. The episode featured Paul Ford talking about his recent experience with Claude Code, and I was genuinely surprised to find some of his comments resonating with me. It helped that Ford wasn’t uncritical about AI (though certainly not as critical as I would have been), but some of it was just that I recognized some of the thrill that he was describing of using tools and resources to learn how to solve a problem. In fact, I found that thrill so contagious that a passing comment he made got me to spend some time once I got to the office converting my Twitter archive into a CSV that I could finally import it into the Day One journaling app that I use.

Required reading, imo.

Oh, okay, maybe not shame so much as butt-covering.

Oh look, they are capable of shame.

Opt out is a terrible way of doing this. I’m so angry that I didn’t even finish the article before posting.

Wild escalation of digital labor issues in generative AI.

Horrifying stories like this should be in our minds every time we think about AI.

I guess I should be reading this for the jokes, but I hadn’t realized Academia.edu had done this, and I’m so angry at the inspiration for the jokes that I haven’t made it any further.

A few thoughts:

First, it is almost comically mean to use the results of a project collecting AI tells to get LLMs to not sound like that. Like, of all the digital labor exploitations of AI, this might be the pettiest.

Second, AI detection is hard, and for all my concerns with AI, I think this is another good example of why policing its use can do more harm than good. I don’t blame the Wikipedia community for doing this project, but I would never recommend this approach in a classroom.

This morning, while getting ready for the day, I spent some time catching up on podcasts, including Nilay Patel’s interview of Stack Overflow CEO Prashanth Chandrasekhar on a recent episode of Decoder (a podcast I’ve spent a lot more time listening to since it went ad free for subscribers). I ditched the Stack Exchange network a year and a half ago over digital labor concerns—I was literally being prevented from deleting my own content from the site, which is bonkers—and I’m honestly not sure why I bookmarked the interview for listening a few days ago. I think it was more than a hate listen, though: For all of my own feelings about generative AI, I make an effort to be open minded, and I was interested in the headline for the interview: “Stack Overflow users don’t trust AI. They’re using it anyway.”

I missed the detail about Disney+ using some of the Sora output, and that makes this whole thing even more about labor exploitation.

I disagree with the copyright framing here (it’s a labor issue), but otherwise, I think this is a good take.

Involving Disney, who infamously stiffed Alan Dean Foster on Star Wars royalties, so clearly demonstrates how the underlying issue with generative AI isn’t copyright, it’s labor.