洪 民憙 (Hong Minhee)

Hello, I'm an open source software engineer in my late 30s living in #Seoul, #Korea, and an avid advocate of #FLOSS and the #fediverse.

I'm the creator of @fedify, an #ActivityPub server framework in #TypeScript, @hollo, an ActivityPub-enabled microblogging software for single users, and @botkit, a simple ActivityPub bot framework.

I'm also very interested in East Asian languages (so-called #CJK) and #Unicode. Feel free to talk to me in #English, #Korean (#한국어), or #Japanese (#日本語), or even in Literary Chinese (#文言文, #漢文)!

#introduction

安寧(안녕)하세요, 저는 서울에 살고 있는 30代(대) 後半(후반) 오픈 소스 소프트웨어 엔지니어이며, 自由(자유)·오픈 소스 소프트웨어와 聯合宇宙(연합우주)(fediverse)의 熱烈(열렬)한 支持者(지지자)입니다.

저는 TypeScript用(용) ActivityPub 서버 프레임워크인 @fedify 프로젝트와 싱글 유저用(용) ActivityPub 마이크로블로그인 @hollo 프로젝트와 ActivityPub 봇 프레임워크인 @botkit 프로젝트의 製作者(제작자)이기도 합니다.

저는 東(동)아시아 言語(언어)(이른바 #CJK)와 유니코드에도 關心(관심)이 많습니다. 聯合宇宙(연합우주)에서는 國漢文混用體(국한문 혼용체)를 쓰고 있어요! 제게 韓國語(한국어)나 英語(영어), 日本語(일본어)로 말을 걸어주세요. (아니면, 漢文(한문)으로도!)

#툿친소 #연친소 #별친소

こんにちは、私はソウルに住んでいる30代後半のオープンソースソフトウェアエンジニアで、自由・オープンソースソフトウェアとフェディバースの熱烈な支持者です。名前は洪 民憙（ホン・ミンヒ）です。

私はTypeScript用のActivityPubサーバーフレームワークである「@fedify」と、ActivityPubをサポートする1人用マイクロブログである 「@hollo」と、ActivityPubのボットを作成する為のシンプルなフレームワークである「@botkit」の作者でもあります。

私は東アジア言語（いわゆるCJK）とUnicodeにも興味が多いです。日本語、英語、韓国語で話しかけてください。（または、漢文でも！）

#自己紹介

‘개와 늑대의 시간’은 불확실한 경계의 시간을 말합니다. 지금 K팝 업계에도 두 개의 시간이 겹쳐 있습니다. 하나는 산업의 발전이고, 다른 하나는 방시혁 사법 리스크입니다.

방시혁과 케이팝, 개와 늑대의 시간

@tokolovesme 그럴까나

Hello ☀️ I’m still here! ✌️

Our tent is too narrow for my whole family. I’ve been sleeping out in the open for several nights in a row. The stars are beautiful but gunfire, explosions and drones are scary, and it’s getting cold.

Also, food is barely affordable.

I don’t know when I’ll lose access, this might again be my last message, please don’t forget about me, and keep sharing and donating and protesting and supporting.

Love and peace.

➡️ https://paypal.me/Mohammedshbair727

➡️ https://chuffed.org/project/mohshbairgaza

Stashing my dev notes here https://github.com/cheeaun/phanpy/discussions/1294 — probably useful for other devs too 🙇‍♂️

Implementation is almost done; just 3 things:
1. There's no way to test "Request to quote"
2. QP filtered for limited accounts
3. Post content is optional if there's CW and quote (doesn't seem to work on official site yet, will check later)

@heka 오오… 좋네요!

@heka 무슨 브라우저예요?

한番(번) 가보고 싶은 곳들:

• 延邊(연변)
• 哈爾賓(합이빈)
• 深圳(선전)
• 神戶(고베)
• 廣島(히로시마)
• 橫濱(요코하마)
• 沖繩(충승)

@xiniha.dev They need to adopt tsgo as soon as possible…

I believe most of it would be spent on running tsc to build the documentation from it 🫠

@hongminhee なつかすぃ…

この頃の日本のR&B、結構好きなんだよね。例えばMISIAの「つつみ込むように…」（1998）とか、倉木麻衣の「Love, Day After Tomorrow」（1999）とか。

宇多田ヒカルのファーストアルバム『First Love』（1999）は、（記憶が正しければ多分）私が初めて聴いたJ-popなんだけど、25年経った今聴いてもやっぱ良いんだよね。個人的に宇多田ヒカルの最近の音楽も好きだけど、なんだかんだこのアルバムほどグッとくるアルバムは無いかな。

fedify를 다른 프로그래밍 언어로 사용할 수 있다면, 어떤 언어가 좋으신가요?

Python -> 하트 Rust -> 축하

기타 언어는 답글로 달아주세요.

#시장조사

Why doesn't Bash's programmable completion provide the cursor offset within the word being completed? With all the complexity around word splitting—shell quoting, escpaing, expansions—figuring out the intra-word cursor position by hand is a nightmare. Would it really be so hard for Bash to offer this info natively, rather than leaving script authors to replicate the shell's own parsing logic?

Okay, it seems up now.

Is gnu.org down or just me?

@rangho_220 Hollo도 처음에는 Bun이었는데 메모리가 새서 Node.js로 바꿨었어요. ㅋㅋㅋ

@rangho_220 프런트엔드에는 모르겠는데 백엔드에는 안 좋은 것 같아요. 메모리 릭이 너무 많아요.

@rangho_220 보는 것만 되는 걸로 알고 있습니다.

Why is publishing packages to #JSR so slow? A lot of the CI time for the Fedify project is spent waiting for the JSR server to process the packages we've uploaded.

사람들이 LLM에 瘧(학)을 떼는 것도 理解(이해)는 간다…

I've signed the Plan Vert letter, calling on Rails Core and the wider Ruby community to fork Rails and cut ties with DHH and his work.

Please sign, the future of Rails and Ruby depends on it. https://github.com/Plan-Vert/open-letter

@kodingwarrior 大體(대체)로 建物(건물)의 幅(폭)이 좁은 것 같아요. 아마도 집값과 耐震設計(내진설계)의 影響(영향)…!?

Its been a while! I just added #HackersPub (https://hackers.pub), #Elk (@elk) and #Elgg (@elgg) icons to #FediverseIconography at https://iconography.fediverse.info

The problem is that Fedify's Activity Vocabulary API supports property hydration. Fedify intentionally hides the following three states of properties of Activity Vocabulary objects, which seems to hinder the application of an origin-based security model:

1. When a complete object is embedded within a property of a JSON-LD object.
2. When a property of a JSON-LD object references an object by URI.
3. When it was initially #2, but the property has since been hydrated.

I'm migrating Fedify from implementing FEP-c7d3 Ownership to FEP-fe34: Origin-based security model, and man, this is more complicated than I thought. It looks like it's going to require major changes to how the Activity Vocabulary API works. This isn't easy… 😂

@liaizon @Tak I think it's a bug on our side (Hackers' Pub).

🥴

• MicroSoft
• Github
• Iphone
• Javascript
• CoPilot
• NodeJS
• NeoVim