洪 民憙 (Hong Minhee)

@tatmius もしよろしければ、月曜日の午前中に少しコーヒーでもいかがでしょうか？ご予定があれば、どうぞ遠慮なくお断りください！ただ、日本語は読む・書くのに比べて会話が苦手なので、少しもどかしい思いをさせてしまうかもしれません。

最近、ハンバーグ嘉がソウルにも開店した。ちょうど家の近くなので、昨日を除いて先週の土曜日から今日まで毎日通っている。今も夕食を食べに来ている。

@tatmius 韓国にいらっしゃったんですね！もしかしてソウルにいらっしゃいますか？

文禄•慶長の役も、軽くは知ってたけど、いざこの年になって詳しく知ってみると、めちゃくちゃヤバい事やってる。

韓国の歴史を知ると、「日本何やってんねん」ってなる事多いな…..

韓国、英語より日本語の方が通じている

大韓民国歴史博物館、韓国近代史観を知るにはかなりよかった。思ってるより最近まで政治は全然色々あって、大変やなぁという感じ。

続報。もう一つのCFP、繰り上げでのご登壇のご相談をいただきました！もちろん二つ返事でお受けして、もう返信も済ませました。嬉しい！

어라, 다른 發表(발표) 하나가 取消(취소)되어서 發表(발표) 해 줄 수 있냐는 메일을 받았다…!

@box464 Yeah, October 1st is too tight; I can't promise v0.6.0 by then. Moving somewhere else first makes sense. Mastodon's 30-day migration cooldown only applies to the account that moved, so your new account can move to a BotKit bot once 0.6 ships. I'll let you know when it's out. Thanks for being willing to try it!

@box464 Thanks for this post! It gave me an idea for a new BotKit feature: letting an existing account move its followers to a bot.

BotKit 0.6.0 should be out in early to mid October, and I expect it to include fedify-dev/botkit#48, which is what your move needs. Could you wait until then?

If things go well and I find the time, v0.6.0 might even cover everything under fedify-dev/botkit#47. Please don't count on that part, though.

@celeduc Good timing, @hongminhee just recently published a proposal for what you're asking: https://hollo.social/@hongminhee/01a0aa1c-a16d-71fa-826a-6841c4d77c18

I would describe this as mature work on the protocol level, but no one can know in advance when (or if ever) it'll be added to other popular ActivityPub platforms.

Casually deciphering posts in languages I don't know is enjoyable and is good mental exercise. I'm glad it doesn't automatically translate everything.

That having been said, sometimes I'd like to publish multilingual posts where I control the translation, the same way you can publish different subtitles for a video (or use automated translation). Same for alt text.

This may be the thing that motivates me to learn something about #ActivityPub

Hey fediverse, happy Earth, Wind & Fire Day!

https://youtube.com/watch?v=Gs069dndIYk

#EarthWindFire #DoYouRemember #21stNightOfSeptember

For non-Korean gamers:

TL;DR: This game is a piece of trash that glorifies Park Chung-hee, the Korean Hitler. Please report this game.

This store page casts Park Chung-hee as a potential "father of a nation" and frames his coup as "national renewal," but never mentions his regime's abuses: about 1,770 "vagrants" were held for unpaid forced labor in Seosan, with beatings and forced mass weddings; the 1972 Yushin Constitution allowed unlimited re-election, and its key emergency decrees were ruled unconstitutional; in 1979 martial law troops crushed the Bu-Ma protests, arresting 1,058.

Sources:

• Store page: https://store.steampowered.com/app/5035220/For_the_Fatherland_Chronicle_of_Park_Chunghee/
• Seosan forced labor (AP/VOA): https://www.voanews.com/a/in-s-korea-ex-vagrants-want-land-promised-for-forced-labor/3798751.html
• State acknowledgment (2026): https://www.khan.co.kr/en/article/202608071731027/
• Yushin Constitution (Library of Congress): https://guides.loc.gov/south-korean-democratization-movement/anti-yusin-movement
• Emergency decrees ruling (Korea Herald): https://www.koreaherald.com/view.php?ud=20130321000846
• Bu-Ma protests (Korea Democracy Foundation): https://archives.kdemo.or.kr/display/en/1970.html
• Bu-Ma arrests: https://en.wikipedia.org/wiki/Busan–Masan_Uprising

new post

i promise i didn't want to write this. i'm pretty scared right now. i'm trying to hold onto hope.

https://jyn.dev/a-year-to-fix-security/

스팀에서 박정희 미화물을 발견했습니다. 혹시 가능하시다면 박정희가 저지른 만행과 그 출처를 담아 신고 부탁 드립니다.

Email, Decoupled From Where and How: A Cross-Runtime, Cross-Provider Email Library for JavaScript and TypeScript, by @hongminhee:

https://hackers.pub/@hongminhee/2026/upyo-email-decoupled-from-where-and-how?ref=frontenddogma.com

#email #tooling #javascript #typescript

今年(금년) 中(중)에 日本(일본) 한 番(번) 가고 싶은데, 갈 理由(이유)가 딱히 없다… JSConf JP 2026 發表(발표)도 떨어졌고… 😂

