洪 民憙 (Hong Minhee)

Hello! I'm Hong Minhee (洪 民憙), an open source software engineer in my late 30s, living in Seoul, Korea. I'm bisexual and non-binary (they/them), and an enthusiastic advocate of free/open source software and the fediverse.

I work full-time on @fedify, an ActivityPub server framework in TypeScript, funded by @sovtechfund. I'm also the creator of @hollo, a single-user ActivityPub microblog; @botkit, an ActivityPub bot framework; Hackers' Pub, a fediverse platform for software developers; and LogTape, a logging library for JavaScript and TypeScript.

I have a long interest in East Asian languages (CJK) and Unicode. I post mostly in English here, though occasionally in Japanese or in mixed-script Korean (國漢文混用體), a traditional writing style that interleaves Chinese characters with the native Korean alphabet. Wanting to write in that style was actually one of the reasons I joined the fediverse. Feel free to talk to me in English, Korean, Japanese, or even Literary Chinese!

#introduction

はじめまして！ソウル在住の30代後半のオープンソースソフトウェアエンジニア、洪 民憙（ホン・ミンヒ）と申します。バイセクシュアル（bisexual）・ノンバイナリー（non-binary）で、自由・オープンソースソフトウェア（F/OSS）とフェディバース（fediverse）の熱烈な支持者です。

STF（@sovtechfund）の支援を受け、TypeScript用ActivityPubサーバーフレームワーク「@fedify」の開発に専念しています。他にも、おひとり様向けのActivityPubマイクロブログ「@hollo」、ActivityPubボットフレームワーク「@botkit」、ソフトウェア開発者向けフェディバースプラットフォームHackers' Pub、JavaScript・TypeScript用ロギングライブラリLogTapeなどの制作者でもあります。

東アジア言語（いわゆるCJK）とUnicodeにも興味があります。このアカウントでは主に英語で投稿していますが、時々日本語や国漢文混用体（漢字ハングル混じり文）の韓国語でも書いています。実はこの文体で書きたくてフェディバースを始めた、という経緯もあります。日本語、英語、韓国語、漢文でも気軽に話しかけてください！

#自己紹介

安寧(안녕)하세요! 저는 서울에 살고 있는 30代(대) 後半(후반)의 오픈 소스 소프트웨어 엔지니어 洪民憙(홍민희)입니다. 兩性愛者(양성애자)(bisexual)이자 논바이너리(non-binary)이며, 自由(자유)·오픈 소스 소프트웨어(F/OSS)와 聯合宇宙(연합우주)(fediverse)의 熱烈(열렬)한 支持者(지지자)이기도 합니다.

STF(@sovtechfund)의 支援(지원)을 받아 TypeScript用(용) ActivityPub 서버 프레임워크 @fedify 開發(개발)에 專業(전업)으로 任(임)하고 있습니다. 그 外(외)에도 싱글 유저用(용) ActivityPub 마이크로블로그 @hollo, ActivityPub 봇 프레임워크 @botkit, 소프트웨어 開發者(개발자)를 위한 聯合宇宙(연합우주) 플랫폼 Hackers' Pub, JavaScript·TypeScript用(용) 로깅 라이브러리 LogTape 等(등)의 製作者(제작자)이기도 합니다.

東(동)아시아 言語(언어)(이른바 CJK)와 Unicode에도 關心(관심)이 많습니다. 이 計定(계정)에서는 主(주)로 英語(영어)로 포스팅하지만, 때때로 日本語(일본어)나 國漢文混用體(국한문 혼용체) 韓國語(한국어)로도 씁니다. 聯合宇宙(연합우주)에 오게 된 動機(동기) 中(중) 하나가 바로 國漢文混用體(국한문 혼용체)로 글을 쓰고 싶었기 때문이기도 하고요. 韓國語(한국어), 英語(영어), 日本語(일본어), 아니면 漢文(한문)으로도 말을 걸어주세요!

#툿친소 #연친소 #별친소 #자기소개

@sabrinkmann Thanks! Stay tuned! 😎

@zundan 1年以上ずっと2.0アルファ版を使っていますが、問題がまったくなく満足しています。

@cheeaun Yeah, I personally prefer the compact syntax (which is widely used) over “readable” ones, but if people get hard to read them, “readable” ones can be a good alternative.

@cheeaun Yeah, exactly! I guess your ex-colleagues might be bothered if patterns were written in Parsec-style syntax. 🤔

