洪 民憙 (Hong Minhee)

高市総理と私の共通点：X JAPANの名曲「Rust Nail」が好きなこと。

An interview with @thisismissem from @APC: FediMod FIRES on building better and decentralised social media applications (by @XavCC).

Probably the biggest thing that I’ve learned over the years of the Fediverse is that it depends almost entirely on volunteer labour. There are a few people that are paid full time to work on the Fediverse. But to actually get the things that you need, it very much largely depends on volunteer labour, because projects are either chasing funding through grants or they're chasing funding through their nations. And those demands can often be at odds with what people overall need or want.

So that's probably the biggest learning from the Fediverse that I have: a lot of it is just run and funded by individuals and volunteers, which often means that it doesn't move as fast as more commercial operations.

Gave a little interview to @APC about my FediMod FIRES project: https://www.apc.org/en/news/fedimod-fires-building-better-and-decentralised-social-media-applications

Loops actors now support interactionPolicy!

https://browser.pub/https://loops.video/@dansup

#Fediverse #ActivityPub

@kodingwarrior 글 업데이트 機能(기능) 만드셔야겠네요… ㅋㅋㅋ

FediDev KR 스프린트 세 번째 모임

한국 연합우주 개발자 모임(FediDev KR)은 연합우주(fediverse) 생태계를 더욱 풍성하게 만들기 위해 다양한 개발자들이 모여 스프린트 모임을 진행하는 커뮤니티입니다. 이 모임은 비정기적으로 개최되며, 모든 기여자들이 각자의 방식으로 생태계에 기여할 수 있는 열린 공간입니다.

지금까지 진행된 프로젝트

• Hollo: 페디버스 기반의 1인용 마이크로 블로그 서비스
• Chamsae: 메시징에 특화된 ActivityPub 기반 서비스
• Fedify: ActivityPub 기반의 서비스를 쉽게 개발할 수 있도록 도와주는 라이브러리
• HackersPub : ActivityPub 기반의 블로깅 서비스
• Moim.live : ActivityPub 기반의 모임 개최 및 체크인 SNS
  이 외에도 많은 개발자들이 각자의 아이디어로 다양한 프로젝트에 기여하고 있습니다.

스프린트 모임에서는 연합우주 생태계를 확장하고 발전시키기 위한 다양한 활동이 이루어집니다. 새로운 서비스를 개발하거나, 응용 프로그램을 제작하고, 번역에 기여하는 등, 기여 방식은 형식에 구애받지 않고 자유롭게 선택할 수 있습니다. 누구나 자신의 역량에 맞는 방법으로 참여할 수 있습니다.

모임은 서울특별시 성동구 상원길 26, 뚝섬역 5번 출구 근처 어딘가에 있는 튜링의 사과에서 진행합니다.
일정은 3월 중순 어딘가에, 모여서 각자 편하게 기여하다가 가시면 됩니다. 처음오는 분들이셔도 좋습니다.

몸만 오시면 됩니다. 비용은 튜링의 사과 이용료만 챙겨 주시면 돼요.
감사합니다.

📅 2026-04-11 11:00 — 18:00 (GMT+9)

View event details

@evan Also, if it'd help to dig deeper, Fedify ships a couple of CLI tools that might be useful here:

• fedify lookup will fetch and display the actor object, including the public key and its owner field, so you can quickly see whether the key document looks correct from the outside.
• fedify inbox spins up a temporary public ActivityPub inbox and lets you send activities to it from your server, so you can observe exactly what Fedify receives and whether the signature verifies.

Both are in the @fedify/cli package. You can install it with:

npm install -g @fedify/cli

Or grab a standalone binary from the releases page.

@evan Yes, that's exactly how it works. When Fedify verifies a draft-cavage signature on an incoming request, it:

1. Extracts the keyId from the Signature header.
2. Fetches the document at that keyId URL, expecting a key object (or an actor with a matching public key embedded).
3. Reads the owner property of the key, which points to the actor's ActivityPub object URL.
4. Fetches that actor object to confirm the key is actually associated with the claimed sender.

So if tags.pub is having a signature-related bug with Fedify, worth checking: does the keyId URL actually resolve to a key object with a correct owner pointing back to the actor? And does the actor object at that owner URL include the public key? If either fetch fails or returns unexpected data, Fedify will reject the signature.

https://nogamesforgenocide.com/

#BDS #FreePalestine #XBox

This piece appears to be a response to my recent essay on craft, alienation, and LLMs, so let me engage with it directly.

