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

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

I'm thinking of proposing a #fediverse/social web community track at @COSCUP 2026 (Aug 8–9, Taipei)—think FOSDEM's Social Web devroom, but in East Asia. Before I submit the CFP, I'd love to get a sense of what to call it. What do you think?

(Boosts appreciated!)

#ActivityPub #SocialWeb #fedidev #COSCUP

@silverpill @phnt That's a fair clarification, and worth being precise about on my end too.

I'm not arguing for historical inevitability—I don't think that's a useful frame for anyone here. What I was saying is closer to a personal read of the current situation: a lot of developers already depend on LLMs in their day-to-day work, and that number seems to be growing quickly. That's an observation, not a law of history, and I could be wrong about where it leads.

The NFT comparison is interesting and I won't dismiss it. My intuition is that LLMs are a different kind of thing—they've become embedded in actual workflows in ways NFTs never were—but I hold that loosely. Technologies do fail in unexpected ways.

What I'm more confident about is the narrower point: maintainers have real authority over their own projects, and I think there's more room in that space than “accept everything” or “reject all AI-assisted contributions.” My own approach with Fedify has been to set conditions rather than draw a line: disclose what you used, show you've actually tested it. Whether that's the right call, others can judge: https://github.com/fedify-dev/fedify/blob/main/AI_POLICY.md.

@alvan Yeah, C# is already kinda feature creep… 😭

蒙古タンメン中本に来た。

C# 15 & .NET 11 preview 3 finally got discriminated unions!

https://github.com/dotnet/csharplang/blob/main/proposals/unions.md

@silverpill @phnt

@silverpill is right that maintainers hold real authority here, and I want to build on that rather than argue against either of you.

The frustration with LLMs is largely legitimate. But “how does this look to outsiders” is a poor criterion for evaluating ethical concerns; by that standard, feminism looks like lunacy to 4chan. The question is whether the concerns are correct, not whether they're legible to the unconvinced.

That said, I don't think making LLMs socially unacceptable is a viable path, and not just because the adoption curve has run too far. The maintainer's authority is real precisely because it's specific: you decide what enters your project. Refusing AI-assisted contributions is a legitimate choice. But declaring LLM use itself impermissible starts to look like “I only accept patches written in Vim, not IDE-generated code”—a demand that grows harder to justify as the tools become ordinary. As maintainer of Fedify, I've taken a middle path: disclose what you used, show you've tested it yourself, and we're fine. See also https://github.com/fedify-dev/fedify/blob/main/AI_POLICY.md.

What worries me more is that the “total rejection vs. total acceptance” framing leaves the actual problem untouched. If we stay inside that binary, OpenAI and the others keep the models, keep the surplus, keep the compute bills externalized onto the climate—with no pressure to change any of it. The ethical problems with LLMs aren't properties of the technology; they're properties of who owns it and under what terms. I've written about this in more depth if it's of interest: Histomat of F/OSS: We should reclaim LLMs, not reject them and a follow-up Acting materialistically in an imperfect world: LLMs as means of production and social relations.

Whoa. UTF-8 is older now than ASCII was when UTF-8 was invented.

We've just added an English homepage for FediDev KR, a community of fediverse developers living in Korea or using the Korean language.

If you're interested in connecting with Korean-speaking fediverse developers, feel free to check it out: https://fedidev.kr/en/.

The Release Candidate for TypeScript 6.0 is now available!

Read up on what's coming up with 6.0 & 7.0, and try it out on your codebase today!

https://devblogs.microsoft.com/typescript/announcing-typescript-6-0-rc/

Today, I had lunch with @Yohei_Zuho and @kur0den0010 from FediLUG Japan, along with @nebuleto from FediDev KR, and it looks like something exciting is going to happen at @COSCUP 2026! Stay tuned!

明日起きたらDeno+Hono+Fedifyに入門する。
おやすも

Has anyone made a good guide for how to ask for survival money on the fediverse yet? One that outlines how tagging strangers isn't a good long term strategy. That it can temporarily work for engagement but sooner or later you will either loose your account or get blocked so much that you don't have much reach. There is this influx of people trying to crowd fund for their survival coming here and we should help provide them with the means to continue to do so sustainability.

오늘 FediLUG 日本(일본)의 @Yohei_Zuho 님과 @kur0den0010 님, 韓國(한국) 聯合宇宙(연합우주) 開發者(개발자) 모임의 @nebuleto 님과 제가 모여서 함께 點心(점심) 食事(식사)를 했습니다. 아무래도 @COSCUP 2026에서 聯合宇宙(연합우주)와 關聯(관련)된 재밌는 일이 일어날 것 같으니, 많은 期待(기대) 付託(부탁)드립니다!

@Yohei_Zuho 一緒に頑張りましょう！これからよろしくお願いします！

えらいことになってきた

Today, I had lunch with @Yohei_Zuho and @kur0den0010 from FediLUG Japan, along with @nebuleto from FediDev KR, and it looks like something exciting is going to happen at @COSCUP 2026! Stay tuned!