The reason people avoid regular expressions is ultimately because of the syntax. No indentation, no comments. It might be a minority opinion, but I think the x (EXTENDED) flag should be the default for regex.

@stefan Thank you! 🥰

@smallcircles Thanks for the kind words! Stay tuned!

@fedify

Congratulations!

I am really delighted with @nlnet decision to select @drfed for an #NGI0 grant. Having good quality developer tools for creating #ActivityPub based solutions is so important for a healthy #fediverse developer ecosystem.

To anyone reading, bookmark the website..

Fedify Studio is focused on alleviating the most pressing issue of "Why is ActivityPub development so frustratingly hard?" that makes it unattractive for newcomers to adopt the technology. And addresses topics of:

- Protocol complexity
- #Interoperability hell
- Debugging nightmare
- Limited visibility

#Fedify from the very start has paid attention to ease of use for fediverse solution developers, not just by their library codebase, but with comprehensive documentation and tools to guide people along. Kudos here to @hongminhee who started this great initiative!

Fedify Studio finally has a proper name: DrFed. We just got @nlnet funding too.

DrFed is our sister project, built alongside #Fedify to tackle the debugging side of #ActivityPub development. It just received @nlnet funding and now has its own account here: @drfed.

#DrFed #fedidev #fediverse #NLnet

Some of you have already heard of us as #Fedify Studio. We now have a proper name: DrFed, short for “Doctor Fed.” We've also just received funding from @nlnet, through the NGI0 Commons Fund.

#DrFed is a web app for debugging #ActivityPub interoperability failures. When two implementations don't federate, the slow part is usually figuring out where the exchange broke: signing, JSON-LD processing, WebFinger, or something less obvious. DrFed's first job is to show where it failed.

We're the team behind @fedify: @2chanhaeng, @gaebalgom, @hongminhee, and @z9mb1. We'll post updates when there's something to try.

#fedidev #fediverse

I Wish Deno Would Keep Doing What It Does Best, by @hongminhee:

https://hackers.pub/@hongminhee/2026/i-wish-deno-would-keep-doing-what-it-does-best?ref=frontenddogma.com

#deno

Hackers' Pubにも数日前に韓国語で書いたことですが、元々Smalltalkに大きな幻想を抱いていて、Lispを最高のプログラミング言語だと信じていました。食べていくためにPythonを使っていましたが、基本的には「許容できるLisp」（acceptable Lisp）として扱っていたのです。

それがどういうわけか、Haskellを本格的に使い始め、それ以来、静的型検査ができないプログラミング言語には魅力を感じなくなりました。Pythonはあっという間に道具箱から姿を消し、その座をTypeScriptが代わりました。Smalltalkへの幻想ももうありません。

一言で言えば、Haskellがプログラミング言語の好みを180度変えてしまったというわけです。

Python 3.14's coolest feature? t-strings - and Psycopg 3.3 already supports them 😎

Just write t"..." and drop your variables in {braces}. Proper syntax, no SQL injection, dynamic queries and identifiers - all handled. No more counting %s placeholders or juggling param dicts!

Check the link in the comments 👀 #Python #PostgreSQL #Database #Development

LG생활건강하면 발을씻자가 유명한데 발을씻자를 써보니 정말 괜찮아서 아니 그럼 손을씻자는 없는 건가 해서 찾아보니 있더군요. 발을씻자 개발팀이 만들었다는데, 거품은 쫀쫀하고, 효소를 통한 세정력이나 시어버터, 유칼립투스 등이 들어간 보습력이 만족스럽습니다.

Optique 1.1.0 is out.

The headline is the new @optique/discover package: point it at a directory of #TypeScript files and it builds a full #CLI command tree, with typed handlers and help/completion included automatically.

Also new: value parsers for file sizes, CSS colors, semver strings, JSON, and KEY=VALUE pairs; seq() for ordered positional grammars; negatableFlag() for --color/--no-color patterns; async Zod/Valibot helpers.

https://github.com/dahlia/optique/discussions/834

