洪 民憙 (Hong Minhee)

古い人間なのでリットルは小文字で書いてしまうのだけど、最近は大文字もOKらしい 視認性は大文字のほうがいいと思う その昔親父にMKSA（現在のSI）で育ったやつは面倒だcgs-emuにしろと揶揄されたもんだけど 単位も時代で変わる 今やキログラム原器は一次標準ではない

오늘 저녁은 곰국을 먹겠습니다.

@bootlegrydia Yeah, I just don't get how people can be so proud of their privilege instead of being ashamed of it.

@hongminhee definitely a very nationalistic dogwhistle and true everywhere, such as "we are so lucky that we are living in China otherwise we'd all lose our lives to COVID like people in US" several years ago

@jj1bdx.tokyo 本当にそうです。

ディアスポラや移民を経験したことのない人たちの妄言でしょうね。 国家分断然り。

「〈自分の国籍〉でよかった」という言葉は、かなりナショナリズム的な発言ですし、下手をすると人種差別的にもなりかねない話ですが、人々は結構安易にそういうことを言いますよね。

YMOも山下達郎もユーミンも基本的には東京23区生まれのボンボンあるいはお嬢様なので、あの感覚が共有できないと歌詞も背景もわからないだろうなとは思う。1970年代にも階級社会は厳然と存在していたということ。

> 합법이면 공정한가: AI 재구현과 카피레프트의 침식

https://news.hada.io/topic?id=27360

https://writings.hongminhee.org/2026/03/legal-vs-legitimate/index.ko-hang-kr.html

https://github.com/chardet/chardet/issues/334

@lmorchard wrote something that stuck with me: AI-assisted coding isn't creating a split among developers. It's revealing one that was always there, just invisible when we all worked the same way.

If you're mourning the loss of the craft itself—the texture of writing code, the satisfaction of an elegant solution—that's real, and no amount of “just adapt” addresses it. You might need to find that satisfaction somewhere else, or accept that work is going to feel different. Frankly, we've been lucky there's been a livelihood in craft up to now.

https://blog.lmorchard.com/2026/03/11/grief-and-the-ai-split/

The JSON-LD Working Group published today a First Public Working Draft of YAML-LD 1.0. [JSON-LD11] is a JSON-based format to serialize Linked Data. In recent years, [YAML] has emerged as a more concise format to represent information that had previously been serialized as [JSON], including API specifications, data schemas, and Linked Data.

#LinkedData #MachineReadable #WebStandards
https://www.w3.org/news/2026/first-public-working-draft-yaml-ld-1-0/

RE: https://explore.alt.store/@altstore/116210899682565583

The wait is over! Today we’re officially joining the fediverse 🚀

AltStore PAL 2.3 is now available and makes it easier than ever to discover new apps from across the social web 🌐

Even better — we’re also launching some awesome fediverse apps on AltStore to celebrate!

Learn more 🧵

Alternative app store AltStore PAL joins the fediverse https://techcrunch.com/2026/03/11/alternative-app-store-altstore-pal-joins-the-fediverse/

@andypiper Happy birthday!

なるほどHollo、他人to他人の絵文字リアクションが出るようになったんだ

오픈소스하자 얘들아

Just read this 2015 piece by @qntm.org on why abolishing time zones is a terrible idea, and it's brilliant. Not because it argues against them, but because it just follows the logic through. By the end you've watched the proposal quietly collapse under its own weight.

https://qntm.org/abolish

既に世の中には文責者としての最低限の責務もろくに果たさずLLMの出力をそのまま公開したとしか思えないようなslopが氾濫しているから、読み手としては感覚的な「slop臭さ」による足切りもしていかないと処理が追いつかないしなあ。何につけてもslopの氾濫とかいうやつが引き起こした歪みが大きすぎる

自力で書いた文章では労力がかかる割にぎこちなく偏見や誤解を招き、LLMを通せばslop臭さから避けられ、自分の母語で書けば当然読まれないまたは読み手が使う機械翻訳ツールの誤訳によるミスコミュニケーションに煩わされることになるというの、どうすれば良いのだろうね。やっぱり印欧語話者に生まれなかったのが悪いのですかね。

正直この文章も、洪さんの今までの活動に対する信用があるからこそ読む気になれるけど、仮にその前提がなければ私も4段落目くらいでLLMっぽさを感じて警戒してしまうところだと思うし、私自身も非母語話者に不利な構造にある種加担しているところはある

@julian Yeah, that's why I'm still writing short words myself. My accent won't go anywhere!

@ddelemeny That's a useful framing, and the article is worth reading. The concern about entropy collapse is real—I've seen it happen when native speakers run their own writing through a model and get something smoother but somehow emptier back.

My situation is a bit different, though. The high-entropy original is in Korean. The LLM's job is to carry that across, not to sand it down. Whether it succeeds is a fair question, but the direction of the process matters. I'm not polishing a draft into blandness; I'm trying to get something that exists in one language to exist in another without losing its shape.

Anyway, this has been a genuinely interesting exchange. Thank you for the link.