일본 페미니스트들 “천황제에 종지부를” 집회 연 이유 https://www.ildaro.com/10545
"그런데, 일본의 페미니스트들 사이에서는 다른 목소리가 제기되었다. 여성도 천황이 될 수 있게 해 달라는 게 아니라, 애초에 혈통과 성별에 따라 누군가의 지위와 삶을 규정하는 천황제를 유지해선 안 된다는 것이다."

Quick update: implementation of FEP-22cd has started in Fedify (PR #1038). Once it's reviewed and merged, it'll ship in Fedify 2.4.0, which I'm aiming to release within September.

Okay, now it's merged!

https://w3id.org/fep/22cd

I'm 92%

however it seems the questionnaire lacks some "neutral" options

like the 7th question about housing prices, the "curb speculative demands" option might slide into "curb foreign nationals" kind of xenophobia

also how I view "a person with different political leaning become my child's spouse" well I don't have a child but it's my child's choice anyway and I don't think I have the power to interfere

the "gender" options also don't contain "non-binary" but I don't expect that much out of an east-asian society

《한겨레》에서 만든 〈나는 얼마나 進步(진보) 或은(혹은) 保守(보수)일까?〉 테스트를 해 봤는데, 「全(전)國民(국민) 中(중) 99%보다 進步(진보) 性向(성향)입니다」라고 떴다.

https://policy-survey-2026.hani.co.kr/results?s=0015yJot

I've been working on a FEP draft for the past few days: FEP-22cd Attributing translations.

Hackers' Pub already machine-translates articles, but I want authors to be able to publish their own translations too, and let organizations split the work across members. Once you do that, Activity Streams doesn't give you much to work with. attributedTo names an author, not a translator. Nothing distinguishes a language a human translated from one an AI produced. And nothing says whether a translation still matches the current text or was written against an older version of the article.

Schema.org already has translator, translationOfWork, and inLanguage for exactly this, so the FEP mostly reuses those instead of minting new vocabulary. I had to decide whether to give each language its own object, linked back to the original, or keep everything on one object the way contentMap already does. Splitting it looked cleaner at first, but it also means spreading replies and reactions across separate posts for each translation. I don't want adding a translation to split the conversation.

I kept everything on one object, using contentMap for the text in each language. The draft adds a translations property to record who translated each version and whether it was translated by a human, generated by a machine, or generated by a machine and reviewed by a human. A timestamp lets you tell whether a translation still matches the current text, without publishing the server's private edit history.

You can discuss it on SocialHub or in the draft PR. If you run anything that touches multilingual content, I'd like to hear where this breaks.

I've been working on a FEP draft for the past few days: FEP-22cd Attributing translations.

Hackers' Pub already machine-translates articles, but I want authors to be able to publish their own translations too, and let organizations split the work across members. Once you do that, Activity Streams doesn't give you much to work with. attributedTo names an author, not a translator. Nothing distinguishes a language a human translated from one an AI produced. And nothing says whether a translation still matches the current text or was written against an older version of the article.

Schema.org already has translator, translationOfWork, and inLanguage for exactly this, so the FEP mostly reuses those instead of minting new vocabulary. I had to decide whether to give each language its own object, linked back to the original, or keep everything on one object the way contentMap already does. Splitting it looked cleaner at first, but it also means spreading replies and reactions across separate posts for each translation. I don't want adding a translation to split the conversation.

I kept everything on one object, using contentMap for the text in each language. The draft adds a translations property to record who translated each version and whether it was translated by a human, generated by a machine, or generated by a machine and reviewed by a human. A timestamp lets you tell whether a translation still matches the current text, without publishing the server's private edit history.

You can discuss it on SocialHub or in the draft PR. If you run anything that touches multilingual content, I'd like to hear where this breaks.

This FEP draft proposes translation credits for language-tagged Activity Streams objects. The metadata records who translated the text into each language and whether the translation was machine-assisted or human-reviewed. It also tracks how up to date each translation is with the source. Servers don't have to expose their private revision history.

It grew out of [Hackers' Pub]'s work on letting authors publish their own article translations.

https://codeberg.org/fediverse/fep/pulls/922

Feedback welcome, thanks!

[Hackers' Pub]: https://hackers.pub/

Optique 1.3.0 is out. Optique is a type-safe combinatorial CLI parser for TypeScript.

Most of this release closes out a long-running effort to fix dependency sources: parsers that read a value another parser resolved, whether from bindEnv(), bindConfig(), or an interactive prompt. Before 1.3.0, whether that value actually reached its reader depended on which order you declared the two parsers in. It doesn't anymore. derivePromptConfig() builds on that fix, letting one prompt's choices adapt to an answer you gave earlier in the same run, so a package manager prompt can offer different options depending on which framework you just picked.

Two new packages ship alongside it: @optique/keyring reads a password from the OS credential store instead of a config file, and @optique/testing gives you four ways to test an Optique-based CLI without parsing rendered stderr.

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

Eunha is my fourth fediverse project. The three others are:

• Oeee Cafe: Community-driven retro art drawing platform
• Naru: Free static website hosting with databases
• typo blue: Blogging platform with fediverse support

https://eunha.social

Eunha is my latest project; It's a Rust re-implementation of Mastodon, aiming for 100% database schema compatibility. It can be a drop-in replacement on top of the Mastodon database you already have. Licensed under the GNU AGPL-3.0.