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

洪 民憙 (Hong Minhee) :nonbinary:

@hongminhee@hollo.social

1,072 following1,877 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

@thisismissem@hachyderm.io · Reply to Emelia 👸🏻

The researchers are trying to attribute the heat increase to the servers running within the data centers, when we know from other research that this likely isn't the case. We have other explanations, they just didn't fit the narrative for this story.

Many datacenters have switched to closed loop cooling systems & have realised that the heat the servers produce is actually a resource they can sell, whether through heat exchange programs or municipal heat networks, or to industrial users who often need heat. Not capturing that heat your datacenters are producing would literally be throwing money away, burning cash.

@thisismissem@hachyderm.io

So I'm seeing this article from NewScientist going around here too, and I'm begging people to use their critical thinking skills for just one minute. This article is misinformation, it is correlation without causation, and honestly, New Scientist should be ashamed at publishing it.

newscientist.com/article/25212

They've now put it behind their paywall, it's quite literally clickbait to convert people to subscribers. Let's look at some of the claims:

”Marinoni says that areas including the Bajío region in Mexico and the Aragon province in Spain saw a 2°C (3.6°F) temperature increase in the 20 years between 2004 and 2024 that couldn’t otherwise be explained.“

I can think of one very easy reason why temperatures in these two regions may have gotten warmer, and it's not data centres: climate change.

We know that climate change on average increased temperatures 1-2°c, meaning some areas saw higher increases than others.

As someone else called out "the Bajio region has a metric fucktonne of oil processing in Salamanca and is a plateau region ringed by mountains so yeah"

yeah, I'm sure it was the data centres and uh, definitely not those oil refineries.

In the most extreme case, the researchers said "temperatures increased by 9.1°C", now, unless we're talking about Elon Musk's data centres which are breaking EPA rules by using multiple truck-sized gas turbine generators, maybe there's another reason for this increase?

Let's have a think about where datacenters are built: they tend to be built on greenfield sites, because that is where land is cheapest.

Once one datacenter moves in, other providers usually follow, so we're looking at temperature increase data for land that has gone from literally being a green field with trees, to a concrete, asphalt roads, and metal roofs with very little green space nor tree coverage.

We know the built environment without tree coverage causes the urban heat island effect, where neighborhoods in the same city with and without tree coverage show significantly different temperatures.

"The urban heat island effect can make the country's most populated cities 20 degrees Fahrenheit warmer than nearby areas" – CBS News explaining heat island effect.

@hongminhee@hollo.social

BotKit is a TypeScript framework I've been building for creating ActivityPub bots that run as their own independent servers—no platform account needed, no Mastodon or Misskey instance to log into. You write a bot, give it a username, and it federates directly with the rest of the fediverse. It's built on top of Fedify, so the low-level protocol work is handled for you: HTTP Signatures, WebFinger, JSON-LD, all of it. What you're left writing is just the bot logic itself.

Version 0.4.0 is out today, with a PostgreSQL repository for production deployments, a remote follow button on the bot profile page, and a few other additions.

Release notes: https://github.com/fedify-dev/botkit/discussions/20

github.com

BotKit 0.4.0: PostgreSQL repository, remote follow button, and Fedify 2.x upgrade · fedify-dev/botkit · Discussion #20

We're pleased to announce BotKit 0.4.0. This release brings a PostgreSQL repository for production deployments, a remote follow button in the built-in web interface, a new API for broadcasting prof...

@botkit@hollo.social

BotKit 0.4.0 is out! This release adds @fedify/botkit-postgres, a PostgreSQL-backed repository for deployments where SQLite isn't enough; a remote follow button on the bot profile page, so visitors can follow directly without manually searching from their own instance; and Session.republishProfile(), which lets you push profile changes to followers without waiting for the next post. It also upgrades the underlying Fedify dependency to 2.1.2, with a few small breaking API changes.

Full release notes:

https://github.com/fedify-dev/botkit/discussions/20

github.com

BotKit 0.4.0: PostgreSQL repository, remote follow button, and Fedify 2.x upgrade · fedify-dev/botkit · Discussion #20

We're pleased to announce BotKit 0.4.0. This release brings a PostgreSQL repository for production deployments, a remote follow button in the built-in web interface, a new API for broadcasting prof...

@kodingwarrior@hackers.pub
@botkit@hollo.social

BotKit 0.4.0 is out! This release adds @fedify/botkit-postgres, a PostgreSQL-backed repository for deployments where SQLite isn't enough; a remote follow button on the bot profile page, so visitors can follow directly without manually searching from their own instance; and Session.republishProfile(), which lets you push profile changes to followers without waiting for the next post. It also upgrades the underlying Fedify dependency to 2.1.2, with a few small breaking API changes.

Full release notes:

https://github.com/fedify-dev/botkit/discussions/20

github.com

BotKit 0.4.0: PostgreSQL repository, remote follow button, and Fedify 2.x upgrade · fedify-dev/botkit · Discussion #20

We're pleased to announce BotKit 0.4.0. This release brings a PostgreSQL repository for production deployments, a remote follow button in the built-in web interface, a new API for broadcasting prof...

@hongminhee@hollo.social

Everyone in tech talks about moats like they're achievements. I keep reading “moat” and thinking: so the idea is to make leaving expensive. Maybe it's just me, but that feels a little grim.

@element@mastodon.matrix.org

🚀 Spaces has landed on Element X!

Navigate chats by department, project or interest - no more overwhelming room lists.

✨ What’s new: filtered chat lists, dedicated Spaces tab, flexible room creation and previews with context.

👉 Download Element X and explore Spaces today!

element.io/blog/spaces-has-lan

element.io

Spaces has landed on Element X!

