洪 民憙 (Hong Minhee)

Work of the day! Me and my colleague have been making something with fabric and electronics :>

< F/OSS Histomat: We Should Reclaim LLMs, Not Reject Them
>

https://writings.hongminhee.org/2026/01/histomat-foss-llm/

The author argues against withdrawing from AI — instead proposing a Training Copyleft license (a GPLv4 / TGPL), following the same pattern as GPLv2 → GPLv3 → AGPL, each evolving to close new exploitation loopholes.

A NEW VERSION of
Requirements for Hangul Text Layout and Typography
한국어 텍스트 레이아웃 및 타이포그래피를 위한 요구사항
has been published.

https://www.w3.org/TR/klreq/

The content was rearranged to match the standard headings used for the W3C Language Enablement Framework.The document is still in English and Korean, with buttons to switch between.

Going forward, we will now begin adding new content.

I've just submitted my post to Lobsters and Hacker News:

• Lobsters: https://lobste.rs/s/vxsjiv/why_craft_lovers_are_losing_their_craft
• Hacker News: https://news.ycombinator.com/item?id=47468389

LLM coding assistants didn't create a split between craft-lovers and make-it-go developers. They revealed one that was always there.

For craft-lovers, what's being bypassed isn't the output but the act itself. Marx called this separation from the act of production. But the alienation isn't coming from the LLM. It's coming from a market that penalizes whoever produces output more slowly.

Why craft-lovers are losing their craft

翻訳というのが軽視されすぎというのもあるかも知れないな。言語ごとに文章構成の癖とかも違うから、実際は母国語で書いてから翻訳すれば良いというものでもないよね。

例えば英語のニュースとかで、日本についての記事で“the Asian country”とか指したりしがちだと思うけど、日本語だったら「そのアジアの国」なんて書き方は翻訳でもない限りまずやらないよね（そもそもこの書き方は偏見とかをエンコードしやすそうだから個人的に好きでない）。こういうこともあって、母国語を経由するよりそのまま対象の言語で書いた方が良かったりしがちだと思っている

シソーラスと睨めっこしながら“delve into”を捻り出した次の日に、LLMが“delve into”を使いすぎと指摘する記事をみかけたことがある私としましてもね……（？）

LLMを搾取的として批判するのはまあ理解できる。最低限の労力も払われていないslopへの嫌悪も当然だ。ただ、前者の論点を措いたときに、自分で責任を持って校正した文章に対してまで文意と無関係な細かい体裁などを論って「自分の言葉」でないから不誠実と謗るのは何かずれていないかと思ってしまう。

LLMにありがちな体裁で足切りするのは確かにslopの排除には有効かも知れないけど、最低限の校正を経た文章に対してのそれは、一見してslopと区別を付けづらいという実用上の都合で正当化されているだけで、偏見であることは否定し得ないのでは。一昔前の喩えを出すなら、「日本語がぎこちないメールはスパム」とかと同類の

LLMに頼らずに「自分の言葉」で（非母語の）文章を書くように素朴に要求されがちなの、その「自分の言葉」とやらが言語能力によって大きな制約を受けることについてもう少し留意してくれても良いのではとは思う。私もｴｰｱｲを扱わずに英語を書いているけど、それにも常に自分の英語のぎこちなさが付き纏ってくるし

@heybran 据我所知，目前韩国人可以免签去中国。最近韩国人确实经常去上海玩。我的妻子明天也要去上海旅行。

@heybran 原来如此！首尔现在还是有点冷呢。

LLMコーディングアシスタントはソフトウェアエンジニアたちの亀裂を作ったのではない。すでにあった亀裂を露わにしただけだ。

匠人気質のソフトウェアエンジニアたちが感じる疎外の源泉はLLMではなく、産出物を遅く出す側に不利益を与える市場にある。Marxの労働疎外論でこの問題を読む新しいエッセイを書いた。

「コーディングを愛する人たちが、なぜコーディングから追い出されているのか」

LLM 코딩 어시스턴트는 소프트웨어 엔지니어들 사이의 分裂(분열)을 만든 게 아니다. 이미 있던 分裂(분열)을 드러낸 것이다.

