洪 民憙 (Hong Minhee) :nonbinary:'s avatar

洪 民憙 (Hong Minhee) :nonbinary:

@hongminhee@hollo.social

1,131 following1,648 followers

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 , , , & . They/them.

서울에 사는 交叉女性主義者이자 社會主義者. 金剛兔(@tokolovesme)의 配偶者. @fedify, @hollo, @botkit 메인테이너. , , , 等으로 自由 소프트웨어 만듦.

()

Pinned

@hongminhee@hollo.social

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!

en.wikipedia.org

Korean mixed script - Wikipedia

Pinned

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

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

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

speakerdeck.com

国漢文混用体からHolloまで

本発表では、韓国語の「国漢文混用体」(漢字ハングル混じり文)を自分のフェディバース投稿に実装したいという小さな目標から始まった旅路を共有します。 この目標を達成するために、ActivityPubのJSON-LDの複雑さやHTTP Signatures、WebFingerなどの仕様を理解する必要性に…

Pinned

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

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

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

logtape.org

LogTape

Unobtrusive logging library with zero dependencies—library-first design for Deno, Node.js, Bun, browsers, and edge functions

@hongminhee@hollo.social

JSConf JP 2026で登壇することになりました。11月22日(日)、東京のベルサール神田で開催されます。

タイトルは「Oseo:SBCLスタイルのJavaScript/TypeScript AOTコンパイラ」。SBCLやChez Schemeのように、動的型付き言語でありながらプログラム全体を事前にネイティブコードへコンパイルするJavaScriptエンジンを作っている、その話をします。TypeScriptの型注釈は最適化のヒントとして使うだけで、決して鵜呑みにしない。ヒントが嘘でも動作は変わらない。そんな設計の話です。

発表は日本語、30分枠、14:10からトラックCです。詳細はこちら。

https://jsconf.jp/2026/ja/talks/hong-minhee

会場でお会いできたら嬉しいです。

jsconf.jp

Oseo:SBCLスタイルのJavaScript/TypeScript AOTコンパイラ | JSConf JP 2026

Common LispのSBCLやSchemeのChez Schemeは動的型付き言語でありながら、プログラム全体を事前にネイティブコードへコンパイルし、何十年もプロダクションで使われてきました。一方JavaScriptは今なお、速く動くにはインタプリタと複数段のJIT、その上に載るデオプティマイゼーション機構が要る言語だと見なされています。この違いはどこから来るのか。この問いから始まったプロジェクトがOseoです。 Oseoはすべての関数を二重にコンパイルします。言語のフルセマンティクスを実装するジェネリックパスが一つあり、値の種類や形状に対して安価なランタイムガードを掛けられる箇所には、その隣に特殊化されたパスを並べます。ガードが失敗すれば、バイナリの中にすでにコンパイルされているジェネリックパスへ分岐するだけです。インタプリタへ落ちることも、デオプティマイズすることもありません。TypeScriptの型表記やJSDocはこの特殊化パスを選ぶヒントとして使われますが、決して鵜呑みにされることはありません。`any`や型アサーション、素のJavaScriptとの相互運用のせいで`: number`という表記はいつでも誤りうるので、Oseoはその可能性をガードで防ぎます。 この発表では、このアイデアが実際にどう動くのかをコードとバイナリで直接お見せします。Node.jsもDenoも使わず、V8が一切リンクされていない純粋なネイティブ実行ファイルがどう作られるか。`--dump-mir`と`--emit-c`で覗いた生成コードの中で、一つのガードが実際にどんな比較と分岐にコンパイルされるか。型ヒントが実行結果を変えてはならないという原則も、同じ領域にある別プロジェクトとの具体的な比較を通じて見ていきます。 Oseoはまだ完成したプロジェクトではありません。この発表は、これまでに証明できたことと、まだ残っている道のりを一緒にお見せする場でもあります。ネイティブI/O、ガベージコレクタ、セルフホスティングまで、システムプログラミングに関心がある方なら貢献できる余地がまだたくさんあります。

