洪 民憙 (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にも興味が多いです。日本語、英語、韓国語で話しかけてください。（または、漢文でも！）

#自己紹介

Fediverse Icons

https://github.com/reiver/fediverse-icons

Free, and in SVG format.

#DeSo #Fediverse #FediverseIcons #Calckey #Castopod #Forgejo #Friendica #FunkWhale #Gitea #GreatApe #Hubzilla #Lemmy #Mastodon #Misskey #Pixelfed #Pleroma #WordPress #WriteFreely

@joepie91 Things that open source projects which have their official X (formerly Twitter) account usually post on their account? News, their roadmaps, questions and answers, and so on!

@joepie91 Software libraries!

Good news! We've officially added #Cloudflare #Workers support to the #Fedify roadmap. We've created a detailed issue to track our implementation plan: https://github.com/fedify-dev/fedify/issues/233.

The effort will be tackled in phases, including compatibility assessment, core adaptations for Workers' environment, KV store and message queue implementations, and finally integration with Cloudflare's ecosystem. This will be a substantial project that we'll break down into several sub-issues.

If you're interested in contributing to any specific aspect of Workers support, please comment on the main issue to coordinate efforts.

#CloudflareWorkers

Or at least, I wish they'd create a Bluesky account and turn on Bridgy Fed.

I wish all the library projects I use had official fediverse accounts so I could follow them.

@me 그냥 접근성 고려 전반을 Apple 제품들이 다른 곳들보다 더 많이 하는 것 같긴 해요.

實(실)은 Fedify에 굵직한 課題(과제)들이 좀 있는데 OSS 컨트리뷰션 아카데미에서 進行(진행)하려고 내가 안 解決(해결)하고 아껴두고 있다.

@hollo 음, 이상하네요. 한 번 팔로 풀었다가 다시 팔로해 보시면…

@hollo 계정 생성한 지 2주 지나야 될 겁니다.

If a module defines a custom exception type and throws that exception within the module, it absolutely must export that exception type as well. I'd think this is basic, but it seems a surprising number of packages declare exception types without exporting them.

What's up with Fresh? 🍋

https://deno.com/blog/an-update-on-fresh

Fedify本、TPM入稿だん！

I mean you've done all the hard work for free open decentralized social networking platform right?

and you're like one inch centimeter away from branding yourself this

I'm not happy with how Mastodon abbreviates Mastodon to mstdn. For me it looks like Microsoft Technical Developer Network or something

hehe ActivityPub strikes back

soon all AI crawlers will need to sign their HTTP requests in the same way

https://blog.cloudflare.com/web-bot-auth/

다음주 수요일부터 OSS 컨트리뷰션 아카데미 멘티 모집을 하는군아.... 연합우주 쪽 사람이라면 Fedify 지원합시다

@Yohei_Zuho 勿論いいです！ありがとうございます！

24日(일)(土(토)) FediDev KR 스프린트 모임에 오시는 분들께는, 귀여운 Fedify 로고 스티커를 나눠 드리겠습니다.

https://hackers.pub/@hongminhee/0196b961-2b85-7b25-b6cf-9900405d52eb

Here is the exciting thing about "vertical decentralization", Bluesky's core innovation: since your PDS and your "app view" can be hosted by two different entities, this means the pool of people who can make Bluesky stop working for you can be taken to a theoretical maximum. For example with Mastodon, if Eugen screws up my app doesn't work. But with Bluesky, since I self-host my PDS, if *either* I *or* Bluesky mess up, it doesn't work! *Everybody* must have a good day *at once* or there's no app

What's actually happening right now is the Bluesky *website* is broken but the *phone app* still works. I propose the following theory:

Mastodon is "horizontally decentralized"; this means if one part of the network goes down the other parts continue working.

Bluesky is "vertically decentralized"; they separated each tech stack component into a slice that can be hosted by a different company. This means if any part of the network goes down they ALL stop working, because the layers interconnect

제가 추천하는 ActivityPub 입문 가이드 목록입니다.

RE: https://hollo.social/@hongminhee/0196cf12-955d-7e42-a4f2-69dd233c55d5

그동안 페디버스 잘 이해 못했는데
되게 혁신적이고 민주적인(?) 온라인 지구촌 방식이네요.

개인적으론 2000년대에 인터넷 처음 썼을 때 느낀 신세계 이후로 두번째입니다

라는 멘션을 받았는데, 혁신적이고 민주적인 온라인 지구촌 방식이라는 표현 좋다

마스토돈이 윤리적인 SNS라고 언급된 기사

https://www.theguardian.com/world/2024/apr/30/stop-children-using-smartphones-until-they-are-13-say-french-experts-in-report

엄밀하게는 프랑스 쪽 연구를 인용한것이긴 한데.... 미성년자에게는 어지간하면 SNS를 멀리하도록 하되, 15세 이상부터는 마스토돈 같은 윤리적 SNS를 쓰도록하는 것은 괜찮다 뭐 그런 언급이 있음

@mikebroberts While the W3C specs exist as a reference, I wouldn't recommend starting there—they're underspecified and don't provide enough practical guidance for implementation.

Instead, I'd suggest these more practical resources:

1. Fedify's Creating your own federated microblog tutorial:

   • Provides a hands-on, step-by-step implementation
   • Covers both the theory and practice in an accessible way
   • Shows how to handle common ActivityPub patterns

2. For a better conceptual overview:

   • Sebastian Jambor's excellent Understanding ActivityPub series
   • Darius Kazemi's A highly opinionated guide to learning about ActivityPub

3. The SocialHub forum has many discussions about implementation practices and challenges faced by developers.

4. The FEP (Fediverse Enhancement Proposals) process documents community-developed extensions and conventions that go beyond the official spec.

The biggest challenge with ActivityPub isn't understanding the core concepts, but navigating all the de facto standards and practices that have evolved beyond the specs. Starting with practical tutorials rather than specs will give you a much clearer path forward.

@silverpill I agree that domain-specific APIs have their place and serve their communities well. Mastodon API, Lemmy API, etc. are certainly designed by experts in their respective domains.

Where I'd offer a different perspective is on the potential for improvement. I believe there's still significant room to enhance developer experience, especially for client apps aiming to provide optimal UI/UX.

My interest in GraphQL isn't about replacing domain expertise, but rather providing a more efficient abstraction layer that could:

1. Reduce over-fetching and under-fetching of data (getting exactly what's needed)
2. Provide better type safety and IDE integration
3. Simplify complex state management on clients
4. Enable more responsive UIs with optimistic updates

I see this as complementary to domain-specific knowledge, not contradictory. Domain experts would still design the underlying data models and relationships—GraphQL would just provide a more flexible way to query them.

As for ActivityPub C2S, I agree it should be the foundation of any universal client API. But the current C2S spec alone doesn't provide the ergonomics needed for modern app development. Ideally, we'd have something that combines ActivityPub's semantic model with more developer-friendly query capabilities.

@mikebroberts While the W3C specs exist as a reference, I wouldn't recommend starting there—they're underspecified and don't provide enough practical guidance for implementation.

Instead, I'd suggest these more practical resources:

1. Fedify's Creating your own federated microblog tutorial:

   • Provides a hands-on, step-by-step implementation
   • Covers both the theory and practice in an accessible way
   • Shows how to handle common ActivityPub patterns

2. For a better conceptual overview:

   • Sebastian Jambor's excellent Understanding ActivityPub series
   • Darius Kazemi's A highly opinionated guide to learning about ActivityPub

3. The SocialHub forum has many discussions about implementation practices and challenges faced by developers.

4. The FEP (Fediverse Enhancement Proposals) process documents community-developed extensions and conventions that go beyond the official spec.

The biggest challenge with ActivityPub isn't understanding the core concepts, but navigating all the de facto standards and practices that have evolved beyond the specs. Starting with practical tutorials rather than specs will give you a much clearer path forward.

@mikebroberts Your project sounds exciting! The blend of blogging and social photos with ActivityPub support is exactly the kind of application that can benefit from federation.

Fedify should work well with your AWS Lambda setup since you're using TypeScript. Fedify supports Node.js (which Lambda offers), along with Deno and Bun. A few considerations for serverless environments:

1. For persistence, you'd want to use something like DynamoDB with Fedify's KvStore interface
2. Lambda's stateless nature means you'll need to handle message queue processing carefully
3. Cold starts might impact performance for less frequent federation operations

The docs include integration examples with Express, which you can adapt for Lambda + API Gateway. Feel free to reach out when you get to the ActivityPub implementation phase—would be happy to provide guidance on adapting Fedify to serverless architecture.

Good luck with your project!

@maxd @hongminhee

What may be interesting is #AsyncAPI which is like #OpenAPI but then oriented towards event-driven architectures. More appropriate for message passing protocols like #ActivityPub.

https://www.asyncapi.com/en

@hongminhee @thisismissem @PuercoPop

For your information, I recently opened an issue to track current #ActivityPub C2S implementations.

This is the list thus far:

#ActivityPods
#Epicyon
#Onepage.pub
#Pleroma
#RDFPub
#Vocata
#FedBOX
#Mitra
#streams
#forte

https://codeberg.org/fediverse/delightful-fediverse-apps/issues/130

Client-side #AndStatus is a well-known attempt to implement it:

https://github.com/andstatus/andstatus/issues/499