國漢文(국한문)을 한글로 바꿔주는 소프트웨어인 Gukhanmun 0.2.0이 릴리스되었습니다. 《標準國語大辭典(표준국어대사전)》과 더불어 《우리말샘》 데이터를 包含(포함)하게 되었고, 各種(각종) 코너 케이스를 더 잘 다루게 되었습니다. 또한, 國漢文(국한문) 原文(원문)에 括弧(괄호)로 한글 倂記(병기)가 되어 있을 境遇(경우), 이를 結果文(결과문)에서도 反映(반영)하여 漢字(한자) 倂記(병기)가 되거나 한글 讀音(독음)이 달리게 되었습니다. 그 밖에도 여러 改善(개선) 事項(사항)들이 있으니, 仔細(자세)한 內容(내용)은 릴리스 노트를 參考(참고)하시기 바랍니다.

https://github.com/dahlia/gukhanmun/discussions/10

「中華LLM」という表現、すごく面白い。🤣

あ、急に冷やし中華が食べたくなった。😅

Optique 1.1.0 is out.

The headline is the new @optique/discover package: point it at a directory of #TypeScript files and it builds a full #CLI command tree, with typed handlers and help/completion included automatically.

Also new: value parsers for file sizes, CSS colors, semver strings, JSON, and KEY=VALUE pairs; seq() for ordered positional grammars; negatableFlag() for --color/--no-color patterns; async Zod/Valibot helpers.

https://github.com/dahlia/optique/discussions/834

國漢文(국한문)을 한글로 바꿔주는 소프트웨어인 Gukhanmun 0.2.0이 릴리스되었습니다. 《標準國語大辭典(표준국어대사전)》과 더불어 《우리말샘》 데이터를 包含(포함)하게 되었고, 各種(각종) 코너 케이스를 더 잘 다루게 되었습니다. 또한, 國漢文(국한문) 原文(원문)에 括弧(괄호)로 한글 倂記(병기)가 되어 있을 境遇(경우), 이를 結果文(결과문)에서도 反映(반영)하여 漢字(한자) 倂記(병기)가 되거나 한글 讀音(독음)이 달리게 되었습니다. 그 밖에도 여러 改善(개선) 事項(사항)들이 있으니, 仔細(자세)한 內容(내용)은 릴리스 노트를 參考(참고)하시기 바랍니다.

https://github.com/dahlia/gukhanmun/discussions/10

I write my name in Chinese characters: 洪民憙. In English I still include them, writing Hong Minhee (洪民憙) rather than the romanization alone.

Part of it is meaning: Chinese characters carry it, hangul doesn't. Mostly, though, it's about the direction of loss. You can derive a Korean or romanized reading from 洪民憙; you can't go the other way. Given 홍민희 or Hong Minhee alone, there's no recovering which characters were intended.

I don't much mind how my name gets pronounced. If a Chinese speaker reads it as Hóng Mǐnxī, or a Japanese speaker arrives at something different, that's fine. The characters are the same. Classical Chinese once worked this way across East Asia: one written text, many readings.

What I care about is the notation.

This is like magic, absolutely awesome. I'm really looking forward to PostgreSQL 19.

Looking Forward to Postgres 19: It's About Time https://lobste.rs/s/ivzqxi #databases
https://www.pgedge.com/blog/looking-forward-to-postgres-19-its-about-time

OSSCA 참여형 프로그램 멘티 모집이 내일(일요일)까지입니다! 관심 있는 분들은 서두르시기 바랍니다!

꿈에서 재밌게 얘기하다가 깨고 나니 이젠 안 계신다는 걸 깨닫고.

아버지와도 할 수 있는 재밌는 이야깃거리가 참 많았는데…

コーディングエージェントでの実装、最初はガーっとやってくれていいんだけど、次第に行きづまることがあり、その理由はAIが自力で階層化設計を案出しないことにあるんじゃないかということを検討している。 AIの問題解決方針は、問題を小問題に分解して、その小問題を解くための関数を作り、関数を組み合わせて全体としての問題が解けるかどうか試す(か、人間に試してもらう)、というわりとオーソドックスなものだとおもうけど、「小問題を解くための関数」には名前がつくけど、これを利用する場所はただのスクリプトで、ここに名前がつかない。部品を作るんだけど、部分がつながった状態の全体には名前がないから、全体というものをまず認識していない。それと全体と部分の関係の調整もできないし、全体的な構造を変えたいときに、部品に捉われて全体の構造が以前のものを引き摺りつづける。 で、これは「つくるべき全体」に名前を与えてやれば解決するんじゃないかと考えて、試してみる。全体に名前を与えて、それを構成する部品を案出させる。全体と部品のレイヤー関係を自分で案出するようにすればいいんじゃないか。