匠人(장인) 氣質(기질)의 소프트웨어 엔지니어들이 느끼는 疎外(소외)의 源泉(원천)은 LLM이 아니다. 그들의 產出物(산출물)을 더 느리게 만드는 쪽에 不利益(불이익)을 주는 市場(시장)이다. Marx의 勞動(노동) 疎外論(소외론)으로 이 問題(문제)를 읽어보는 새 글을 썼다.

〈왜 코딩을 사랑하는 사람들이 코딩에서 밀려나는가〉 (한글)

LLM coding assistants didn't create a split between craft-lovers and make-it-go developers. They revealed one that was always there.

For craft-lovers, what's being bypassed isn't the output but the act itself. Marx called this separation from the act of production. But the alienation isn't coming from the LLM. It's coming from a market that penalizes whoever produces output more slowly.

Why craft-lovers are losing their craft

より形式的に述べるならば、RDF Semantics（<https://www.w3.org/TR/2014/REC-rdf11-mt-20140225/>）によれば、RDFS interpretationにおいて

```turtle
as:attachment rdfs:range [ owl:unionOf ( as:Object as:Link ) ] .
s as:attachment o .
```

というのは、

```turtle
o rdf:type [ owl:unionOf ( as:Object as:Link ) ] .
```

をentailするという意味でしかない。特に、RDFSを含むRDF Schemaの仕様で定義されるsemantic extensionはあらゆるグラフに対してエラーにならないとされている（“None of the semantic extensions normatively defined in this document impose such syntactic restrictions on RDF graphs.”）。

自分でも何を言っているのか分からなくなってきた（？）