@hongminhee@hollo.social

今週の日曜日にJSConf JP 2026で発表するんだけど、スライドがまだ1枚もできてない。果たして無事に発表できるのか… 😱

jsconf.jp

Oseo:SBCLスタイルのJavaScript/TypeScript AOTコンパイラ | JSConf JP 2026

Common LispのSBCLやSchemeのChez Schemeは動的型付き言語でありながら、プログラム全体を事前にネイティブコードへコンパイルし、何十年もプロダクションで使われてきました。一方JavaScriptは今なお、速く動くにはインタプリタと複数段のJIT、その上に載るデオプティマイゼーション機構が要る言語だと見なされています。この違いはどこから来るのか。この問いから始まったプロジェクトがOseoです。 Oseoはすべての関数を二重にコンパイルします。言語のフルセマンティクスを実装するジェネリックパスが一つあり、値の種類や形状に対して安価なランタイムガードを掛けられる箇所には、その隣に特殊化されたパスを並べます。ガードが失敗すれば、バイナリの中にすでにコンパイルされているジェネリックパスへ分岐するだけです。インタプリタへ落ちることも、デオプティマイズすることもありません。TypeScriptの型表記やJSDocはこの特殊化パスを選ぶヒントとして使われますが、決して鵜呑みにされることはありません。`any`や型アサーション、素のJavaScriptとの相互運用のせいで`: number`という表記はいつでも誤りうるので、Oseoはその可能性をガードで防ぎます。 この発表では、このアイデアが実際にどう動くのかをコードとバイナリで直接お見せします。Node.jsもDenoも使わず、V8が一切リンクされていない純粋なネイティブ実行ファイルがどう作られるか。`--dump-mir`と`--emit-c`で覗いた生成コードの中で、一つのガードが実際にどんな比較と分岐にコンパイルされるか。型ヒントが実行結果を変えてはならないという原則も、同じ領域にある別プロジェクトとの具体的な比較を通じて見ていきます。 Oseoはまだ完成したプロジェクトではありません。この発表は、これまでに証明できたことと、まだ残っている道のりを一緒にお見せする場でもあります。ネイティブI/O、ガベージコレクタ、セルフホスティングまで、システムプログラミングに関心がある方なら貢献できる余地がまだたくさんあります。

@hongminhee@hollo.social

I released Optique 1.4.0, a type-safe CLI parser for TypeScript.

If your CLI has one main action and a few subcommands, you can now set a default command. For example, app src/main.ts can run the same action as app run src/main.ts, while app build still runs its own subcommand. No need to rewrite argv yourself.

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

github.com

Optique 1.4.0: Default commands, Markdown references, and more focused help · dahlia/optique · Discussion #1139

Optique is a type-safe combinatorial CLI parser for TypeScript built from composable parser functions. Parser definitions drive runtime parsing, help and completion output, and the inferred value t...

@hongminhee@hollo.social

I have to show off this little flying squirrel. My spouse, @tokolovesme, drew it for Oseo, a new F/OSS project I've been spending a lot of time on lately.

The name Oseo comes from the Sino-Korean reading of 鼯鼠, which means “flying squirrel.”

The Oseo logo: a black silhouette of a flying squirrel seen head-on against a white background. It has rounded ears, four paws spread wide, two white curved eyes, and a white dot for a nose. Its tail curves down and to the right.
ALT text

The Oseo logo: a black silhouette of a flying squirrel seen head-on against a white background. It has rounded ears, four paws spread wide, two white curved eyes, and a white dot for a nose. Its tail curves down and to the right.

Five black flying squirrel sketches on a white page, with handwritten Korean notes and arrows. The center sketch, boxed in red and outlined in green, is labeled “this one focuses on the shape of a flying squirrel” (이건 날다람쥐 形態에 焦點). A similar sketch on the right has notes that read “this one is truer to the shape of  ✧ a star” (이건  ✧ 별이 더 正直한 模樣) and “star + face + tail” (별 + 얼굴 + 꼬리).

