What is Hackers' Pub?

Hackers' Pub is a place for software engineers to share their knowledge and experience with each other. It's also an ActivityPub-enabled social network, so you can follow your favorite hackers in the fediverse and get their latest posts in your feed.

0
0
0
0
0
0
0
0
1
0

#MicrosoftAgentFramework 워크샵에서 한나절만에 이걸 다 한다구요? 네, 정말로 다 합니다!

참가신청 👉 https://bit.ly/agentcamp-daegu-2026

맞다AI가 와 함께 하는 #AgentCamp 지금 바로 신청하세요!

#matdaaiga #agentcamp #globalai #ai #microsoft #agentframework #foundry #mcp #aspire
#Agent Camp

0
0
0
0
0
6
0
0
0

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.

@GargronEugen Rochko 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.

@GargronEugen Rochko 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 @GargronEugen Rochko 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.

5
13
0
0
0
1
0
0
0
0
0
0
0
0
1
1
0
0
0

군사 목표달성하면 도망가는..?
"이란 전쟁 종료 시점에 대해 "궁극적으로 작전은 최고사령관(트럼프 대통령)이 군사적 목표가 완전히 달성되었다고 판단할 때, 그리고 이란이 자신들의 선언 여부와 무관하게 완전하고 무조건적 항복 상태에 이르렀다고 판단할 때"라며 미국의 판단에 따라 이란 군사작전을 끝낼 수 있음을 시사"
n.news.naver.com/mnews/article

0
0
0

Mastodon has a new human-over-AI contribution policy.

tl;dr:

- The human contributor is the sole party responsible for the contribution.

- If AI was used to generate a significant portion of your contribution (i.e. beyond simple autocomplete), we require you to disclose it in the Pull Request description.

- If you cannot guarantee the provenance and legal safety of the AI-generated code, do not submit it.

- Cases of repeated violations of these ... guidelines could result in a ban from our repositories.

github.com/mastodon/.github/bl

0
17
0
0

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.

@GargronEugen Rochko 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.

@GargronEugen Rochko 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 @GargronEugen Rochko 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.

5
13
0

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.

@GargronEugen Rochko 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.

@GargronEugen Rochko 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 @GargronEugen Rochko 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.

5
13
0
0
0
0
0
0

美國和以色列聯手攻擊伊朗,擊殺最高領袖哈梅內伊。烏克蘭駐南非大使 Olexander Scherba 上星期在 x 發文,指伊朗駐比勒陀利亞大使館通知他們,已為哈梅內伊和被擊殺的軍方領袖設弔唁冊,他認為這情況奇怪,決定公開回應。

Scherba 回應伊朗邀請,指要「提醒」伊朗外交官幾點。他指出,伊朗作為羅俄斯的盟友,已故的伊朗領導人們,雙手沾滿烏克蘭人的鮮血,無數烏克蘭人被伊朗製的沙赫德無人機和其他武器殺死,「伊朗的領袖是為烏克蘭人帶來無盡傷痛的幫兇。」

「作為一個有信仰的人,我盡量不為他人的死而歡慶…但過去三年每晚都聽到伊朗製造的殺戮機器,在基輔和其他烏克蘭城市上空咆哮,我忍不住希望所有罪犯都受到應有的懲罰。」

Scherba 最後指,他個人並不認識伊朗的外交官,作為個人亦和他無仇無怨,明白有時好的外交官要為壞領袖的決策賣單,「但我也希望你明白,哈梅內伊之死我不會感到傷感,也不會為此致哀。」
instagram.com/p/DVugOc7j0uI/

0
0
0
0
0
0
0
0
0
0