洪 民憙 (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 try to be polite when I write prompts for LLMs. Especially in languages like Korean or Japanese that have grammatical honorifics, I make sure to use the formal, respectful form of speech (what's known as 敬語—gyeongeo or keigo). I joke with my friends that I'm using polite language early on to be pardoned for my sins when AI eventually takes over the world, but the real reason is that I don't want to get used to speaking to someone in a commanding tone. It makes me think I might start believing it's “okay” to order around certain intelligent beings, almost like condoning slavery.

@sirber83 @julian Thanks! You might not have been able to find it because you were searching for “JavaScript” instead of “TypeScript.” What do you mean by “standalone” by the way? Fedify is typically used in together with with other web frameworks like Express or Next.js.

Update: Just added Valibot integration as well!

https://unstable.optique.dev/concepts/valueparsers#valibot-integration

Update: Just added automatic metavar inference!

The help text now gets smarter labels based on your Zod schema:

• z.string().email() → EMAIL
• z.coerce.number().int() → INTEGER
• z.enum([…]) → CHOICE

No manual configuration needed.

https://github.com/dahlia/optique/commit/d4903dfdb88727a488dedb6a73ad8997868246e1

@mikebroberts Zod's a solid choice! The transform stuff can be tricky at first but becomes second nature.

Let me know if you end up trying Optique—always curious to hear feedback.

Community deployments 🙇‍♂️ https://github.com/cheeaun/phanpy?tab=readme-ov-file#community-deployments

Optique 0.7.0 will support Zod schemas as value parsers.

Seemed like a natural fit—same validation logic for both CLI and app code.

https://github.com/dahlia/optique/issues/39

근데 果然(과연) 이런 게 興味(흥미)로운 內容(내용)일까…? 🤔

We’re also looking ahead to what comes next. In another blog post published today, we introduced Mastodon’s new leadership team. Our Executive Director is @mellifluousbox (formerly, CFO of Mastodon gGmbH), who has already represented Mastodon on international stages.

We also shared an organisational update, and a fundraising update, in that blog post.

https://blog.joinmastodon.org/2025/11/the-future-is-ours-to-build-together/

Our Founder, @Gargron is stepping down from his position as CEO. He shared a reflection on his time building and growing Mastodon on our blog.

We want to take a moment to express the Mastodon team’s deep gratitude and admiration for Eugen, and for the technology and community he has built here. We’re thrilled he’s staying on in an advisory capacity.

https://blog.joinmastodon.org/2025/11/my-next-chapter-with-mastodon

Hey everyone, we have some pretty big news to share. You might remember that we announced a big restructuring for the Mastodon team earlier this year. Today marks an important milestone in this transition.

#Mastodon #Fediverse #SocialWeb

If you're a software developer and need to create a presentation with a lot of code, I highly recommend you consider Slidev (by @antfu.me). Especially if you need to include TypeScript code!

Slidev is web-based presentation software made for software developers. It offers a wide variety of ways to present code in your slides, like highlighting specific code in sequence, displaying TypeScript type information in tooltips through Twoslash integration, a “magic move” feature that compares the before and after of your code with a cool animation, the ability to embed the Monaco editor, and more.

This was my first time using Slidev, but I was captivated by its rich feature set. You should give it a try too!

그나저나 Slidev는 소프트웨어 프로그래머를 爲(위)한 정말 잘 만든 發表(발표) 슬라이드 作成(작성) 소프트웨어 같다. 特(특)히, 슬라이드에 TypeScript 코드를 꽤 包含(포함)해야 하는 發表(발표) 資料(자료)를 만든다면 Slidev를 使用(사용)해 볼 것을 勸(권)한다. Twoslash가 支援(지원)된다…!

꼭 TypeScript 코드가 아니더라도 特定(특정) 줄들을 順序(순서)대로 強調(강조)하는 것도 되고, 라이브로 코드를 고칠 수도 있다. 비포 애프터로 두 코드를 比較(비교)할 때도 매직 무브로 괜찮은 演出(연출)이 可能(가능)하다.

아무튼 Slidev 最高(최고)…!

Optique 發表(발표) 資料(자료) 아직도 만드는 中(중)… 이걸 이렇게 며칠씩 붙잡고 있는 게 말이 되나…

By the way, both Elixir and Ruby are programming languages that are really not my cup of tea…

Setting up an Akkoma instance to test the LitePubRelay implementation of the @fedify/relay package (by @z9mb1)…

어려운 사람 테스트: 난 함께 지내기 매우 쉬운 사람입니다. https://www.idrlabs.com/kr/difficult-person/20-30-10-10-15-15-10/result.php

@kodingwarrior 쉬엄쉬엄 하세요…

#Hollo 0.7 brings a redesigned #notification system with much better performance. We've moved from generating #notifications on-demand to storing them as they happen, which makes the notifications endpoint about 60% faster. We've also added response compression (though if you're using a reverse proxy, you probably had this already).

More notably, Hollo 0.7 implements Mastodon's v2 grouped notifications API. Notifications like favorites, follows, and reblogs targeting the same post or account are now grouped together server-side, reducing clutter. Clients that support the new API (introduced in #Mastodon 4.3) will show cleaner, more organized notifications automatically.

Hollo 0.7 is still in development, but we're excited to share it with you when it's ready!

If I really end up buying a Steam Machine, I guess I'll have to get a Steam Controller too, right…? 🤔

Holloの通知取得APIが遅くなってから結構経つけど、ようやく今見てる。今日中に直すのが目標！

@jnkrtech That's a really interesting idea! The “greedy but respect defined handlers” approach would definitely be more user-friendly—no worrying about option order is a big win.

The challenge is that it would require a significant architectural change to how Optique currently works. Right now, parsing is a single-pass, left-to-right process where each parser consumes tokens as it encounters them. Your suggestion would need something like a two-pass system:

1. First pass: scan all tokens and match against explicitly defined parsers
2. Second pass: collect remaining unmatched tokens into passThrough()

This is doable, but it's a fairly fundamental shift from the current design. 🤔

I really like where you're going with this though. Let me spend some time thinking about whether there's a way to support this pattern without requiring a major redesign. Maybe there's a middle ground, or maybe the two-pass approach is worth it for the better DX.

And good luck convincing your team to switch! 🥰

Interesting design question for #Optique (a type-safe #CLI parser for #TypeScript): how should it handle unrecognized options in wrapper/proxy tools? Proposed three modes but wondering if the complexity is worth it. Thoughts?

https://github.com/dahlia/optique/issues/35

Even though I already have three gaming consoles (a PlayStation 5, a Nintendo Switch 2, and a Steam Deck), I still find myself wanting to buy a Steam Machine. 😂

12月(월) 初(초)에 할 Optique 發表(발표)를 爲(위)한 슬라이드 資料(자료)를 만들고 있는데, Optique의 具顯(구현) 細部事項(세부사항)까지 다뤄야 할 지, 아니면 使用者(사용자) 立場(입장)에서의 콘셉트나 API 같은 걸 爲主(위주)로 다뤄야 할 지 苦悶(고민)이네… 具顯(구현) 디테일을 다루려고 하면 주어진 發表(발표) 時間(시간)인 30分(분) 안에 못 끝낼 것 같다는 느낌도 들어가지고…

This is super cool! I could see myself using it if/when I publish videos on Youtube.

Chris Hayes built a single-user ActivityPub server for sharing YouTube videos on the fediverse using Fedify and Next.js. The source code is available at https://codeberg.org/chris-hayes/yt-on-fedi.

It's alive! 🧟

After a bit of trial-error, got fediverse comments showing on a #nextjs site running #fedify. My personal fediverse-connected youtube mirror is now mostly feature complete.
(The video post in the screenshot is over here: https://watch.hayes.software/video/16)
#fediverse

空が高い
冬だねえ

@shauna reminds me I need to finish the Fedify / @adonisframework integration so folks can move fast with the full stack Adonis provides