The small squirrel at the bottom became the logo. It has round ears, outstretched paws, white crescent eyes, a dot for a nose, and a curved tail. A note beside it reads, “I drew this in 30 seconds. Is it daijōbu (‘okay’ in Japanese) …?” (30秒만에 그린 건데 大丈夫[다이죠부]…?)
ALT text

Five black flying squirrel sketches on a white page, with handwritten Korean notes and arrows. The center sketch, boxed in red and outlined in green, is labeled “this one focuses on the shape of a flying squirrel” (이건 날다람쥐 形態에 焦點). A similar sketch on the right has notes that read “this one is truer to the shape of ✧ a star” (이건 ✧ 별이 더 正直한 模樣) and “star + face + tail” (별 + 얼굴 + 꼬리). The small squirrel at the bottom became the logo. It has round ears, outstretched paws, white crescent eyes, a dot for a nose, and a curved tail. A note beside it reads, “I drew this in 30 seconds. Is it daijōbu (‘okay’ in Japanese) …?” (30秒만에 그린 건데 大丈夫[다이죠부]…?)

@hongminhee@hollo.social

With Codeberg down, I can still read the Fediverse Enhancement Proposals (FEPs) on Codeberg Pages: https://fediverse.codeberg.page/fep/.

I can't clone the Git repo from Codeberg right now, though. I found a copy at https://github.com/social-web-foundation/fep, but it looks like it hasn't been updated in a while.

It got me thinking: it'd be nice to have a mirror for days like this. Maybe the existing GitHub copy could serve as the mirror, or one could live on another forge like @codefloe. Codeberg would still be the home for FEPs; the mirror would just give us somewhere else to clone from.

github.com

GitHub - social-web-foundation/fep

Contribute to social-web-foundation/fep development by creating an account on GitHub.

@Codeberg@social.anoxinon.de

codeberg.org is unfortunately down right now due to a yet undefined issue with our domain. It was not expired and not transferred, the domain is completely gone from our account and we did not receive any email notifications, and it is currently in the status clientHold. We are currently trying to contact our registrar to get more information right now & trying to resolve this issue, but this is probably going to take some time.

We are sorry for the inconveniences & are working on a solution.

@Codeberg@social.anoxinon.de

codeberg.org is unfortunately down right now due to a yet undefined issue with our domain. It was not expired and not transferred, the domain is completely gone from our account and we did not receive any email notifications, and it is currently in the status clientHold. We are currently trying to contact our registrar to get more information right now & trying to resolve this issue, but this is probably going to take some time.

We are sorry for the inconveniences & are working on a solution.

@pkgupdt@fedi1.pkgu.net

https://magicant.github.io/yash/

내가 interactive shell로 쓰고 있는 Yet Another Shell. 일본인 개발자가 만들어서, 다국어 지원이 잘 되어 있어서 쓰기 시작했는데, 쓸수록 좋다. 무엇보다 소규모 오픈소스 플젝에서 이렇게까지 자동화 테스트 코드가 있는 건 처음 본다. 숙련된 개발자가 소중하게 작성해 온 플젝. 무엇보다 곳곳에서 보이는 꼼꼼함이 맘에 든다. 나도 이런 코드를 남기면 좋겠다.

magicant.github.io

Yash: yet another shell - a POSIX command line shell

@Steve_Bate@mastodon.social
@dansup@mastodon.social

Fediverse Events + FediDB.

Imagine being able to plan a fediverse event (online, in-person or both) without a specific date or venue, and seek interested attendees that can indicate if they Will Attend or Maybe Attend, with a comment feed and the ability to send event updates to them via DM on FediDB.

All the pieces were there, I just needed to connect and polish them. Shipping soon!

FediDB events feature
ALT text

FediDB events feature

@_elena@mastodon.social

Good morning Fedi friends!

Routine reminder that the at is accepting proposals for talks.

There are two available formats: 25 minutes and 8 minutes.