RDFの意味論においては`as:attachment`の値域が`as:Object`または`as:Link`であるというのは、`as:attachment`の値として`as:Object`でも`as:Linkでもないものを指定したらエラーとなるという意味*ではなく*、`as:attachment`の値として指定されたものは全て`as:Object`または`as:Link`であると見なしますという意味であるはずなので、この場合は拒否する方が間違いな気がする（自信がない）
QT: https://hollo.social/@hongminhee/019d0eaa-637d-70e4-b110-fb96d4f2cf24 [参照]

Thinking about LLMs as a means of production, the alienation of labor they create, and the social conditions that cause this alienation… I'll probably write a new blog post about it.

So, an interesting issue came up in the #Fedify repo that I've been thinking about: #629.

You know how every #fediverse server uses schema:PropertyValue in actor attachment for profile metadata fields (like “Website”, “GitHub”, etc.)? Turns out, strict #AS2 validators like browser.pub reject it, because the AS2 spec says attachment should only contain Object or Link—and PropertyValue is a schema.org type, not an Activity Streams 2.0 type.

The thing is, we can't just drop the type like we did with Endpoints (#576), because Mastodon and others rely on seeing "type": "PropertyValue" to render profile fields. But at the same time, it's technically not spec-compliant.

I'm leaning towards writing a #FEP to formalize this existing practice rather than trying to invent a new type (like toot:PropertyValue extending Object), which would be a nightmare to migrate across the whole fediverse.

What do you all think? Has anyone else run into this? Would love to hear thoughts from implementers and spec folks.

#fedidev #ActivityPub #ActivityStreams #ActivityStreams2 #AS2 #PropertyValue

Checked in at 튜링의사과 by @hongminhee@hollo.social

出튜

아, 昨日(작일)이 春分(춘분)이었구나.

Tick-tock, deadlines are closing in ⏳

🔹 Mar 23 — Community Track Proposal Deadline
Missed the info session? Check out the slides here 👉 https://s.coscup.org/26brief

🔹 Mar 27 — Early Bird CfP Deadline
👉 https://s.coscup.org/earlybirdcfpen

Got questions? Join us on Telegram:
https://t.me/coscupchat
Or email us at program@coscup.org

@silverpill Fair point. I'm probably biased by spending most of my time in the JavaScript and TypeScript ecosystem, where this pattern is hard to avoid. TypeScript itself being the elephant in the room doesn't help.

OpenAI to acquire Astral

What strikes me most about this acquisition isn't the AI angle. It's the question of why so many open source tools get built by startup teams in the first place.

I maintain an open source project funded by the Sovereign Tech Fund. Getting there wasn't easy: the application process is long, the amounts are modest compared to a VC round, and you have to build community trust before any of that becomes possible. But the result is a project that isn't on anyone's exit timeline.

I'm not saying the startup path is without its own difficulties. But structurally, it offloads the costs onto the community that eventually comes to depend on you. By the time those costs come due, the founders have either cashed out or the company is circling the drain, and the users are left holding the bag. What's happening to Astral fits that pattern almost too neatly.

The healthier model, I think, is to build community first and then seek public or nonprofit funding: NLnet, STF, or similar. It's slower and harder, but it doesn't have a built-in betrayal baked into the structure.

Part of what makes this difficult is that public funding for open source infrastructure is still very uneven geographically. I'm based in Korea, and there's essentially nothing here comparable to what European developers can access. I had no choice but to turn to European funds, because there was simply no domestic equivalent. That's a structural problem worth taking seriously. The more countries that leave this entirely to the private sector, the more we end up watching exactly this kind of thing play out.

Wir sollten „Public Money = Public Social Media” also mehr pushen.
Habt Spaß und wenn ihr könnt, baut doch etwas mit z. B. @fedify oder @botkit.
Damit das Ganze hier aber wirklich skaliert, braucht es schlichtweg mehr Geld. Natürlich auch mehr Strukturen und Spezifikationen. Dass hier überhaupt etwas gebaut wird, ist schon großartig. Im Ehrenamt lässt sich nur schwer eine Alternative zu Big Tech aufbauen, wenn man möchte, dass ein Großteil der Bevölkerung Lust hat, diese Anwendungen zu benutzen. Geschweige vom Onboarding, auch auf dem Platten land.
Wer von Open Source spricht, sollte beim Fediverse Funding nicht schweigen.

Hier noch einmal eine Linkliste von Tools:
- Ihr habt Bock auf hübsche Wraps-Grafiken für euren Account: https://mastodon-wrapped.playground.54gradsoftware.de/
- Ihr wollt eure Account-Einstellungen checken: https://mastodon-account-checker.playground.54gradsoftware.de/
- Ihr wollt wissen, welche Organisationen schon auf Mastodon sind (täglich frisch aktualisiert): https://mastodon-account-checker.playground.54gradsoftware.de/
- Jede Konferenz/Treffen braucht ein Hashtag und eine https://fediwall.de/
- Tägliche coole Geschichtlichen Wikipedia Links gibt es hier: @heute_vor

had to install `noto-fonts-core` to see @north's https://ဪ.com Burmese test domain on mnt flavored debian and already installed `fonts-noto-cjk` the other day to see @hongminhee's korean posts. I think we should probably move to shipping all the noto base fonts tbh

First release for Hackers Pub Android Client

https://github.com/hackers-pub/android/releases/tag/v1.0.0

The -f option for the git push command, which is an alias for --force, should be re-aliased to --force-with-lease.

#Git

@brettm Could I see the problematic JSON-LD document?

@julian

Good day all! Upcoming episode of Fireside Fedi!

The #livestream will be on: stream.firesidefedi.live

Special Guest: @hongminhee@hollo.social

An intersectionalist, feminist, and socialist living in Seoul (UTC+09:00). @tokolovesme's spouse. Who's behind @fedify, @hollo, and @botkit. Write some free software in #TypeScript, #Haskell, #Rust, & #Python. They/them.

Follow @ozoned@stream.firesidefedi.live to be alerted when we go live! So don't miss it!

It will happen on 06 April 2026 at 08:30 US Eastern Time ( UTC-4 )

If by any ungodly chance you miss the show:

#PeerTube ( #VOD ): tubefree.org/@firesidefedi #firesidefedi #fediverse #fedi #interview #freesoftware #opensource #userfreedom #freedom #resistance