The argument collapses every social and structural explanation into a single move: the individual chose it. This is the classic libertarian reduction, and it has a well-known failure mode. Under this framework, there is no coherent distinction between a choice made under duress and a choice made freely. If a developer uses LLM coding assistants because their livelihood depends on keeping pace with colleagues who do, and the author's response is that no one forced them, well, no one forces a person at gunpoint to hand over their wallet either. The gun is still there.

The author acknowledges, mid-essay, that the system “can change incentives and tradeoffs.” But this is precisely what a structural analysis is. Once you admit that incentives can be arranged such that a person has no viable path except the one the system rewards, you have already conceded the core Marxian point. Calling it “alienation” or not is just terminology.

What the alienation framework actually claims is not that individuals don't choose. It's that the conditions under which those choices are made matter morally and analytically. My own essay is careful about this: I noted explicitly that the tension between craft and efficiency doesn't vanish under different political arrangements. The question survives capitalism; capitalism just answers it harshly. Dismissing this as a “denial of the craftsman” misreads the argument.

On LLM capabilities: the claim that none of these problems can be solved by LLMs (understanding systems, architecture decisions, debugging) reads as confident as of roughly two years ago. The frontier has moved. Coding agents are already handling non-trivial architectural reasoning in constrained domains, and the trajectory is visible. Anchoring the argument to current limitations, stated as permanent ones, is a move that ages badly.

[Also cross-posted to Lobsters and Hacker News threads.]

TypeScript 6.0 is now available!

This release brings better type-checking for methods, new standard library features, new module features for Node.js, and more!

But most important, this release brings us one step closer to the upcoming native-speed 7.0!

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

Ditto:

'Why are you still on Bluesky too?'

'But did you *delete* your Twitter account?'

’You said you switched to Proton mail too, oh that’s bad, once someone at Proton said something’

It’s nice to see new neighbours move into the Fediverse. It feels unwelcoming to see people immediately interview them about the purity of their intentions. Or telling them You’re Doing It Wrong. They've just arrived on a journey away from Big Tech. Maybe they'd prefer to be offered a seat and a cup of tea.

Every time a newcomer posts an introduction and somebody tells them they shouldn’t have joined Mastodon.social and need to move to a different server, an angel loses their wings.

@BoydStephenSmithJr Yeah, actually, I'd rather use PureScript than TypeScript too. 😂

@evan Haha, well if that's the case, how about upgrading to the latest version of Node.js? The latest Node.js version can run TypeScript files natively!

@sublimer はい、それにNode.js単体では型チェックも行われませんよね。ただ、簡単なスクリプトを書く際にはかなり便利だと思います。（型チェックはVisual Studio Codeのようなエディタで行われると想定した場合）

Node.jsでTypeScript使えるやつはあくまでも型情報を落としているだけなので、Node.jsでTypeScriptを直接実行できるけどV8が直接実行しているわけではない
V8が直接TypeScript実行できるようになったらブラウザでもTypeScript使えるようになるのかな

FYI, the latest Node.js can run TypeScript code directly without a build process using the node script.ts command.

@evan I'm not sure if you'll like it, but why don't you give Deno a try? You can run .ts files directly without a separate build pipeline.

@mariusor Deno might be it, but it's run by a VC-funded startup… 😂

@SRAZKVT Yeah, its governance is indeed problematic. I hope they migrate their governance on TypeScript to an independent foundation.

@Razemix Yeah, for simple projects, transpilation would be overkill indeed. By the way, that's why I'd preferred Deno over Node.js. Node.js also transforms TypeScript code by default though.

@gosha Haha, I've always had my doubts about Rails' aesthetics.

@abnv Yeah, that's fair enough indeed!

Is anyone still sticking to #JavaScript instead of using #TypeScript? If so, why are you sticking with it? Please let me know your reasons!

TSKaigi 2026に採択されました。「TypeScriptのclassはなぜこうなったのか」というタイトルで、classの歴史的経緯・落とし穴・使いどころを体系的に整理する30分セッションです。

https://kosui.me/posts/2026/03/tskaigi

📢TSKaigi 2026の基調講演は、MicrosoftのPrincipal Software Engineer、Jake Bailey氏をお迎えします。

TypeScriptチームでパフォーマンスやインフラ、エコシステム整備を主に担当されています。 タイトルは『TS7: How We Got There』。「中の人」のご登壇をお楽しみに！

https://x.com/tskaigi/status/2035661614847001050?s=20

残念ながら落ちてしまった。😭

まあ、それでも参加はするけどね。

https://tskaigi.hatenablog.com/entry/2026/03/22/185722

TSKaigi 2026 プロポーザル採択者発表 https://tskaigi.hatenablog.com/entry/2026/03/22/185722

ついに発表された

We make our choices, and then our choices make us.

https://writings.hongminhee.org/2026/01/ethics-of-small-actions/