More details are available here:
🔗 : lists.fosdem.org/hyperkitty/li

⏳ The submission deadline is November 27. Acceptance notifications come soon thereafter, on December 1.

📝 You can submit your proposal here: pretalx.fosdem.org/fosdem-2027

I'll be working on my proposal this week 🤗

pretalx.fosdem.org

FOSDEM 2027

Schedule, talks and talk submissions for FOSDEM 2027

@kizu@front-end.social

New blog post: “Cursors”.

blog.kizu.dev/cursors/

In which I take a cursory glance at a victory that CSSWG did hand out to us in this pointless debate about if buttons have more in common with blank space compared to links.

blog.kizu.dev

Cursors

In which I take a cursory glance at a victory that CSSWG did hand out to us in this pointless debate about if buttons have more in common with blank space compared to links.

@socialcg@w3c.social

A new draft report from the Community Group is now available: "Seek Item".

It defines a new (optional) endpoint that ActivityPub API clients can use to efficiently access a page in an OrderedCollection that contains a specific item, such as the one the client has last seen. This can improve efficiency and responsiveness of ActivityPub clients.

swicg.github.io/activitypub-ap

swicg.github.io

Seek Item

@hongminhee@hollo.social

The three of us who maintain Fedify (@z9mb1, @2chanhaeng, and I) have all submitted proposals to the Social Web devroom at FOSDEM 2027. I wonder how many of us will get to give a talk. I'll probably talk about implementing portable objects (FEP-ef61) in Fedify, @z9mb1 will cover how Fedify has evolved over the past year and what lies ahead, and @2chanhaeng will talk about DrFed.

drfed.org

DrFed — The ActivityPub debugging platform

DrFed is a web-based platform for developing and debugging ActivityPub implementations, built by the team behind Fedify.

The quoted post is hidden while awaiting the author's approval.

@hongminhee@hollo.social · Reply to Samuel Brinkmann

@sabrinkmann @Floppy Two directions I know of. If a hosted service is fine, something like Sentry. For self-hosting, SigNoz is the only F/OSS option I know with easy OpenTelemetry ingestion; I don't know what else is out there. It has a paid cloud version too.

I think Sentry used to have an F/OSS edition. I'm not sure it still exists, or whether it accepts OTLP though.

signoz.io

SigNoz | The Open Source Datadog Alternative

SigNoz Cloud is a one-stop observability tool built on top of OpenTelemetry. Get APM, logs, traces, metrics, exceptions, AI observability & alerts in a single tool.

@hongminhee@hollo.social

ChanHaeng Lee (@2chanhaeng), one of the @fedify maintainers, is asking the which of his two projects he should present in the Social Web devroom at @fosdem 2027.