Apparently there's a group called the 分散型SNSユーザー有志(Decentralized SNS User Volunteers). It seems to be a separate decentralized SNS group from Tyazuki's 分散型SNSの会(Decentralized SNS Gathering) and Nawashiro's Decentralized SNS Meetup@continue5645@misskey.io. This "Decentralized SNS User Volunteers" group appears to be run by someone called もちもちずきん(Mochi-Mochi-Zukin). By the way, my group @KawaneRio@misskey.io is the Misskey VRChat Group @MiVRC@misskey.io. Wait, that's even more niche than decentralized SNS...
#Fediverse


分散型SNSユーザー有志といふものがあるらしい。茶好きさんの分散型SNSの会や、Nawashiroさんの分散SNS集会@continue5645@misskey.ioとは別の分散型SNSグループらしく、こちら分散型SNSユーザー有志はもちもちずきんさんって方によって揮られてゐるらしい。 知らなかった、そんなの・・・
ちなみに我 @KawaneRio@misskey.io のグループは MisskeyVRChat部 @MiVRC@misskey.io ね。いや分散型SNSよりさらに限定されてるやんけ・・・
#分散型SNS

[Federated systems need better affordances]
by @voboda
https://blog.voboda.com/better-affordances-for-federated-systems

#moim_live #fedidev

I'm building an open source ActivityPub service called "Moim" — 모임 in Korean, meaning gathering or meetup. It started as a federated RSVP service, but I realized I wanted to connect people even beyond events. Events are where people come together, yes — but places carry meaning on their own, even in quiet, ordinary moments.

So Moim is about helping people feel connected: through events, and through the simple act of sharing where they are.

Right now, I'm focusing on three areas:

• CRM for Event Organizers A proper SaaS-like experience built for people who run events. I'm actively reaching out to organizers to shape this.
• A Federated RSVP Service I want Moim's RSVP experience to feel just as polished as anything outside the Fediverse — and ideally, better. Being federated shouldn't mean settling for less.
• A Check-in Sharing System I miss what Foursquare Swarm used to be. I want to bring that feeling back, built for the Fediverse.

I don't know yet if I'm building the right thing. But I'll keep going, and do my best to make it something worth using. If I'm ready, I will officially announce to public.

선비 브라우저 擴張 프로그램 테스트 用 글.

moim.live 에 authorized fetch 지원 완료

Let's stop saying Fediverse is federated + universe and start saying it's federated + diverse

最近、開発作業でよく使うツールをいくつか変更した。

最初のきっかけは、コードエージェントをもう少し快適に使える環境を探していて Warp を試してみたことだったと思う。そこから連鎖的に環境を見直すことになり、

• tmux → zellij
• zsh → fish
• vi → hx (Helix)
• iTerm2 → Ghostty という感じで、思った以上に大きく変わった。
• 最初は軽く触ってみるだけのつもりだったのだが、使い心地がかなり良くて、業務用のMacはほぼ完全にこの環境へ移行した。個人用のMacは、時間があるときに少しずつ切り替えていく予定。
• とはいえ、まだいくつか気になるバグもある。例えば、zellijで韓国語フォルダ名が文字化けする問題、fish + Ghostty の組み合わせで、ウィンドウサイズを小さくすると thread 'main' panickedが出る問題 など。
• 完全に安定しているとは言い難いが、今のところは許容しながら使っている。

Obsidian への完全移行

• ただ、それ以上に大きな変化だったのは ドキュメント管理を Obsidianに移したこと。実は3年くらい前にも、業務日誌を書く用途で少しだけ使っていたのだけど、そのときは結局定着しなかった。今回は思い切って、個人用・業務用を含めたすべての「第二の脳」的なメモ保管庫として使い始めた。過去のメモも、時間を見つけて少しずつ移行している。これまで使っていたメモツールはこんな感じ。Heynote, Simplenote, vscode-memo-life-for-you, Dynalist, Notion, そのほか、Google DriveやDropboxに散らばっているドキュメント。正直、かなり分散していた。

移行のきっかけ

きっかけは、Claude Codeとの会話ログや plan.md（計画ファイル）を保存する場所を探していたこと。ちょうど良い Markdown ベースの保存場所を探していて、「そういえば Obsidian があったな」と思い出した。さらに調べてみると、今後 CLIサポートも予定されている、プラグインが非常に豊富、 Markdownベースでローカル管理できる。など、改めて見るとかなり自分の用途に合っている。それに、今の時代は AIに相談しながら段階的に環境を整えられるので、プラグインの多さにもそこまで抵抗を感じなかった。

一番気に入っているポイント

そして、個人的に一番気に入っているのはアプリ内のフォントを自由に変更できること。 Macでも、モバイルアプリでもフォントを変えられるのは、自分にとってはかなり大きい。 Obsidian自体もそのままで十分気に入っているのだけど、正直このフォント変更機能だけでも、多少の不満点はすべて相殺できるくらいのメリットだと思っている。

メタモンのシロノワールブルーベリーフロマージュ食べにコメダ珈琲店に来た。

モスバーガーに来て焼肉のライスバーガーを食べた。写真は無い。

getting reccomended a Korean video teaching a Chinese part of Japanese auto-translated to English

I'm sure this will be very useful to me.

京鴨汁つけうどんを食べに来た。

@wildwestrom 그냥 놀러 왔어요! 사람들도 좀 만나고요. ㅎㅎ

宿にチェックインした。

@Yohei_Zuho 😭