@phnt Multilingual posting is something I've actually been thinking about and experimenting with already. I'm building a fediverse platform for software developers called Hackers' Pub, where I've been prototyping exactly this kind of feature. My other project, @hollo, is where I post from right now, and I'd like to bring something similar there eventually—the main obstacle is that most fediverse platforms don't properly render multilingual posts even when they receive them—the protocol already supports it via contentMap, but implementations like Mastodon tend to pick one language arbitrarily rather than presenting all of them.

Outside the fediverse, my blog already works this way: each post is written in multiple languages (Korean, Japanese, and English), not as translations filed separately but as the same post published in all three. It's a pattern I find natural given how I actually think and write across languages.

On Google Translate: I stopped using it for Korean–English a long time ago, for the same reasons you'd expect. These days I mostly use Kagi Translate, which is LLM-based and noticeably better for distant language pairs. The gap between that and older MT is stark enough that I think “machine translation” has started to mean two quite different things depending on which generation of tools you're talking about.

@julian I actually just addressed something close to this in a reply up the thread—might be worth a read!

@ddelemeny @silverpill I relate to the immersion argument, and I think it's part of why I avoided machine translation for so long—not out of principle, but because the output wasn't worth learning from. Older MT between Korean and English produced something closer to a word-by-word skeleton than actual language. You couldn't look at it and think: oh, that's how a native speaker would put it. It was more like a scaffold you had to tear down before building anything.

LLMs are different enough that I've had to revise that instinct. The output is often genuinely idiomatic, and when I read a phrase that lands exactly right, there's a recognition that functions a lot like learning—the same feeling as encountering a sentence in a book and thinking: I'll remember that. I do find myself absorbing expressions that way, probably more than I would have expected.

That said, I think your point holds at the edges. For shorter writing I still work without assistance, partly for practical reasons and partly because I notice the difference when I don't. So I suspect I'm arriving at something similar to what you're describing, just from the other direction—using the tool for longer texts while trying to keep the muscle from atrophying entirely on shorter ones.

The dynamic you mention with German and Korean is interesting too. Korean was my concern about English; I imagine the lack of immersion shapes the experience in ways that are hard to compensate for with tools alone.

@julian Thank you for saying this. The ActivityPub development community being Euro-America-centric isn't just a cultural observation. It shapes what gets built, what use cases are considered, and whose needs are treated as edge cases. Language is a big part of that, and I'm glad the point landed.

And yes, apparently the chardet post found its audience. I was not expecting that particular piece to take off, but I'll take it!

@hongminhee@hollo.social I think your post makes me think more critically about the use of LLMs for translation services. It is easy for me to judge from a position of privilege because I am a native English speaker, and I do not realize the access I am given simply because of it.

While reading your post it also made me think about the sacrifices you made to contribute to this community. There are precious few people in the Asia-Pacific region who regularly contribute to AP development, and a large part of that is the language barrier.

If LLM-translation makes the AP development community less euro-america-centric, then I am all for it. Cultural differences we can work through, but language barriers are harder to bypass!

Aside, congratulations for making it onto Hacker News front page

@ddelemeny @silverpill The confidence comes from an asymmetry I suspect many non-native speakers will recognize: I can read English much better than I can write it.

When I write in English on my own, I often know, as I'm writing, that something is off—that the sentence doesn't carry the weight I intended, or that the nuance I wanted is somewhere between the words I've chosen. I just don't always know how to fix it. When I write in Korean first and then work with an LLM, I can read the result and check it against what I meant. Sometimes I'll see a phrase and think: yes, exactly that, I didn't know how to get there myself. That moment of recognition is the verification step.

So I'm not trusting the machine blindly. I'm using my reading ability—which is reasonably good—to audit an output that my writing ability couldn't have produced alone. It's an imperfect process, but it's not as unmoored as handing a text to a system and walking away.

Your point about polyglot authors is well taken. The tool works better when the person using it can actually evaluate what it produces. I'd agree that's a meaningful distinction.

I've been thinking about adding federation health monitoring to #Fedify—not as a separate data store or custom API, but by extending the existing #OpenTelemetry integration. The idea is to expose delivery outcomes, signature verification failures, and per-remote-host error rates as OpenTelemetry metrics alongside the spans Fedify already emits. If you already have a Prometheus or Grafana setup, you'd get federation observability basically for free. Circuit breaker behavior (temporarily skipping a remote server that's been consistently unreachable) could surface as OpenTelemetry events, keeping everything in the same trace context rather than scattered across separate logs.

Does this sound useful to you? I'm curious whether people building on Fedify—or running federated servers in general—would actually reach for this, and what kinds of things you'd most want to observe. Happy to hear any thoughts.

#fedidev #ActivityPub

To be precise, it's not English as a language that I hate, but English as a form of power.

From back when I used to flip through a thick dictionary, taking a minute for each sentence, to now, when I use an LLM to write in English, people don't realize that I'm personally speaking to them in English for their sake. Honestly, I just want to speak in Korean. I hate English.