I'm writing this in English.

Not because English is my first language—it isn't. I'm writing this in English because if I wrote it in Korean, the people I'm addressing would run it through an outdated translator, misread it, and respond to something I never said. The responsibility for that mistranslation would fall on me. It always does.

This is the thing Eugen Rochko's post misses, despite its good intentions.

@Gargron argues that LLMs are no substitute for human translators, and that people who think otherwise don't actually rely on translation. He's right about some of this. A machine-translated novel is not the same as one rendered by a skilled human translator. But the argument rests on a premise that only makes sense from a certain position: that translation is primarily about quality, about the aesthetic experience of reading literature in another language.

For many of us, translation is first about access.

The professional translation market doesn't scale to cover everything. It never has. What gets translated—and into which languages—follows the logic of cultural hegemony. Works from dominant Western languages flow outward, translated into everything. Works from East Asian languages trickle in, selectively, slowly, on someone else's schedule. The asymmetry isn't incidental; it's structural.

@Gargron notes, fairly, that machine translation existed decades before LLMs. But this is only half the story, and which half matters depends entirely on which languages you're talking about. European language pairs were reasonably serviceable with older tools. Korean–English, Japanese–English, Chinese–English? Genuinely usable translation for these pairs arrived with the LLM era. Treating “machine translation” as a monolithic technology with a uniform history erases the experience of everyone whose language sits far from the Indo-European center.

There's also something uncomfortable in the framing of the button-press thought experiment: “I would erase LLMs even if it took machine translation with it.” For someone whose language has always been peripheral, that button looks very different. It's not an abstract philosophical position; it's a statement about whose access to information is expendable.

I want to be clear: none of this is an argument that LLMs are good, or that the harms @Gargron describes aren't real. They are. But a critique of AI doesn't become more universal by ignoring whose languages have always been on the margins. If anything, a serious critique of AI's political economy should be more attentive to those asymmetries, not less.

The fact that I'm writing this in English, carefully, so it won't be misread—that's not incidental to my argument. That is my argument.

@hongminhee @Gargron
I would like to add one point that I rarely see addressed: a translation is also a responsability, that the text provided is faithful to the original, possibly imperfect, but faithful.

If it is provided to you, at your request, them it's a contract between you and your provider. You might say that automatic translation is better than nothing.

But if it is imposed on you, as in subtitles, then you have no other choice but them and the responsability is on the provider. In this case, automatic translation will essentially not be admissible.

@antoinechambertloir The distinction you're drawing is a useful one, and I largely agree with it. When translation is imposed on you with no alternative, the responsibility for its faithfulness lies with whoever imposed it.

But it makes me ask: which category does my situation fall into?

I'm writing this reply in English. Not because I chose English as my preferred language of expression, but because if I wrote it in Korean, it would either be ignored or filtered through whatever tool my interlocutor happens to have on hand—and any resulting misreading would be treated as my problem. So I write in English, carefully, to preempt that. Is that a voluntary choice? Formally, yes. Practically, it sits much closer to the “imposed” end of your spectrum than it might appear.

The contract model works cleanly when both parties have genuinely equivalent alternatives. When one party's only real options are “use this tool” or “don’t participate,” the contract framing starts to obscure more than it reveals.

@Gargron

@hongminhee @Gargron on this network, I would find rude that you answer me in Korean as you would find rude that I answer you in French. But the software is connected with automatic translation system that may allow you to start some interaction, in a language or another, possibly falling out onto English. We both have this possibility, which allows us to share the responsability.
(And if you didn't speak a single word out of Korean, and I didn't speak a word out of French, we wouldn't have much choice then, but trust that system!)
@hongminhee @Gargron Imagine we start following each other. Then you will see the posts I send in French, and I will see yours in Korean, as I see many on German or Spanish (although I speak German but not Spanish). In any case, some freedom emerges.

@antoinechambertloir I appreciate the spirit of what you're describing, and the fediverse's approach to translation is genuinely one of its nicer features.

I'd just gently push back on one assumption: that the automatic translation available to both of us is roughly equivalent. French–English and Korean–English are not the same problem for these systems. The linguistic distance is much greater, the training data has historically been thinner, and the results have reflected that gap for a long time. It's only fairly recently that Korean–English machine translation has become reliable enough to carry a real conversation without significant loss.

So when you write in French and I write in Korean, we're not quite sharing the responsibility equally—at least not yet. Though I do think we're getting closer, which is perhaps the most honest thing I can say about where I stand on all of this.