Spaces have landed on Element X! Spaces bring a faster, cleaner and more intuitive way to organise conversations. Gone are the long, overwhelming room lists as you can now navigate discussions by department, project or interest with a single tap.

@hongminhee@hollo.social

After a pretty long break, I'm back to working on @botkit. The upcoming v0.4.0 isn't going to be a big release—mainly a major @fedify version bump and some general cleanup—but it felt like time to dust it off.

@hongminhee@hollo.social

標準國語大辭典(표준국어대사전)》 MCP 서버를 만들었습니다.

旣存(기존)에도 《標國大(표국대)》 MCP들이 있긴 한데, 그냥 標題語(표제어)랑 뜻풀이만 덜렁 주는 데다가, 每番(매번) stdict.korean.go.kr 서버에 要請(요청)하는 ()으로 作動(작동)해서 레이트 리미트에 걸리더라고요. 제가 만든 건 아예 全體(전체) 辭典(사전) 데이터를 맨 처음에 받은 다음에 그걸 SQLite에 넣고 照會(조회)합니다.

github.com

GitHub - dahlia/ko-stdict-mcp: 《표준국어대사전》 MCP 서버

《표준국어대사전》 MCP 서버. Contribute to dahlia/ko-stdict-mcp development by creating an account on GitHub.

@ppatel@mstdn.social

"But I fundamentally disagree with the conclusion.
The proposed solution is denial and isolation: block the crawlers, withdraw from centralized forges like GitHub, make our work inaccessible to AI scrapers, shun those who use these “anti-ethical tools” from our communities. I understand the anger behind it. But I think it misses something important and misreads the historical pattern that has shaped FLOSS itself."

We should reclaim LLMs, not reject them

writings.hongminhee.org/2026/0

writings.hongminhee.org

Histomat of F/OSS: We should reclaim LLMs, not reject them

A few days ago I read a blog post titled On FLOSS and training LLMs . It captures well the frustration spreading through the free and open source software…

@hongminhee@hollo.social · Reply to John O'Nolan

@john That’s fascinating—and it makes sense that you'd notice it more sharply than most. I hadn't really thought about how deep it goes beyond the obvious ones. “Vivid” is a good example; I use it all the time without thinking.

@hongminhee@hollo.social

I've been trying not to use words like “blindly” and “eye-opening.” Using blindness to mean not knowing or not noticing something doesn't sit right with me. But English isn't my first language, so finding replacements is harder than I expected. Sometimes “uncritically” works for “blindly,” but not always. I still haven't found a good casual replacement for “eye-opening.” I don't think people who use these words are bad. I just don't want to use them myself.

@hongminhee@hollo.social · Reply to Wartezimmer

@Kaesekuchen Honestly, yes, it's global state… just scoped per thread/task. The advantage over a plain global is that you get isolation across concurrent requests without threading values through every call. The debugging experience with contextvars was rough in my memory, though I haven't used it in a while. Statically typed implicits feel safer to me because they desugar to actual arguments, so the compiler keeps track. The footgun either way is that context-dependent functions proliferate silently and become hard to refactor out.

Reading this also made me realize I've had a soft spot for dynamic scoping/implicits for a long time… probably since I first used @mitsuhiko's Flask, where the request context object was just there without you having to pass it around. Felt like magic, then felt like a footgun, then felt like a reasonable tradeoff again. Python has since put contextvars in the standard library, which is essentially the same idea.

docs.python.org

contextvars — Context Variables

This module provides APIs to manage, store, and access context-local state. The ContextVar class is used to declare and work with Context Variables. The copy_context() function and the Context clas...

@hongminhee@hollo.social

Enjoyed this wiki post by the author of Garnet on effect systems: [[PonderingEffects]]. What I liked is that it doesn't just describe the design space: it's honest about what the author finds confusing or unconvincing, including a skeptical take on algebraic effect handlers specifically. The Lobsters thread is worth reading too; someone points out that what the post calls “effects on data” is already studied under the name coeffects, which was news to me.

lobste.rs

Pondering Effects

6 comments

@hollo@hollo.social

Hollo has always been headless—no built-in frontend, just a Mastodon-compatible API. You pick your own client. That's kind of the point.

But we've been wondering: what if Hollo shipped its own web frontend? The Mastodon-compatible API would stay, so your current client setup wouldn't change. It'd just be one more option.

Would you use it?

  • Yes, I'd switch to it3 (6%)
  • Maybe, depending on what it offers12 (22%)
  • No, I'd stick with my current client8 (15%)
  • I'm just curious / not a Hollo user31 (57%)
@rick@rmendes.net

Reading Hong Minhee with my coffee this morning, its again one of these moments where I stumble on something that express exactly (and better) what I had in mind, in a latent space, without being able to express it so beautifully.

I want my code to be used for LLM training. What I don’t want is for that training to produce proprietary models that become the exclusive property of AI corporations. The problem isn’t the technology or even the training process itself. The problem is the enclosure of the commons, the privatization of collective knowledge, the one-way flow of value from the many to the few.

The question isn’t whether to use LLMs or adapt to them—that ship has sailed. The question is: who owns the models? Who benefits from the commons that trained them? If millions of F/OSS developers contributed their code to the public domain, should the resulting models be proprietary? This isn’t just about centralization or market dynamics. It’s about whether the fruits of collective labor remain collective, or become private property.

More from where that come from here, here and here



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

🔗 https://rmendes.net/bookmarks/2026/03/22/yes-we-should-reclaim-llms-not-reject-them

rmendes.net

Yes, We should reclaim LLMs, not reject them.

Yes, We should reclaim LLMs, not reject them. 22 March 2026 AI 🔖 https://writings.hongminhee.org/2026/01/histomat-foss-llm/ - Reading Hong Minhee with my coffee this morning, its again one of these m...