@drfed is an debugging tool that he is building with @z9mb1, @gaebalgom, and me. fedi.blue (https://fedi.blue) is a library for servers that interoperate over both ActivityPub and the AT Protocol. Both would make good talks, which is why I would rather the audience picked.

The poll closes on 13 November 2026, so vote for the one you would rather sit through. has three maintainers now, and all three of us are going to 2027 and submitting proposals to the devroom. (The CFP is open until 27 November 2026 if you have a talk of your own.)

fedi.blue

Hello, world

The quoted post is hidden while awaiting the author's approval.

@2chanhaeng@hackers.pub

Hello, Fediverse! I’m trying to decide what topic to present at FOSDEM 2027 – Social Web Devroom. Which of these two would you be more excited to hear about?

  • DrFed: DrFed is an ActivityPub debugging tool that @hongminhee, @z9mb1, @gaebalgom, and I are building as a team.
  • fedi.blue: fedi.blue is a library for building servers that interoperate with the ActivityPub and AT protocols.
  • DrFed: ActivityPub Debugging Tool1 (100%)
  • fedi.blue: Bridge between AP & AT Protocol0 (0%)

fedi.blue

Hello, world

@geeknews@mastodon.social

국내 오픈소스 소액 지원 사업 'FOSS for All Microgrants 2026' 수혜 프로젝트 5곳

FOSS for All이 올해 처음 진행한 기부금 모집 및 분배 사업에서 지원한 13개 프로젝트 및 커뮤니티 중 5곳을 선정했습니다. 각 프로젝트에 소액 지원금을 전달할 예정입니다.

선정된 프로젝트는 Z80 프로세서용 LLVM 백엔드 llvm-z80, 요청 처리 과정을 명시적으로 드러내는 Go 웹 프레임워크 Spine, Windows 11 작업 표시줄에 위젯을 넣는 Deskband11Lib, PDF로 제본용 소책자를 만드는 HornPenguin Booklet, 국한문혼용체를 한글로 변환하는 Gukhanmun입니다.

news.hada.io/topic?id=36847

@hongminhee@hollo.social

I've been carrying around an idea for a federated code forge for a while. Two things sharpened it recently: Tangled's post on the federated code forge, which builds a forge on the AT Protocol, and a Jujutsu workshop (Korean) by Seongmin Lee (@boltless.me), who works at Tangled, held at @turingappledev.

My version would build on ForgeFed, the protocol for code forges (spec), so that repositories, issues and merge requests federate the way posts already do. The idea is early enough that I haven't even come up with a codename. What I want from it, roughly:

  • Git and Jujutsu (so-called jj) as equal clients. Not Git hosting with Jujutsu support bolted on, but a forge that understands both, so what Jujutsu is actually good at, stacked changes, becomes a first-class unit of review instead of a pile of separate pull requests.
  • No owner layer. Since the point is federation, one instance represents one person or one organization, permissions are managed per server, and a repository lives at forge.example/myrepo instead of forge.example/owner/myrepo.
  • A migration path off GitHub that keeps the history. Importing the code is easy; importing the issues, pull requests and discussions with their original authors attached is the part that matters. I'd keep a placeholder for each GitHub account and let whoever owns that account prove it, after which the instance swaps in their fediverse actor, so attribution carries over. How to express that claim in ActivityPub is the part I haven't figured out. It may need a new FEP.

Where this stands: I haven't read the whole spec, Fedify doesn't ship the vocabulary yet (fedify-dev/fedify#751), and I have too much else going on to start soon. If you've run a forge or implemented ForgeFed, I'd like to hear whether any of this makes sense.

github.com

@fedify/forgefed package for ForgeFed vocabulary support · Issue #751 · fedify-dev/fedify

Background ForgeFed defines an ActivityPub federation protocol for software forges such as Gitea and Forgejo. The spec adds forge-specific actor types (Repository, TicketTracker, PatchTracker, Proj...

@fossforall@mastodon.social · Reply to FOSS for All

다음 편에서도 Microgrants에 지원한 오픈소스 프로젝트들을 이어서 소개할게요.

더 많은 한국의 오픈소스 이야기가 궁금하다면, FOSS for All을 팔로우해 주세요! 🌱

@fossforall@mastodon.social

우리가 만난 오픈소스 프로젝트들 ① 🌱

한국의 오픈소스 문화가 무럭무럭 자랄 수 있도록, FOSS for All Microgrants가 시작되었어요.

2026년 Microgrants 사업에 함께한 국내 오픈소스 프로젝트·커뮤니티를 만나보세요!

(아래에 계속! 👇)

@hongminhee@hollo.social

커피를 못 마시긴 하지만, 커피챗은 언제나 歡迎(환영)입니다! 專業(전업) F/OSS 開發(개발)이나 F/OSS 프로젝트로 STF나 NLnet 같은 公的(공적) 資金(자금) 받는 要領(요령)에 關心(관심) 있으시면 DM이나 이메일로 聯絡(연락) 주세요! 꼭 저런 主題(주제)가 아니더라도 소프트웨어 開發(개발) 全般(전반)이나 漢字(한자)·國漢文(국한문)混用體(혼용체) 等(등) 多樣(다양)한 主題(주제)도 좋습니다.