#fedidev

Jeff Sikes

@box464@mastodon.social

Just installed the fedify CLI tool on my Mac. Very useful tool for AP developers and tinkerers alike.

You can ask to to look up an AP object and it returns the response. Cool!

`fedify lookup https://spark.box464.social/pub/actors/spark464`

https://fedify.dev/cli

Thanks, @fedify

Fedify: an ActivityPub server framework

@fedify@hollo.social

🎉 Huge shoutout to two amazing contributors from Korea's #OSSCA program who've made excellent contributions to #Fedify!

👏 @gaebalgom tackled a tricky terminal compatibility issue in PR #282, fixing the fedify node command's favicon display on terminal emulators without truecolor support (#168). His solution elegantly detects terminal capabilities and falls back to 256-color mode when needed—ensuring a great experience across different environments.

🌟 @joonnot enhanced Fedify's #WebFinger functionality in PR #281 by adding a configurable maxRedirection option to the lookupWebFinger() function (#248). He transformed a hardcoded limitation into a flexible, user-customizable parameter while maintaining perfect backward compatibility.

Both delivered thoughtful, well-implemented solutions that showcase the quality of contributions coming from the OSSCA program. Welcome to the Fedify community!

🎉 Big thanks to @2chanhaeng for his first contribution to #Fedify! He implemented the new fedify webfinger command in PR #278, which allows isolated #WebFinger lookups for testing configurations. This addresses the need for developers to test WebFinger functionality without performing comprehensive object retrieval.

The contribution includes:

A new fedify webfinger <handle> command that accepts @user@domain format handles or URIs
Clean JSON output of WebFinger JRD results
Proper error handling for invalid handles and lookup failures
Complete #CLI integration with help text and usage examples

This was originally filed as issue #260 and marked as a good first issue—perfect for newcomers to learn the codebase structure while contributing meaningful functionality. The PR has been merged and will be included in the upcoming Fedify 1.8.0 release.

We appreciate all first-time contributors who help make Fedify better for the entire #fediverse community. Welcome aboard, ChanHaeng!

Fedify: an ActivityPub server framework

@fedify@hollo.social

The contribution includes:

A new fedify webfinger <handle> command that accepts @user@domain format handles or URIs
Clean JSON output of WebFinger JRD results
Proper error handling for invalid handles and lookup failures
Complete #CLI integration with help text and usage examples

We appreciate all first-time contributors who help make Fedify better for the entire #fediverse community. Welcome aboard, ChanHaeng!

Fedify: an ActivityPub server framework

@fedify@hollo.social

The contribution includes:

A new fedify webfinger <handle> command that accepts @user@domain format handles or URIs
Clean JSON output of WebFinger JRD results
Proper error handling for invalid handles and lookup failures
Complete #CLI integration with help text and usage examples

We appreciate all first-time contributors who help make Fedify better for the entire #fediverse community. Welcome aboard, ChanHaeng!

Fedify: an ActivityPub server framework

@fedify@hollo.social

The contribution includes:

A new fedify webfinger <handle> command that accepts @user@domain format handles or URIs
Clean JSON output of WebFinger JRD results
Proper error handling for invalid handles and lookup failures
Complete #CLI integration with help text and usage examples

We appreciate all first-time contributors who help make Fedify better for the entire #fediverse community. Welcome aboard, ChanHaeng!

Fedify: an ActivityPub server framework

@fedify@hollo.social

The contribution includes:

A new fedify webfinger <handle> command that accepts @user@domain format handles or URIs
Clean JSON output of WebFinger JRD results
Proper error handling for invalid handles and lookup failures
Complete #CLI integration with help text and usage examples

We appreciate all first-time contributors who help make Fedify better for the entire #fediverse community. Welcome aboard, ChanHaeng!

Fedify: an ActivityPub server framework

@fedify@hollo.social

The contribution includes:

A new fedify webfinger <handle> command that accepts @user@domain format handles or URIs
Clean JSON output of WebFinger JRD results
Proper error handling for invalid handles and lookup failures
Complete #CLI integration with help text and usage examples

We appreciate all first-time contributors who help make Fedify better for the entire #fediverse community. Welcome aboard, ChanHaeng!

Fedify: an ActivityPub server framework

@fedify@hollo.social

The contribution includes:

A new fedify webfinger <handle> command that accepts @user@domain format handles or URIs
Clean JSON output of WebFinger JRD results
Proper error handling for invalid handles and lookup failures
Complete #CLI integration with help text and usage examples

We appreciate all first-time contributors who help make Fedify better for the entire #fediverse community. Welcome aboard, ChanHaeng!

Fedify: an ActivityPub server framework

@fedify@hollo.social

The contribution includes:

A new fedify webfinger <handle> command that accepts @user@domain format handles or URIs
Clean JSON output of WebFinger JRD results
Proper error handling for invalid handles and lookup failures
Complete #CLI integration with help text and usage examples

We appreciate all first-time contributors who help make Fedify better for the entire #fediverse community. Welcome aboard, ChanHaeng!

Fedify: an ActivityPub server framework

@fedify@hollo.social

The contribution includes:

A new fedify webfinger <handle> command that accepts @user@domain format handles or URIs
Clean JSON output of WebFinger JRD results
Proper error handling for invalid handles and lookup failures
Complete #CLI integration with help text and usage examples

We appreciate all first-time contributors who help make Fedify better for the entire #fediverse community. Welcome aboard, ChanHaeng!

Fedify: an ActivityPub server framework

@fedify@hollo.social

The contribution includes:

A new fedify webfinger <handle> command that accepts @user@domain format handles or URIs
Clean JSON output of WebFinger JRD results
Proper error handling for invalid handles and lookup failures
Complete #CLI integration with help text and usage examples

We appreciate all first-time contributors who help make Fedify better for the entire #fediverse community. Welcome aboard, ChanHaeng!

#FediDev #Newsmast #DownTime #Mastodon

Newsmast

@newsmast@newsmast.social

From tomorrow morning, the Newsmast app will be down! ⚠️

As we move to our new app, the current Newsmast app will go down for a period of maintenance.

In this time, you may see Newmast Channels also go down or be less responsive as we migrate them to a new server.

We can't wait to show you the new look Newsmast! Thanks so much for your patience.

@box464@mastodon.social

Just installed the fedify CLI tool on my Mac. Very useful tool for AP developers and tinkerers alike.

You can ask to to look up an AP object and it returns the response. Cool!

`fedify lookup https://spark.box464.social/pub/actors/spark464`

https://fedify.dev/cli

Thanks, @fedify

#Fedify #fedidev #opensource #mentoring

洪民憙 (Hong Minhee)

@hongminhee@hollo.social · Reply to 洪民憙 (Hong Minhee)'s post

And just finished writing a comprehensive contributor guide for the #OSSCA mentees!

You can check it out here—it's Korean though: https://hackers.pub/@hongminhee/2025/ossca-fedify-contributors-guide.

It covers everything from setting up the #fediverse accounts and development environment to finding good first issues. While it's primarily for the OSSCA participants, anyone interested in contributing to @fedify is welcome to use it as a reference.

Ready to onboard the next wave of #ActivityPub developers!

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

안내

이 문서는 기본적으로 오픈 소스 컨트리뷰션 아카데미 참여형 프로그램을 진행하게 된 멘티들을 위한 것입니다만, Fedify 프로젝트에 기여하고 싶은 분들이라면 얼마든지 활용하셔도 좋습니다.

안녕하세요. 오픈 소스 컨트리뷰션 아카데미 참여형 프로그램에서 Fedify 프로젝트를 함께 할 멘토 홍민희입니다.

Fedify 프로젝트에 참여하시게 된 것을 진심으로 환영합니다. 본 문서에서는 여러분이 앞으로 Fedify 프로젝트에 기여하기 위해서 알고 준비해야 하는 것들을 정리했습니다. 조금 긴 내용이 될 수도 있지만, 차근차근 읽어보시고 따라해야 할 과제는 따라해 주시기 바랍니다. 본 문서에 나온 과제들은 본격적인 기여를 위해 반드시 선행되어야 합니다.

소통 채널

중요

OSSCA 자체 Discord 서버에도 초대되셨을 것입니다만, 그곳에서는 행사에 관한 이야기만 주로 하게 될 겁니다. 실제 기여와 개발에 관련된 이야기는 지금부터 설명할 Fedify 프로젝트의 Discord 서버에서 이뤄지게 됩니다.

가장 먼저 해야 할 것은 Fedify 프로젝트의 Discord 서버에 입장하는 것입니다. 만약 아직 Discord 계정이 없다면 하나 만드세요. 꽤 많은 오픈 소스 프로젝트들이 Discord에서 소통을 합니다. Discord 계정을 만들어 두면 앞으로 다양한 오픈 소스 프로젝트에 기여할 때 쓸모가 많을 것입니다.

Fedify 프로젝트의 Discord 서버에 입장하면, 다음과 같은 질문이 뜹니다:

What language do you speak? どの言語を話しますか？ 어떤 언어를 쓰시나요?

그러면 한국어를 포함해 자신이 이해할 수 있는 언어들을 선택하시면 됩니다. 그러면 여러 채널들이 보이게 되는데, 그 중에서 여러분이 주로 이용하게 될 채널은 #fedify-dev-ko 채널입니다.

본 문서를 읽고 따라하면서 중간에 어려움이 있거나 막히는 부분이 있으면 해당 채널에서 편하게 질문하시면 됩니다.

프로젝트 관련해서 궁금한 점은 사소한 것이라도 Discord 서버에서 질문 주세요. “시간이 날 때 천천히 해결해야지”보다는 일단 물어보는게 낫습니다. 특히 초반의 많은 문제는, 보통 질문을 많이 하면 빨리 해결됩니다. 시간을 정해두세요. 이를테면 30분으로 정했으면 30분 내로 해결이 안되면 일단 질문을 합시다.

과제

Discord 서버에 입장하신 뒤, #fedify-dev-ko 채널에서 간단히 자기 소개를 해 주세요. 본인의 이름과 GitHub 아이디를 꼭 알려주시기 바랍니다.

권고

원활하고 즉시적인 소통을 위해서는 모바일 앱으로 알림을 받을 수 있어야 합니다. 본인의 스마트폰에 Discord 앱을 설치하고 로그인한 뒤, 알림을 허용해 주세요. 랩톱 및 데스크톱 환경에서도 Discord 앱을 설치하고 항상 실행해 두실 것을 권합니다.

권고

가능하다면 Discord 계정의 아바타를 GitHub 계정의 프로필 사진과 통일해 주세요. 멘티가 워낙 많기 때문에 누가 누군지 기억하기 어렵기 때문입니다. 특히, 아무런 이미지도 설정해 두지 않은 분들은 아무 그림이라도 좋으니 시인성을 위해 설정을 부탁드립니다.

연합우주(fediverse)란?

안내

이미 연합우주나 ActivityPub에 대해 익숙하신 분들은 설명은 건너 뛰시고 이 섹션 마지막의 과제만 하셔도 괜찮습니다.

Fedify 프로젝트가 어떤 프로젝트인지 이해하기 위해서는, 우선 페디버스(fediverse), 즉 한국어로 연합우주에 대해 기본적인 이해를 갖출 필요가 있습니다.

종래의 중앙집권적인 SNS들은 크게 두 가지 특징이 있습니다. 첫째로, SNS에 올리는 사용자들의 모든 데이터를 특정 기업이 사유한다는 것입니다. 둘째로, 서로 다른 SNS끼리는 소통할 수 없다는 것입니다. 특히, 두번째 특징은 이메일을 생각해 보면 아주 자연스러운 것은 아니라는 것을 알 수 있습니다. 네이버 메일을 쓰는 사람이 Gmail을 쓰는 사람과 소통할 수 없을까요? 그렇지 않지요. 하지만 Instagram 사용자는 X (舊 Twitter) 사용자와 소통할 수 없습니다.

이러한 문제를 해결하고자 나온 대안 SNS들이 있습니다. Mastodon이나 Pixelfed 같은 것들이 그렇습니다. 그리고 이러한 SNS들은 누구라도 자신의 서버에 설치가 가능합니다. 실제로 홈 서버에서 돌아가는 Mastodon 서버도 꽤 많습니다. 물론, 직접 서버를 운영하고 싶지 않은 대부분의 사람들에게는 대형 서버라는 선택지도 있습니다. 이를테면, Mastodon 서버 중에서 가장 사용자가 많은 서버인 mastodon.social은 Mastodon 개발 팀이 직접 운영하는 서버입니다.

하지만 이런 의문이 드실 수 있습니다. 자신의 홈 서버에 Mastodon을 설치해봤자 혼자 쓰는 일기장이 아닌가? 사실, Mastodon 서버들은 서로 소통이 가능합니다. 마치 이메일과도 같습니다. 자신의 홈 서버에 이메일 서버를 설치하여 자신만의 이메일 주소를 만들어도, 네이버 메일이나 Gmail과 서로 메일을 주고 받을 수 있는 것처럼요. 실제로, Mastodon의 계정 이름은 이메일 주소와 비슷하게 생겼습니다:

@username@server.com

이렇게 서로 다른 Mastodon 서버끼리 소통할 수 있도록 고안된 표준이 바로 ActivityPub 프로토콜입니다. 참고로, 이 ActivityPub 프로토콜은 Mastodon 프로젝트가 독자적으로 정한 게 아니라, W3C에서 웹 표준으로 정한 것입니다. 따라서 Mastodon 뿐만 아니라, Pixelfed 등 ActivityPub을 구현하는 다른 소프트웨어들도 서로 소통이 됩니다. Mastodon에서 Pixelfed로 댓글 다는 것도 되고, Pixelfed 사용자가 Mastodon 사용자를 팔로하는 것도 됩니다.

이렇게 서로 다른 SNS 소프트웨어, 사로 다른 서버끼리 자유롭게 소통이 가능한 구조를 연합(federation)이라고 부릅니다. 어떻게 보면, 이렇게 연합된 서로 다른 SNS들을 모두 합쳐서 하나의 SNS라고 볼 수도 있습니다. 이를 부르는 말이 바로 연합우주, 페디버스입니다.

연합우주는 현재도 꾸준히 커 가고 있습니다. 최근에는 Meta의 Threads도 ActivityPub을 구현하게 되었고, WordPress도 ActivityPub 플러그인을 공식적으로 개발했습니다. 특히, 기존의 연합우주 소프트웨어들은 각자의 서버에 직접 설치할 수 있는 오픈 소스 소프트웨어였던 것에 반해, Threads는 오픈 소스가 아님에도 ActivityPub을 구현했다는 점에서 상당히 이례적이라고 할 수 있습니다. 이런 방식의 연합도 가능하다는 것이죠.

안내

연합우주에 관해 좀 더 자세히 알고 싶어지셨다면, 〈연합우주(fediverse)와 ActivityPub 프로토콜 이해하기: 개발자를 위한 가이드〉라는 글도 읽어보시면 좋습니다.

과제

아직 연합우주를 경험해 본 적 없다면, 계정을 하나 만들어 봅시다. 계정을 만들기 위해서는 어떤 소프트웨어를 쓸 지 먼저 정해야 합니다. Mastodon과 Misskey는 일종의 X처럼 단문을 중심으로 한 SNS입니다. Pixelfed는 Instagram처럼 사진을 중심으로 한 SNS입니다. Meta의 Threads도 있습니다. 현재 읽고 계시는 이 글이 올라온 Hackers' Pub도 사실은 연합우주의 일부로서, 소프트웨어 개발자들을 위한 SNS입니다. 이 중 어떤 것을 선택하시든 서로 소통하는 데에는 문제가 없습니다.

만약 Mastodon이나 Misskey, Pixelfed를 선택하셨다면, 서버를 고르셔야 합니다. (물론, 서버를 직접 구축하시는 것도 괜찮습니다. 아마 많은 걸 배우실 수 있을 겁니다.) 무슨 서버를 골라야 할 지 모르시겠다면, Mastodon의 경우 silicon.moe 서버를, Misskey의 경우 stella.place 서버를, Pixelfed의 경우 chueok.pics 서버를 권합니다.

만약 Threads를 고르셨다면, 서버를 고를 필요가 없습니다. Threads는 설치형 소프트웨어가 아니라 Meta에서 운영하는 상용 서비스이기 때문입니다. 다만, 설정에 가셔서 페디버스 공유 설정을 켜 주셔야 합니다.

만약 Hackers' Pub을 고르셨다면, 역시 서버를 고를 필요가 없습니다. 단 하나의 서버만 있기 때문입니다. 다만, 초대장이 필요하므로 멘토에게 초대장을 요청하시기 바랍니다.

과제

연합우주 계정이 생기셨다면, 이제 친구를 사귀어야 합니다. 다른 멘티들에게 계정 주소를 물어보고 서로 팔로를 해 보세요. 멘토도 팔로해 보세요. (멘토도 맞팔 하겠습니다.) 멘토의 연합우주 계정 주소는 @hongminhee@hackers.pub입니다.

계정 주소로 팔로하는 방법은 소프트웨어마다 조금씩 다르지만, 대부분의 경우 검색창에 주소를 입력하면 해당 계정이 보입니다. 계정이 보인다면 팔로 버튼을 누르면 됩니다.

과제

생성한 계정으로 멘토의 계정인 @hongminhee@hackers.pub을 멘션하여 글을 써 주세요. 글 내용은 뭐든 좋습니다.

JavaScript와 TypeScript

안내

이미 JavaScript와 TypeScript에 익숙하시다면 이 챕터는 넘기셔도 됩니다.

Fedify 프로젝트는 TypeScript로 작성되어 있습니다. TypeScript는 JavaScript에 정적 타입 검사를 추가한 언어로, 런타임에 버그를 발생시키는 잘못된 코드를 코드 작성 시에 미리 알 수 있도록 도와줍니다. TypeScript를 이해하려면 먼저 JavaScript를 이해해야 합니다.

아직 JavaScript에 익숙하지 않으신 분들은 《모던 JavaScript 튜토리얼》의 파트 1을 읽고 따라해 볼 것을 권합니다. 파트 2 이후의 내용은 Fedify 프로젝트에 기여하는 데에 크게 필요하지 않으므로 읽지 않으셔도 좋습니다.

JavaScript에는 어느 정도 익숙하지만 아직 TypeScript에 익숙하지 않으신 분들께는, 《The TypeScript Handbook》을 읽고 따라해 볼 것을 권합니다. 참고로 핸드북 페이지 우측 상단에 한국어 번역으로 가는 링크가 있습니다.

사실 오픈 소스 프로젝트에 기여하기 위해 반드시 그 프로젝트에서 쓰이는 언어를 속속들이 깊게 이해해야 하는 건 아닙니다. 기여할 때 필요한 만큼만 이해해도 좋으니, 어느 정도 언어 문법에 익숙해졌다 싶으면 실제 Fedify 코드를 읽는 것을 좀 더 추천합니다. 코드를 읽다가 이해가 안 되는 부분이 있으면 해당 언어 문법에 대해 따로 조사하는 식으로 익히시는 게 더 효율적입니다. 정 이해가 안 되는 경우에는 부담 없이 Fedify 프로젝트 Discord 서버의 #fedify-dev-ko 채널에서 질문해 주세요.

Fedify란?

여러분은 웹 서버 애플리케이션을 만들 때 HTTP를 직접 구현하시나요? 아마도 대부분은 그렇지 않을 겁니다. 그러기엔 할 게 너무 많기 때문이죠. 대신 우리는 대부분 Express나 Next.js, Django 같은 웹 프레임워크를 이용해서 개발하게 됩니다.

마찬가지로, 연합우주 SNS 소프트웨어를 구현하려고 할 경우, ActivityPub을 바닥부터 구현하기에는 너무 할 게 많습니다. 따라서 개발을 쉽게 해 줄 프레임워크가 필요한데, 그게 바로 Fedify입니다.

어떤 오픈 소스 프로젝트든 간에, 해당 프로젝트에 기여하기 위해서는 먼저 그 소프트웨어를 써보고 기본적인 기능들을 숙지해야 합니다. 써보지도 않은 소프트웨어에 기여를 하는 것은 무리입니다. 여러분도 Fedify에 기여하기에 앞서 Fedify를 써 볼 필요가 있습니다.

Fedify는 연합우주 소프트웨어를 만드는 도구이므로, Fedify를 사용한다고 하면 연합우주 소프트웨어를 만들어 본다는 뜻이 됩니다. Fedify를 사용하여 작은 ActivityPub 서버 소프트웨어를 만들어 보세요. Fedify를 써 보면서 이해가 안 가거나 중간에 막히는 게 있다면 Discord 서버의 #fedify-help-ko 채널에서 질문하세요.

과제

Fedify를 배우고 써보는 가장 쉬운 방법은 튜토리얼을 읽고 따라하는 것입니다. Fedify 공식 튜토리얼의 한국어판인 〈나만의 연합우주 마이크로블로그 만들기〉를 읽고 그대로 따라서 진행하세요. 빠르면 하루, 느긋하게 하면 사흘 정도 걸립니다. 중간에 막히는 부분이 있으면 멘토에게 부담 없이 질문하세요.

저장소 포크 및 클론

주의

Windows 환경에서 작업하실 때는 (WSL을 사용하지 않는다면) Git의 core.autocrlf 설정을 꺼 주시기 바랍니다:

git config --global core.autocrlf false

안내

Fedify 프로젝트를 Windows 환경에서 개발할 수는 있지만, Linux나 macOS에 비해 편의성이 떨어지는 것도 사실입니다. 가능하면 WSL을 세팅하시고 WSL 안에서 작업하시는 걸 추천드립니다.

Fedify의 GitHub에 저장소가 올라가 있습니다. 해당 저장소를 각자 포크(fork)하신 뒤, 포크한 저장소를 로컬에 클론하세요. 클론하신 뒤, 클론한 로컬 저장소 안에 들어가 업스트림 저장소를 리모트로 추가하시는 것을 권합니다:

git remote add upstream https://github.com/fedify-dev/fedify.git
git fetch upstream
git pull --set-upstream upstream main

개발 환경 설정

Fedify의 개발 환경 설정은 일반적인 JavaScript 프로젝트들에 비해 조금 복잡한 편입니다. Node.js 이외에도 Deno와 Bun 등 여러 런타임을 지원해야 하기 때문인데요. Fedify의 개발을 위해서는 다음 소프트웨어가 시스템에 모두 설치되어 있어야 합니다:

Node.js v22 이상
Deno v2 이상
Bun 최신 버전
pnpm 최신 버전

하나하나 직접 설치하셔도 좋습니다만, 귀찮으시다면 mise라는 개발 환경 설정 소프트웨어를 이용하는 것을 권합니다. mise는 정말 다양한 방법으로 설치가 가능합니다:

sudo pacman -S mise      # Arch Linux
brew install mise        # macOS
winget install jdx.mise  # Windows
# 이 외에도 다양한 플랫폼 지원

설치하고 나서 PATH 환경 변수에 mise가 관리하는 소프트웨어들을 추가하도록 mise를 활성화해야 합니다. 활성화하는 방법은 어떤 셸을 사용하느냐에 따라 다릅니다:

zsh

echo 'eval "$(mise activate zsh)"' >> "${ZDOTDIR-$HOME}/.zshrc"
. "${ZDOTDIR-$HOME}/.zshrc"

Bash

echo 'eval "$(mise activate bash)"' >> ~/.bashrc
. ~/.bashrc

PowerShell

echo 'mise activate pwsh | Out-String | Invoke-Expression' >> $HOME\Documents\PowerShell\Microsoft.PowerShell_profile.ps1
. $HOME\Documents\PowerShell\Microsoft.PowerShell_profile.ps1

팁

대부분의 Linux의 경우 (또는 Windows의 WSL 안에서 작업하는 경우) 별 다른 설정을 하지 않았다면 bash를 쓰고 계실 것입니다. macOS를 쓰시고 별 다른 설정을 하지 않으셨다면 zsh을 쓰고 계실 것입니다. (WSL이 아닌) Windows의 경우에는 명령 프롬프트가 아닌 PowerShell 안에서 작업하셔야 합니다.

mise를 설치하셨다면, 로컬 저장소 안에 들어가 다음 명령어로 필요한 모든 소프트웨어를 한 번에 설치하실 수 있습니다:

mise install --yes

위 명령어를 실행하면 아래와 같이 Fedify 저장소 안에 들어있는 mise 설정 파일을 신뢰하겠냐는 프롬프트가 뜹니다. Yes를 선택해 주세요:

mise config files in ~/fedify are not trusted. Trust them?


   Yes     No     All  

←/→ toggle • y/n/a/enter submit

개발 환경이 잘 설정되었는지 확인하기 위해 Fedify의 전체 테스트 스위트를 실행해 봅시다. 첫 실행 시 통상 5분 정도 소요됩니다:

deno task test-all

Git 훅도 설치합니다:

deno task hooks:install

마지막으로 실제 편집 환경을 구성해야 합니다. 본 문서에서는 Visual Studio Code를 사용하는 것을 가정하겠습니다만, 같은 Visual Studio Code 계열인 Cursor나 Windsurf에서도 과정은 대동소이합니다.

경고

Visual Studio와 Visual Studio Code는 서로 전혀 다른 별개의 제품이니 주의하세요.

안내

여러분이 Emacs나 Vim의 독실한 신자라면 Visual Studio Code를 사용하고 싶지 않을 수 있습니다. 그런 경우, Deno의 공식 환경 설정 문서를 참고하여 Deno 랭귀지 서버를 설정해 주시기 바랍니다.

우선 로컬 저장소 안에서 code 명령어를 통해 Visual Studio Code를 띄웁니다:

code .     # Visual Studio Code를 사용하는 경우
cursor .   # Cursor를 사용하는 경우
windsurf . # Windsurf를 사용하는 경우

Visual Studio Code 창이 뜨면, 화면 가운데에 다음과 같은 프롬프트 창이 뜹니다:

이 폴더에 있는 파일의 작성자를 신뢰합니까?

프롬프트에서 예, 작성자를 신뢰합니다 버튼을 선택합니다. 그러면 오른쪽 아래에 다음과 같은 작은 프롬프트 창이 뜹니다:

이 리포지토리에 대해 권장되는 Street Side Software, Red Hat 등의 확장을(를) 설치하시겠습니까?

프롬프트에서 설치 버튼을 선택합니다. 그러면 화면 가운데에 다음과 같은 프롬프트 창이 뜹니다:

게시자 “Street Side Software” 신뢰하고 다른 2?

프롬프트에서 게시자 신뢰 및 설치를 선택합니다. 그러면 Visual Studio Code에 Fedify 개발에 필요한 확장들이 설치되게 됩니다.

이로써 Fedify 기여에 필요한 기본적인 개발 환경 설정이 끝났습니다.

JavaScript 런타임

Fedify는 Deno, Node.js, Bun 등 다양한 JavaScript 런타임을 지원해야 합니다. 과연 JavaScript 런타임이 뭘까요?

JavaScript는 비교적 작은 언어입니다. 여러분이 process.exit() 같은 메서드를 활용하신 적 있다면, 이는 JavaScript 자체의 기능이 아니라 Node.js라는 특정한 JavaScript 런타임이 제공하는 기능입니다. 마찬가지로, 웹 브라우저에서 제공하는 DOM API 역시 JavaScript 자체의 기능이 아니라 웹 브라우저라는 (일종의) JavaScript 런타임이 제공하는 기능이라고 볼 수 있습니다.

JavaScript 런타임은 기본적으로 다음과 같은 역할을 합니다:

JavaScript 코드를 실제로 실행합니다.
JavaScript 언어로 사용 가능한 런타임 API를 제공합니다. 런타임 API로는 console.log(), Node.js의 process.exit(), 웹 브라우저의 window.alert() 같은 것들이 있습니다.
모듈 시스템을 제공합니다. 예를 들어, Node.js는 node_modules/ 디렉터리 기반의 모듈 시스템을 제공하는 반면, Deno에서는 임포트 맵(import map) 기반의 모듈 시스템을 제공합니다. Node.js에서는 npm이나 pnpm, Yarn 등의 패키지 관리자를 사용해야 하지만, Deno나 Bun은 자체적인 패키지 관리자를 제공합니다. 웹 브라우저나 Cloudflare Workers는 패키지 관리자를 제공하지 않기 때문에 번들링이라는 과정을 거쳐야 합니다.

앞서 설명한 모든 것을 속속들이 이해해야 할 필요는 없습니다. 중요한 것은, 같은 JavaScript라고 하더라도 어느 런타임에서 실행하냐에 따라 상당히 다른 방식으로 언어를 사용해야 한다는 점입니다.

그러면 Fedify 프로젝트는 다양한 JavaScript 런타임을 어떻게 동시에 다 지원할 수 있을까요? 크게 두 가지 방법이 있습니다:

지원해야 하는 JavaScript 런타임 모두에서 공통적으로 지원하는 API만을 사용합니다.
런타임에 따라 다른 코드를 실행하도록 코드를 여러 벌 작성합니다.

Fedify 프로젝트는 두 가지 방법 모두 사용하고 있으며, 지원하는 모든 JavaScript 런타임에서 테스트 스위트를 실행해서 Fedify의 모든 기능이 각 JavaScript 런타임에서 잘 동작하는지를 검사합니다.

Fedify 저장소의 구조

2025년 7월 현재, Fedify 프로젝트의 저장소는 다음과 같은 구조로 되어 있습니다:

fedify/ — Fedify의 핵심인 @fedify/fedify 패키지입니다. 이 패키지는 Deno, Node.js, Bun, Cloudflare Workers 환경에서 동작합니다.
cli/ — Fedify 사용자들을 위한 CLI 개발 도구인 @fedify/cli 패키지입니다. 이 패키지는 Deno로만 작성됩니다.
amqp/ — AMQP/RabbitMQ 드라이버인 @fedify/amqp 패키지입니다.
express/ — Express 프레임워크와의 연동 모듈인 @fedify/express 패키지입니다.
h3/ — h3 프레임워크와의 연동 모듈인 @fedify/h3 패키지입니다.
postgres/ — PostgreSQL 드라이버인 @fedify/postgres 패키지입니다.
redis/ — Redis 드라이버인 @fedify/redis 패키지입니다.
docs/ — Fedify의 문서가 포함되어 있습니다. https://fedify.dev/ 웹사이트의 소스 코드입니다. VitePress로 구축되어 있습니다.
examples/ — 이름 그대로 Fedify를 사용하는 예제 프로젝트들이 들어 있습니다.
scripts/ — 프로젝트 관리를 위한 스크립트들이 들어 있습니다. 대부분의 경우 건드릴 일이 없을 겁니다.

여러분은 주로 fedify/ 디렉터리 및 cli/ 디렉터리에서 작업을 하게 될 것입니다.

린트와 테스트

여느 오픈 소스 프로젝트들이 그렇듯, Fedify 프로젝트도 나름의 코딩 컨벤션과 규칙들이 있습니다. 다행히 이들 대부분은 커밋하기 전에 기계적으로 검사가 가능합니다. 다음 명령어는 현재 프로젝트의 코드가 코딩 컨벤션을 잘 지키고 타입 오류가 없는지 검사합니다:

deno task check

다음 명령어는 코드를 코딩 컨벤션에 맞게 알아서 서식화합니다:

deno fmt

앞서 언급한 것처럼, 다음 명령어는 Fedify 프로젝트의 전체 테스트 스위트를 실행하고 필요한 검사를 수행합니다. 풀 리퀘스트를 올리기 전에 한 번 실행해 보십시오:

deno task test-all

@fedify/fedify 패키지를 수정했을 경우, 수정과 관련된 일부 테스트 코드만 빠르게 실행해 보고 싶을 수 있습니다. 그럴 때는 다음과 같이 -f @fedify/fedify 옵션과 --filter 옵션을 함께 활용해 보세요 (태스크 이름이 test-all이 아니라 test임에 주의하세요):

deno task -f @fedify/fedify test --filter verifyRequest

혹은 -f @fedify/fedify 옵션을 쓰는 대신 직접 fedify/ 디렉터리 안에서 deno task test 명령어를 사용하셔도 됩니다:

cd fedify/
deno task test --filter verifyRequest

참고로 --filter 옵션은 테스트 케이스 이름을 부분 문자열로 검색합니다. 이를테면, 다음과 같은 테스트가 있을 경우:

test("anArbitraryTest", () => {
  // … 생략 …
});

다음과 같은 방식으로 모두 실행이 가능합니다:

deno task -f @fedify/fedify test --filter anArbitraryTest
deno task -f @fedify/fedify test --filter   Arbitrary
deno task -f @fedify/fedify test --filter            Test

앞서 설명한 deno task test 명령어는 Deno 런타임에서 테스트 스위트를 실행합니다. Node.js에서도 잘 돌아가나 확인하기 위해서는 Node.js 런타임에서도 테스트 스위트를 실행해 봐야 합니다. fedify/ 디렉터리 안쪽에서 pnpm test 명령어를 통해 Node.js에서 테스트 스위트를 돌려 볼 수 있습니다:

cd fedify/
pnpm test

일부 테스트만 빠르게 실행해 보고 싶을 경우 --test-name-pattern 옵션을 활용하세요:

pnpm test --test-name-pattern verifyRequest

Bun에서도 잘 돌아가는지 확인하려면 fedify/ 디렉터리 안쪽에서 pnpm test:bun 명령어를 사용하세요:

pnpm test:bun

일부 테스트만 빠르게 실행해 보고 싶을 경우 마찬가지로 --test-name-pattern 옵션을 활용하세요:

pnpm test:bun --test-name-pattern verifyRequest

마지막으로, Cloudflare Workers에서도 잘 돌아가는지 검사해야 합니다. 이 경우에는 pnpm test:cfworkers 명령어를 활용하세요:

pnpm test:cfworkers

일부 테스트만 빠르게 실행해 보고 싶을 경우 인자로 부분 문자열 키워드를 넘기면 됩니다:

pnpm test:cfworkers verifyRequest

사실, 앞서 설명했던 deno task test-all 명령어는 한 번에 Deno, Node.js, Bun, Cloudflare Workers 모두에서 테스트 스위트를 실행하는 명령어입니다.

안내

테스트 실행 시 실패하는 케이스가 있나요? 그것 자체가 기여할 좋은 기회입니다. 실패하는 테스트가 성공하도록 직접 코드를 고쳐서 풀 리퀘스트를 올리셔도 좋고, 이슈 트래커에 이슈를 만들기만 해도 좋은 기여가 됩니다.

@fedify/cli: Fedify CLI 도구

@fedify/cli 패키지는 Fedify를 이용하여 ActivityPub 서버를 구현하는 개발자들을 위한 CLI 편의 도구로서, 주로 ActivityPub 서버 개발을 할 때 디버그나 테스트를 위해 필요한 기능들을 제공합니다. 라이브러리 패키지인 @fedify/fedify와 다르게 @fedify/cli는 패키지는 애플리케이션이기 때문에 코드를 수정한 뒤 바로 사용해 볼 수가 있습니다. 또한, 굳이 여러 런타임을 지원할 필요가 없기 때문에 Deno 환경만 신경쓰면 됩니다.

그런 이유로, @fedify/cli 패키지는 처음 기여하기에 좋습니다. 참고로 @fedif/cli는 CLI 애플리케이션 프레임워크로 Cliffy를 사용하고 있으니, 관련해서 궁금한 게 있다면 Cliffy 문서를 참고해 주세요.

일감 찾기

중요

오픈 소스 프로젝트에서는 할 일을 자발적으로 찾아야 합니다. 직장이 아니므로, 다른 누군가가 할 일을 할당해 주지 않습니다. 사실, 오픈 소스에서 활발하게 활동하는 프로그래머들은 단순히 소프트웨어 개발 실력이 좋은 게 아니라, 적절한 할 일을 잘 찾아내는 능력이 있습니다. 이 때 “적절하다”는 것은 자신의 실력으로 해낼 수 있을 정도의 난이도면서도 프로젝트에 임팩트를 낼 수 있는 것을 뜻합니다.

대부분의 오픈 소스 프로젝트는 할 일을 이슈 트래커에서 관리합니다. Fedify 역시 GitHub에서 제공하는 이슈 트래커로 할 일들을 관리하고 있습니다. 특별한 이유가 없는 한, 이슈는 기본적으로 영어로 작성되거나, 적어도 영어가 병기되어야 합니다. 영어가 익숙치 않은 분들은 Kagi 번역 등을 활용하시면 될 것 같습니다. 언어 때문에 어려우신 분은 멘토에게 도움을 청하세요.

이슈는 크게 세 종류로 나뉩니다:

피처 (feature): 말 그대로 새로운 기능을 뜻합니다.
버그 (bug): 기존에 있던 기능의 오작동을 뜻합니다.
태스크 (task): 신기능이나 버그 이외의 작업들을 가리킵니다. 예를 들면, 문서 수정 등이 여기에 속합니다.
미분류 (no type): 아직 분류되지 않은 이슈들인데, 이슈는 어떻게든 분류되어야 하므로 보통은 없습니다.

위의 분류와는 별개로, Fedify 이슈 트래커에서는 레이블을 구조화하여 활용하고 있습니다. 대부분의 레이블은 범례/레이블 이름 형식을 따르며, 대표적으로는 다음과 같은 것들이 있습니다:

difficulty/beginner: 쉬운 난이도
good first issue: 처음 기여하는 사람에게 적합
help wanted: 도움 필요
type/documentation: 문서 관련

안내

좀 더 자세히 확인하실 분은 전체 레이블 목록을 확인하세요.

여기서 여러분이 가장 주목하셔야 할 레이블은 바로 good first issue입니다. 해당 레이블이 붙은 이슈는 처음 기여하는 사람에게 적합하기 때문에, 여러분의 첫 기여 때 할 일을 찾을 때 도움이 됩니다. 이슈들을 찬찬히 읽어보시고 해 볼 만한 일감을 고르세요. 이슈를 읽어도 이해가 안 될 경우에는 댓글로 질문을 남기거나 멘토에게 질문하세요.

기여해 볼 이슈를 찾으셨다면, 해당 이슈를 이미 다른 사람이 진행중인지 확인하세요. 아무도 진행하고 있지 않다면 진행하겠다는 댓글을 이슈에 달아주세요.

과제

처음 기여할 이슈를 찾아 이슈에 댓글을 달아주세요. 이슈를 못 찾겠다면 멘토에게 도움을 요청하세요. 멘토가 기여할 만한 일을 함께 찾아줄 수 있습니다.

안내

굳이 이슈 트래커에 이미 있는 이슈 중에서만 고를 필요는 없습니다. Fedify를 써 보면서 개선할 부분을 발견하셨다면, 그걸 이슈로 만들어서 직접 해결하셔도 좋습니다. 사실, 오픈 소스의 많은 이슈들이 이슈를 제기한 사람에 의해 해결됩니다.

추가 정보 및 질문

본 문서에서 다루지 못한 내용도 많이 있을 것입니다. 아래 문서들은 부족한 부분을 좀 더 보충해 줄 수 있습니다:

본 문서를 읽다가 혹은 읽고 나서도 궁금한 점이 있다면 얼마든지 멘토에게 질문해 주세요. Discord 서버에서 질문하셔도 좋고, GitHub Discussions에 질문 글을 올리셔도 좋습니다.

Fedify: an ActivityPub server framework

@fedify@hollo.social

#Fedify has moved to a monorepo structure with unified versioning across all packages (@fedify/fedify, @fedify/cli, database adapters & framework integrations).

All packages now release together, making dependency management much simpler!

#Fedify #fedidev #opensource #mentoring

ALT text details

Fedify monorepo structure diagram showing all packages (@fedify/fedify, @fedify/cli, database adapters, framework integrations) unified with shared versioning

洪民憙 (Hong Minhee)

@hongminhee@hollo.social · Reply to 洪民憙 (Hong Minhee)'s post

And just finished writing a comprehensive contributor guide for the #OSSCA mentees!

You can check it out here—it's Korean though: https://hackers.pub/@hongminhee/2025/ossca-fedify-contributors-guide.

Ready to onboard the next wave of #ActivityPub developers!

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

안내

안녕하세요. 오픈 소스 컨트리뷰션 아카데미 참여형 프로그램에서 Fedify 프로젝트를 함께 할 멘토 홍민희입니다.

소통 채널

중요

Fedify 프로젝트의 Discord 서버에 입장하면, 다음과 같은 질문이 뜹니다:

What language do you speak? どの言語を話しますか？ 어떤 언어를 쓰시나요?

본 문서를 읽고 따라하면서 중간에 어려움이 있거나 막히는 부분이 있으면 해당 채널에서 편하게 질문하시면 됩니다.

과제

Discord 서버에 입장하신 뒤, #fedify-dev-ko 채널에서 간단히 자기 소개를 해 주세요. 본인의 이름과 GitHub 아이디를 꼭 알려주시기 바랍니다.

권고

연합우주(fediverse)란?

안내

이미 연합우주나 ActivityPub에 대해 익숙하신 분들은 설명은 건너 뛰시고 이 섹션 마지막의 과제만 하셔도 괜찮습니다.

@username@server.com

안내

과제

생성한 계정으로 멘토의 계정인 @hongminhee@hackers.pub을 멘션하여 글을 써 주세요. 글 내용은 뭐든 좋습니다.

JavaScript와 TypeScript

안내

이미 JavaScript와 TypeScript에 익숙하시다면 이 챕터는 넘기셔도 됩니다.

Fedify란?

과제

저장소 포크 및 클론

주의

Windows 환경에서 작업하실 때는 (WSL을 사용하지 않는다면) Git의 core.autocrlf 설정을 꺼 주시기 바랍니다:

git config --global core.autocrlf false

안내

git remote add upstream https://github.com/fedify-dev/fedify.git
git fetch upstream
git pull --set-upstream upstream main

개발 환경 설정

Node.js v22 이상
Deno v2 이상
Bun 최신 버전
pnpm 최신 버전

sudo pacman -S mise      # Arch Linux
brew install mise        # macOS
winget install jdx.mise  # Windows
# 이 외에도 다양한 플랫폼 지원

zsh

echo 'eval "$(mise activate zsh)"' >> "${ZDOTDIR-$HOME}/.zshrc"
. "${ZDOTDIR-$HOME}/.zshrc"

Bash

echo 'eval "$(mise activate bash)"' >> ~/.bashrc
. ~/.bashrc

PowerShell

echo 'mise activate pwsh | Out-String | Invoke-Expression' >> $HOME\Documents\PowerShell\Microsoft.PowerShell_profile.ps1
. $HOME\Documents\PowerShell\Microsoft.PowerShell_profile.ps1

팁

mise를 설치하셨다면, 로컬 저장소 안에 들어가 다음 명령어로 필요한 모든 소프트웨어를 한 번에 설치하실 수 있습니다:

mise install --yes

위 명령어를 실행하면 아래와 같이 Fedify 저장소 안에 들어있는 mise 설정 파일을 신뢰하겠냐는 프롬프트가 뜹니다. Yes를 선택해 주세요:

mise config files in ~/fedify are not trusted. Trust them?


   Yes     No     All  

←/→ toggle • y/n/a/enter submit

개발 환경이 잘 설정되었는지 확인하기 위해 Fedify의 전체 테스트 스위트를 실행해 봅시다. 첫 실행 시 통상 5분 정도 소요됩니다:

deno task test-all

Git 훅도 설치합니다:

deno task hooks:install

경고

Visual Studio와 Visual Studio Code는 서로 전혀 다른 별개의 제품이니 주의하세요.

안내

우선 로컬 저장소 안에서 code 명령어를 통해 Visual Studio Code를 띄웁니다:

code .     # Visual Studio Code를 사용하는 경우
cursor .   # Cursor를 사용하는 경우
windsurf . # Windsurf를 사용하는 경우

Visual Studio Code 창이 뜨면, 화면 가운데에 다음과 같은 프롬프트 창이 뜹니다:

이 폴더에 있는 파일의 작성자를 신뢰합니까?

프롬프트에서 예, 작성자를 신뢰합니다 버튼을 선택합니다. 그러면 오른쪽 아래에 다음과 같은 작은 프롬프트 창이 뜹니다:

이 리포지토리에 대해 권장되는 Street Side Software, Red Hat 등의 확장을(를) 설치하시겠습니까?

프롬프트에서 설치 버튼을 선택합니다. 그러면 화면 가운데에 다음과 같은 프롬프트 창이 뜹니다:

게시자 “Street Side Software” 신뢰하고 다른 2?

프롬프트에서 게시자 신뢰 및 설치를 선택합니다. 그러면 Visual Studio Code에 Fedify 개발에 필요한 확장들이 설치되게 됩니다.

이로써 Fedify 기여에 필요한 기본적인 개발 환경 설정이 끝났습니다.

JavaScript 런타임

Fedify는 Deno, Node.js, Bun 등 다양한 JavaScript 런타임을 지원해야 합니다. 과연 JavaScript 런타임이 뭘까요?

JavaScript 런타임은 기본적으로 다음과 같은 역할을 합니다:

JavaScript 코드를 실제로 실행합니다.
JavaScript 언어로 사용 가능한 런타임 API를 제공합니다. 런타임 API로는 console.log(), Node.js의 process.exit(), 웹 브라우저의 window.alert() 같은 것들이 있습니다.
모듈 시스템을 제공합니다. 예를 들어, Node.js는 node_modules/ 디렉터리 기반의 모듈 시스템을 제공하는 반면, Deno에서는 임포트 맵(import map) 기반의 모듈 시스템을 제공합니다. Node.js에서는 npm이나 pnpm, Yarn 등의 패키지 관리자를 사용해야 하지만, Deno나 Bun은 자체적인 패키지 관리자를 제공합니다. 웹 브라우저나 Cloudflare Workers는 패키지 관리자를 제공하지 않기 때문에 번들링이라는 과정을 거쳐야 합니다.

그러면 Fedify 프로젝트는 다양한 JavaScript 런타임을 어떻게 동시에 다 지원할 수 있을까요? 크게 두 가지 방법이 있습니다:

지원해야 하는 JavaScript 런타임 모두에서 공통적으로 지원하는 API만을 사용합니다.
런타임에 따라 다른 코드를 실행하도록 코드를 여러 벌 작성합니다.

Fedify 저장소의 구조

2025년 7월 현재, Fedify 프로젝트의 저장소는 다음과 같은 구조로 되어 있습니다:

fedify/ — Fedify의 핵심인 @fedify/fedify 패키지입니다. 이 패키지는 Deno, Node.js, Bun, Cloudflare Workers 환경에서 동작합니다.
cli/ — Fedify 사용자들을 위한 CLI 개발 도구인 @fedify/cli 패키지입니다. 이 패키지는 Deno로만 작성됩니다.
amqp/ — AMQP/RabbitMQ 드라이버인 @fedify/amqp 패키지입니다.
express/ — Express 프레임워크와의 연동 모듈인 @fedify/express 패키지입니다.
h3/ — h3 프레임워크와의 연동 모듈인 @fedify/h3 패키지입니다.
postgres/ — PostgreSQL 드라이버인 @fedify/postgres 패키지입니다.
redis/ — Redis 드라이버인 @fedify/redis 패키지입니다.
docs/ — Fedify의 문서가 포함되어 있습니다. https://fedify.dev/ 웹사이트의 소스 코드입니다. VitePress로 구축되어 있습니다.
examples/ — 이름 그대로 Fedify를 사용하는 예제 프로젝트들이 들어 있습니다.
scripts/ — 프로젝트 관리를 위한 스크립트들이 들어 있습니다. 대부분의 경우 건드릴 일이 없을 겁니다.

여러분은 주로 fedify/ 디렉터리 및 cli/ 디렉터리에서 작업을 하게 될 것입니다.

린트와 테스트

deno task check

다음 명령어는 코드를 코딩 컨벤션에 맞게 알아서 서식화합니다:

deno fmt

deno task test-all

deno task -f @fedify/fedify test --filter verifyRequest

혹은 -f @fedify/fedify 옵션을 쓰는 대신 직접 fedify/ 디렉터리 안에서 deno task test 명령어를 사용하셔도 됩니다:

cd fedify/
deno task test --filter verifyRequest

참고로 --filter 옵션은 테스트 케이스 이름을 부분 문자열로 검색합니다. 이를테면, 다음과 같은 테스트가 있을 경우:

test("anArbitraryTest", () => {
  // … 생략 …
});

다음과 같은 방식으로 모두 실행이 가능합니다:

deno task -f @fedify/fedify test --filter anArbitraryTest
deno task -f @fedify/fedify test --filter   Arbitrary
deno task -f @fedify/fedify test --filter            Test

cd fedify/
pnpm test

일부 테스트만 빠르게 실행해 보고 싶을 경우 --test-name-pattern 옵션을 활용하세요:

pnpm test --test-name-pattern verifyRequest

Bun에서도 잘 돌아가는지 확인하려면 fedify/ 디렉터리 안쪽에서 pnpm test:bun 명령어를 사용하세요:

pnpm test:bun

일부 테스트만 빠르게 실행해 보고 싶을 경우 마찬가지로 --test-name-pattern 옵션을 활용하세요:

pnpm test:bun --test-name-pattern verifyRequest

마지막으로, Cloudflare Workers에서도 잘 돌아가는지 검사해야 합니다. 이 경우에는 pnpm test:cfworkers 명령어를 활용하세요:

pnpm test:cfworkers

일부 테스트만 빠르게 실행해 보고 싶을 경우 인자로 부분 문자열 키워드를 넘기면 됩니다:

pnpm test:cfworkers verifyRequest

사실, 앞서 설명했던 deno task test-all 명령어는 한 번에 Deno, Node.js, Bun, Cloudflare Workers 모두에서 테스트 스위트를 실행하는 명령어입니다.

안내

@fedify/cli: Fedify CLI 도구

일감 찾기

중요

이슈는 크게 세 종류로 나뉩니다:

피처 (feature): 말 그대로 새로운 기능을 뜻합니다.
버그 (bug): 기존에 있던 기능의 오작동을 뜻합니다.
태스크 (task): 신기능이나 버그 이외의 작업들을 가리킵니다. 예를 들면, 문서 수정 등이 여기에 속합니다.
미분류 (no type): 아직 분류되지 않은 이슈들인데, 이슈는 어떻게든 분류되어야 하므로 보통은 없습니다.

difficulty/beginner: 쉬운 난이도
good first issue: 처음 기여하는 사람에게 적합
help wanted: 도움 필요
type/documentation: 문서 관련

@fedify@hollo.social

#Fedify has moved to a monorepo structure with unified versioning across all packages (@fedify/fedify, @fedify/cli, database adapters & framework integrations).

All packages now release together, making dependency management much simpler!

https://bird.makeup/users/davidfowl/statuses/1939555328343085175

ALT text details

Fedify monorepo structure diagram showing all packages (@fedify/fedify, @fedify/cli, database adapters, framework integrations) unified with shared versioning

Vincent Cloutier

@vincent@r.town

I've just deployed the first set of changes to have proper activitypub quotes on bird.makeup, those exemples should (in theory) work on Mastodon 4.4 and others implementations that support those:

https://bird.makeup/users/bigtechalert/statuses/1937857604488970603

https://bird.makeup/users/nntaleb/statuses/1937556442103288296

Can you all test and report back? I will fix any incompatibilty with any implementation #fedidev

Vincent Cloutier

@vincent@r.town

I've just deployed the first set of changes to have proper activitypub quotes on bird.makeup, those exemples should (in theory) work on Mastodon 4.4 and others implementations that support those:

https://bird.makeup/users/davidfowl/statuses/1939555328343085175

https://bird.makeup/users/bigtechalert/statuses/1937857604488970603

https://bird.makeup/users/nntaleb/statuses/1937556442103288296

Can you all test and report back? I will fix any incompatibilty with any implementation #fedidev

Vincent Cloutier

@vincent@r.town

I've just deployed the first set of changes to have proper activitypub quotes on bird.makeup, those exemples should (in theory) work on Mastodon 4.4 and others implementations that support those:

https://bird.makeup/users/davidfowl/statuses/1939555328343085175

https://bird.makeup/users/bigtechalert/statuses/1937857604488970603

https://bird.makeup/users/nntaleb/statuses/1937556442103288296

Can you all test and report back? I will fix any incompatibilty with any implementation #fedidev

Hollo

@hollo@hollo.social

Introducing #Hollo. Hollo is an #ActivityPub-enabled single-user microblogging software. Although it's for a single user, it also supports creating and running multiple accounts for different topics.

It's headless, meaning you can use existing #Mastodon client apps instead, with its Mastodon-compatible APIs. It has most feature parity with Mastodon. Two big differences with Mastodon is that you can use #Markdown in the content of your posts and you can quote another post.

Oh, and Hollo is built using #Bun and #Fedify.

https://hollo.social/@fedify/0194b112-b604-7d03-84e0-4faaf4ab46cd

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

As the maintainer of #Fedify, I'd be grateful for your support to help keep the project sustainable!

Fedify: an ActivityPub server framework

@fedify@hollo.social

🎉 Excited to announce that #Fedify is now on Open Collective! Support the project's development starting at:

Backer (from $5/mo)
Supporter (from $25/mo)
Sponsor (from $100/mo)
Corporate Sponsor (from $500/mo)
Custom donations welcome

Your support will help us maintain and improve Fedify. Check it out here:

#OpenCollective #support #backing #sponsor #donation

ALT text details

Fedify's Open Collective page showing the project logo, description as “A TypeScript library for building federated server apps powered by ActivityPub and other standards”, and five contribution tiers starting from $5/month Backer to $500/month Corporate Sponsor, with custom contribution options available.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

As the maintainer of #Fedify, I'd be grateful for your support to help keep the project sustainable!

https://hollo.social/@fedify/0194b112-b604-7d03-84e0-4faaf4ab46cd

Fedify: an ActivityPub server framework

@fedify@hollo.social

🎉 Excited to announce that #Fedify is now on Open Collective! Support the project's development starting at:

Backer (from $5/mo)
Supporter (from $25/mo)
Sponsor (from $100/mo)
Corporate Sponsor (from $500/mo)
Custom donations welcome

Your support will help us maintain and improve Fedify. Check it out here:

#OpenCollective #support #backing #sponsor #donation

ALT text details

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

As the maintainer of #Fedify, I'd be grateful for your support to help keep the project sustainable!

https://hollo.social/@fedify/0194b112-b604-7d03-84e0-4faaf4ab46cd

Fedify: an ActivityPub server framework

@fedify@hollo.social

🎉 Excited to announce that #Fedify is now on Open Collective! Support the project's development starting at:

Backer (from $5/mo)
Supporter (from $25/mo)
Sponsor (from $100/mo)
Corporate Sponsor (from $500/mo)
Custom donations welcome

Your support will help us maintain and improve Fedify. Check it out here:

#OpenCollective #support #backing #sponsor #donation

ALT text details

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Excited to share that I've joined #OSSCA (Open Source Software Contribution Academy) as a mentor for the @fedify project!

OSSCA is a national program run by South Korea's NIPA (National IT Industry Promotion Agency) through their Open Source Software Support Center, aimed at fostering the next generation of open source contributors.

We're currently in the process of selecting around 20 mentees who will start contributing to #Fedify once the selection is complete. I've been busy preparing good first issues to help them get started on their open source journey.

Looking forward to working with these new contributors and seeing what amazing things we can build together!

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

I've been thinking about client-server interactions in the #fediverse. #ActivityPub #C2S isn't widely used, and most clients rely on Mastodon-compatible APIs instead.

What if we created a new standardized API based on GraphQL + Relay for client-server communication, while keeping ActivityPub for server-to-server federation?

The Mastodon-compatible API lacks formal schema definitions for code generation and type checking, which hurts developer productivity. And ActivityPub C2S is honestly too cumbersome to use directly from client apps.

#GraphQL would give us type safety, efficient data fetching (only get what you need), and the ability to evolve the API without breaking clients. #Relay's features for pagination, caching, and optimistic updates seem perfect for social apps.

Would this be valuable to our community? What challenges do you see? How might we handle backward compatibility? And should this be formalized as an FEP?

Curious what others think about this approach.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Excited to share that I've joined #OSSCA (Open Source Software Contribution Academy) as a mentor for the @fedify project!

Looking forward to working with these new contributors and seeing what amazing things we can build together!

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Excited to share that I've joined #OSSCA (Open Source Software Contribution Academy) as a mentor for the @fedify project!

Looking forward to working with these new contributors and seeing what amazing things we can build together!

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Excited to share that I've joined #OSSCA (Open Source Software Contribution Academy) as a mentor for the @fedify project!

Looking forward to working with these new contributors and seeing what amazing things we can build together!

Fedify: an ActivityPub server framework

@fedify@hollo.social

We are pleased to announce the release of #Fedify 1.7.0. This release was expedited at the request of the Ghost team, who are actively using Fedify for their #ActivityPub implementation. As a result, several features originally planned for this version have been moved to Fedify 1.8.0 to ensure timely delivery of the most critical improvements.

This release focuses on enhancing message queue functionality and improving compatibility with ActivityPub servers through refined HTTP signature handling.

Native retry mechanism support

This release introduces support for native retry mechanisms in message queue backends. The new MessageQueue.nativeRetrial property allows queue implementations to indicate whether they provide built-in retry functionality, enabling Fedify to optimize its retry behavior accordingly.

When nativeRetrial is set to true, Fedify will delegate retry handling to the queue backend rather than implementing its own retry logic. This approach reduces overhead and leverages the proven retry mechanisms of established queue systems.

Current implementations with native retry support include:

DenoKvMessageQueue — utilizes Deno KV's automatic retry with exponential backoff
WorkersMessageQueue — leverages Cloudflare Queues' automatic retry and dead-letter queue features
AmqpMessageQueue — can now be configured to use AMQP broker's native retry mechanisms

The InProcessMessageQueue continues to use Fedify's internal retry mechanism, while ParallelMessageQueue inherits the retry behavior from its wrapped queue.

AMQP message queue improvements

Alongside Fedify 1.7.0, we have also released @fedify/amqp 0.3.0. This release adds the nativeRetrial option to AmqpMessageQueueOptions, enabling you to leverage your AMQP broker's built-in retry mechanisms. When enabled, this option allows the AMQP broker to handle message retries according to its configured policies, rather than relying on Fedify's internal retry logic.

Configurable double-knocking

The new FederationOptions.firstKnock option provides control over the HTTP Signatures specification used for the initial signature attempt when communicating with previously unknown servers.

Previously, the first knock for newly encountered servers always used RFC 9421 (HTTP Message Signatures), falling back to draft-cavage-http-signatures-12 if needed. With this release, you can now configure which specification to use for the first knock when communicating with unknown servers, with RFC 9421 remaining the default.

Summary

This release maintains Fedify's commitment to reliability and compatibility while laying the groundwork for more efficient message processing. The native retry mechanism support will particularly benefit applications using queue backends with sophisticated retry capabilities, while the double-knocking mechanism addresses real-world compatibility challenges in the ActivityPub ecosystem.

For detailed technical information about these changes, please refer to the changelog in the repository.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Excited to share that I've joined #OSSCA (Open Source Software Contribution Academy) as a mentor for the @fedify project!

Looking forward to working with these new contributors and seeing what amazing things we can build together!

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Excited to share that I've joined #OSSCA (Open Source Software Contribution Academy) as a mentor for the @fedify project!

Looking forward to working with these new contributors and seeing what amazing things we can build together!

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're pleased to share that Encyclia has joined our success stories.

@encyclia bridges academic research to the #fediverse by making #ORCID researcher profiles and publications discoverable through #ActivityPub—built with #Fedify for seamless interoperability across Mastodon and other fediverse platforms.

Tim Chambers

@tchambers@indieweb.social

@fedify@hollo.social

We're pleased to share that Encyclia has joined our success stories.

This demonstrates Fedify's versatility beyond traditional social networking, helping specialized domains connect to the federated web.

We're also grateful for #Encyclia's sponsorship support, which helps make Fedify's development possible.

Learn more about Encyclia at https://encyclia.pub/. 📚

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're pleased to share that Encyclia has joined our success stories.

This demonstrates Fedify's versatility beyond traditional social networking, helping specialized domains connect to the federated web.

We're also grateful for #Encyclia's sponsorship support, which helps make Fedify's development possible.

Learn more about Encyclia at https://encyclia.pub/. 📚

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're pleased to share that Encyclia has joined our success stories.

This demonstrates Fedify's versatility beyond traditional social networking, helping specialized domains connect to the federated web.

We're also grateful for #Encyclia's sponsorship support, which helps make Fedify's development possible.

Learn more about Encyclia at https://encyclia.pub/. 📚

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Excited to share that I've joined #OSSCA (Open Source Software Contribution Academy) as a mentor for the @fedify project!

Looking forward to working with these new contributors and seeing what amazing things we can build together!

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Excited to share that I've joined #OSSCA (Open Source Software Contribution Academy) as a mentor for the @fedify project!

Looking forward to working with these new contributors and seeing what amazing things we can build together!

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're pleased to share that Encyclia has joined our success stories.

This demonstrates Fedify's versatility beyond traditional social networking, helping specialized domains connect to the federated web.

We're also grateful for #Encyclia's sponsorship support, which helps make Fedify's development possible.

Learn more about Encyclia at https://encyclia.pub/. 📚

Fedify: an ActivityPub server framework

@fedify@hollo.social

This release focuses on enhancing message queue functionality and improving compatibility with ActivityPub servers through refined HTTP signature handling.

Native retry mechanism support

Current implementations with native retry support include:

DenoKvMessageQueue — utilizes Deno KV's automatic retry with exponential backoff
WorkersMessageQueue — leverages Cloudflare Queues' automatic retry and dead-letter queue features
AmqpMessageQueue — can now be configured to use AMQP broker's native retry mechanisms

The InProcessMessageQueue continues to use Fedify's internal retry mechanism, while ParallelMessageQueue inherits the retry behavior from its wrapped queue.

AMQP message queue improvements

Configurable double-knocking

The new FederationOptions.firstKnock option provides control over the HTTP Signatures specification used for the initial signature attempt when communicating with previously unknown servers.

Summary

For detailed technical information about these changes, please refer to the changelog in the repository.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Excited to share that I've joined #OSSCA (Open Source Software Contribution Academy) as a mentor for the @fedify project!

Looking forward to working with these new contributors and seeing what amazing things we can build together!

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Excited to share that I've joined #OSSCA (Open Source Software Contribution Academy) as a mentor for the @fedify project!

Looking forward to working with these new contributors and seeing what amazing things we can build together!

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Excited to share that I've joined #OSSCA (Open Source Software Contribution Academy) as a mentor for the @fedify project!

Looking forward to working with these new contributors and seeing what amazing things we can build together!

Fedify: an ActivityPub server framework

@fedify@hollo.social

This release focuses on enhancing message queue functionality and improving compatibility with ActivityPub servers through refined HTTP signature handling.

Native retry mechanism support

Current implementations with native retry support include:

DenoKvMessageQueue — utilizes Deno KV's automatic retry with exponential backoff
WorkersMessageQueue — leverages Cloudflare Queues' automatic retry and dead-letter queue features
AmqpMessageQueue — can now be configured to use AMQP broker's native retry mechanisms

The InProcessMessageQueue continues to use Fedify's internal retry mechanism, while ParallelMessageQueue inherits the retry behavior from its wrapped queue.

AMQP message queue improvements

Configurable double-knocking

The new FederationOptions.firstKnock option provides control over the HTTP Signatures specification used for the initial signature attempt when communicating with previously unknown servers.

Summary

For detailed technical information about these changes, please refer to the changelog in the repository.

@fedify@hollo.social

We're pleased to share that Encyclia has joined our success stories.

This demonstrates Fedify's versatility beyond traditional social networking, helping specialized domains connect to the federated web.

We're also grateful for #Encyclia's sponsorship support, which helps make Fedify's development possible.

Learn more about Encyclia at https://encyclia.pub/. 📚

Fedify: an ActivityPub server framework

@fedify@hollo.social

This release focuses on enhancing message queue functionality and improving compatibility with ActivityPub servers through refined HTTP signature handling.

Native retry mechanism support

Current implementations with native retry support include:

DenoKvMessageQueue — utilizes Deno KV's automatic retry with exponential backoff
WorkersMessageQueue — leverages Cloudflare Queues' automatic retry and dead-letter queue features
AmqpMessageQueue — can now be configured to use AMQP broker's native retry mechanisms

The InProcessMessageQueue continues to use Fedify's internal retry mechanism, while ParallelMessageQueue inherits the retry behavior from its wrapped queue.

AMQP message queue improvements

Configurable double-knocking

Native retry mechanism support

Current implementations with native retry support include:

DenoKvMessageQueue — utilizes Deno KV's automatic retry with exponential backoff
WorkersMessageQueue — leverages Cloudflare Queues' automatic retry and dead-letter queue features
AmqpMessageQueue — can now be configured to use AMQP broker's native retry mechanisms

The InProcessMessageQueue continues to use Fedify's internal retry mechanism, while ParallelMessageQueue inherits the retry behavior from its wrapped queue.

AMQP message queue improvements

Configurable double-knocking

The new FederationOptions.firstKnock option provides control over the HTTP Signatures specification used for the initial signature attempt when communicating with previously unknown servers.

Summary

For detailed technical information about these changes, please refer to the changelog in the repository.

Fedify: an ActivityPub server framework

@fedify@hollo.social

This release focuses on enhancing message queue functionality and improving compatibility with ActivityPub servers through refined HTTP signature handling.

Native retry mechanism support

Current implementations with native retry support include:

DenoKvMessageQueue — utilizes Deno KV's automatic retry with exponential backoff
WorkersMessageQueue — leverages Cloudflare Queues' automatic retry and dead-letter queue features
AmqpMessageQueue — can now be configured to use AMQP broker's native retry mechanisms

The InProcessMessageQueue continues to use Fedify's internal retry mechanism, while ParallelMessageQueue inherits the retry behavior from its wrapped queue.

AMQP message queue improvements

Configurable double-knocking

The new FederationOptions.firstKnock option provides control over the HTTP Signatures specification used for the initial signature attempt when communicating with previously unknown servers.

Summary

For detailed technical information about these changes, please refer to the changelog in the repository.

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're pleased to share that Encyclia has joined our success stories.

This demonstrates Fedify's versatility beyond traditional social networking, helping specialized domains connect to the federated web.

We're also grateful for #Encyclia's sponsorship support, which helps make Fedify's development possible.

Learn more about Encyclia at https://encyclia.pub/. 📚

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're pleased to share that Encyclia has joined our success stories.

This demonstrates Fedify's versatility beyond traditional social networking, helping specialized domains connect to the federated web.

We're also grateful for #Encyclia's sponsorship support, which helps make Fedify's development possible.

Learn more about Encyclia at https://encyclia.pub/. 📚

Tim Chambers

@tchambers@indieweb.social

👋 Everyone: see what you think:

The Seven Deadly #Fediverse UX Sins Part 2: The Road To Redemption: https://www.timothychambers.net/2025/06/24/the-seven-deadly-fediverse-ux.html

Don't claim that these are final answers - but hope they help continue constructive motion to final answers!

cc: @renchap @dansup
@cheeaun @scottjenson @newsmast @andypiper @ricmac @evan @laurenshof @pfefferle @fediversenews #fedidev #mastodev @timbray

BotKit by Fedify

@fedify@hollo.social

This release focuses on enhancing message queue functionality and improving compatibility with ActivityPub servers through refined HTTP signature handling.

Native retry mechanism support

Current implementations with native retry support include:

DenoKvMessageQueue — utilizes Deno KV's automatic retry with exponential backoff
WorkersMessageQueue — leverages Cloudflare Queues' automatic retry and dead-letter queue features
AmqpMessageQueue — can now be configured to use AMQP broker's native retry mechanisms

The InProcessMessageQueue continues to use Fedify's internal retry mechanism, while ParallelMessageQueue inherits the retry behavior from its wrapped queue.

AMQP message queue improvements

Configurable double-knocking

Native retry mechanism support

Current implementations with native retry support include:

DenoKvMessageQueue — utilizes Deno KV's automatic retry with exponential backoff
WorkersMessageQueue — leverages Cloudflare Queues' automatic retry and dead-letter queue features
AmqpMessageQueue — can now be configured to use AMQP broker's native retry mechanisms

The InProcessMessageQueue continues to use Fedify's internal retry mechanism, while ParallelMessageQueue inherits the retry behavior from its wrapped queue.

AMQP message queue improvements

Configurable double-knocking

The new FederationOptions.firstKnock option provides control over the HTTP Signatures specification used for the initial signature attempt when communicating with previously unknown servers.

Summary

For detailed technical information about these changes, please refer to the changelog in the repository.

Fedify: an ActivityPub server framework

@fedify@hollo.social

This release focuses on enhancing message queue functionality and improving compatibility with ActivityPub servers through refined HTTP signature handling.

Native retry mechanism support

Current implementations with native retry support include:

DenoKvMessageQueue — utilizes Deno KV's automatic retry with exponential backoff
WorkersMessageQueue — leverages Cloudflare Queues' automatic retry and dead-letter queue features
AmqpMessageQueue — can now be configured to use AMQP broker's native retry mechanisms

The InProcessMessageQueue continues to use Fedify's internal retry mechanism, while ParallelMessageQueue inherits the retry behavior from its wrapped queue.

AMQP message queue improvements

Configurable double-knocking

The new FederationOptions.firstKnock option provides control over the HTTP Signatures specification used for the initial signature attempt when communicating with previously unknown servers.

Summary

For detailed technical information about these changes, please refer to the changelog in the repository.

Fedify: an ActivityPub server framework

@fedify@hollo.social

This release focuses on enhancing message queue functionality and improving compatibility with ActivityPub servers through refined HTTP signature handling.

Native retry mechanism support

Current implementations with native retry support include:

DenoKvMessageQueue — utilizes Deno KV's automatic retry with exponential backoff
WorkersMessageQueue — leverages Cloudflare Queues' automatic retry and dead-letter queue features
AmqpMessageQueue — can now be configured to use AMQP broker's native retry mechanisms

The InProcessMessageQueue continues to use Fedify's internal retry mechanism, while ParallelMessageQueue inherits the retry behavior from its wrapped queue.

AMQP message queue improvements

Configurable double-knocking

The new FederationOptions.firstKnock option provides control over the HTTP Signatures specification used for the initial signature attempt when communicating with previously unknown servers.

Summary

For detailed technical information about these changes, please refer to the changelog in the repository.

Fedify: an ActivityPub server framework

@fedify@hollo.social

This release focuses on enhancing message queue functionality and improving compatibility with ActivityPub servers through refined HTTP signature handling.

Native retry mechanism support

Current implementations with native retry support include:

DenoKvMessageQueue — utilizes Deno KV's automatic retry with exponential backoff
WorkersMessageQueue — leverages Cloudflare Queues' automatic retry and dead-letter queue features
AmqpMessageQueue — can now be configured to use AMQP broker's native retry mechanisms

The InProcessMessageQueue continues to use Fedify's internal retry mechanism, while ParallelMessageQueue inherits the retry behavior from its wrapped queue.

AMQP message queue improvements

Configurable double-knocking

The new FederationOptions.firstKnock option provides control over the HTTP Signatures specification used for the initial signature attempt when communicating with previously unknown servers.

Summary

For detailed technical information about these changes, please refer to the changelog in the repository.

#fediDev #mastodev #nodeinfo

Fedify: an ActivityPub server framework

@fedify@hollo.social

This release focuses on enhancing message queue functionality and improving compatibility with ActivityPub servers through refined HTTP signature handling.

Native retry mechanism support

Current implementations with native retry support include:

DenoKvMessageQueue — utilizes Deno KV's automatic retry with exponential backoff
WorkersMessageQueue — leverages Cloudflare Queues' automatic retry and dead-letter queue features
AmqpMessageQueue — can now be configured to use AMQP broker's native retry mechanisms

The InProcessMessageQueue continues to use Fedify's internal retry mechanism, while ParallelMessageQueue inherits the retry behavior from its wrapped queue.

AMQP message queue improvements

Configurable double-knocking

👋 Everyone: see what you think:

The Seven Deadly #Fediverse UX Sins Part 2: The Road To Redemption: https://www.timothychambers.net/2025/06/24/the-seven-deadly-fediverse-ux.html

Don't claim that these are final answers - but hope they help continue constructive motion to final answers!

cc: @renchap @dansup
@cheeaun @scottjenson @newsmast @andypiper @ricmac @evan @laurenshof @pfefferle @fediversenews #fedidev #mastodev @timbray

Tim Chambers

@tchambers@indieweb.social

👋 Everyone: see what you think:

The Seven Deadly #Fediverse UX Sins Part 2: The Road To Redemption: https://www.timothychambers.net/2025/06/24/the-seven-deadly-fediverse-ux.html

Don't claim that these are final answers - but hope they help continue constructive motion to final answers!

cc: @renchap @dansup
@cheeaun @scottjenson @newsmast @andypiper @ricmac @evan @laurenshof @pfefferle @fediversenews #fedidev #mastodev @timbray

mousebot

@mousebot@todon.nl

do any fedi client devs know how to get a nodeinfo request to work? in the browser i receive JSON, while with my client i receive an HTML error saying use the web or a client.

EDIT: solved, you just have to not fuck everything up in your request (no special details required).

aliceif she was teto

@aliceif@mkultra.x27.one

Jumping off this:

Does markdown-but-suitable-for-IM-and-comments have anything to point at? Any specs? Any test suites? #markdown #standards #fedidev

RE: https://mkultra.x27.one/notes/a9c69ant7hg40knu

aliceif she was teto

@aliceif@mkultra.x27.one · Reply to Hazelnoot's post

@hazelnoot@enby.life improving compatibility with "markdown" is a very dangerous goal to set.

Markdown as daringfireball specified it is an underspecced bad markup system for blogs that is unsuitable for implementation (underspecced with early on a lot of competing interpretations of vague or missing parts of how markdown works).

Implementing a formalized version of "Markdown" like CommonMark is also a horrible idea.
it's still fundamentally for blogs not posts and you run into utterly unsuitable for SNS problems like newlines in CommonMark and original Markdown being ignored unless preceded by two spaces. The probably #1 hardest to anticipate and find+understand the solution against part of the original Markdown and CommonMark. But there's also other problems like lists...

@hollo@hollo.social uses CommonMark and trips me up regularly - the read-only web frontend often formats very different than the MastodonAPI clients I use that use a non-standard markdown more in the style of misskey or discord that doesn't do horrible newline mangling.

Yes, causing animations with normal looking markup notation is bad but please don't set yourself up for adhering to a spec you do not want to adhere to.

wakest ⁂

@liaizon@social.wake.st

Meta Fediverse by Facebook Threads by Instagram with built tracking and WhatsApp ads is live!
https://about.fb.com/news/2025/06/its-now-easier-see-more-fediverse-content-threads #fediverse #meta #fedidev #threads

ALT text details

A screenshot of the official Facebook announcement

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

연합우주(fediverse)를 사용해본 사람이라면 한 번쯤 경험했을 것입니다. 흥미로운 토론이 벌어지고 있는 것 같은데, 막상 그 대화를 들여다보면 답글이 몇 개 밖에 보이지 않거나, 맥락을 알 수 없는 답글들만 띄엄띄엄 나타나는 현상 말입니다. 마치 여러 사람이 모여 토론하고 있는데, 그 중 일부의 말만 들리는 것처럼 느껴집니다.

이것이 바로 연합우주 사용자들이 종종 겪는 “조용한 연합우주”(quiet fediverse) 문제입니다. 2025년 2월 브뤼셀 FOSDEM에서 열린 The Fediverse is Quiet—Let's Fix That! 발표는 이 문제를 정면으로 다뤘습니다.

이 글에서는 연합우주의 대화 단절 문제가 왜 발생하는지, 그리고 이를 해결하기 위해 개발자들이 제시한 두 가지 주요 접근법을 자세히 살펴보겠습니다. 각 방식의 기술적 원리부터 실제 구현 사례, 그리고 각각의 장단점까지 풍부한 예시와 함께 설명하겠습니다.

Note

이 글은 NodeBB의 @julian 씨가 작성한 Backfilling Conversations: Two Major Approaches를 주요 참고 자료로 하여, 한국 개발자 커뮤니티를 위해 한국어로 번역하고 추가 분석을 더한 글입니다.

원글의 구조와 핵심 아이디어를 바탕으로 하되, 기술적 개념 설명을 보강하고 실제 구현 사례를 추가했습니다. AI의 도움을 받아 작성되었습니다.

원작자 @julian 씨와 활발한 논의에 참여해주신 연합우주 개발자 커뮤니티에 감사드립니다.

문제의 근본 원인: ActivityPub의 분산 특성

ActivityPub이란?

먼저 연합우주의 기반이 되는 ActivityPub 프로토콜을 이해해야 합니다. ActivityPub은 분산형 소셜 네트워크를 위한 W3C 표준 프로토콜로, 서로 다른 서버의 사용자들이 상호작용할 수 있게 해줍니다.

ActivityPub에서 모든 상호작용은 액티비티(activity)라는 형태로 표현됩니다. 예를 들어, 새 게시물을 작성하면 Create(Note) 액티비티가 생성되고, 답글을 달면 역시 Create(Note) 액티비티가 생성되어 해당 게시물에 대한 답글임을 나타냅니다. 자세한 내용은 ActivityStreams 2.0 스펙에서 확인할 수 있습니다.

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Create",
  "id": "https://alice.example/activities/create-reply-123",
  "actor": "https://alice.example/users/alice",
  "published": "2025-06-09T10:30:00Z",
  "to": ["https://bob.example/users/bob"],
  "object": {
    "type": "Note",
    "id": "https://alice.example/notes/reply-123",
    "content": "정말 흥미로운 관점이네요!",
    "inReplyTo": "https://bob.example/posts/original-post",
    "attributedTo": "https://alice.example/users/alice"
  }
}

분산의 딜레마

ActivityPub의 분산 특성이 바로 문제의 원인입니다. 중앙화된 플랫폼(X, Facebook 등)과 달리, 연합우주에서는 대화가 여러 서버에 걸쳐 분산되어 저장됩니다.

Alice(alice.example)가 원글을 작성하고, Bob(bob.example)이 Alice의 글에 답글을 달고, Charlie(charlie.example)가 Bob의 답글에 다시 답글을 달고, Dave(dave.example)가 Alice의 원글에 직접 답글을 다는 상황을 생각해보세요:

Alice의 원글
├── Bob의 댓글
│   └── Charlie의 댓글
└── Dave의 댓글

이때 각 서버는 다음과 같은 정보만 가지고 있을 수 있습니다. alice.example은 Alice의 원글과 Bob의 답글, Dave의 답글은 알지만 Charlie의 답글은 모를 수 있습니다. bob.example은 Alice의 원글과 Bob의 답글, Charlie의 답글은 알지만 Dave의 답글은 모를 수 있습니다. 결과적으로 어느 누구도 전체 대화의 완전한 그림을 볼 수 없게 됩니다.

해결책을 위한 기반 개념: `context` 속성

두 가지 주요 해결책을 살펴보기 전에, 핵심이 되는 context 속성에 대해 이해해야 합니다. ActivityStreams 2.0에서 정의된 context 속성은 관련된 오브젝트들을 그룹화하기 위해 사용됩니다. 하지만 스펙에서는 이를 “의도적으로 모호하게”(intentionally vague) 정의했기 때문에, 실제 구현에서는 다양한 방식으로 활용되고 있습니다.

실제 `context` 값의 형태들

1. 단순 식별자

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "첫 번째 댓글입니다",
  "context": "https://example.com/conversations/abc123"
}

2. Mastodon 스타일 (`ostatus:conversation`)

Mastodon은 ActivityPub 표준의 context와 함께 OStatus 시절부터 사용해온 conversation 속성을 병행 사용합니다.

{
  "@context": [
    "https://www.w3.org/ns/activitystreams",
    {
      "ostatus": "http://ostatus.org#",
      "conversation": "ostatus:conversation"
    }
  ],
  "type": "Note",
  "content": "이것은 답글입니다",
  "context": "https://mastodon.social/contexts/abc123",
  "conversation": "tag:mastodon.social,2025:objectId=12345:objectType=Conversation"
}

3. 해석 가능한 컬렉션 URL (FEP 7888 방식)

이 경우 컨텍스트 URL로 GET 요청을 보내면 해당 대화의 모든 게시물을 포함한 OrderedCollection이 반환됩니다. 이는 FEP-7888: Demystifying the context property에서 제안한 방식입니다.

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "스레드 대화의 일부입니다",
  "context": "https://forum.example/topics/technology/thread-42",
  "inReplyTo": "https://forum.example/posts/789"
}

첫 번째 접근법: 답글 트리 크롤링 (reply tree crawling)

개요와 역사

답글 트리 크롤링 방식은 Mastodon의 @jonny 씨가 개척한 방법입니다. 2024년 4월 15일 처음 제안되어 2025년 3월 12일 Mastodon 코어에 병합되었습니다.

이 방식의 핵심 아이디어는 “모든 답글을 가져오기”(fetch all replies)입니다. 답글 트리 전체를 순차적으로 크롤링하여 누락된 대화를 찾아내는 것입니다.

기술적 작동 원리

1. 필요한 전제 조건

이 방식이 작동하려면 모든 ActivityPub 오브젝트가 replies 컬렉션을 제공해야 합니다. 이는 ActivityPub 오브젝트가 받은 답글들의 목록을 나타내는 컬렉션입니다. 이를 통해 특정 게시물에 달린 모든 답글을 탐색할 수 있습니다.

{
  "id": "https://alice.example/posts/1",
  "type": "Note",
  "content": "어떻게 생각하세요?",
  "replies": {
    "type": "OrderedCollection",
    "id": "https://alice.example/posts/1/replies",
    "totalItems": 3,
    "first": "https://alice.example/posts/1/replies?page=1"
  }
}

2. 크롤링 알고리즘

답글 트리 크롤링의 작동 방식은 본질적으로 깊이 우선 탐색(DFS)과 유사합니다. 시작점이 되는 게시물부터 시작해서 모든 답글을 찾아 내려가는 과정을 반복합니다.

구체적인 과정을 살펴보면, 먼저 시작 게시물의 replies 컬렉션을 확인합니다. 이 컬렉션에는 해당 게시물에 직접 달린 답글들의 목록이 들어있습니다. 그 다음 각 답글을 하나씩 가져와서 처리하는데, 여기서 중요한 것은 각 답글 역시 자신만의 replies 컬렉션을 가질 수 있다는 점입니다.

async function crawlReplyTree(postUrl: URL): Promise<Note[]> {
  const post = await fetchNote(postUrl);
  const allReplies: Note[] = [];
  
  const replies = await post.getReplies();
  if (replies) {
    for await (const reply of replies.getItems()) {
      if (reply instanceof Note) {
        allReplies.push(reply);
        const subReplies = await crawlReplyTree(reply.id!);
        allReplies.push(...subReplies);
      }
    }
  }
  
  return allReplies;
}

이 방식의 핵심은 각 노드(게시물)가 자신에게 달린 답글들의 목록을 정확히 제공한다는 가정에 기반한다는 점입니다.

3. Mastodon의 실제 구현

Mastodon에서는 이론적인 알고리즘을 실제 네트워크 환경에 맞게 조정한 구현을 사용합니다. 핵심적인 차이점은 현실적인 제약들을 고려한다는 점입니다.

@jonny 씨의 설명에 따르면, 현재 구현에는 몇 가지 실용적인 고려사항이 포함되어 있습니다. 확장된 게시물에서 시작해서 아래로 진행하며, 트리의 어느 지점에서든 크롤링을 시작할 수 있고, 중복 크롤링을 방지하는 쿨다운 메커니즘을 포함합니다.

장점

범용성: inReplyTo와 replies 속성은 거의 모든 ActivityPub 구현에서 보편적으로 사용됩니다. 따라서 기존 인프라를 크게 변경하지 않고도 적용할 수 있습니다.
구현 간 일관성: 대부분의 ActivityPub 구현체에서 이 속성들의 사용법이 크게 다르지 않습니다.
완전한 트리 구성: 이상적인 경우 모든 브랜치와 리프를 포함한 완전한 대화 트리를 얻을 수 있습니다.

단점

네트워크 취약성: 답글 트리의 단일 노드가 일시적 또는 영구적으로 접근 불가능하면, 해당 노드에서 파생되는 모든 브랜치들도 접근할 수 없게 됩니다.
선형적 작업량 증가: CPU 시간, 네트워크 요청 등의 작업량이 답글 트리 크기에 비례하여 선형적으로 증가합니다. 대규모 토론에서는 성능 문제가 발생할 수 있습니다.
재크롤링 필요성: 새로운 브랜치 발견을 위해서는 전체 답글 트리를 다시 크롤링해야 합니다. 빠르게 성장하는 토론에서는 크롤링 시작 시점에 따라 완전한 트리를 얻지 못할 수 있습니다.
불완전한 구현 현실: 현실적으로 모든 ActivityPub 구현체가 replies 컬렉션을 제공하지는 않습니다. Mastodon은 성능상 이유로 같은 서버의 답글만 최대 5개까지 replies 컬렉션에 포함하며, 많은 소규모 구현체들은 성능상 이유로 이를 생략하거나 불완전하게 구현합니다.

현재 구현 현황

현재 Mastodon이 이 방식의 유일한 완전한 구현체입니다. 하지만 이 방식은 Mastodon 고유의 것이 아니며, 다른 구현체들도 채택할 수 있습니다.

두 번째 접근법: 컨텍스트 소유자 기반 방식 (context owner approach)

개요와 배경

컨텍스트 소유자 방식은 여러 FEP^[1]의 결합으로 탄생했습니다. FEP-7888은 “context 속성 명확화”(demystifying the context property)를 다루고, FEP-171b는 “대화 컨테이너”(conversation containers)를 정의하며, FEP-f228은 위 FEP들의 통합 및 확장을 제안합니다.

이 방식의 핵심은 “컨텍스트 소유자”(context owner) 개념입니다. 대화의 원 작성자나 지정된 주체가 해당 대화의 모든 내용을 관리하는 중앙화된 접근법입니다.

기술적 작동 원리

1. 컨텍스트 소유자의 역할

컨텍스트 소유자는 누가 되는가? 일반적으로 스레드의 최상위 게시물(루트 포스트)을 작성한 사용자가 컨텍스트 소유자가 됩니다. 예를 들어, Alice가 “오늘 날씨가 어떤가요?”라는 원글을 작성했다면, Alice가 해당 대화의 컨텍스트 소유자가 되는 것입니다.

그러나 포럼이나 그룹 환경에서는 포럼 관리자나 그룹 소유자가 컨텍스트 소유자 역할을 할 수도 있습니다. 핵심은 누군가 한 명이 해당 대화의 “정규 멤버십”을 결정할 권한을 가진다는 점입니다.

컨텍스트 소유자는 자신이 관리하는 대화의 모든 멤버를 포함하는 OrderedCollection을 제공합니다.

{
  "@context": [
    "https://www.w3.org/ns/activitystreams",
    "https://w3id.org/fep/171b"
  ],
  "type": "OrderedCollection",
  "id": "https://alice.example/conversations/tech-discussion",
  "attributedTo": "https://alice.example/users/alice",
  "collectionOf": "Activity",
  "totalItems": 15,
  "orderedItems": [
    "https://alice.example/activities/add/1",
    "https://alice.example/activities/add/2",
    "https://alice.example/activities/add/3"
  ]
}

2. 두 단계 액티비티 프로세스

이 방식에서는 댓글 추가가 반드시 두 단계로 이루어져야 합니다. 왜 이렇게 복잡하게 해야 할까요?

첫 번째 이유는 모더레이션입니다. 단순히 답글을 작성한다고 해서 자동으로 해당 대화에 포함되는 것이 아니라, 컨텍스트 소유자의 승인을 거쳐야 합니다.

두 번째 이유는 일관성입니다. 컨텍스트 소유자가 관리하는 컬렉션에는 Add 액티비티들만 들어가므로, 나중에 이 컬렉션을 읽는 다른 서버들이 “이것들은 모두 컨텍스트 소유자가 승인한 내용들”이라는 것을 명확히 알 수 있습니다.

세 번째 이유는 확산(broadcasting)입니다. 직접 댓글 뿐만 아니라 대화에 속하는 모든 댓글과 대댓글은 모두 컨텍스트 소유자에게 전송되기에 컨텍스트 소유자는 그 대화에 포함되는 모든 노드를 파악하고 있습니다. 따라서, 모든 대화 참여자들에게 새 댓글이 추가되었다는 것을 통보할 수 있습니다.

1단계: 답글 작성자가 일반적인 Create(Note) 액티비티 전송

Bob이 Alice의 게시물에 답글을 달고 싶어합니다. Bob은 평소처럼 Create(Note) 액티비티를 생성하되, Note 오브젝트의 context 속성에 Alice가 관리하는 대화 ID를 포함합니다.

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Create",
  "actor": "https://bob.example/users/bob",
  "published": "2025-06-09T11:00:00Z",
  "to": ["https://alice.example/users/alice"],
  "object": {
    "type": "Note",
    "id": "https://bob.example/notes/reply-456",
    "content": "정말 좋은 지적이군요!",
    "inReplyTo": "https://alice.example/posts/original",
    "context": "https://alice.example/conversations/tech-discussion"
  }
}

중요한 점은 Bob이 이 액티비티를 컨텍스트 소유자인 Alice에게 직접 전송한다는 것입니다(to 필드 참조). 이는 Alice가 Bob의 답글을 알 수 있도록 하기 위함입니다.

2단계: 컨텍스트 소유자(Alice)가 Add(Note) 액티비티 생성

Alice는 Bob의 답글을 받고, 이것이 자신의 대화에 포함할 만한 내용이라고 판단합니다. 그러면 Alice는 Add(Note) 액티비티를 생성하여 Bob의 답글을 자신의 대화 컬렉션에 추가합니다.

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Add",
  "actor": "https://alice.example/users/alice",
  "published": "2025-06-09T11:05:00Z",
  "object": "https://bob.example/notes/reply-456",
  "target": {
    "type": "OrderedCollection",
    "id": "https://alice.example/conversations/tech-discussion",
    "attributedTo": "https://alice.example/users/alice"
  },
  "to": ["https://www.w3.org/ns/activitystreams#Public"]
}

이 Add 액티비티는 “Alice가 Bob의 답글을 자신의 대화에 공식적으로 포함시켰다”는 의미입니다. 만약 Alice가 Bob의 답글이 스팸이나 부적절한 내용이라고 판단했다면, 이 Add(Note) 액티비티를 생성하지 않을 수 있습니다.

3. 백필 메커니즘

개별 구현체들은 컨텍스트 소유자에게 전체 대화 내용을 요청할 수 있습니다.

async function performContextBackfill(contextUrl: URL): Promise<Note[]> {
  const collection = await fetchCollection(contextUrl);
  const notes: Note[] = [];
  
  for await (const item of collection.getItems()) {
    if (item instanceof Add) {
      const note = await item.getObject();
      if (note instanceof Note) {
        notes.push(note);
      }
    }
  }
  
  return notes;
}

장점

의사 중앙화(pseudo-centralization)의 이점: 컨텍스트 소유자가 제공하는 “단일 진실의 원천”(single source of truth)을 통해 일관된 대화 상태를 유지할 수 있습니다.
효율적인 네트워크 사용: 컨텍스트 소유자에게 한 번의 요청으로 전체 대화를 가져올 수 있어, 답글 트리 크롤링보다 네트워크 효율성이 높습니다.
중간 노드 장애 극복: 답글 트리 크롤링과 달리, 중간 노드가 다운되어도 컨텍스트 소유자를 통해 전체 대화에 접근할 수 있습니다.
효율적인 중복 제거: 컨텍스트 레벨에서 오브젝트 중복 제거가 가능하여 전체 네트워크 요청 수와 CPU 시간을 줄일 수 있습니다.
동기화 최적화: ID 해시섬을 통한 동기화 방법으로 네트워크 호출을 더욱 줄일 수 있습니다.

단점

컨텍스트 소유자 의존성: 가장 큰 약점은 컨텍스트 소유자에 대한 의존성입니다. 컨텍스트 소유자 서버에 접근할 수 없으면 전체 대화 백필이 불가능해집니다.
제한된 가시성: 컨텍스트 소유자는 자신이 알고 있는 오브젝트/액티비티만 응답할 수 있습니다.
상위 전파 누락 문제: 핵심적인 한계로, 루트로 다시 상위 전파되지 않는 하위 브랜치들은 컨텍스트 소유자가 알 수 없습니다.
구현체 지원 필요: 컨텍스트 소유자가 이 방식을 지원해야만 작동하므로, 다른 백필 전략과 결합해야 합니다.

현재 구현 현황

NodeBB, Discourse, WordPress, Frequency, Mitra, Streams가 현재 이 방식을 구현하고 있으며, Lemmy와 Piefed가 관심을 표명하고 있습니다.

중요한 논쟁 포인트들

1. 모더레이션 패러다임의 충돌

관련 NodeBB 스레드에서 @silverpill 씨가 제기한 핵심적인 문제점입니다.

두 접근 방식이 서로 충돌하지 않는다고 했지만, 이 ‘스레딩 패러다임’들은 모더레이션 문제에 대해 서로 다른 해결책을 제시합니다.

I don't fully agree with this statement, because these ‘threading paradigms’ suggest two different solutions to the problem of moderation.

컨텍스트 소유자 방식의 모더레이션

Alice가 스팸 댓글에 대해 Add(Note) 액티비티를 생성하지 않으면, 해당 댓글은 대화에서 제외됩니다.

답글 트리 크롤링의 모더레이션

각 답글이 독립적이며, 작성자들이 직접 답글만 모더레이션할 수 있습니다. 원글 작성자가 전체 대화를 제어할 수 없습니다.

2. 상위 전파 누락 문제의 해결책

어드레싱 규칙 활용 (FEP-171b)

FEP-171b에서는 “답글의 audience는 대화 루트에서 복사되어야 한다”(The audience of a reply MUST be copied from a conversation root)는 규칙을 제시합니다.

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Create",
  "actor": "https://charlie.example/users/charlie",
  "object": {
    "type": "Note",
    "content": "Bob의 댓글에 대한 답글",
    "inReplyTo": "https://bob.example/comments/2",
    "context": "https://alice.example/conversations/1",
    "to": [
      "https://bob.example/users/bob",
      "https://alice.example/users/alice"
    ]
  }
}

하이브리드 백필 메커니즘

많은 구현체가 여러 방식을 조합하는 방식을 채택합니다.

async function hybridBackfill(conversationId: URL): Promise<Note[]> {
  const strategies = [
    () => contextOwnerBackfill(conversationId),
    () => replyTreeCrawling(conversationId),
    () => mentionBasedDiscovery(conversationId)
  ];
  
  for (const strategy of strategies) {
    try {
      const result = await strategy();
      if (result.length > 0) return result;
    } catch (error) {
      console.warn('Strategy failed, trying next:', error);
    }
  }
  
  return [];
}

추가적인 백필 메커니즘들

주기적 크롤링 백필: 이 방식은 마치 정기적인 건강검진과 같습니다. 시스템이 정해진 주기마다 활발한 대화들을 점검하여 누락된 답글이 있는지 확인합니다.
사용자 트리거 백필: 사용자가 특정 대화 페이지에 접속하면, 시스템은 즉시 현재 보유한 컨텍스트 컬렉션을 검토하고 실시간으로 누락된 답글들을 탐색합니다.

멘션 기반 백필: 사용자들이 대화에서 다른 사람을 멘션하는 자연스러운 행동을 통해 누락된 답글 체인을 발견하는 메커니즘입니다.

async function onMentionReceived(activity: Create): Promise<void> {
  const mention = await activity.getObject();

  if (mention.context && mention.replyTargetId) {
    const missingChain = await traceReplyChain(await mention.getReplyTarget());
    await addToContext(mention.context, missingChain);
  }
}

실제 도전과제들

순환 참조 방지: 백필 과정에서 무한 루프에 빠지는 것을 방지하는 것은 매우 중요합니다. 실제 구현에서는 방문한 URL을 추적하고, 최대 탐색 깊이를 제한하는 안전장치를 마련합니다.
성능 최적화: 대규모 대화에서는 수백 개의 답글이 달릴 수 있고, 이를 모두 한 번에 처리하려고 하면 서버에 과도한 부하가 걸릴 수 있습니다. 일괄 처리(batch processing)는 여러 대화를 동시에 처리할 때 작은 그룹으로 나누어 순차적으로 처리하고 각 배치 사이에 짧은 휴식 시간을 두는 방식입니다.
오류 처리 및 복구: 분산 네트워크 환경에서는 다양한 종류의 오류가 발생할 수 있습니다. 실제 구현에서는 여러 백필 전략을 순차적으로 시도하는 복원력 있는 접근법을 사용합니다.

표준화 노력과 미래 전망

FEP 수렴 논의

현재 연합우주 커뮤니티에서는 FEP 수렴 스레드를 통해 여러 FEP들을 통합하려는 노력이 진행되고 있습니다.

이 논의에서 다루고 있는 주요 FEP들은 공개적으로 추가 가능한 ActivityPub 컬렉션을 정의하는 FEP-400e, 애매하게 정의된 context 속성에 대한 구체적인 사용법을 제시하는 FEP-7888, 중앙화된 대화 관리 메커니즘을 다루는 FEP-171b, 그리고 답글 트리의 전체적인 시각화 방법을 제안하는 FEP-76ea입니다.

구현체 간 협력

현재 다양한 구현체들이 실용적인 상호 호환성을 위해 협력하고 있습니다. 이는 완벽한 표준이 확정되기를 기다리기보다는, 현재 사용 가능한 방법들을 조합해서 최선의 결과를 얻으려는 실무적 접근입니다.

NodeBB와 Discourse의 협력 사례

이 두 포럼 소프트웨어는 포럼에 특화된 백필 메커니즘을 공유하고 있습니다. 포럼의 특성상 대화가 구조화되어 있고 장기간 지속되는 경우가 많아서, 토픽과 카테고리 개념을 활용한 컨텍스트 관리가 특히 중요합니다.

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "context": "https://community.nodebb.org/topic/18844",
  "audience": "https://community.nodebb.org/category/development",
  "tag": [
    {
      "type": "Link",
      "href": "https://meta.discourse.org/t/activitypub-support/12345",
      "rel": "related"
    }
  ]
}

Mastodon과의 호환성 고려

Mastodon은 가장 큰 연합우주 플랫폼이기 때문에, 다른 구현체들은 Mastodon과의 호환성을 고려해야 합니다. 특히 Mastodon이 사용하는 ostatus:conversation 개념을 함께 지원하는 경우가 많습니다.

{
  "@context": [
    "https://www.w3.org/ns/activitystreams",
    {
      "ostatus": "http://ostatus.org#",
      "conversation": "ostatus:conversation"
    }
  ],
  "type": "Note",
  "content": "Mastodon 호환 답글",
  "context": "https://mastodon.social/contexts/abc123",
  "conversation": "tag:mastodon.social,2025:objectId=12345:objectType=Conversation"
}

이런 하위 호환성 유지는 연합우주 생태계의 분열을 방지하고 사용자 경험을 개선하는 데 중요한 역할을 합니다.

향후 개발 방향: 하이브리드 접근법의 표준화

미래에는 단일한 “정답”을 찾는 것보다는 여러 방식을 체계적으로 조합하는 표준화된 접근법이 등장할 가능성이 높습니다. 이는 각 방식의 장점을 살리면서 단점을 보완하는 best-of-both-worlds 접근법입니다.

모범 사례 가이드라인

다중 전략 구현: 절대로 하나의 백필 방식에만 의존하지 마세요. 연합우주의 다양성과 불확실성을 고려할 때, 여러 전략을 조합하는 것이 필수적입니다. 각 전략은 서로 다른 상황에서 강점을 보이므로, 상황에 따라 적절한 전략을 선택할 수 있는 유연성을 확보해야 합니다.

예를 들어, 활발한 포럼 토론에서는 컨텍스트 소유자 방식이 효과적일 수 있지만, Mastodon의 일반적인 대화에서는 답글 트리 크롤링이 더 적합할 수 있습니다.
리소스 관리: 백필 작업은 상당한 서버 리소스를 소모할 수 있습니다. 특히 인기 있는 대화나 대규모 토론의 경우 수백 개의 네트워크 요청이 필요할 수 있습니다. 따라서 적절한 제한과 조절 메커니즘을 구현해야 합니다.
모니터링 및 로깅: 백필 시스템의 성능과 신뢰성을 지속적으로 모니터링하는 것이 중요합니다. 어떤 방식이 가장 효과적인지, 어떤 종류의 오류가 자주 발생하는지 등을 추적해야 합니다.

결론

“조용한 연합우주” 문제는 분산형 소셜 네트워크의 근본적인 도전과제입니다. 이 글에서 살펴본 두 가지 주요 접근법—답글 트리 크롤링과 컨텍스트 소유자 방식—은 각각 고유한 장단점을 가지고 있습니다.

핵심 통찰

완벽한 해결책은 없습니다. 두 접근법 모두 특정 상황에서 한계를 보입니다. 분산 네트워크의 본질적인 특성상 100% 완벽한 대화 복구는 현실적으로 어려울 수 있습니다.

하이브리드 접근이 현실적입니다. 대부분의 성공적인 구현체들은 여러 백필 전략을 조합해서 사용합니다. 한 가지 방법이 실패해도 다른 방법으로 보완할 수 있는 탄력성이 중요합니다.

표준화가 진행 중입니다. FEP 과정을 통해 상호 호환성을 높이려는 노력이 계속되고 있습니다. 하지만 완전한 표준을 기다리기보다는 현재 가능한 방법들을 실용적으로 조합하는 것이 더 현실적입니다.

사용자 경험이 핵심입니다. 기술적 완성도도 중요하지만, 최종적으로는 사용자가 완전한 대화를 볼 수 있느냐가 관건입니다. 기술적 우아함보다는 실용적 효과를 우선시해야 합니다.

앞으로의 방향

연합우주의 대화 백필 문제는 단순히 기술적인 문제를 넘어서 분산형 네트워크에서의 거버넌스, 모더레이션, 사용자 경험의 복합적인 문제입니다.

특히 모더레이션 패러다임의 차이는 단순한 기술적 호환성을 넘어서는 철학적 문제입니다. 컨텍스트 소유자가 전체 대화를 제어할 수 있어야 하는가, 아니면 각 답글 작성자가 독립적으로 모더레이션할 수 있어야 하는가? 이런 질문들은 연합우주가 어떤 종류의 소셜 공간이 되어야 하는지에 대한 근본적인 고민과 연결됩니다.

2025년은 이러한 문제들에 대한 해결책들이 본격적으로 배포되고 테스트되는 해가 될 것으로 보입니다. 개발자들과 사용자들의 지속적인 관심과 참여를 통해, 연합우주가 더욱 풍부하고 연결된 소셜 네트워크로 발전해 나갈 수 있을 것입니다.

중요한 것은 완벽함보다는 개선입니다. 현재의 “조용한 연합우주” 문제가 완전히 해결되지는 않더라도, 이런 노력들을 통해 사용자들이 더 완전한 대화를 경험할 수 있게 된다면 그것만으로도 의미 있는 진전이라고 할 수 있습니다.

Fediverse Enhancement Proposal의 약자로, 연합우주의 개선사항을 제안하고 논의하기 위한 공식적인 문서 체계입니다. 새로운 기능이나 프로토콜 확장을 표준화하는 과정에서 사용됩니다. ↩︎

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

Note

원글의 구조와 핵심 아이디어를 바탕으로 하되, 기술적 개념 설명을 보강하고 실제 구현 사례를 추가했습니다. AI의 도움을 받아 작성되었습니다.

원작자 @julian 씨와 활발한 논의에 참여해주신 연합우주 개발자 커뮤니티에 감사드립니다.

문제의 근본 원인: ActivityPub의 분산 특성

ActivityPub이란?

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Create",
  "id": "https://alice.example/activities/create-reply-123",
  "actor": "https://alice.example/users/alice",
  "published": "2025-06-09T10:30:00Z",
  "to": ["https://bob.example/users/bob"],
  "object": {
    "type": "Note",
    "id": "https://alice.example/notes/reply-123",
    "content": "정말 흥미로운 관점이네요!",
    "inReplyTo": "https://bob.example/posts/original-post",
    "attributedTo": "https://alice.example/users/alice"
  }
}

분산의 딜레마

Alice의 원글
├── Bob의 댓글
│   └── Charlie의 댓글
└── Dave의 댓글

해결책을 위한 기반 개념: `context` 속성

실제 `context` 값의 형태들

1. 단순 식별자

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "첫 번째 댓글입니다",
  "context": "https://example.com/conversations/abc123"
}

2. Mastodon 스타일 (`ostatus:conversation`)

Mastodon은 ActivityPub 표준의 context와 함께 OStatus 시절부터 사용해온 conversation 속성을 병행 사용합니다.

{
  "@context": [
    "https://www.w3.org/ns/activitystreams",
    {
      "ostatus": "http://ostatus.org#",
      "conversation": "ostatus:conversation"
    }
  ],
  "type": "Note",
  "content": "이것은 답글입니다",
  "context": "https://mastodon.social/contexts/abc123",
  "conversation": "tag:mastodon.social,2025:objectId=12345:objectType=Conversation"
}

3. 해석 가능한 컬렉션 URL (FEP 7888 방식)

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "스레드 대화의 일부입니다",
  "context": "https://forum.example/topics/technology/thread-42",
  "inReplyTo": "https://forum.example/posts/789"
}

첫 번째 접근법: 답글 트리 크롤링 (reply tree crawling)

개요와 역사

답글 트리 크롤링 방식은 Mastodon의 @jonny 씨가 개척한 방법입니다. 2024년 4월 15일 처음 제안되어 2025년 3월 12일 Mastodon 코어에 병합되었습니다.

기술적 작동 원리

1. 필요한 전제 조건

{
  "id": "https://alice.example/posts/1",
  "type": "Note",
  "content": "어떻게 생각하세요?",
  "replies": {
    "type": "OrderedCollection",
    "id": "https://alice.example/posts/1/replies",
    "totalItems": 3,
    "first": "https://alice.example/posts/1/replies?page=1"
  }
}

2. 크롤링 알고리즘

async function crawlReplyTree(postUrl: URL): Promise<Note[]> {
  const post = await fetchNote(postUrl);
  const allReplies: Note[] = [];
  
  const replies = await post.getReplies();
  if (replies) {
    for await (const reply of replies.getItems()) {
      if (reply instanceof Note) {
        allReplies.push(reply);
        const subReplies = await crawlReplyTree(reply.id!);
        allReplies.push(...subReplies);
      }
    }
  }
  
  return allReplies;
}

이 방식의 핵심은 각 노드(게시물)가 자신에게 달린 답글들의 목록을 정확히 제공한다는 가정에 기반한다는 점입니다.

3. Mastodon의 실제 구현

장점

범용성: inReplyTo와 replies 속성은 거의 모든 ActivityPub 구현에서 보편적으로 사용됩니다. 따라서 기존 인프라를 크게 변경하지 않고도 적용할 수 있습니다.
구현 간 일관성: 대부분의 ActivityPub 구현체에서 이 속성들의 사용법이 크게 다르지 않습니다.
완전한 트리 구성: 이상적인 경우 모든 브랜치와 리프를 포함한 완전한 대화 트리를 얻을 수 있습니다.

단점

네트워크 취약성: 답글 트리의 단일 노드가 일시적 또는 영구적으로 접근 불가능하면, 해당 노드에서 파생되는 모든 브랜치들도 접근할 수 없게 됩니다.
선형적 작업량 증가: CPU 시간, 네트워크 요청 등의 작업량이 답글 트리 크기에 비례하여 선형적으로 증가합니다. 대규모 토론에서는 성능 문제가 발생할 수 있습니다.
재크롤링 필요성: 새로운 브랜치 발견을 위해서는 전체 답글 트리를 다시 크롤링해야 합니다. 빠르게 성장하는 토론에서는 크롤링 시작 시점에 따라 완전한 트리를 얻지 못할 수 있습니다.
불완전한 구현 현실: 현실적으로 모든 ActivityPub 구현체가 replies 컬렉션을 제공하지는 않습니다. Mastodon은 성능상 이유로 같은 서버의 답글만 최대 5개까지 replies 컬렉션에 포함하며, 많은 소규모 구현체들은 성능상 이유로 이를 생략하거나 불완전하게 구현합니다.

현재 구현 현황

현재 Mastodon이 이 방식의 유일한 완전한 구현체입니다. 하지만 이 방식은 Mastodon 고유의 것이 아니며, 다른 구현체들도 채택할 수 있습니다.

두 번째 접근법: 컨텍스트 소유자 기반 방식 (context owner approach)

개요와 배경

기술적 작동 원리

1. 컨텍스트 소유자의 역할

컨텍스트 소유자는 자신이 관리하는 대화의 모든 멤버를 포함하는 OrderedCollection을 제공합니다.

{
  "@context": [
    "https://www.w3.org/ns/activitystreams",
    "https://w3id.org/fep/171b"
  ],
  "type": "OrderedCollection",
  "id": "https://alice.example/conversations/tech-discussion",
  "attributedTo": "https://alice.example/users/alice",
  "collectionOf": "Activity",
  "totalItems": 15,
  "orderedItems": [
    "https://alice.example/activities/add/1",
    "https://alice.example/activities/add/2",
    "https://alice.example/activities/add/3"
  ]
}

2. 두 단계 액티비티 프로세스

이 방식에서는 댓글 추가가 반드시 두 단계로 이루어져야 합니다. 왜 이렇게 복잡하게 해야 할까요?

1단계: 답글 작성자가 일반적인 Create(Note) 액티비티 전송

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Create",
  "actor": "https://bob.example/users/bob",
  "published": "2025-06-09T11:00:00Z",
  "to": ["https://alice.example/users/alice"],
  "object": {
    "type": "Note",
    "id": "https://bob.example/notes/reply-456",
    "content": "정말 좋은 지적이군요!",
    "inReplyTo": "https://alice.example/posts/original",
    "context": "https://alice.example/conversations/tech-discussion"
  }
}

2단계: 컨텍스트 소유자(Alice)가 Add(Note) 액티비티 생성

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Add",
  "actor": "https://alice.example/users/alice",
  "published": "2025-06-09T11:05:00Z",
  "object": "https://bob.example/notes/reply-456",
  "target": {
    "type": "OrderedCollection",
    "id": "https://alice.example/conversations/tech-discussion",
    "attributedTo": "https://alice.example/users/alice"
  },
  "to": ["https://www.w3.org/ns/activitystreams#Public"]
}

3. 백필 메커니즘

개별 구현체들은 컨텍스트 소유자에게 전체 대화 내용을 요청할 수 있습니다.

async function performContextBackfill(contextUrl: URL): Promise<Note[]> {
  const collection = await fetchCollection(contextUrl);
  const notes: Note[] = [];
  
  for await (const item of collection.getItems()) {
    if (item instanceof Add) {
      const note = await item.getObject();
      if (note instanceof Note) {
        notes.push(note);
      }
    }
  }
  
  return notes;
}

장점

의사 중앙화(pseudo-centralization)의 이점: 컨텍스트 소유자가 제공하는 “단일 진실의 원천”(single source of truth)을 통해 일관된 대화 상태를 유지할 수 있습니다.
효율적인 네트워크 사용: 컨텍스트 소유자에게 한 번의 요청으로 전체 대화를 가져올 수 있어, 답글 트리 크롤링보다 네트워크 효율성이 높습니다.
중간 노드 장애 극복: 답글 트리 크롤링과 달리, 중간 노드가 다운되어도 컨텍스트 소유자를 통해 전체 대화에 접근할 수 있습니다.
효율적인 중복 제거: 컨텍스트 레벨에서 오브젝트 중복 제거가 가능하여 전체 네트워크 요청 수와 CPU 시간을 줄일 수 있습니다.
동기화 최적화: ID 해시섬을 통한 동기화 방법으로 네트워크 호출을 더욱 줄일 수 있습니다.

단점

컨텍스트 소유자 의존성: 가장 큰 약점은 컨텍스트 소유자에 대한 의존성입니다. 컨텍스트 소유자 서버에 접근할 수 없으면 전체 대화 백필이 불가능해집니다.
제한된 가시성: 컨텍스트 소유자는 자신이 알고 있는 오브젝트/액티비티만 응답할 수 있습니다.
상위 전파 누락 문제: 핵심적인 한계로, 루트로 다시 상위 전파되지 않는 하위 브랜치들은 컨텍스트 소유자가 알 수 없습니다.
구현체 지원 필요: 컨텍스트 소유자가 이 방식을 지원해야만 작동하므로, 다른 백필 전략과 결합해야 합니다.

현재 구현 현황

NodeBB, Discourse, WordPress, Frequency, Mitra, Streams가 현재 이 방식을 구현하고 있으며, Lemmy와 Piefed가 관심을 표명하고 있습니다.

중요한 논쟁 포인트들

1. 모더레이션 패러다임의 충돌

관련 NodeBB 스레드에서 @silverpill 씨가 제기한 핵심적인 문제점입니다.

두 접근 방식이 서로 충돌하지 않는다고 했지만, 이 ‘스레딩 패러다임’들은 모더레이션 문제에 대해 서로 다른 해결책을 제시합니다.

I don't fully agree with this statement, because these ‘threading paradigms’ suggest two different solutions to the problem of moderation.

컨텍스트 소유자 방식의 모더레이션

Alice가 스팸 댓글에 대해 Add(Note) 액티비티를 생성하지 않으면, 해당 댓글은 대화에서 제외됩니다.

답글 트리 크롤링의 모더레이션

각 답글이 독립적이며, 작성자들이 직접 답글만 모더레이션할 수 있습니다. 원글 작성자가 전체 대화를 제어할 수 없습니다.

2. 상위 전파 누락 문제의 해결책

어드레싱 규칙 활용 (FEP-171b)

FEP-171b에서는 “답글의 audience는 대화 루트에서 복사되어야 한다”(The audience of a reply MUST be copied from a conversation root)는 규칙을 제시합니다.

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Create",
  "actor": "https://charlie.example/users/charlie",
  "object": {
    "type": "Note",
    "content": "Bob의 댓글에 대한 답글",
    "inReplyTo": "https://bob.example/comments/2",
    "context": "https://alice.example/conversations/1",
    "to": [
      "https://bob.example/users/bob",
      "https://alice.example/users/alice"
    ]
  }
}

하이브리드 백필 메커니즘

많은 구현체가 여러 방식을 조합하는 방식을 채택합니다.

async function hybridBackfill(conversationId: URL): Promise<Note[]> {
  const strategies = [
    () => contextOwnerBackfill(conversationId),
    () => replyTreeCrawling(conversationId),
    () => mentionBasedDiscovery(conversationId)
  ];
  
  for (const strategy of strategies) {
    try {
      const result = await strategy();
      if (result.length > 0) return result;
    } catch (error) {
      console.warn('Strategy failed, trying next:', error);
    }
  }
  
  return [];
}

추가적인 백필 메커니즘들

주기적 크롤링 백필: 이 방식은 마치 정기적인 건강검진과 같습니다. 시스템이 정해진 주기마다 활발한 대화들을 점검하여 누락된 답글이 있는지 확인합니다.
사용자 트리거 백필: 사용자가 특정 대화 페이지에 접속하면, 시스템은 즉시 현재 보유한 컨텍스트 컬렉션을 검토하고 실시간으로 누락된 답글들을 탐색합니다.

멘션 기반 백필: 사용자들이 대화에서 다른 사람을 멘션하는 자연스러운 행동을 통해 누락된 답글 체인을 발견하는 메커니즘입니다.

async function onMentionReceived(activity: Create): Promise<void> {
  const mention = await activity.getObject();

  if (mention.context && mention.replyTargetId) {
    const missingChain = await traceReplyChain(await mention.getReplyTarget());
    await addToContext(mention.context, missingChain);
  }
}

실제 도전과제들

순환 참조 방지: 백필 과정에서 무한 루프에 빠지는 것을 방지하는 것은 매우 중요합니다. 실제 구현에서는 방문한 URL을 추적하고, 최대 탐색 깊이를 제한하는 안전장치를 마련합니다.
성능 최적화: 대규모 대화에서는 수백 개의 답글이 달릴 수 있고, 이를 모두 한 번에 처리하려고 하면 서버에 과도한 부하가 걸릴 수 있습니다. 일괄 처리(batch processing)는 여러 대화를 동시에 처리할 때 작은 그룹으로 나누어 순차적으로 처리하고 각 배치 사이에 짧은 휴식 시간을 두는 방식입니다.
오류 처리 및 복구: 분산 네트워크 환경에서는 다양한 종류의 오류가 발생할 수 있습니다. 실제 구현에서는 여러 백필 전략을 순차적으로 시도하는 복원력 있는 접근법을 사용합니다.

표준화 노력과 미래 전망

FEP 수렴 논의

현재 연합우주 커뮤니티에서는 FEP 수렴 스레드를 통해 여러 FEP들을 통합하려는 노력이 진행되고 있습니다.

구현체 간 협력

NodeBB와 Discourse의 협력 사례

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "context": "https://community.nodebb.org/topic/18844",
  "audience": "https://community.nodebb.org/category/development",
  "tag": [
    {
      "type": "Link",
      "href": "https://meta.discourse.org/t/activitypub-support/12345",
      "rel": "related"
    }
  ]
}

Mastodon과의 호환성 고려

{
  "@context": [
    "https://www.w3.org/ns/activitystreams",
    {
      "ostatus": "http://ostatus.org#",
      "conversation": "ostatus:conversation"
    }
  ],
  "type": "Note",
  "content": "Mastodon 호환 답글",
  "context": "https://mastodon.social/contexts/abc123",
  "conversation": "tag:mastodon.social,2025:objectId=12345:objectType=Conversation"
}

이런 하위 호환성 유지는 연합우주 생태계의 분열을 방지하고 사용자 경험을 개선하는 데 중요한 역할을 합니다.

향후 개발 방향: 하이브리드 접근법의 표준화

모범 사례 가이드라인

다중 전략 구현: 절대로 하나의 백필 방식에만 의존하지 마세요. 연합우주의 다양성과 불확실성을 고려할 때, 여러 전략을 조합하는 것이 필수적입니다. 각 전략은 서로 다른 상황에서 강점을 보이므로, 상황에 따라 적절한 전략을 선택할 수 있는 유연성을 확보해야 합니다.

예를 들어, 활발한 포럼 토론에서는 컨텍스트 소유자 방식이 효과적일 수 있지만, Mastodon의 일반적인 대화에서는 답글 트리 크롤링이 더 적합할 수 있습니다.
리소스 관리: 백필 작업은 상당한 서버 리소스를 소모할 수 있습니다. 특히 인기 있는 대화나 대규모 토론의 경우 수백 개의 네트워크 요청이 필요할 수 있습니다. 따라서 적절한 제한과 조절 메커니즘을 구현해야 합니다.
모니터링 및 로깅: 백필 시스템의 성능과 신뢰성을 지속적으로 모니터링하는 것이 중요합니다. 어떤 방식이 가장 효과적인지, 어떤 종류의 오류가 자주 발생하는지 등을 추적해야 합니다.

결론

핵심 통찰

앞으로의 방향

연합우주의 대화 백필 문제는 단순히 기술적인 문제를 넘어서 분산형 네트워크에서의 거버넌스, 모더레이션, 사용자 경험의 복합적인 문제입니다.

Fediverse Enhancement Proposal의 약자로, 연합우주의 개선사항을 제안하고 논의하기 위한 공식적인 문서 체계입니다. 새로운 기능이나 프로토콜 확장을 표준화하는 과정에서 사용됩니다. ↩︎

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

Note

원글의 구조와 핵심 아이디어를 바탕으로 하되, 기술적 개념 설명을 보강하고 실제 구현 사례를 추가했습니다. AI의 도움을 받아 작성되었습니다.

원작자 @julian 씨와 활발한 논의에 참여해주신 연합우주 개발자 커뮤니티에 감사드립니다.

문제의 근본 원인: ActivityPub의 분산 특성

ActivityPub이란?

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Create",
  "id": "https://alice.example/activities/create-reply-123",
  "actor": "https://alice.example/users/alice",
  "published": "2025-06-09T10:30:00Z",
  "to": ["https://bob.example/users/bob"],
  "object": {
    "type": "Note",
    "id": "https://alice.example/notes/reply-123",
    "content": "정말 흥미로운 관점이네요!",
    "inReplyTo": "https://bob.example/posts/original-post",
    "attributedTo": "https://alice.example/users/alice"
  }
}

분산의 딜레마

Alice의 원글
├── Bob의 댓글
│   └── Charlie의 댓글
└── Dave의 댓글

해결책을 위한 기반 개념: `context` 속성

실제 `context` 값의 형태들

1. 단순 식별자

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "첫 번째 댓글입니다",
  "context": "https://example.com/conversations/abc123"
}

2. Mastodon 스타일 (`ostatus:conversation`)

Mastodon은 ActivityPub 표준의 context와 함께 OStatus 시절부터 사용해온 conversation 속성을 병행 사용합니다.

{
  "@context": [
    "https://www.w3.org/ns/activitystreams",
    {
      "ostatus": "http://ostatus.org#",
      "conversation": "ostatus:conversation"
    }
  ],
  "type": "Note",
  "content": "이것은 답글입니다",
  "context": "https://mastodon.social/contexts/abc123",
  "conversation": "tag:mastodon.social,2025:objectId=12345:objectType=Conversation"
}

3. 해석 가능한 컬렉션 URL (FEP 7888 방식)

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "스레드 대화의 일부입니다",
  "context": "https://forum.example/topics/technology/thread-42",
  "inReplyTo": "https://forum.example/posts/789"
}

첫 번째 접근법: 답글 트리 크롤링 (reply tree crawling)

개요와 역사

답글 트리 크롤링 방식은 Mastodon의 @jonny 씨가 개척한 방법입니다. 2024년 4월 15일 처음 제안되어 2025년 3월 12일 Mastodon 코어에 병합되었습니다.

기술적 작동 원리

1. 필요한 전제 조건

{
  "id": "https://alice.example/posts/1",
  "type": "Note",
  "content": "어떻게 생각하세요?",
  "replies": {
    "type": "OrderedCollection",
    "id": "https://alice.example/posts/1/replies",
    "totalItems": 3,
    "first": "https://alice.example/posts/1/replies?page=1"
  }
}

2. 크롤링 알고리즘

async function crawlReplyTree(postUrl: URL): Promise<Note[]> {
  const post = await fetchNote(postUrl);
  const allReplies: Note[] = [];
  
  const replies = await post.getReplies();
  if (replies) {
    for await (const reply of replies.getItems()) {
      if (reply instanceof Note) {
        allReplies.push(reply);
        const subReplies = await crawlReplyTree(reply.id!);
        allReplies.push(...subReplies);
      }
    }
  }
  
  return allReplies;
}

이 방식의 핵심은 각 노드(게시물)가 자신에게 달린 답글들의 목록을 정확히 제공한다는 가정에 기반한다는 점입니다.

3. Mastodon의 실제 구현

장점

범용성: inReplyTo와 replies 속성은 거의 모든 ActivityPub 구현에서 보편적으로 사용됩니다. 따라서 기존 인프라를 크게 변경하지 않고도 적용할 수 있습니다.
구현 간 일관성: 대부분의 ActivityPub 구현체에서 이 속성들의 사용법이 크게 다르지 않습니다.
완전한 트리 구성: 이상적인 경우 모든 브랜치와 리프를 포함한 완전한 대화 트리를 얻을 수 있습니다.

단점

네트워크 취약성: 답글 트리의 단일 노드가 일시적 또는 영구적으로 접근 불가능하면, 해당 노드에서 파생되는 모든 브랜치들도 접근할 수 없게 됩니다.
선형적 작업량 증가: CPU 시간, 네트워크 요청 등의 작업량이 답글 트리 크기에 비례하여 선형적으로 증가합니다. 대규모 토론에서는 성능 문제가 발생할 수 있습니다.
재크롤링 필요성: 새로운 브랜치 발견을 위해서는 전체 답글 트리를 다시 크롤링해야 합니다. 빠르게 성장하는 토론에서는 크롤링 시작 시점에 따라 완전한 트리를 얻지 못할 수 있습니다.
불완전한 구현 현실: 현실적으로 모든 ActivityPub 구현체가 replies 컬렉션을 제공하지는 않습니다. Mastodon은 성능상 이유로 같은 서버의 답글만 최대 5개까지 replies 컬렉션에 포함하며, 많은 소규모 구현체들은 성능상 이유로 이를 생략하거나 불완전하게 구현합니다.

현재 구현 현황

현재 Mastodon이 이 방식의 유일한 완전한 구현체입니다. 하지만 이 방식은 Mastodon 고유의 것이 아니며, 다른 구현체들도 채택할 수 있습니다.

두 번째 접근법: 컨텍스트 소유자 기반 방식 (context owner approach)

개요와 배경

기술적 작동 원리

1. 컨텍스트 소유자의 역할

컨텍스트 소유자는 자신이 관리하는 대화의 모든 멤버를 포함하는 OrderedCollection을 제공합니다.

{
  "@context": [
    "https://www.w3.org/ns/activitystreams",
    "https://w3id.org/fep/171b"
  ],
  "type": "OrderedCollection",
  "id": "https://alice.example/conversations/tech-discussion",
  "attributedTo": "https://alice.example/users/alice",
  "collectionOf": "Activity",
  "totalItems": 15,
  "orderedItems": [
    "https://alice.example/activities/add/1",
    "https://alice.example/activities/add/2",
    "https://alice.example/activities/add/3"
  ]
}

2. 두 단계 액티비티 프로세스

이 방식에서는 댓글 추가가 반드시 두 단계로 이루어져야 합니다. 왜 이렇게 복잡하게 해야 할까요?

1단계: 답글 작성자가 일반적인 Create(Note) 액티비티 전송

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Create",
  "actor": "https://bob.example/users/bob",
  "published": "2025-06-09T11:00:00Z",
  "to": ["https://alice.example/users/alice"],
  "object": {
    "type": "Note",
    "id": "https://bob.example/notes/reply-456",
    "content": "정말 좋은 지적이군요!",
    "inReplyTo": "https://alice.example/posts/original",
    "context": "https://alice.example/conversations/tech-discussion"
  }
}

2단계: 컨텍스트 소유자(Alice)가 Add(Note) 액티비티 생성

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Add",
  "actor": "https://alice.example/users/alice",
  "published": "2025-06-09T11:05:00Z",
  "object": "https://bob.example/notes/reply-456",
  "target": {
    "type": "OrderedCollection",
    "id": "https://alice.example/conversations/tech-discussion",
    "attributedTo": "https://alice.example/users/alice"
  },
  "to": ["https://www.w3.org/ns/activitystreams#Public"]
}

3. 백필 메커니즘

개별 구현체들은 컨텍스트 소유자에게 전체 대화 내용을 요청할 수 있습니다.

async function performContextBackfill(contextUrl: URL): Promise<Note[]> {
  const collection = await fetchCollection(contextUrl);
  const notes: Note[] = [];
  
  for await (const item of collection.getItems()) {
    if (item instanceof Add) {
      const note = await item.getObject();
      if (note instanceof Note) {
        notes.push(note);
      }
    }
  }
  
  return notes;
}

장점

의사 중앙화(pseudo-centralization)의 이점: 컨텍스트 소유자가 제공하는 “단일 진실의 원천”(single source of truth)을 통해 일관된 대화 상태를 유지할 수 있습니다.
효율적인 네트워크 사용: 컨텍스트 소유자에게 한 번의 요청으로 전체 대화를 가져올 수 있어, 답글 트리 크롤링보다 네트워크 효율성이 높습니다.
중간 노드 장애 극복: 답글 트리 크롤링과 달리, 중간 노드가 다운되어도 컨텍스트 소유자를 통해 전체 대화에 접근할 수 있습니다.
효율적인 중복 제거: 컨텍스트 레벨에서 오브젝트 중복 제거가 가능하여 전체 네트워크 요청 수와 CPU 시간을 줄일 수 있습니다.
동기화 최적화: ID 해시섬을 통한 동기화 방법으로 네트워크 호출을 더욱 줄일 수 있습니다.

단점

컨텍스트 소유자 의존성: 가장 큰 약점은 컨텍스트 소유자에 대한 의존성입니다. 컨텍스트 소유자 서버에 접근할 수 없으면 전체 대화 백필이 불가능해집니다.
제한된 가시성: 컨텍스트 소유자는 자신이 알고 있는 오브젝트/액티비티만 응답할 수 있습니다.
상위 전파 누락 문제: 핵심적인 한계로, 루트로 다시 상위 전파되지 않는 하위 브랜치들은 컨텍스트 소유자가 알 수 없습니다.
구현체 지원 필요: 컨텍스트 소유자가 이 방식을 지원해야만 작동하므로, 다른 백필 전략과 결합해야 합니다.

현재 구현 현황

NodeBB, Discourse, WordPress, Frequency, Mitra, Streams가 현재 이 방식을 구현하고 있으며, Lemmy와 Piefed가 관심을 표명하고 있습니다.

중요한 논쟁 포인트들

1. 모더레이션 패러다임의 충돌

관련 NodeBB 스레드에서 @silverpill 씨가 제기한 핵심적인 문제점입니다.

두 접근 방식이 서로 충돌하지 않는다고 했지만, 이 ‘스레딩 패러다임’들은 모더레이션 문제에 대해 서로 다른 해결책을 제시합니다.

I don't fully agree with this statement, because these ‘threading paradigms’ suggest two different solutions to the problem of moderation.

컨텍스트 소유자 방식의 모더레이션

Alice가 스팸 댓글에 대해 Add(Note) 액티비티를 생성하지 않으면, 해당 댓글은 대화에서 제외됩니다.

답글 트리 크롤링의 모더레이션

각 답글이 독립적이며, 작성자들이 직접 답글만 모더레이션할 수 있습니다. 원글 작성자가 전체 대화를 제어할 수 없습니다.

2. 상위 전파 누락 문제의 해결책

어드레싱 규칙 활용 (FEP-171b)

FEP-171b에서는 “답글의 audience는 대화 루트에서 복사되어야 한다”(The audience of a reply MUST be copied from a conversation root)는 규칙을 제시합니다.

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Create",
  "actor": "https://charlie.example/users/charlie",
  "object": {
    "type": "Note",
    "content": "Bob의 댓글에 대한 답글",
    "inReplyTo": "https://bob.example/comments/2",
    "context": "https://alice.example/conversations/1",
    "to": [
      "https://bob.example/users/bob",
      "https://alice.example/users/alice"
    ]
  }
}

하이브리드 백필 메커니즘

많은 구현체가 여러 방식을 조합하는 방식을 채택합니다.

async function hybridBackfill(conversationId: URL): Promise<Note[]> {
  const strategies = [
    () => contextOwnerBackfill(conversationId),
    () => replyTreeCrawling(conversationId),
    () => mentionBasedDiscovery(conversationId)
  ];
  
  for (const strategy of strategies) {
    try {
      const result = await strategy();
      if (result.length > 0) return result;
    } catch (error) {
      console.warn('Strategy failed, trying next:', error);
    }
  }
  
  return [];
}

추가적인 백필 메커니즘들

주기적 크롤링 백필: 이 방식은 마치 정기적인 건강검진과 같습니다. 시스템이 정해진 주기마다 활발한 대화들을 점검하여 누락된 답글이 있는지 확인합니다.
사용자 트리거 백필: 사용자가 특정 대화 페이지에 접속하면, 시스템은 즉시 현재 보유한 컨텍스트 컬렉션을 검토하고 실시간으로 누락된 답글들을 탐색합니다.

멘션 기반 백필: 사용자들이 대화에서 다른 사람을 멘션하는 자연스러운 행동을 통해 누락된 답글 체인을 발견하는 메커니즘입니다.

async function onMentionReceived(activity: Create): Promise<void> {
  const mention = await activity.getObject();

  if (mention.context && mention.replyTargetId) {
    const missingChain = await traceReplyChain(await mention.getReplyTarget());
    await addToContext(mention.context, missingChain);
  }
}

실제 도전과제들

순환 참조 방지: 백필 과정에서 무한 루프에 빠지는 것을 방지하는 것은 매우 중요합니다. 실제 구현에서는 방문한 URL을 추적하고, 최대 탐색 깊이를 제한하는 안전장치를 마련합니다.
성능 최적화: 대규모 대화에서는 수백 개의 답글이 달릴 수 있고, 이를 모두 한 번에 처리하려고 하면 서버에 과도한 부하가 걸릴 수 있습니다. 일괄 처리(batch processing)는 여러 대화를 동시에 처리할 때 작은 그룹으로 나누어 순차적으로 처리하고 각 배치 사이에 짧은 휴식 시간을 두는 방식입니다.
오류 처리 및 복구: 분산 네트워크 환경에서는 다양한 종류의 오류가 발생할 수 있습니다. 실제 구현에서는 여러 백필 전략을 순차적으로 시도하는 복원력 있는 접근법을 사용합니다.

표준화 노력과 미래 전망

FEP 수렴 논의

현재 연합우주 커뮤니티에서는 FEP 수렴 스레드를 통해 여러 FEP들을 통합하려는 노력이 진행되고 있습니다.

구현체 간 협력

NodeBB와 Discourse의 협력 사례

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "context": "https://community.nodebb.org/topic/18844",
  "audience": "https://community.nodebb.org/category/development",
  "tag": [
    {
      "type": "Link",
      "href": "https://meta.discourse.org/t/activitypub-support/12345",
      "rel": "related"
    }
  ]
}

Mastodon과의 호환성 고려

{
  "@context": [
    "https://www.w3.org/ns/activitystreams",
    {
      "ostatus": "http://ostatus.org#",
      "conversation": "ostatus:conversation"
    }
  ],
  "type": "Note",
  "content": "Mastodon 호환 답글",
  "context": "https://mastodon.social/contexts/abc123",
  "conversation": "tag:mastodon.social,2025:objectId=12345:objectType=Conversation"
}

이런 하위 호환성 유지는 연합우주 생태계의 분열을 방지하고 사용자 경험을 개선하는 데 중요한 역할을 합니다.

향후 개발 방향: 하이브리드 접근법의 표준화

모범 사례 가이드라인

다중 전략 구현: 절대로 하나의 백필 방식에만 의존하지 마세요. 연합우주의 다양성과 불확실성을 고려할 때, 여러 전략을 조합하는 것이 필수적입니다. 각 전략은 서로 다른 상황에서 강점을 보이므로, 상황에 따라 적절한 전략을 선택할 수 있는 유연성을 확보해야 합니다.

예를 들어, 활발한 포럼 토론에서는 컨텍스트 소유자 방식이 효과적일 수 있지만, Mastodon의 일반적인 대화에서는 답글 트리 크롤링이 더 적합할 수 있습니다.
리소스 관리: 백필 작업은 상당한 서버 리소스를 소모할 수 있습니다. 특히 인기 있는 대화나 대규모 토론의 경우 수백 개의 네트워크 요청이 필요할 수 있습니다. 따라서 적절한 제한과 조절 메커니즘을 구현해야 합니다.
모니터링 및 로깅: 백필 시스템의 성능과 신뢰성을 지속적으로 모니터링하는 것이 중요합니다. 어떤 방식이 가장 효과적인지, 어떤 종류의 오류가 자주 발생하는지 등을 추적해야 합니다.

결론

핵심 통찰

앞으로의 방향

연합우주의 대화 백필 문제는 단순히 기술적인 문제를 넘어서 분산형 네트워크에서의 거버넌스, 모더레이션, 사용자 경험의 복합적인 문제입니다.

Fediverse Enhancement Proposal의 약자로, 연합우주의 개선사항을 제안하고 논의하기 위한 공식적인 문서 체계입니다. 새로운 기능이나 프로토콜 확장을 표준화하는 과정에서 사용됩니다. ↩︎

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

Note

원글의 구조와 핵심 아이디어를 바탕으로 하되, 기술적 개념 설명을 보강하고 실제 구현 사례를 추가했습니다. AI의 도움을 받아 작성되었습니다.

원작자 @julian 씨와 활발한 논의에 참여해주신 연합우주 개발자 커뮤니티에 감사드립니다.

문제의 근본 원인: ActivityPub의 분산 특성

ActivityPub이란?

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Create",
  "id": "https://alice.example/activities/create-reply-123",
  "actor": "https://alice.example/users/alice",
  "published": "2025-06-09T10:30:00Z",
  "to": ["https://bob.example/users/bob"],
  "object": {
    "type": "Note",
    "id": "https://alice.example/notes/reply-123",
    "content": "정말 흥미로운 관점이네요!",
    "inReplyTo": "https://bob.example/posts/original-post",
    "attributedTo": "https://alice.example/users/alice"
  }
}

분산의 딜레마

Alice의 원글
├── Bob의 댓글
│   └── Charlie의 댓글
└── Dave의 댓글

해결책을 위한 기반 개념: `context` 속성

실제 `context` 값의 형태들

1. 단순 식별자

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "첫 번째 댓글입니다",
  "context": "https://example.com/conversations/abc123"
}

2. Mastodon 스타일 (`ostatus:conversation`)

Mastodon은 ActivityPub 표준의 context와 함께 OStatus 시절부터 사용해온 conversation 속성을 병행 사용합니다.

{
  "@context": [
    "https://www.w3.org/ns/activitystreams",
    {
      "ostatus": "http://ostatus.org#",
      "conversation": "ostatus:conversation"
    }
  ],
  "type": "Note",
  "content": "이것은 답글입니다",
  "context": "https://mastodon.social/contexts/abc123",
  "conversation": "tag:mastodon.social,2025:objectId=12345:objectType=Conversation"
}

3. 해석 가능한 컬렉션 URL (FEP 7888 방식)

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "스레드 대화의 일부입니다",
  "context": "https://forum.example/topics/technology/thread-42",
  "inReplyTo": "https://forum.example/posts/789"
}

첫 번째 접근법: 답글 트리 크롤링 (reply tree crawling)

개요와 역사

답글 트리 크롤링 방식은 Mastodon의 @jonny 씨가 개척한 방법입니다. 2024년 4월 15일 처음 제안되어 2025년 3월 12일 Mastodon 코어에 병합되었습니다.

기술적 작동 원리

1. 필요한 전제 조건

{
  "id": "https://alice.example/posts/1",
  "type": "Note",
  "content": "어떻게 생각하세요?",
  "replies": {
    "type": "OrderedCollection",
    "id": "https://alice.example/posts/1/replies",
    "totalItems": 3,
    "first": "https://alice.example/posts/1/replies?page=1"
  }
}

2. 크롤링 알고리즘

async function crawlReplyTree(postUrl: URL): Promise<Note[]> {
  const post = await fetchNote(postUrl);
  const allReplies: Note[] = [];
  
  const replies = await post.getReplies();
  if (replies) {
    for await (const reply of replies.getItems()) {
      if (reply instanceof Note) {
        allReplies.push(reply);
        const subReplies = await crawlReplyTree(reply.id!);
        allReplies.push(...subReplies);
      }
    }
  }
  
  return allReplies;
}

이 방식의 핵심은 각 노드(게시물)가 자신에게 달린 답글들의 목록을 정확히 제공한다는 가정에 기반한다는 점입니다.

3. Mastodon의 실제 구현

장점

범용성: inReplyTo와 replies 속성은 거의 모든 ActivityPub 구현에서 보편적으로 사용됩니다. 따라서 기존 인프라를 크게 변경하지 않고도 적용할 수 있습니다.
구현 간 일관성: 대부분의 ActivityPub 구현체에서 이 속성들의 사용법이 크게 다르지 않습니다.
완전한 트리 구성: 이상적인 경우 모든 브랜치와 리프를 포함한 완전한 대화 트리를 얻을 수 있습니다.

단점

네트워크 취약성: 답글 트리의 단일 노드가 일시적 또는 영구적으로 접근 불가능하면, 해당 노드에서 파생되는 모든 브랜치들도 접근할 수 없게 됩니다.
선형적 작업량 증가: CPU 시간, 네트워크 요청 등의 작업량이 답글 트리 크기에 비례하여 선형적으로 증가합니다. 대규모 토론에서는 성능 문제가 발생할 수 있습니다.
재크롤링 필요성: 새로운 브랜치 발견을 위해서는 전체 답글 트리를 다시 크롤링해야 합니다. 빠르게 성장하는 토론에서는 크롤링 시작 시점에 따라 완전한 트리를 얻지 못할 수 있습니다.
불완전한 구현 현실: 현실적으로 모든 ActivityPub 구현체가 replies 컬렉션을 제공하지는 않습니다. Mastodon은 성능상 이유로 같은 서버의 답글만 최대 5개까지 replies 컬렉션에 포함하며, 많은 소규모 구현체들은 성능상 이유로 이를 생략하거나 불완전하게 구현합니다.

현재 구현 현황

현재 Mastodon이 이 방식의 유일한 완전한 구현체입니다. 하지만 이 방식은 Mastodon 고유의 것이 아니며, 다른 구현체들도 채택할 수 있습니다.

두 번째 접근법: 컨텍스트 소유자 기반 방식 (context owner approach)

개요와 배경

기술적 작동 원리

1. 컨텍스트 소유자의 역할

컨텍스트 소유자는 자신이 관리하는 대화의 모든 멤버를 포함하는 OrderedCollection을 제공합니다.

{
  "@context": [
    "https://www.w3.org/ns/activitystreams",
    "https://w3id.org/fep/171b"
  ],
  "type": "OrderedCollection",
  "id": "https://alice.example/conversations/tech-discussion",
  "attributedTo": "https://alice.example/users/alice",
  "collectionOf": "Activity",
  "totalItems": 15,
  "orderedItems": [
    "https://alice.example/activities/add/1",
    "https://alice.example/activities/add/2",
    "https://alice.example/activities/add/3"
  ]
}

2. 두 단계 액티비티 프로세스

이 방식에서는 댓글 추가가 반드시 두 단계로 이루어져야 합니다. 왜 이렇게 복잡하게 해야 할까요?

1단계: 답글 작성자가 일반적인 Create(Note) 액티비티 전송

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Create",
  "actor": "https://bob.example/users/bob",
  "published": "2025-06-09T11:00:00Z",
  "to": ["https://alice.example/users/alice"],
  "object": {
    "type": "Note",
    "id": "https://bob.example/notes/reply-456",
    "content": "정말 좋은 지적이군요!",
    "inReplyTo": "https://alice.example/posts/original",
    "context": "https://alice.example/conversations/tech-discussion"
  }
}

2단계: 컨텍스트 소유자(Alice)가 Add(Note) 액티비티 생성

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Add",
  "actor": "https://alice.example/users/alice",
  "published": "2025-06-09T11:05:00Z",
  "object": "https://bob.example/notes/reply-456",
  "target": {
    "type": "OrderedCollection",
    "id": "https://alice.example/conversations/tech-discussion",
    "attributedTo": "https://alice.example/users/alice"
  },
  "to": ["https://www.w3.org/ns/activitystreams#Public"]
}

3. 백필 메커니즘

개별 구현체들은 컨텍스트 소유자에게 전체 대화 내용을 요청할 수 있습니다.

async function performContextBackfill(contextUrl: URL): Promise<Note[]> {
  const collection = await fetchCollection(contextUrl);
  const notes: Note[] = [];
  
  for await (const item of collection.getItems()) {
    if (item instanceof Add) {
      const note = await item.getObject();
      if (note instanceof Note) {
        notes.push(note);
      }
    }
  }
  
  return notes;
}

장점

의사 중앙화(pseudo-centralization)의 이점: 컨텍스트 소유자가 제공하는 “단일 진실의 원천”(single source of truth)을 통해 일관된 대화 상태를 유지할 수 있습니다.
효율적인 네트워크 사용: 컨텍스트 소유자에게 한 번의 요청으로 전체 대화를 가져올 수 있어, 답글 트리 크롤링보다 네트워크 효율성이 높습니다.
중간 노드 장애 극복: 답글 트리 크롤링과 달리, 중간 노드가 다운되어도 컨텍스트 소유자를 통해 전체 대화에 접근할 수 있습니다.
효율적인 중복 제거: 컨텍스트 레벨에서 오브젝트 중복 제거가 가능하여 전체 네트워크 요청 수와 CPU 시간을 줄일 수 있습니다.
동기화 최적화: ID 해시섬을 통한 동기화 방법으로 네트워크 호출을 더욱 줄일 수 있습니다.

단점

컨텍스트 소유자 의존성: 가장 큰 약점은 컨텍스트 소유자에 대한 의존성입니다. 컨텍스트 소유자 서버에 접근할 수 없으면 전체 대화 백필이 불가능해집니다.
제한된 가시성: 컨텍스트 소유자는 자신이 알고 있는 오브젝트/액티비티만 응답할 수 있습니다.
상위 전파 누락 문제: 핵심적인 한계로, 루트로 다시 상위 전파되지 않는 하위 브랜치들은 컨텍스트 소유자가 알 수 없습니다.
구현체 지원 필요: 컨텍스트 소유자가 이 방식을 지원해야만 작동하므로, 다른 백필 전략과 결합해야 합니다.

현재 구현 현황

NodeBB, Discourse, WordPress, Frequency, Mitra, Streams가 현재 이 방식을 구현하고 있으며, Lemmy와 Piefed가 관심을 표명하고 있습니다.

중요한 논쟁 포인트들

1. 모더레이션 패러다임의 충돌

관련 NodeBB 스레드에서 @silverpill 씨가 제기한 핵심적인 문제점입니다.

두 접근 방식이 서로 충돌하지 않는다고 했지만, 이 ‘스레딩 패러다임’들은 모더레이션 문제에 대해 서로 다른 해결책을 제시합니다.

I don't fully agree with this statement, because these ‘threading paradigms’ suggest two different solutions to the problem of moderation.

컨텍스트 소유자 방식의 모더레이션

Alice가 스팸 댓글에 대해 Add(Note) 액티비티를 생성하지 않으면, 해당 댓글은 대화에서 제외됩니다.

답글 트리 크롤링의 모더레이션

각 답글이 독립적이며, 작성자들이 직접 답글만 모더레이션할 수 있습니다. 원글 작성자가 전체 대화를 제어할 수 없습니다.

2. 상위 전파 누락 문제의 해결책

어드레싱 규칙 활용 (FEP-171b)

FEP-171b에서는 “답글의 audience는 대화 루트에서 복사되어야 한다”(The audience of a reply MUST be copied from a conversation root)는 규칙을 제시합니다.

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Create",
  "actor": "https://charlie.example/users/charlie",
  "object": {
    "type": "Note",
    "content": "Bob의 댓글에 대한 답글",
    "inReplyTo": "https://bob.example/comments/2",
    "context": "https://alice.example/conversations/1",
    "to": [
      "https://bob.example/users/bob",
      "https://alice.example/users/alice"
    ]
  }
}

하이브리드 백필 메커니즘

많은 구현체가 여러 방식을 조합하는 방식을 채택합니다.

async function hybridBackfill(conversationId: URL): Promise<Note[]> {
  const strategies = [
    () => contextOwnerBackfill(conversationId),
    () => replyTreeCrawling(conversationId),
    () => mentionBasedDiscovery(conversationId)
  ];
  
  for (const strategy of strategies) {
    try {
      const result = await strategy();
      if (result.length > 0) return result;
    } catch (error) {
      console.warn('Strategy failed, trying next:', error);
    }
  }
  
  return [];
}

추가적인 백필 메커니즘들

주기적 크롤링 백필: 이 방식은 마치 정기적인 건강검진과 같습니다. 시스템이 정해진 주기마다 활발한 대화들을 점검하여 누락된 답글이 있는지 확인합니다.
사용자 트리거 백필: 사용자가 특정 대화 페이지에 접속하면, 시스템은 즉시 현재 보유한 컨텍스트 컬렉션을 검토하고 실시간으로 누락된 답글들을 탐색합니다.

멘션 기반 백필: 사용자들이 대화에서 다른 사람을 멘션하는 자연스러운 행동을 통해 누락된 답글 체인을 발견하는 메커니즘입니다.

async function onMentionReceived(activity: Create): Promise<void> {
  const mention = await activity.getObject();

  if (mention.context && mention.replyTargetId) {
    const missingChain = await traceReplyChain(await mention.getReplyTarget());
    await addToContext(mention.context, missingChain);
  }
}

실제 도전과제들

순환 참조 방지: 백필 과정에서 무한 루프에 빠지는 것을 방지하는 것은 매우 중요합니다. 실제 구현에서는 방문한 URL을 추적하고, 최대 탐색 깊이를 제한하는 안전장치를 마련합니다.
성능 최적화: 대규모 대화에서는 수백 개의 답글이 달릴 수 있고, 이를 모두 한 번에 처리하려고 하면 서버에 과도한 부하가 걸릴 수 있습니다. 일괄 처리(batch processing)는 여러 대화를 동시에 처리할 때 작은 그룹으로 나누어 순차적으로 처리하고 각 배치 사이에 짧은 휴식 시간을 두는 방식입니다.
오류 처리 및 복구: 분산 네트워크 환경에서는 다양한 종류의 오류가 발생할 수 있습니다. 실제 구현에서는 여러 백필 전략을 순차적으로 시도하는 복원력 있는 접근법을 사용합니다.

표준화 노력과 미래 전망

FEP 수렴 논의

현재 연합우주 커뮤니티에서는 FEP 수렴 스레드를 통해 여러 FEP들을 통합하려는 노력이 진행되고 있습니다.

구현체 간 협력

NodeBB와 Discourse의 협력 사례

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "context": "https://community.nodebb.org/topic/18844",
  "audience": "https://community.nodebb.org/category/development",
  "tag": [
    {
      "type": "Link",
      "href": "https://meta.discourse.org/t/activitypub-support/12345",
      "rel": "related"
    }
  ]
}

Mastodon과의 호환성 고려

{
  "@context": [
    "https://www.w3.org/ns/activitystreams",
    {
      "ostatus": "http://ostatus.org#",
      "conversation": "ostatus:conversation"
    }
  ],
  "type": "Note",
  "content": "Mastodon 호환 답글",
  "context": "https://mastodon.social/contexts/abc123",
  "conversation": "tag:mastodon.social,2025:objectId=12345:objectType=Conversation"
}

이런 하위 호환성 유지는 연합우주 생태계의 분열을 방지하고 사용자 경험을 개선하는 데 중요한 역할을 합니다.

향후 개발 방향: 하이브리드 접근법의 표준화

모범 사례 가이드라인

다중 전략 구현: 절대로 하나의 백필 방식에만 의존하지 마세요. 연합우주의 다양성과 불확실성을 고려할 때, 여러 전략을 조합하는 것이 필수적입니다. 각 전략은 서로 다른 상황에서 강점을 보이므로, 상황에 따라 적절한 전략을 선택할 수 있는 유연성을 확보해야 합니다.

예를 들어, 활발한 포럼 토론에서는 컨텍스트 소유자 방식이 효과적일 수 있지만, Mastodon의 일반적인 대화에서는 답글 트리 크롤링이 더 적합할 수 있습니다.
리소스 관리: 백필 작업은 상당한 서버 리소스를 소모할 수 있습니다. 특히 인기 있는 대화나 대규모 토론의 경우 수백 개의 네트워크 요청이 필요할 수 있습니다. 따라서 적절한 제한과 조절 메커니즘을 구현해야 합니다.
모니터링 및 로깅: 백필 시스템의 성능과 신뢰성을 지속적으로 모니터링하는 것이 중요합니다. 어떤 방식이 가장 효과적인지, 어떤 종류의 오류가 자주 발생하는지 등을 추적해야 합니다.

결론

핵심 통찰

앞으로의 방향

연합우주의 대화 백필 문제는 단순히 기술적인 문제를 넘어서 분산형 네트워크에서의 거버넌스, 모더레이션, 사용자 경험의 복합적인 문제입니다.

Fediverse Enhancement Proposal의 약자로, 연합우주의 개선사항을 제안하고 논의하기 위한 공식적인 문서 체계입니다. 새로운 기능이나 프로토콜 확장을 표준화하는 과정에서 사용됩니다. ↩︎

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

Note

원글의 구조와 핵심 아이디어를 바탕으로 하되, 기술적 개념 설명을 보강하고 실제 구현 사례를 추가했습니다. AI의 도움을 받아 작성되었습니다.

원작자 @julian 씨와 활발한 논의에 참여해주신 연합우주 개발자 커뮤니티에 감사드립니다.

문제의 근본 원인: ActivityPub의 분산 특성

ActivityPub이란?

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Create",
  "id": "https://alice.example/activities/create-reply-123",
  "actor": "https://alice.example/users/alice",
  "published": "2025-06-09T10:30:00Z",
  "to": ["https://bob.example/users/bob"],
  "object": {
    "type": "Note",
    "id": "https://alice.example/notes/reply-123",
    "content": "정말 흥미로운 관점이네요!",
    "inReplyTo": "https://bob.example/posts/original-post",
    "attributedTo": "https://alice.example/users/alice"
  }
}

분산의 딜레마

Alice의 원글
├── Bob의 댓글
│   └── Charlie의 댓글
└── Dave의 댓글

해결책을 위한 기반 개념: `context` 속성

실제 `context` 값의 형태들

1. 단순 식별자

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "첫 번째 댓글입니다",
  "context": "https://example.com/conversations/abc123"
}

2. Mastodon 스타일 (`ostatus:conversation`)

Mastodon은 ActivityPub 표준의 context와 함께 OStatus 시절부터 사용해온 conversation 속성을 병행 사용합니다.

{
  "@context": [
    "https://www.w3.org/ns/activitystreams",
    {
      "ostatus": "http://ostatus.org#",
      "conversation": "ostatus:conversation"
    }
  ],
  "type": "Note",
  "content": "이것은 답글입니다",
  "context": "https://mastodon.social/contexts/abc123",
  "conversation": "tag:mastodon.social,2025:objectId=12345:objectType=Conversation"
}

3. 해석 가능한 컬렉션 URL (FEP 7888 방식)

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "스레드 대화의 일부입니다",
  "context": "https://forum.example/topics/technology/thread-42",
  "inReplyTo": "https://forum.example/posts/789"
}

첫 번째 접근법: 답글 트리 크롤링 (reply tree crawling)

개요와 역사

답글 트리 크롤링 방식은 Mastodon의 @jonny 씨가 개척한 방법입니다. 2024년 4월 15일 처음 제안되어 2025년 3월 12일 Mastodon 코어에 병합되었습니다.

기술적 작동 원리

1. 필요한 전제 조건

{
  "id": "https://alice.example/posts/1",
  "type": "Note",
  "content": "어떻게 생각하세요?",
  "replies": {
    "type": "OrderedCollection",
    "id": "https://alice.example/posts/1/replies",
    "totalItems": 3,
    "first": "https://alice.example/posts/1/replies?page=1"
  }
}

2. 크롤링 알고리즘

async function crawlReplyTree(postUrl: URL): Promise<Note[]> {
  const post = await fetchNote(postUrl);
  const allReplies: Note[] = [];
  
  const replies = await post.getReplies();
  if (replies) {
    for await (const reply of replies.getItems()) {
      if (reply instanceof Note) {
        allReplies.push(reply);
        const subReplies = await crawlReplyTree(reply.id!);
        allReplies.push(...subReplies);
      }
    }
  }
  
  return allReplies;
}

이 방식의 핵심은 각 노드(게시물)가 자신에게 달린 답글들의 목록을 정확히 제공한다는 가정에 기반한다는 점입니다.

3. Mastodon의 실제 구현

장점

범용성: inReplyTo와 replies 속성은 거의 모든 ActivityPub 구현에서 보편적으로 사용됩니다. 따라서 기존 인프라를 크게 변경하지 않고도 적용할 수 있습니다.
구현 간 일관성: 대부분의 ActivityPub 구현체에서 이 속성들의 사용법이 크게 다르지 않습니다.
완전한 트리 구성: 이상적인 경우 모든 브랜치와 리프를 포함한 완전한 대화 트리를 얻을 수 있습니다.

단점

네트워크 취약성: 답글 트리의 단일 노드가 일시적 또는 영구적으로 접근 불가능하면, 해당 노드에서 파생되는 모든 브랜치들도 접근할 수 없게 됩니다.
선형적 작업량 증가: CPU 시간, 네트워크 요청 등의 작업량이 답글 트리 크기에 비례하여 선형적으로 증가합니다. 대규모 토론에서는 성능 문제가 발생할 수 있습니다.
재크롤링 필요성: 새로운 브랜치 발견을 위해서는 전체 답글 트리를 다시 크롤링해야 합니다. 빠르게 성장하는 토론에서는 크롤링 시작 시점에 따라 완전한 트리를 얻지 못할 수 있습니다.
불완전한 구현 현실: 현실적으로 모든 ActivityPub 구현체가 replies 컬렉션을 제공하지는 않습니다. Mastodon은 성능상 이유로 같은 서버의 답글만 최대 5개까지 replies 컬렉션에 포함하며, 많은 소규모 구현체들은 성능상 이유로 이를 생략하거나 불완전하게 구현합니다.

현재 구현 현황

현재 Mastodon이 이 방식의 유일한 완전한 구현체입니다. 하지만 이 방식은 Mastodon 고유의 것이 아니며, 다른 구현체들도 채택할 수 있습니다.

두 번째 접근법: 컨텍스트 소유자 기반 방식 (context owner approach)

개요와 배경

기술적 작동 원리

1. 컨텍스트 소유자의 역할

컨텍스트 소유자는 자신이 관리하는 대화의 모든 멤버를 포함하는 OrderedCollection을 제공합니다.

{
  "@context": [
    "https://www.w3.org/ns/activitystreams",
    "https://w3id.org/fep/171b"
  ],
  "type": "OrderedCollection",
  "id": "https://alice.example/conversations/tech-discussion",
  "attributedTo": "https://alice.example/users/alice",
  "collectionOf": "Activity",
  "totalItems": 15,
  "orderedItems": [
    "https://alice.example/activities/add/1",
    "https://alice.example/activities/add/2",
    "https://alice.example/activities/add/3"
  ]
}

2. 두 단계 액티비티 프로세스

이 방식에서는 댓글 추가가 반드시 두 단계로 이루어져야 합니다. 왜 이렇게 복잡하게 해야 할까요?

1단계: 답글 작성자가 일반적인 Create(Note) 액티비티 전송

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Create",
  "actor": "https://bob.example/users/bob",
  "published": "2025-06-09T11:00:00Z",
  "to": ["https://alice.example/users/alice"],
  "object": {
    "type": "Note",
    "id": "https://bob.example/notes/reply-456",
    "content": "정말 좋은 지적이군요!",
    "inReplyTo": "https://alice.example/posts/original",
    "context": "https://alice.example/conversations/tech-discussion"
  }
}

2단계: 컨텍스트 소유자(Alice)가 Add(Note) 액티비티 생성

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Add",
  "actor": "https://alice.example/users/alice",
  "published": "2025-06-09T11:05:00Z",
  "object": "https://bob.example/notes/reply-456",
  "target": {
    "type": "OrderedCollection",
    "id": "https://alice.example/conversations/tech-discussion",
    "attributedTo": "https://alice.example/users/alice"
  },
  "to": ["https://www.w3.org/ns/activitystreams#Public"]
}

3. 백필 메커니즘

개별 구현체들은 컨텍스트 소유자에게 전체 대화 내용을 요청할 수 있습니다.

async function performContextBackfill(contextUrl: URL): Promise<Note[]> {
  const collection = await fetchCollection(contextUrl);
  const notes: Note[] = [];
  
  for await (const item of collection.getItems()) {
    if (item instanceof Add) {
      const note = await item.getObject();
      if (note instanceof Note) {
        notes.push(note);
      }
    }
  }
  
  return notes;
}

장점

의사 중앙화(pseudo-centralization)의 이점: 컨텍스트 소유자가 제공하는 “단일 진실의 원천”(single source of truth)을 통해 일관된 대화 상태를 유지할 수 있습니다.
효율적인 네트워크 사용: 컨텍스트 소유자에게 한 번의 요청으로 전체 대화를 가져올 수 있어, 답글 트리 크롤링보다 네트워크 효율성이 높습니다.
중간 노드 장애 극복: 답글 트리 크롤링과 달리, 중간 노드가 다운되어도 컨텍스트 소유자를 통해 전체 대화에 접근할 수 있습니다.
효율적인 중복 제거: 컨텍스트 레벨에서 오브젝트 중복 제거가 가능하여 전체 네트워크 요청 수와 CPU 시간을 줄일 수 있습니다.
동기화 최적화: ID 해시섬을 통한 동기화 방법으로 네트워크 호출을 더욱 줄일 수 있습니다.

단점

컨텍스트 소유자 의존성: 가장 큰 약점은 컨텍스트 소유자에 대한 의존성입니다. 컨텍스트 소유자 서버에 접근할 수 없으면 전체 대화 백필이 불가능해집니다.
제한된 가시성: 컨텍스트 소유자는 자신이 알고 있는 오브젝트/액티비티만 응답할 수 있습니다.
상위 전파 누락 문제: 핵심적인 한계로, 루트로 다시 상위 전파되지 않는 하위 브랜치들은 컨텍스트 소유자가 알 수 없습니다.
구현체 지원 필요: 컨텍스트 소유자가 이 방식을 지원해야만 작동하므로, 다른 백필 전략과 결합해야 합니다.

현재 구현 현황

NodeBB, Discourse, WordPress, Frequency, Mitra, Streams가 현재 이 방식을 구현하고 있으며, Lemmy와 Piefed가 관심을 표명하고 있습니다.

중요한 논쟁 포인트들

1. 모더레이션 패러다임의 충돌

관련 NodeBB 스레드에서 @silverpill 씨가 제기한 핵심적인 문제점입니다.

두 접근 방식이 서로 충돌하지 않는다고 했지만, 이 ‘스레딩 패러다임’들은 모더레이션 문제에 대해 서로 다른 해결책을 제시합니다.

I don't fully agree with this statement, because these ‘threading paradigms’ suggest two different solutions to the problem of moderation.

컨텍스트 소유자 방식의 모더레이션

Alice가 스팸 댓글에 대해 Add(Note) 액티비티를 생성하지 않으면, 해당 댓글은 대화에서 제외됩니다.

답글 트리 크롤링의 모더레이션

각 답글이 독립적이며, 작성자들이 직접 답글만 모더레이션할 수 있습니다. 원글 작성자가 전체 대화를 제어할 수 없습니다.

2. 상위 전파 누락 문제의 해결책

어드레싱 규칙 활용 (FEP-171b)

FEP-171b에서는 “답글의 audience는 대화 루트에서 복사되어야 한다”(The audience of a reply MUST be copied from a conversation root)는 규칙을 제시합니다.

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Create",
  "actor": "https://charlie.example/users/charlie",
  "object": {
    "type": "Note",
    "content": "Bob의 댓글에 대한 답글",
    "inReplyTo": "https://bob.example/comments/2",
    "context": "https://alice.example/conversations/1",
    "to": [
      "https://bob.example/users/bob",
      "https://alice.example/users/alice"
    ]
  }
}

하이브리드 백필 메커니즘

많은 구현체가 여러 방식을 조합하는 방식을 채택합니다.

async function hybridBackfill(conversationId: URL): Promise<Note[]> {
  const strategies = [
    () => contextOwnerBackfill(conversationId),
    () => replyTreeCrawling(conversationId),
    () => mentionBasedDiscovery(conversationId)
  ];
  
  for (const strategy of strategies) {
    try {
      const result = await strategy();
      if (result.length > 0) return result;
    } catch (error) {
      console.warn('Strategy failed, trying next:', error);
    }
  }
  
  return [];
}

추가적인 백필 메커니즘들

주기적 크롤링 백필: 이 방식은 마치 정기적인 건강검진과 같습니다. 시스템이 정해진 주기마다 활발한 대화들을 점검하여 누락된 답글이 있는지 확인합니다.
사용자 트리거 백필: 사용자가 특정 대화 페이지에 접속하면, 시스템은 즉시 현재 보유한 컨텍스트 컬렉션을 검토하고 실시간으로 누락된 답글들을 탐색합니다.

멘션 기반 백필: 사용자들이 대화에서 다른 사람을 멘션하는 자연스러운 행동을 통해 누락된 답글 체인을 발견하는 메커니즘입니다.

async function onMentionReceived(activity: Create): Promise<void> {
  const mention = await activity.getObject();

  if (mention.context && mention.replyTargetId) {
    const missingChain = await traceReplyChain(await mention.getReplyTarget());
    await addToContext(mention.context, missingChain);
  }
}

실제 도전과제들

순환 참조 방지: 백필 과정에서 무한 루프에 빠지는 것을 방지하는 것은 매우 중요합니다. 실제 구현에서는 방문한 URL을 추적하고, 최대 탐색 깊이를 제한하는 안전장치를 마련합니다.
성능 최적화: 대규모 대화에서는 수백 개의 답글이 달릴 수 있고, 이를 모두 한 번에 처리하려고 하면 서버에 과도한 부하가 걸릴 수 있습니다. 일괄 처리(batch processing)는 여러 대화를 동시에 처리할 때 작은 그룹으로 나누어 순차적으로 처리하고 각 배치 사이에 짧은 휴식 시간을 두는 방식입니다.
오류 처리 및 복구: 분산 네트워크 환경에서는 다양한 종류의 오류가 발생할 수 있습니다. 실제 구현에서는 여러 백필 전략을 순차적으로 시도하는 복원력 있는 접근법을 사용합니다.

표준화 노력과 미래 전망

FEP 수렴 논의

현재 연합우주 커뮤니티에서는 FEP 수렴 스레드를 통해 여러 FEP들을 통합하려는 노력이 진행되고 있습니다.

구현체 간 협력

NodeBB와 Discourse의 협력 사례

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "context": "https://community.nodebb.org/topic/18844",
  "audience": "https://community.nodebb.org/category/development",
  "tag": [
    {
      "type": "Link",
      "href": "https://meta.discourse.org/t/activitypub-support/12345",
      "rel": "related"
    }
  ]
}

Mastodon과의 호환성 고려

{
  "@context": [
    "https://www.w3.org/ns/activitystreams",
    {
      "ostatus": "http://ostatus.org#",
      "conversation": "ostatus:conversation"
    }
  ],
  "type": "Note",
  "content": "Mastodon 호환 답글",
  "context": "https://mastodon.social/contexts/abc123",
  "conversation": "tag:mastodon.social,2025:objectId=12345:objectType=Conversation"
}

이런 하위 호환성 유지는 연합우주 생태계의 분열을 방지하고 사용자 경험을 개선하는 데 중요한 역할을 합니다.

향후 개발 방향: 하이브리드 접근법의 표준화

모범 사례 가이드라인

다중 전략 구현: 절대로 하나의 백필 방식에만 의존하지 마세요. 연합우주의 다양성과 불확실성을 고려할 때, 여러 전략을 조합하는 것이 필수적입니다. 각 전략은 서로 다른 상황에서 강점을 보이므로, 상황에 따라 적절한 전략을 선택할 수 있는 유연성을 확보해야 합니다.

예를 들어, 활발한 포럼 토론에서는 컨텍스트 소유자 방식이 효과적일 수 있지만, Mastodon의 일반적인 대화에서는 답글 트리 크롤링이 더 적합할 수 있습니다.
리소스 관리: 백필 작업은 상당한 서버 리소스를 소모할 수 있습니다. 특히 인기 있는 대화나 대규모 토론의 경우 수백 개의 네트워크 요청이 필요할 수 있습니다. 따라서 적절한 제한과 조절 메커니즘을 구현해야 합니다.
모니터링 및 로깅: 백필 시스템의 성능과 신뢰성을 지속적으로 모니터링하는 것이 중요합니다. 어떤 방식이 가장 효과적인지, 어떤 종류의 오류가 자주 발생하는지 등을 추적해야 합니다.

결론

핵심 통찰

앞으로의 방향

연합우주의 대화 백필 문제는 단순히 기술적인 문제를 넘어서 분산형 네트워크에서의 거버넌스, 모더레이션, 사용자 경험의 복합적인 문제입니다.

Fediverse Enhancement Proposal의 약자로, 연합우주의 개선사항을 제안하고 논의하기 위한 공식적인 문서 체계입니다. 새로운 기능이나 프로토콜 확장을 표준화하는 과정에서 사용됩니다. ↩︎

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

Note

원글의 구조와 핵심 아이디어를 바탕으로 하되, 기술적 개념 설명을 보강하고 실제 구현 사례를 추가했습니다. AI의 도움을 받아 작성되었습니다.

원작자 @julian 씨와 활발한 논의에 참여해주신 연합우주 개발자 커뮤니티에 감사드립니다.

문제의 근본 원인: ActivityPub의 분산 특성

ActivityPub이란?

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Create",
  "id": "https://alice.example/activities/create-reply-123",
  "actor": "https://alice.example/users/alice",
  "published": "2025-06-09T10:30:00Z",
  "to": ["https://bob.example/users/bob"],
  "object": {
    "type": "Note",
    "id": "https://alice.example/notes/reply-123",
    "content": "정말 흥미로운 관점이네요!",
    "inReplyTo": "https://bob.example/posts/original-post",
    "attributedTo": "https://alice.example/users/alice"
  }
}

분산의 딜레마

Alice의 원글
├── Bob의 댓글
│   └── Charlie의 댓글
└── Dave의 댓글

해결책을 위한 기반 개념: `context` 속성

실제 `context` 값의 형태들

1. 단순 식별자

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "첫 번째 댓글입니다",
  "context": "https://example.com/conversations/abc123"
}

2. Mastodon 스타일 (`ostatus:conversation`)

Mastodon은 ActivityPub 표준의 context와 함께 OStatus 시절부터 사용해온 conversation 속성을 병행 사용합니다.

{
  "@context": [
    "https://www.w3.org/ns/activitystreams",
    {
      "ostatus": "http://ostatus.org#",
      "conversation": "ostatus:conversation"
    }
  ],
  "type": "Note",
  "content": "이것은 답글입니다",
  "context": "https://mastodon.social/contexts/abc123",
  "conversation": "tag:mastodon.social,2025:objectId=12345:objectType=Conversation"
}

3. 해석 가능한 컬렉션 URL (FEP 7888 방식)

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "스레드 대화의 일부입니다",
  "context": "https://forum.example/topics/technology/thread-42",
  "inReplyTo": "https://forum.example/posts/789"
}

첫 번째 접근법: 답글 트리 크롤링 (reply tree crawling)

개요와 역사

답글 트리 크롤링 방식은 Mastodon의 @jonny 씨가 개척한 방법입니다. 2024년 4월 15일 처음 제안되어 2025년 3월 12일 Mastodon 코어에 병합되었습니다.

기술적 작동 원리

1. 필요한 전제 조건

{
  "id": "https://alice.example/posts/1",
  "type": "Note",
  "content": "어떻게 생각하세요?",
  "replies": {
    "type": "OrderedCollection",
    "id": "https://alice.example/posts/1/replies",
    "totalItems": 3,
    "first": "https://alice.example/posts/1/replies?page=1"
  }
}

2. 크롤링 알고리즘

async function crawlReplyTree(postUrl: URL): Promise<Note[]> {
  const post = await fetchNote(postUrl);
  const allReplies: Note[] = [];
  
  const replies = await post.getReplies();
  if (replies) {
    for await (const reply of replies.getItems()) {
      if (reply instanceof Note) {
        allReplies.push(reply);
        const subReplies = await crawlReplyTree(reply.id!);
        allReplies.push(...subReplies);
      }
    }
  }
  
  return allReplies;
}

이 방식의 핵심은 각 노드(게시물)가 자신에게 달린 답글들의 목록을 정확히 제공한다는 가정에 기반한다는 점입니다.

3. Mastodon의 실제 구현

장점

범용성: inReplyTo와 replies 속성은 거의 모든 ActivityPub 구현에서 보편적으로 사용됩니다. 따라서 기존 인프라를 크게 변경하지 않고도 적용할 수 있습니다.
구현 간 일관성: 대부분의 ActivityPub 구현체에서 이 속성들의 사용법이 크게 다르지 않습니다.
완전한 트리 구성: 이상적인 경우 모든 브랜치와 리프를 포함한 완전한 대화 트리를 얻을 수 있습니다.

단점

네트워크 취약성: 답글 트리의 단일 노드가 일시적 또는 영구적으로 접근 불가능하면, 해당 노드에서 파생되는 모든 브랜치들도 접근할 수 없게 됩니다.
선형적 작업량 증가: CPU 시간, 네트워크 요청 등의 작업량이 답글 트리 크기에 비례하여 선형적으로 증가합니다. 대규모 토론에서는 성능 문제가 발생할 수 있습니다.
재크롤링 필요성: 새로운 브랜치 발견을 위해서는 전체 답글 트리를 다시 크롤링해야 합니다. 빠르게 성장하는 토론에서는 크롤링 시작 시점에 따라 완전한 트리를 얻지 못할 수 있습니다.
불완전한 구현 현실: 현실적으로 모든 ActivityPub 구현체가 replies 컬렉션을 제공하지는 않습니다. Mastodon은 성능상 이유로 같은 서버의 답글만 최대 5개까지 replies 컬렉션에 포함하며, 많은 소규모 구현체들은 성능상 이유로 이를 생략하거나 불완전하게 구현합니다.

현재 구현 현황

현재 Mastodon이 이 방식의 유일한 완전한 구현체입니다. 하지만 이 방식은 Mastodon 고유의 것이 아니며, 다른 구현체들도 채택할 수 있습니다.

두 번째 접근법: 컨텍스트 소유자 기반 방식 (context owner approach)

개요와 배경

기술적 작동 원리

1. 컨텍스트 소유자의 역할

컨텍스트 소유자는 자신이 관리하는 대화의 모든 멤버를 포함하는 OrderedCollection을 제공합니다.

{
  "@context": [
    "https://www.w3.org/ns/activitystreams",
    "https://w3id.org/fep/171b"
  ],
  "type": "OrderedCollection",
  "id": "https://alice.example/conversations/tech-discussion",
  "attributedTo": "https://alice.example/users/alice",
  "collectionOf": "Activity",
  "totalItems": 15,
  "orderedItems": [
    "https://alice.example/activities/add/1",
    "https://alice.example/activities/add/2",
    "https://alice.example/activities/add/3"
  ]
}

2. 두 단계 액티비티 프로세스

이 방식에서는 댓글 추가가 반드시 두 단계로 이루어져야 합니다. 왜 이렇게 복잡하게 해야 할까요?

1단계: 답글 작성자가 일반적인 Create(Note) 액티비티 전송

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Create",
  "actor": "https://bob.example/users/bob",
  "published": "2025-06-09T11:00:00Z",
  "to": ["https://alice.example/users/alice"],
  "object": {
    "type": "Note",
    "id": "https://bob.example/notes/reply-456",
    "content": "정말 좋은 지적이군요!",
    "inReplyTo": "https://alice.example/posts/original",
    "context": "https://alice.example/conversations/tech-discussion"
  }
}

2단계: 컨텍스트 소유자(Alice)가 Add(Note) 액티비티 생성

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Add",
  "actor": "https://alice.example/users/alice",
  "published": "2025-06-09T11:05:00Z",
  "object": "https://bob.example/notes/reply-456",
  "target": {
    "type": "OrderedCollection",
    "id": "https://alice.example/conversations/tech-discussion",
    "attributedTo": "https://alice.example/users/alice"
  },
  "to": ["https://www.w3.org/ns/activitystreams#Public"]
}

3. 백필 메커니즘

개별 구현체들은 컨텍스트 소유자에게 전체 대화 내용을 요청할 수 있습니다.

async function performContextBackfill(contextUrl: URL): Promise<Note[]> {
  const collection = await fetchCollection(contextUrl);
  const notes: Note[] = [];
  
  for await (const item of collection.getItems()) {
    if (item instanceof Add) {
      const note = await item.getObject();
      if (note instanceof Note) {
        notes.push(note);
      }
    }
  }
  
  return notes;
}

장점

의사 중앙화(pseudo-centralization)의 이점: 컨텍스트 소유자가 제공하는 “단일 진실의 원천”(single source of truth)을 통해 일관된 대화 상태를 유지할 수 있습니다.
효율적인 네트워크 사용: 컨텍스트 소유자에게 한 번의 요청으로 전체 대화를 가져올 수 있어, 답글 트리 크롤링보다 네트워크 효율성이 높습니다.
중간 노드 장애 극복: 답글 트리 크롤링과 달리, 중간 노드가 다운되어도 컨텍스트 소유자를 통해 전체 대화에 접근할 수 있습니다.
효율적인 중복 제거: 컨텍스트 레벨에서 오브젝트 중복 제거가 가능하여 전체 네트워크 요청 수와 CPU 시간을 줄일 수 있습니다.
동기화 최적화: ID 해시섬을 통한 동기화 방법으로 네트워크 호출을 더욱 줄일 수 있습니다.

단점

컨텍스트 소유자 의존성: 가장 큰 약점은 컨텍스트 소유자에 대한 의존성입니다. 컨텍스트 소유자 서버에 접근할 수 없으면 전체 대화 백필이 불가능해집니다.
제한된 가시성: 컨텍스트 소유자는 자신이 알고 있는 오브젝트/액티비티만 응답할 수 있습니다.
상위 전파 누락 문제: 핵심적인 한계로, 루트로 다시 상위 전파되지 않는 하위 브랜치들은 컨텍스트 소유자가 알 수 없습니다.
구현체 지원 필요: 컨텍스트 소유자가 이 방식을 지원해야만 작동하므로, 다른 백필 전략과 결합해야 합니다.

현재 구현 현황

NodeBB, Discourse, WordPress, Frequency, Mitra, Streams가 현재 이 방식을 구현하고 있으며, Lemmy와 Piefed가 관심을 표명하고 있습니다.

중요한 논쟁 포인트들

1. 모더레이션 패러다임의 충돌

관련 NodeBB 스레드에서 @silverpill 씨가 제기한 핵심적인 문제점입니다.

두 접근 방식이 서로 충돌하지 않는다고 했지만, 이 ‘스레딩 패러다임’들은 모더레이션 문제에 대해 서로 다른 해결책을 제시합니다.

I don't fully agree with this statement, because these ‘threading paradigms’ suggest two different solutions to the problem of moderation.

컨텍스트 소유자 방식의 모더레이션

Alice가 스팸 댓글에 대해 Add(Note) 액티비티를 생성하지 않으면, 해당 댓글은 대화에서 제외됩니다.

답글 트리 크롤링의 모더레이션

각 답글이 독립적이며, 작성자들이 직접 답글만 모더레이션할 수 있습니다. 원글 작성자가 전체 대화를 제어할 수 없습니다.

2. 상위 전파 누락 문제의 해결책

어드레싱 규칙 활용 (FEP-171b)

FEP-171b에서는 “답글의 audience는 대화 루트에서 복사되어야 한다”(The audience of a reply MUST be copied from a conversation root)는 규칙을 제시합니다.

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Create",
  "actor": "https://charlie.example/users/charlie",
  "object": {
    "type": "Note",
    "content": "Bob의 댓글에 대한 답글",
    "inReplyTo": "https://bob.example/comments/2",
    "context": "https://alice.example/conversations/1",
    "to": [
      "https://bob.example/users/bob",
      "https://alice.example/users/alice"
    ]
  }
}

하이브리드 백필 메커니즘

많은 구현체가 여러 방식을 조합하는 방식을 채택합니다.

async function hybridBackfill(conversationId: URL): Promise<Note[]> {
  const strategies = [
    () => contextOwnerBackfill(conversationId),
    () => replyTreeCrawling(conversationId),
    () => mentionBasedDiscovery(conversationId)
  ];
  
  for (const strategy of strategies) {
    try {
      const result = await strategy();
      if (result.length > 0) return result;
    } catch (error) {
      console.warn('Strategy failed, trying next:', error);
    }
  }
  
  return [];
}

추가적인 백필 메커니즘들

주기적 크롤링 백필: 이 방식은 마치 정기적인 건강검진과 같습니다. 시스템이 정해진 주기마다 활발한 대화들을 점검하여 누락된 답글이 있는지 확인합니다.
사용자 트리거 백필: 사용자가 특정 대화 페이지에 접속하면, 시스템은 즉시 현재 보유한 컨텍스트 컬렉션을 검토하고 실시간으로 누락된 답글들을 탐색합니다.

멘션 기반 백필: 사용자들이 대화에서 다른 사람을 멘션하는 자연스러운 행동을 통해 누락된 답글 체인을 발견하는 메커니즘입니다.

async function onMentionReceived(activity: Create): Promise<void> {
  const mention = await activity.getObject();

  if (mention.context && mention.replyTargetId) {
    const missingChain = await traceReplyChain(await mention.getReplyTarget());
    await addToContext(mention.context, missingChain);
  }
}

실제 도전과제들

순환 참조 방지: 백필 과정에서 무한 루프에 빠지는 것을 방지하는 것은 매우 중요합니다. 실제 구현에서는 방문한 URL을 추적하고, 최대 탐색 깊이를 제한하는 안전장치를 마련합니다.
성능 최적화: 대규모 대화에서는 수백 개의 답글이 달릴 수 있고, 이를 모두 한 번에 처리하려고 하면 서버에 과도한 부하가 걸릴 수 있습니다. 일괄 처리(batch processing)는 여러 대화를 동시에 처리할 때 작은 그룹으로 나누어 순차적으로 처리하고 각 배치 사이에 짧은 휴식 시간을 두는 방식입니다.
오류 처리 및 복구: 분산 네트워크 환경에서는 다양한 종류의 오류가 발생할 수 있습니다. 실제 구현에서는 여러 백필 전략을 순차적으로 시도하는 복원력 있는 접근법을 사용합니다.

표준화 노력과 미래 전망

FEP 수렴 논의

현재 연합우주 커뮤니티에서는 FEP 수렴 스레드를 통해 여러 FEP들을 통합하려는 노력이 진행되고 있습니다.

구현체 간 협력

NodeBB와 Discourse의 협력 사례

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "context": "https://community.nodebb.org/topic/18844",
  "audience": "https://community.nodebb.org/category/development",
  "tag": [
    {
      "type": "Link",
      "href": "https://meta.discourse.org/t/activitypub-support/12345",
      "rel": "related"
    }
  ]
}

Mastodon과의 호환성 고려

{
  "@context": [
    "https://www.w3.org/ns/activitystreams",
    {
      "ostatus": "http://ostatus.org#",
      "conversation": "ostatus:conversation"
    }
  ],
  "type": "Note",
  "content": "Mastodon 호환 답글",
  "context": "https://mastodon.social/contexts/abc123",
  "conversation": "tag:mastodon.social,2025:objectId=12345:objectType=Conversation"
}

이런 하위 호환성 유지는 연합우주 생태계의 분열을 방지하고 사용자 경험을 개선하는 데 중요한 역할을 합니다.

향후 개발 방향: 하이브리드 접근법의 표준화

모범 사례 가이드라인

다중 전략 구현: 절대로 하나의 백필 방식에만 의존하지 마세요. 연합우주의 다양성과 불확실성을 고려할 때, 여러 전략을 조합하는 것이 필수적입니다. 각 전략은 서로 다른 상황에서 강점을 보이므로, 상황에 따라 적절한 전략을 선택할 수 있는 유연성을 확보해야 합니다.

예를 들어, 활발한 포럼 토론에서는 컨텍스트 소유자 방식이 효과적일 수 있지만, Mastodon의 일반적인 대화에서는 답글 트리 크롤링이 더 적합할 수 있습니다.
리소스 관리: 백필 작업은 상당한 서버 리소스를 소모할 수 있습니다. 특히 인기 있는 대화나 대규모 토론의 경우 수백 개의 네트워크 요청이 필요할 수 있습니다. 따라서 적절한 제한과 조절 메커니즘을 구현해야 합니다.
모니터링 및 로깅: 백필 시스템의 성능과 신뢰성을 지속적으로 모니터링하는 것이 중요합니다. 어떤 방식이 가장 효과적인지, 어떤 종류의 오류가 자주 발생하는지 등을 추적해야 합니다.

결론

핵심 통찰

앞으로의 방향

연합우주의 대화 백필 문제는 단순히 기술적인 문제를 넘어서 분산형 네트워크에서의 거버넌스, 모더레이션, 사용자 경험의 복합적인 문제입니다.

Fediverse Enhancement Proposal의 약자로, 연합우주의 개선사항을 제안하고 논의하기 위한 공식적인 문서 체계입니다. 새로운 기능이나 프로토콜 확장을 표준화하는 과정에서 사용됩니다. ↩︎

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

Note

원글의 구조와 핵심 아이디어를 바탕으로 하되, 기술적 개념 설명을 보강하고 실제 구현 사례를 추가했습니다. AI의 도움을 받아 작성되었습니다.

원작자 @julian 씨와 활발한 논의에 참여해주신 연합우주 개발자 커뮤니티에 감사드립니다.

문제의 근본 원인: ActivityPub의 분산 특성

ActivityPub이란?

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Create",
  "id": "https://alice.example/activities/create-reply-123",
  "actor": "https://alice.example/users/alice",
  "published": "2025-06-09T10:30:00Z",
  "to": ["https://bob.example/users/bob"],
  "object": {
    "type": "Note",
    "id": "https://alice.example/notes/reply-123",
    "content": "정말 흥미로운 관점이네요!",
    "inReplyTo": "https://bob.example/posts/original-post",
    "attributedTo": "https://alice.example/users/alice"
  }
}

분산의 딜레마

Alice의 원글
├── Bob의 댓글
│   └── Charlie의 댓글
└── Dave의 댓글

해결책을 위한 기반 개념: `context` 속성

실제 `context` 값의 형태들

1. 단순 식별자

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "첫 번째 댓글입니다",
  "context": "https://example.com/conversations/abc123"
}

2. Mastodon 스타일 (`ostatus:conversation`)

Mastodon은 ActivityPub 표준의 context와 함께 OStatus 시절부터 사용해온 conversation 속성을 병행 사용합니다.

{
  "@context": [
    "https://www.w3.org/ns/activitystreams",
    {
      "ostatus": "http://ostatus.org#",
      "conversation": "ostatus:conversation"
    }
  ],
  "type": "Note",
  "content": "이것은 답글입니다",
  "context": "https://mastodon.social/contexts/abc123",
  "conversation": "tag:mastodon.social,2025:objectId=12345:objectType=Conversation"
}

3. 해석 가능한 컬렉션 URL (FEP 7888 방식)

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "스레드 대화의 일부입니다",
  "context": "https://forum.example/topics/technology/thread-42",
  "inReplyTo": "https://forum.example/posts/789"
}

첫 번째 접근법: 답글 트리 크롤링 (reply tree crawling)

개요와 역사

답글 트리 크롤링 방식은 Mastodon의 @jonny 씨가 개척한 방법입니다. 2024년 4월 15일 처음 제안되어 2025년 3월 12일 Mastodon 코어에 병합되었습니다.

기술적 작동 원리

1. 필요한 전제 조건

{
  "id": "https://alice.example/posts/1",
  "type": "Note",
  "content": "어떻게 생각하세요?",
  "replies": {
    "type": "OrderedCollection",
    "id": "https://alice.example/posts/1/replies",
    "totalItems": 3,
    "first": "https://alice.example/posts/1/replies?page=1"
  }
}

2. 크롤링 알고리즘

async function crawlReplyTree(postUrl: URL): Promise<Note[]> {
  const post = await fetchNote(postUrl);
  const allReplies: Note[] = [];
  
  const replies = await post.getReplies();
  if (replies) {
    for await (const reply of replies.getItems()) {
      if (reply instanceof Note) {
        allReplies.push(reply);
        const subReplies = await crawlReplyTree(reply.id!);
        allReplies.push(...subReplies);
      }
    }
  }
  
  return allReplies;
}

이 방식의 핵심은 각 노드(게시물)가 자신에게 달린 답글들의 목록을 정확히 제공한다는 가정에 기반한다는 점입니다.

3. Mastodon의 실제 구현

장점

범용성: inReplyTo와 replies 속성은 거의 모든 ActivityPub 구현에서 보편적으로 사용됩니다. 따라서 기존 인프라를 크게 변경하지 않고도 적용할 수 있습니다.
구현 간 일관성: 대부분의 ActivityPub 구현체에서 이 속성들의 사용법이 크게 다르지 않습니다.
완전한 트리 구성: 이상적인 경우 모든 브랜치와 리프를 포함한 완전한 대화 트리를 얻을 수 있습니다.

단점

네트워크 취약성: 답글 트리의 단일 노드가 일시적 또는 영구적으로 접근 불가능하면, 해당 노드에서 파생되는 모든 브랜치들도 접근할 수 없게 됩니다.
선형적 작업량 증가: CPU 시간, 네트워크 요청 등의 작업량이 답글 트리 크기에 비례하여 선형적으로 증가합니다. 대규모 토론에서는 성능 문제가 발생할 수 있습니다.
재크롤링 필요성: 새로운 브랜치 발견을 위해서는 전체 답글 트리를 다시 크롤링해야 합니다. 빠르게 성장하는 토론에서는 크롤링 시작 시점에 따라 완전한 트리를 얻지 못할 수 있습니다.
불완전한 구현 현실: 현실적으로 모든 ActivityPub 구현체가 replies 컬렉션을 제공하지는 않습니다. Mastodon은 성능상 이유로 같은 서버의 답글만 최대 5개까지 replies 컬렉션에 포함하며, 많은 소규모 구현체들은 성능상 이유로 이를 생략하거나 불완전하게 구현합니다.

현재 구현 현황

현재 Mastodon이 이 방식의 유일한 완전한 구현체입니다. 하지만 이 방식은 Mastodon 고유의 것이 아니며, 다른 구현체들도 채택할 수 있습니다.

두 번째 접근법: 컨텍스트 소유자 기반 방식 (context owner approach)

개요와 배경

기술적 작동 원리

1. 컨텍스트 소유자의 역할

컨텍스트 소유자는 자신이 관리하는 대화의 모든 멤버를 포함하는 OrderedCollection을 제공합니다.

{
  "@context": [
    "https://www.w3.org/ns/activitystreams",
    "https://w3id.org/fep/171b"
  ],
  "type": "OrderedCollection",
  "id": "https://alice.example/conversations/tech-discussion",
  "attributedTo": "https://alice.example/users/alice",
  "collectionOf": "Activity",
  "totalItems": 15,
  "orderedItems": [
    "https://alice.example/activities/add/1",
    "https://alice.example/activities/add/2",
    "https://alice.example/activities/add/3"
  ]
}

2. 두 단계 액티비티 프로세스

이 방식에서는 댓글 추가가 반드시 두 단계로 이루어져야 합니다. 왜 이렇게 복잡하게 해야 할까요?

1단계: 답글 작성자가 일반적인 Create(Note) 액티비티 전송

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Create",
  "actor": "https://bob.example/users/bob",
  "published": "2025-06-09T11:00:00Z",
  "to": ["https://alice.example/users/alice"],
  "object": {
    "type": "Note",
    "id": "https://bob.example/notes/reply-456",
    "content": "정말 좋은 지적이군요!",
    "inReplyTo": "https://alice.example/posts/original",
    "context": "https://alice.example/conversations/tech-discussion"
  }
}

2단계: 컨텍스트 소유자(Alice)가 Add(Note) 액티비티 생성

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Add",
  "actor": "https://alice.example/users/alice",
  "published": "2025-06-09T11:05:00Z",
  "object": "https://bob.example/notes/reply-456",
  "target": {
    "type": "OrderedCollection",
    "id": "https://alice.example/conversations/tech-discussion",
    "attributedTo": "https://alice.example/users/alice"
  },
  "to": ["https://www.w3.org/ns/activitystreams#Public"]
}

3. 백필 메커니즘

개별 구현체들은 컨텍스트 소유자에게 전체 대화 내용을 요청할 수 있습니다.

async function performContextBackfill(contextUrl: URL): Promise<Note[]> {
  const collection = await fetchCollection(contextUrl);
  const notes: Note[] = [];
  
  for await (const item of collection.getItems()) {
    if (item instanceof Add) {
      const note = await item.getObject();
      if (note instanceof Note) {
        notes.push(note);
      }
    }
  }
  
  return notes;
}

장점

의사 중앙화(pseudo-centralization)의 이점: 컨텍스트 소유자가 제공하는 “단일 진실의 원천”(single source of truth)을 통해 일관된 대화 상태를 유지할 수 있습니다.
효율적인 네트워크 사용: 컨텍스트 소유자에게 한 번의 요청으로 전체 대화를 가져올 수 있어, 답글 트리 크롤링보다 네트워크 효율성이 높습니다.
중간 노드 장애 극복: 답글 트리 크롤링과 달리, 중간 노드가 다운되어도 컨텍스트 소유자를 통해 전체 대화에 접근할 수 있습니다.
효율적인 중복 제거: 컨텍스트 레벨에서 오브젝트 중복 제거가 가능하여 전체 네트워크 요청 수와 CPU 시간을 줄일 수 있습니다.
동기화 최적화: ID 해시섬을 통한 동기화 방법으로 네트워크 호출을 더욱 줄일 수 있습니다.

단점

컨텍스트 소유자 의존성: 가장 큰 약점은 컨텍스트 소유자에 대한 의존성입니다. 컨텍스트 소유자 서버에 접근할 수 없으면 전체 대화 백필이 불가능해집니다.
제한된 가시성: 컨텍스트 소유자는 자신이 알고 있는 오브젝트/액티비티만 응답할 수 있습니다.
상위 전파 누락 문제: 핵심적인 한계로, 루트로 다시 상위 전파되지 않는 하위 브랜치들은 컨텍스트 소유자가 알 수 없습니다.
구현체 지원 필요: 컨텍스트 소유자가 이 방식을 지원해야만 작동하므로, 다른 백필 전략과 결합해야 합니다.

현재 구현 현황

NodeBB, Discourse, WordPress, Frequency, Mitra, Streams가 현재 이 방식을 구현하고 있으며, Lemmy와 Piefed가 관심을 표명하고 있습니다.

중요한 논쟁 포인트들

1. 모더레이션 패러다임의 충돌

관련 NodeBB 스레드에서 @silverpill 씨가 제기한 핵심적인 문제점입니다.

두 접근 방식이 서로 충돌하지 않는다고 했지만, 이 ‘스레딩 패러다임’들은 모더레이션 문제에 대해 서로 다른 해결책을 제시합니다.

I don't fully agree with this statement, because these ‘threading paradigms’ suggest two different solutions to the problem of moderation.

컨텍스트 소유자 방식의 모더레이션

Alice가 스팸 댓글에 대해 Add(Note) 액티비티를 생성하지 않으면, 해당 댓글은 대화에서 제외됩니다.

답글 트리 크롤링의 모더레이션

각 답글이 독립적이며, 작성자들이 직접 답글만 모더레이션할 수 있습니다. 원글 작성자가 전체 대화를 제어할 수 없습니다.

2. 상위 전파 누락 문제의 해결책

어드레싱 규칙 활용 (FEP-171b)

FEP-171b에서는 “답글의 audience는 대화 루트에서 복사되어야 한다”(The audience of a reply MUST be copied from a conversation root)는 규칙을 제시합니다.

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Create",
  "actor": "https://charlie.example/users/charlie",
  "object": {
    "type": "Note",
    "content": "Bob의 댓글에 대한 답글",
    "inReplyTo": "https://bob.example/comments/2",
    "context": "https://alice.example/conversations/1",
    "to": [
      "https://bob.example/users/bob",
      "https://alice.example/users/alice"
    ]
  }
}

하이브리드 백필 메커니즘

많은 구현체가 여러 방식을 조합하는 방식을 채택합니다.

async function hybridBackfill(conversationId: URL): Promise<Note[]> {
  const strategies = [
    () => contextOwnerBackfill(conversationId),
    () => replyTreeCrawling(conversationId),
    () => mentionBasedDiscovery(conversationId)
  ];
  
  for (const strategy of strategies) {
    try {
      const result = await strategy();
      if (result.length > 0) return result;
    } catch (error) {
      console.warn('Strategy failed, trying next:', error);
    }
  }
  
  return [];
}

추가적인 백필 메커니즘들

주기적 크롤링 백필: 이 방식은 마치 정기적인 건강검진과 같습니다. 시스템이 정해진 주기마다 활발한 대화들을 점검하여 누락된 답글이 있는지 확인합니다.
사용자 트리거 백필: 사용자가 특정 대화 페이지에 접속하면, 시스템은 즉시 현재 보유한 컨텍스트 컬렉션을 검토하고 실시간으로 누락된 답글들을 탐색합니다.

멘션 기반 백필: 사용자들이 대화에서 다른 사람을 멘션하는 자연스러운 행동을 통해 누락된 답글 체인을 발견하는 메커니즘입니다.

async function onMentionReceived(activity: Create): Promise<void> {
  const mention = await activity.getObject();

  if (mention.context && mention.replyTargetId) {
    const missingChain = await traceReplyChain(await mention.getReplyTarget());
    await addToContext(mention.context, missingChain);
  }
}

실제 도전과제들

순환 참조 방지: 백필 과정에서 무한 루프에 빠지는 것을 방지하는 것은 매우 중요합니다. 실제 구현에서는 방문한 URL을 추적하고, 최대 탐색 깊이를 제한하는 안전장치를 마련합니다.
성능 최적화: 대규모 대화에서는 수백 개의 답글이 달릴 수 있고, 이를 모두 한 번에 처리하려고 하면 서버에 과도한 부하가 걸릴 수 있습니다. 일괄 처리(batch processing)는 여러 대화를 동시에 처리할 때 작은 그룹으로 나누어 순차적으로 처리하고 각 배치 사이에 짧은 휴식 시간을 두는 방식입니다.
오류 처리 및 복구: 분산 네트워크 환경에서는 다양한 종류의 오류가 발생할 수 있습니다. 실제 구현에서는 여러 백필 전략을 순차적으로 시도하는 복원력 있는 접근법을 사용합니다.

표준화 노력과 미래 전망

FEP 수렴 논의

현재 연합우주 커뮤니티에서는 FEP 수렴 스레드를 통해 여러 FEP들을 통합하려는 노력이 진행되고 있습니다.

구현체 간 협력

NodeBB와 Discourse의 협력 사례

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "context": "https://community.nodebb.org/topic/18844",
  "audience": "https://community.nodebb.org/category/development",
  "tag": [
    {
      "type": "Link",
      "href": "https://meta.discourse.org/t/activitypub-support/12345",
      "rel": "related"
    }
  ]
}

Mastodon과의 호환성 고려

{
  "@context": [
    "https://www.w3.org/ns/activitystreams",
    {
      "ostatus": "http://ostatus.org#",
      "conversation": "ostatus:conversation"
    }
  ],
  "type": "Note",
  "content": "Mastodon 호환 답글",
  "context": "https://mastodon.social/contexts/abc123",
  "conversation": "tag:mastodon.social,2025:objectId=12345:objectType=Conversation"
}

이런 하위 호환성 유지는 연합우주 생태계의 분열을 방지하고 사용자 경험을 개선하는 데 중요한 역할을 합니다.

향후 개발 방향: 하이브리드 접근법의 표준화

모범 사례 가이드라인

다중 전략 구현: 절대로 하나의 백필 방식에만 의존하지 마세요. 연합우주의 다양성과 불확실성을 고려할 때, 여러 전략을 조합하는 것이 필수적입니다. 각 전략은 서로 다른 상황에서 강점을 보이므로, 상황에 따라 적절한 전략을 선택할 수 있는 유연성을 확보해야 합니다.

예를 들어, 활발한 포럼 토론에서는 컨텍스트 소유자 방식이 효과적일 수 있지만, Mastodon의 일반적인 대화에서는 답글 트리 크롤링이 더 적합할 수 있습니다.
리소스 관리: 백필 작업은 상당한 서버 리소스를 소모할 수 있습니다. 특히 인기 있는 대화나 대규모 토론의 경우 수백 개의 네트워크 요청이 필요할 수 있습니다. 따라서 적절한 제한과 조절 메커니즘을 구현해야 합니다.
모니터링 및 로깅: 백필 시스템의 성능과 신뢰성을 지속적으로 모니터링하는 것이 중요합니다. 어떤 방식이 가장 효과적인지, 어떤 종류의 오류가 자주 발생하는지 등을 추적해야 합니다.

결론

핵심 통찰

앞으로의 방향

연합우주의 대화 백필 문제는 단순히 기술적인 문제를 넘어서 분산형 네트워크에서의 거버넌스, 모더레이션, 사용자 경험의 복합적인 문제입니다.

Fediverse Enhancement Proposal의 약자로, 연합우주의 개선사항을 제안하고 논의하기 위한 공식적인 문서 체계입니다. 새로운 기능이나 프로토콜 확장을 표준화하는 과정에서 사용됩니다. ↩︎

deutrino

@deutrino@mstdn.io

Fedilab users, vote on #Codeberg for these issues on my quality-of-life fixes wishlist! :blobwobble:

Add support for quoted posts: https://codeberg.org/tom79/Fedilab/issues/700

Make server announcements more visible: https://codeberg.org/tom79/Fedilab/issues/865

Implement grouping of boosts in timeline to a similar degree as Mastodon web client: https://codeberg.org/tom79/Fedilab/issues/857

Improve the UX of timeline refreshment: https://codeberg.org/tom79/Fedilab/issues/703#issuecomment-5040264

Support filters in Pleroma (and Akkoma): https://codeberg.org/tom79/Fedilab/issues/555

Fedify: an ActivityPub server framework

@fedify@hollo.social

Did you know? #Fedify provides #documentation optimized for LLMs through the llms.txt standard.

Available endpoints:

https://fedify.dev/llms.txt — Core documentation overview
https://fedify.dev/llms-full.txt — Complete documentation dump

Useful for training #AI assistants on #ActivityPub/#fediverse development, building documentation chatbots, or #LLM-powered dev tools.

#fedidev #RFC9421 #HTTPSignatures #HTTPMessageSignatures #CloudflareWorkers

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're excited to announce the release of #Fedify 1.6.1, which marks the beginning of the 1.6 series following the retraction of version 1.6.0. This release introduces significant new capabilities that expand Fedify's deployment options and enhance security compatibility across the #fediverse.

🌐 Cloudflare Workers support

Fedify 1.6 introduces first-class support for Cloudflare Workers, enabling #serverless deployment of #ActivityPub applications at the edge.

New components

WorkersKvStore: A key–value store implementation using Cloudflare's KV API for persistent storage in Workers environments
WorkersMessageQueue: A message queue implementation leveraging Cloudflare Queues for reliable message processing

Key features

Seamless integration with #Cloudflare's serverless runtime
Automatic handling of queue message processing through Workers' queue() method
Support for Node.js compatibility flag required for Fedify's cryptographic operations
Manual queue processing via Federation.processQueuedTask() method

For a complete working example, see the Cloudflare Workers example in the Fedify repository.

🏗️ Federation builder pattern

Fedify 1.6 introduces the FederationBuilder class and createFederationBuilder() function to support deferred federation instantiation. This pattern provides several benefits:

Deferred instantiation: Set up dispatchers and listeners before creating the federation object
Better code organization: Avoid circular dependencies and improve project structure
Cloudflare #Workers compatibility: Accommodates binding-based architectures where resources are passed as arguments rather than globals
Modular setup: Build complex federations piece by piece before instantiation

The builder pattern is particularly useful for large applications and environments like Cloudflare Workers where configuration data is only available at runtime.

🔐 HTTP Message Signatures (RFC 9421)

Fedify 1.6 implements the official HTTP Message Signatures standard (RFC 9421) specification, the final revision of the HTTP Signatures specification.

Double-knocking mechanism

To ensure maximum compatibility across the fediverse, Fedify 1.6 introduces an intelligent double-knocking mechanism:

Primary attempt: RFC 9421 (HTTP Message Signatures) for modern implementations
Fallback: Draft cavage version for legacy compatibility
Adaptive caching: The system remembers which version each server supports to optimize future requests

This approach ensures seamless communication with both modern and legacy ActivityPub implementations while positioning Fedify at the forefront of security standards.

Interoperability testing

The RFC 9421 implementation has been thoroughly tested for interoperability with existing ActivityPub implementations that support RFC 9421 signature verification:

Mitra 4.4.0: Successfully verified Fedify-generated RFC 9421 signatures
Mastodon 4.4.0 development version: Tested RFC 9421 signature verification against Fedify's implementation (refer to Mastodon PR #34814, though Mastodon 4.4.0 has not yet been released)

These tests confirm that other ActivityPub implementations can successfully verify RFC 9421 signatures generated by Fedify, ensuring proper federation as the ecosystem gradually adopts the official specification. While these implementations currently support verification of RFC 9421 signatures, they do not yet generate RFC 9421 signatures themselves—making Fedify one of the first ActivityPub implementations to support both generation and verification of the modern standard.

🔍 WebFinger enhancements

Dedicated WebFinger lookup

The new Context.lookupWebFinger() method provides direct access to WebFinger data, offering developers more granular control over account discovery and resource resolution beyond the higher-level Context.lookupObject() method.

🛠 Context API improvements

Context data replacement

The new Context.clone() method enables dynamic context data replacement, providing greater flexibility in request processing and data flow management. This is particularly useful for middleware implementations and complex request routing scenarios.

🚀 Migration considerations

Backward compatibility

Fedify 1.6 maintains full backward compatibility with existing applications. The new HTTP Message Signatures and double-knocking mechanisms work transparently without requiring any code changes.

Node.js version requirement

Important: Fedify 1.6 requires Node.js 22.0.0 or later for Node.js environments. This change does not affect applications using Deno or Bun runtimes. If you're currently using Node.js, please ensure your environment meets this requirement before upgrading.

New deployment options

For new deployments, consider leveraging Cloudflare Workers support for:

Global edge deployment with low latency
Serverless scaling and automatic resource management
Integration with Cloudflare's ecosystem of services

🎯 Looking forward

Fedify 1.6 represents a significant expansion of deployment possibilities while maintaining the framework's commitment to broad compatibility across the fediverse. The addition of Cloudflare Workers support opens new architectural patterns for federated applications, while the RFC 9421 implementation ensures Fedify stays current with emerging ActivityPub security standards.

For detailed migration guides, API documentation, and examples, please visit the Fedify documentation. Join our community on Matrix or Discord for support and discussions.

deutrino

@deutrino@mstdn.io

Fedilab users, vote on #Codeberg for these issues on my quality-of-life fixes wishlist! :blobwobble:

Add support for quoted posts: https://codeberg.org/tom79/Fedilab/issues/700

Make server announcements more visible: https://codeberg.org/tom79/Fedilab/issues/865

Implement grouping of boosts in timeline to a similar degree as Mastodon web client: https://codeberg.org/tom79/Fedilab/issues/857

Improve the UX of timeline refreshment: https://codeberg.org/tom79/Fedilab/issues/703#issuecomment-5040264

Support filters in Pleroma (and Akkoma): https://codeberg.org/tom79/Fedilab/issues/555

deutrino

@deutrino@mstdn.io

Fedilab users, vote on #Codeberg for these issues on my quality-of-life fixes wishlist! :blobwobble:

Add support for quoted posts: https://codeberg.org/tom79/Fedilab/issues/700

Make server announcements more visible: https://codeberg.org/tom79/Fedilab/issues/865

Implement grouping of boosts in timeline to a similar degree as Mastodon web client: https://codeberg.org/tom79/Fedilab/issues/857

Improve the UX of timeline refreshment: https://codeberg.org/tom79/Fedilab/issues/703#issuecomment-5040264

Support filters in Pleroma (and Akkoma): https://codeberg.org/tom79/Fedilab/issues/555

deutrino

@deutrino@mstdn.io

Fedilab users, vote on #Codeberg for these issues on my quality-of-life fixes wishlist! :blobwobble:

Add support for quoted posts: https://codeberg.org/tom79/Fedilab/issues/700

Make server announcements more visible: https://codeberg.org/tom79/Fedilab/issues/865

Implement grouping of boosts in timeline to a similar degree as Mastodon web client: https://codeberg.org/tom79/Fedilab/issues/857

Improve the UX of timeline refreshment: https://codeberg.org/tom79/Fedilab/issues/703#issuecomment-5040264

Support filters in Pleroma (and Akkoma): https://codeberg.org/tom79/Fedilab/issues/555

#fedidev #RFC9421 #HTTPSignatures #HTTPMessageSignatures #CloudflareWorkers

Fedify: an ActivityPub server framework

@fedify@hollo.social

🌐 Cloudflare Workers support

Fedify 1.6 introduces first-class support for Cloudflare Workers, enabling #serverless deployment of #ActivityPub applications at the edge.

New components

WorkersKvStore: A key–value store implementation using Cloudflare's KV API for persistent storage in Workers environments
WorkersMessageQueue: A message queue implementation leveraging Cloudflare Queues for reliable message processing

Key features

Seamless integration with #Cloudflare's serverless runtime
Automatic handling of queue message processing through Workers' queue() method
Support for Node.js compatibility flag required for Fedify's cryptographic operations
Manual queue processing via Federation.processQueuedTask() method

For a complete working example, see the Cloudflare Workers example in the Fedify repository.

🏗️ Federation builder pattern

Fedify 1.6 introduces the FederationBuilder class and createFederationBuilder() function to support deferred federation instantiation. This pattern provides several benefits:

Deferred instantiation: Set up dispatchers and listeners before creating the federation object
Better code organization: Avoid circular dependencies and improve project structure
Cloudflare #Workers compatibility: Accommodates binding-based architectures where resources are passed as arguments rather than globals
Modular setup: Build complex federations piece by piece before instantiation

The builder pattern is particularly useful for large applications and environments like Cloudflare Workers where configuration data is only available at runtime.

🔐 HTTP Message Signatures (RFC 9421)

Fedify 1.6 implements the official HTTP Message Signatures standard (RFC 9421) specification, the final revision of the HTTP Signatures specification.

Double-knocking mechanism

To ensure maximum compatibility across the fediverse, Fedify 1.6 introduces an intelligent double-knocking mechanism:

Primary attempt: RFC 9421 (HTTP Message Signatures) for modern implementations
Fallback: Draft cavage version for legacy compatibility
Adaptive caching: The system remembers which version each server supports to optimize future requests

This approach ensures seamless communication with both modern and legacy ActivityPub implementations while positioning Fedify at the forefront of security standards.

Interoperability testing

The RFC 9421 implementation has been thoroughly tested for interoperability with existing ActivityPub implementations that support RFC 9421 signature verification:

Mitra 4.4.0: Successfully verified Fedify-generated RFC 9421 signatures
Mastodon 4.4.0 development version: Tested RFC 9421 signature verification against Fedify's implementation (refer to Mastodon PR #34814, though Mastodon 4.4.0 has not yet been released)

🔍 WebFinger enhancements

Dedicated WebFinger lookup

🛠 Context API improvements

Context data replacement

🚀 Migration considerations

Backward compatibility

Fedify 1.6 maintains full backward compatibility with existing applications. The new HTTP Message Signatures and double-knocking mechanisms work transparently without requiring any code changes.

Node.js version requirement

New deployment options

For new deployments, consider leveraging Cloudflare Workers support for:

Global edge deployment with low latency
Serverless scaling and automatic resource management
Integration with Cloudflare's ecosystem of services

🎯 Looking forward

For detailed migration guides, API documentation, and examples, please visit the Fedify documentation. Join our community on Matrix or Discord for support and discussions.

Fedify: an ActivityPub server framework

@fedify@hollo.social

🌐 Cloudflare Workers support

Fedify 1.6 introduces first-class support for Cloudflare Workers, enabling #serverless deployment of #ActivityPub applications at the edge.

New components

WorkersKvStore: A key–value store implementation using Cloudflare's KV API for persistent storage in Workers environments
WorkersMessageQueue: A message queue implementation leveraging Cloudflare Queues for reliable message processing

Key features

Seamless integration with #Cloudflare's serverless runtime
Automatic handling of queue message processing through Workers' queue() method
Support for Node.js compatibility flag required for Fedify's cryptographic operations
Manual queue processing via Federation.processQueuedTask() method

For a complete working example, see the Cloudflare Workers example in the Fedify repository.

🏗️ Federation builder pattern

Fedify 1.6 introduces the FederationBuilder class and createFederationBuilder() function to support deferred federation instantiation. This pattern provides several benefits:

Deferred instantiation: Set up dispatchers and listeners before creating the federation object
Better code organization: Avoid circular dependencies and improve project structure
Cloudflare #Workers compatibility: Accommodates binding-based architectures where resources are passed as arguments rather than globals
Modular setup: Build complex federations piece by piece before instantiation

The builder pattern is particularly useful for large applications and environments like Cloudflare Workers where configuration data is only available at runtime.

🔐 HTTP Message Signatures (RFC 9421)

Fedify 1.6 implements the official HTTP Message Signatures standard (RFC 9421) specification, the final revision of the HTTP Signatures specification.

Double-knocking mechanism

To ensure maximum compatibility across the fediverse, Fedify 1.6 introduces an intelligent double-knocking mechanism:

Primary attempt: RFC 9421 (HTTP Message Signatures) for modern implementations
Fallback: Draft cavage version for legacy compatibility
Adaptive caching: The system remembers which version each server supports to optimize future requests

This approach ensures seamless communication with both modern and legacy ActivityPub implementations while positioning Fedify at the forefront of security standards.

Interoperability testing

The RFC 9421 implementation has been thoroughly tested for interoperability with existing ActivityPub implementations that support RFC 9421 signature verification:

Mitra 4.4.0: Successfully verified Fedify-generated RFC 9421 signatures
Mastodon 4.4.0 development version: Tested RFC 9421 signature verification against Fedify's implementation (refer to Mastodon PR #34814, though Mastodon 4.4.0 has not yet been released)

🔍 WebFinger enhancements

Dedicated WebFinger lookup

🛠 Context API improvements

Context data replacement

🚀 Migration considerations

Backward compatibility

Fedify 1.6 maintains full backward compatibility with existing applications. The new HTTP Message Signatures and double-knocking mechanisms work transparently without requiring any code changes.

Node.js version requirement

New deployment options

For new deployments, consider leveraging Cloudflare Workers support for:

Global edge deployment with low latency
Serverless scaling and automatic resource management
Integration with Cloudflare's ecosystem of services

🎯 Looking forward

For detailed migration guides, API documentation, and examples, please visit the Fedify documentation. Join our community on Matrix or Discord for support and discussions.

#fedidev #RFC9421 #HTTPSignatures #HTTPMessageSignatures #CloudflareWorkers

Fedify: an ActivityPub server framework

@fedify@hollo.social

🌐 Cloudflare Workers support

Fedify 1.6 introduces first-class support for Cloudflare Workers, enabling #serverless deployment of #ActivityPub applications at the edge.

New components

WorkersKvStore: A key–value store implementation using Cloudflare's KV API for persistent storage in Workers environments
WorkersMessageQueue: A message queue implementation leveraging Cloudflare Queues for reliable message processing

Key features

Seamless integration with #Cloudflare's serverless runtime
Automatic handling of queue message processing through Workers' queue() method
Support for Node.js compatibility flag required for Fedify's cryptographic operations
Manual queue processing via Federation.processQueuedTask() method

For a complete working example, see the Cloudflare Workers example in the Fedify repository.

🏗️ Federation builder pattern

Fedify 1.6 introduces the FederationBuilder class and createFederationBuilder() function to support deferred federation instantiation. This pattern provides several benefits:

Deferred instantiation: Set up dispatchers and listeners before creating the federation object
Better code organization: Avoid circular dependencies and improve project structure
Cloudflare #Workers compatibility: Accommodates binding-based architectures where resources are passed as arguments rather than globals
Modular setup: Build complex federations piece by piece before instantiation

The builder pattern is particularly useful for large applications and environments like Cloudflare Workers where configuration data is only available at runtime.

🔐 HTTP Message Signatures (RFC 9421)

Fedify 1.6 implements the official HTTP Message Signatures standard (RFC 9421) specification, the final revision of the HTTP Signatures specification.

Double-knocking mechanism

To ensure maximum compatibility across the fediverse, Fedify 1.6 introduces an intelligent double-knocking mechanism:

Primary attempt: RFC 9421 (HTTP Message Signatures) for modern implementations
Fallback: Draft cavage version for legacy compatibility
Adaptive caching: The system remembers which version each server supports to optimize future requests

This approach ensures seamless communication with both modern and legacy ActivityPub implementations while positioning Fedify at the forefront of security standards.

Interoperability testing

The RFC 9421 implementation has been thoroughly tested for interoperability with existing ActivityPub implementations that support RFC 9421 signature verification:

Mitra 4.4.0: Successfully verified Fedify-generated RFC 9421 signatures
Mastodon 4.4.0 development version: Tested RFC 9421 signature verification against Fedify's implementation (refer to Mastodon PR #34814, though Mastodon 4.4.0 has not yet been released)

🔍 WebFinger enhancements

Dedicated WebFinger lookup

🛠 Context API improvements

Context data replacement

🚀 Migration considerations

Backward compatibility

Fedify 1.6 maintains full backward compatibility with existing applications. The new HTTP Message Signatures and double-knocking mechanisms work transparently without requiring any code changes.

Node.js version requirement

New deployment options

For new deployments, consider leveraging Cloudflare Workers support for:

Global edge deployment with low latency
Serverless scaling and automatic resource management
Integration with Cloudflare's ecosystem of services

🎯 Looking forward

For detailed migration guides, API documentation, and examples, please visit the Fedify documentation. Join our community on Matrix or Discord for support and discussions.

#fedidev #RFC9421 #HTTPSignatures #HTTPMessageSignatures #CloudflareWorkers

Fedify: an ActivityPub server framework

@fedify@hollo.social

🌐 Cloudflare Workers support

Fedify 1.6 introduces first-class support for Cloudflare Workers, enabling #serverless deployment of #ActivityPub applications at the edge.

New components

WorkersKvStore: A key–value store implementation using Cloudflare's KV API for persistent storage in Workers environments
WorkersMessageQueue: A message queue implementation leveraging Cloudflare Queues for reliable message processing

Key features

Seamless integration with #Cloudflare's serverless runtime
Automatic handling of queue message processing through Workers' queue() method
Support for Node.js compatibility flag required for Fedify's cryptographic operations
Manual queue processing via Federation.processQueuedTask() method

For a complete working example, see the Cloudflare Workers example in the Fedify repository.

🏗️ Federation builder pattern

Fedify 1.6 introduces the FederationBuilder class and createFederationBuilder() function to support deferred federation instantiation. This pattern provides several benefits:

Deferred instantiation: Set up dispatchers and listeners before creating the federation object
Better code organization: Avoid circular dependencies and improve project structure
Cloudflare #Workers compatibility: Accommodates binding-based architectures where resources are passed as arguments rather than globals
Modular setup: Build complex federations piece by piece before instantiation

The builder pattern is particularly useful for large applications and environments like Cloudflare Workers where configuration data is only available at runtime.

🔐 HTTP Message Signatures (RFC 9421)

Fedify 1.6 implements the official HTTP Message Signatures standard (RFC 9421) specification, the final revision of the HTTP Signatures specification.

Double-knocking mechanism

To ensure maximum compatibility across the fediverse, Fedify 1.6 introduces an intelligent double-knocking mechanism:

Primary attempt: RFC 9421 (HTTP Message Signatures) for modern implementations
Fallback: Draft cavage version for legacy compatibility
Adaptive caching: The system remembers which version each server supports to optimize future requests

This approach ensures seamless communication with both modern and legacy ActivityPub implementations while positioning Fedify at the forefront of security standards.

Interoperability testing

The RFC 9421 implementation has been thoroughly tested for interoperability with existing ActivityPub implementations that support RFC 9421 signature verification:

Mitra 4.4.0: Successfully verified Fedify-generated RFC 9421 signatures
Mastodon 4.4.0 development version: Tested RFC 9421 signature verification against Fedify's implementation (refer to Mastodon PR #34814, though Mastodon 4.4.0 has not yet been released)

🔍 WebFinger enhancements

Dedicated WebFinger lookup

🛠 Context API improvements

Context data replacement

🚀 Migration considerations

Backward compatibility

Fedify 1.6 maintains full backward compatibility with existing applications. The new HTTP Message Signatures and double-knocking mechanisms work transparently without requiring any code changes.

Node.js version requirement

New deployment options

For new deployments, consider leveraging Cloudflare Workers support for:

Global edge deployment with low latency
Serverless scaling and automatic resource management
Integration with Cloudflare's ecosystem of services

🎯 Looking forward

For detailed migration guides, API documentation, and examples, please visit the Fedify documentation. Join our community on Matrix or Discord for support and discussions.

#fedidev #RFC9421 #HTTPSignatures #HTTPMessageSignatures #CloudflareWorkers

Fedify: an ActivityPub server framework

@fedify@hollo.social

🌐 Cloudflare Workers support

Fedify 1.6 introduces first-class support for Cloudflare Workers, enabling #serverless deployment of #ActivityPub applications at the edge.

New components

WorkersKvStore: A key–value store implementation using Cloudflare's KV API for persistent storage in Workers environments
WorkersMessageQueue: A message queue implementation leveraging Cloudflare Queues for reliable message processing

Key features

Seamless integration with #Cloudflare's serverless runtime
Automatic handling of queue message processing through Workers' queue() method
Support for Node.js compatibility flag required for Fedify's cryptographic operations
Manual queue processing via Federation.processQueuedTask() method

For a complete working example, see the Cloudflare Workers example in the Fedify repository.

🏗️ Federation builder pattern

Fedify 1.6 introduces the FederationBuilder class and createFederationBuilder() function to support deferred federation instantiation. This pattern provides several benefits:

Deferred instantiation: Set up dispatchers and listeners before creating the federation object
Better code organization: Avoid circular dependencies and improve project structure
Cloudflare #Workers compatibility: Accommodates binding-based architectures where resources are passed as arguments rather than globals
Modular setup: Build complex federations piece by piece before instantiation

The builder pattern is particularly useful for large applications and environments like Cloudflare Workers where configuration data is only available at runtime.

🔐 HTTP Message Signatures (RFC 9421)

Fedify 1.6 implements the official HTTP Message Signatures standard (RFC 9421) specification, the final revision of the HTTP Signatures specification.

Double-knocking mechanism

To ensure maximum compatibility across the fediverse, Fedify 1.6 introduces an intelligent double-knocking mechanism:

Primary attempt: RFC 9421 (HTTP Message Signatures) for modern implementations
Fallback: Draft cavage version for legacy compatibility
Adaptive caching: The system remembers which version each server supports to optimize future requests

This approach ensures seamless communication with both modern and legacy ActivityPub implementations while positioning Fedify at the forefront of security standards.

Interoperability testing

The RFC 9421 implementation has been thoroughly tested for interoperability with existing ActivityPub implementations that support RFC 9421 signature verification:

Mitra 4.4.0: Successfully verified Fedify-generated RFC 9421 signatures
Mastodon 4.4.0 development version: Tested RFC 9421 signature verification against Fedify's implementation (refer to Mastodon PR #34814, though Mastodon 4.4.0 has not yet been released)

🔍 WebFinger enhancements

Dedicated WebFinger lookup

🛠 Context API improvements

Context data replacement

🚀 Migration considerations

Backward compatibility

Fedify 1.6 maintains full backward compatibility with existing applications. The new HTTP Message Signatures and double-knocking mechanisms work transparently without requiring any code changes.

Node.js version requirement

New deployment options

For new deployments, consider leveraging Cloudflare Workers support for:

Global edge deployment with low latency
Serverless scaling and automatic resource management
Integration with Cloudflare's ecosystem of services

🎯 Looking forward

For detailed migration guides, API documentation, and examples, please visit the Fedify documentation. Join our community on Matrix or Discord for support and discussions.

#fedidev #RFC9421 #HTTPSignatures #HTTPMessageSignatures #CloudflareWorkers

Fedify: an ActivityPub server framework

@fedify@hollo.social

🌐 Cloudflare Workers support

Fedify 1.6 introduces first-class support for Cloudflare Workers, enabling #serverless deployment of #ActivityPub applications at the edge.

New components

WorkersKvStore: A key–value store implementation using Cloudflare's KV API for persistent storage in Workers environments
WorkersMessageQueue: A message queue implementation leveraging Cloudflare Queues for reliable message processing

Key features

Seamless integration with #Cloudflare's serverless runtime
Automatic handling of queue message processing through Workers' queue() method
Support for Node.js compatibility flag required for Fedify's cryptographic operations
Manual queue processing via Federation.processQueuedTask() method

For a complete working example, see the Cloudflare Workers example in the Fedify repository.

🏗️ Federation builder pattern

Fedify 1.6 introduces the FederationBuilder class and createFederationBuilder() function to support deferred federation instantiation. This pattern provides several benefits:

Deferred instantiation: Set up dispatchers and listeners before creating the federation object
Better code organization: Avoid circular dependencies and improve project structure
Cloudflare #Workers compatibility: Accommodates binding-based architectures where resources are passed as arguments rather than globals
Modular setup: Build complex federations piece by piece before instantiation

The builder pattern is particularly useful for large applications and environments like Cloudflare Workers where configuration data is only available at runtime.

🔐 HTTP Message Signatures (RFC 9421)

Fedify 1.6 implements the official HTTP Message Signatures standard (RFC 9421) specification, the final revision of the HTTP Signatures specification.

Double-knocking mechanism

To ensure maximum compatibility across the fediverse, Fedify 1.6 introduces an intelligent double-knocking mechanism:

Primary attempt: RFC 9421 (HTTP Message Signatures) for modern implementations
Fallback: Draft cavage version for legacy compatibility
Adaptive caching: The system remembers which version each server supports to optimize future requests

This approach ensures seamless communication with both modern and legacy ActivityPub implementations while positioning Fedify at the forefront of security standards.

Interoperability testing

The RFC 9421 implementation has been thoroughly tested for interoperability with existing ActivityPub implementations that support RFC 9421 signature verification:

Mitra 4.4.0: Successfully verified Fedify-generated RFC 9421 signatures
Mastodon 4.4.0 development version: Tested RFC 9421 signature verification against Fedify's implementation (refer to Mastodon PR #34814, though Mastodon 4.4.0 has not yet been released)

🔍 WebFinger enhancements

Dedicated WebFinger lookup

🛠 Context API improvements

Context data replacement

🚀 Migration considerations

Backward compatibility

Fedify 1.6 maintains full backward compatibility with existing applications. The new HTTP Message Signatures and double-knocking mechanisms work transparently without requiring any code changes.

Node.js version requirement

New deployment options

For new deployments, consider leveraging Cloudflare Workers support for:

Global edge deployment with low latency
Serverless scaling and automatic resource management
Integration with Cloudflare's ecosystem of services

🎯 Looking forward

For detailed migration guides, API documentation, and examples, please visit the Fedify documentation. Join our community on Matrix or Discord for support and discussions.

#fedidev #RFC9421 #HTTPSignatures #HTTPMessageSignatures #CloudflareWorkers

Fedify: an ActivityPub server framework

@fedify@hollo.social

🌐 Cloudflare Workers support

Fedify 1.6 introduces first-class support for Cloudflare Workers, enabling #serverless deployment of #ActivityPub applications at the edge.

New components

WorkersKvStore: A key–value store implementation using Cloudflare's KV API for persistent storage in Workers environments
WorkersMessageQueue: A message queue implementation leveraging Cloudflare Queues for reliable message processing

Key features

Seamless integration with #Cloudflare's serverless runtime
Automatic handling of queue message processing through Workers' queue() method
Support for Node.js compatibility flag required for Fedify's cryptographic operations
Manual queue processing via Federation.processQueuedTask() method

For a complete working example, see the Cloudflare Workers example in the Fedify repository.

🏗️ Federation builder pattern

Fedify 1.6 introduces the FederationBuilder class and createFederationBuilder() function to support deferred federation instantiation. This pattern provides several benefits:

Deferred instantiation: Set up dispatchers and listeners before creating the federation object
Better code organization: Avoid circular dependencies and improve project structure
Cloudflare #Workers compatibility: Accommodates binding-based architectures where resources are passed as arguments rather than globals
Modular setup: Build complex federations piece by piece before instantiation

The builder pattern is particularly useful for large applications and environments like Cloudflare Workers where configuration data is only available at runtime.

🔐 HTTP Message Signatures (RFC 9421)

Fedify 1.6 implements the official HTTP Message Signatures standard (RFC 9421) specification, the final revision of the HTTP Signatures specification.

Double-knocking mechanism

To ensure maximum compatibility across the fediverse, Fedify 1.6 introduces an intelligent double-knocking mechanism:

Primary attempt: RFC 9421 (HTTP Message Signatures) for modern implementations
Fallback: Draft cavage version for legacy compatibility
Adaptive caching: The system remembers which version each server supports to optimize future requests

This approach ensures seamless communication with both modern and legacy ActivityPub implementations while positioning Fedify at the forefront of security standards.

Interoperability testing

The RFC 9421 implementation has been thoroughly tested for interoperability with existing ActivityPub implementations that support RFC 9421 signature verification:

Mitra 4.4.0: Successfully verified Fedify-generated RFC 9421 signatures
Mastodon 4.4.0 development version: Tested RFC 9421 signature verification against Fedify's implementation (refer to Mastodon PR #34814, though Mastodon 4.4.0 has not yet been released)

🔍 WebFinger enhancements

Dedicated WebFinger lookup

🛠 Context API improvements

Context data replacement

🚀 Migration considerations

Backward compatibility

Fedify 1.6 maintains full backward compatibility with existing applications. The new HTTP Message Signatures and double-knocking mechanisms work transparently without requiring any code changes.

Node.js version requirement

New deployment options

For new deployments, consider leveraging Cloudflare Workers support for:

Global edge deployment with low latency
Serverless scaling and automatic resource management
Integration with Cloudflare's ecosystem of services

🎯 Looking forward

For detailed migration guides, API documentation, and examples, please visit the Fedify documentation. Join our community on Matrix or Discord for support and discussions.

#fedidev #RFC9421 #HTTPSignatures #HTTPMessageSignatures #CloudflareWorkers

Fedify: an ActivityPub server framework

@fedify@hollo.social

🌐 Cloudflare Workers support

Fedify 1.6 introduces first-class support for Cloudflare Workers, enabling #serverless deployment of #ActivityPub applications at the edge.

New components

WorkersKvStore: A key–value store implementation using Cloudflare's KV API for persistent storage in Workers environments
WorkersMessageQueue: A message queue implementation leveraging Cloudflare Queues for reliable message processing

Key features

Seamless integration with #Cloudflare's serverless runtime
Automatic handling of queue message processing through Workers' queue() method
Support for Node.js compatibility flag required for Fedify's cryptographic operations
Manual queue processing via Federation.processQueuedTask() method

For a complete working example, see the Cloudflare Workers example in the Fedify repository.

🏗️ Federation builder pattern

Fedify 1.6 introduces the FederationBuilder class and createFederationBuilder() function to support deferred federation instantiation. This pattern provides several benefits:

Deferred instantiation: Set up dispatchers and listeners before creating the federation object
Better code organization: Avoid circular dependencies and improve project structure
Cloudflare #Workers compatibility: Accommodates binding-based architectures where resources are passed as arguments rather than globals
Modular setup: Build complex federations piece by piece before instantiation

The builder pattern is particularly useful for large applications and environments like Cloudflare Workers where configuration data is only available at runtime.

🔐 HTTP Message Signatures (RFC 9421)

Fedify 1.6 implements the official HTTP Message Signatures standard (RFC 9421) specification, the final revision of the HTTP Signatures specification.

Double-knocking mechanism

To ensure maximum compatibility across the fediverse, Fedify 1.6 introduces an intelligent double-knocking mechanism:

Primary attempt: RFC 9421 (HTTP Message Signatures) for modern implementations
Fallback: Draft cavage version for legacy compatibility
Adaptive caching: The system remembers which version each server supports to optimize future requests

This approach ensures seamless communication with both modern and legacy ActivityPub implementations while positioning Fedify at the forefront of security standards.

Interoperability testing

The RFC 9421 implementation has been thoroughly tested for interoperability with existing ActivityPub implementations that support RFC 9421 signature verification:

Mitra 4.4.0: Successfully verified Fedify-generated RFC 9421 signatures
Mastodon 4.4.0 development version: Tested RFC 9421 signature verification against Fedify's implementation (refer to Mastodon PR #34814, though Mastodon 4.4.0 has not yet been released)

🔍 WebFinger enhancements

Dedicated WebFinger lookup

🛠 Context API improvements

Context data replacement

🚀 Migration considerations

Backward compatibility

Fedify 1.6 maintains full backward compatibility with existing applications. The new HTTP Message Signatures and double-knocking mechanisms work transparently without requiring any code changes.

Node.js version requirement

New deployment options

For new deployments, consider leveraging Cloudflare Workers support for:

Global edge deployment with low latency
Serverless scaling and automatic resource management
Integration with Cloudflare's ecosystem of services

🎯 Looking forward

For detailed migration guides, API documentation, and examples, please visit the Fedify documentation. Join our community on Matrix or Discord for support and discussions.

#fedidev #RFC9421 #HTTPSignatures #HTTPMessageSignatures #CloudflareWorkers

Fedify: an ActivityPub server framework

@fedify@hollo.social

🌐 Cloudflare Workers support

Fedify 1.6 introduces first-class support for Cloudflare Workers, enabling #serverless deployment of #ActivityPub applications at the edge.

New components

WorkersKvStore: A key–value store implementation using Cloudflare's KV API for persistent storage in Workers environments
WorkersMessageQueue: A message queue implementation leveraging Cloudflare Queues for reliable message processing

Key features

Seamless integration with #Cloudflare's serverless runtime
Automatic handling of queue message processing through Workers' queue() method
Support for Node.js compatibility flag required for Fedify's cryptographic operations
Manual queue processing via Federation.processQueuedTask() method

For a complete working example, see the Cloudflare Workers example in the Fedify repository.

🏗️ Federation builder pattern

Fedify 1.6 introduces the FederationBuilder class and createFederationBuilder() function to support deferred federation instantiation. This pattern provides several benefits:

Deferred instantiation: Set up dispatchers and listeners before creating the federation object
Better code organization: Avoid circular dependencies and improve project structure
Cloudflare #Workers compatibility: Accommodates binding-based architectures where resources are passed as arguments rather than globals
Modular setup: Build complex federations piece by piece before instantiation

The builder pattern is particularly useful for large applications and environments like Cloudflare Workers where configuration data is only available at runtime.

🔐 HTTP Message Signatures (RFC 9421)

Fedify 1.6 implements the official HTTP Message Signatures standard (RFC 9421) specification, the final revision of the HTTP Signatures specification.

Double-knocking mechanism

To ensure maximum compatibility across the fediverse, Fedify 1.6 introduces an intelligent double-knocking mechanism:

Primary attempt: RFC 9421 (HTTP Message Signatures) for modern implementations
Fallback: Draft cavage version for legacy compatibility
Adaptive caching: The system remembers which version each server supports to optimize future requests

This approach ensures seamless communication with both modern and legacy ActivityPub implementations while positioning Fedify at the forefront of security standards.

Interoperability testing

The RFC 9421 implementation has been thoroughly tested for interoperability with existing ActivityPub implementations that support RFC 9421 signature verification:

Mitra 4.4.0: Successfully verified Fedify-generated RFC 9421 signatures
Mastodon 4.4.0 development version: Tested RFC 9421 signature verification against Fedify's implementation (refer to Mastodon PR #34814, though Mastodon 4.4.0 has not yet been released)

🔍 WebFinger enhancements

Dedicated WebFinger lookup

🛠 Context API improvements

Context data replacement

🚀 Migration considerations

Backward compatibility

Fedify 1.6 maintains full backward compatibility with existing applications. The new HTTP Message Signatures and double-knocking mechanisms work transparently without requiring any code changes.

Node.js version requirement

New deployment options

For new deployments, consider leveraging Cloudflare Workers support for:

Global edge deployment with low latency
Serverless scaling and automatic resource management
Integration with Cloudflare's ecosystem of services

🎯 Looking forward

For detailed migration guides, API documentation, and examples, please visit the Fedify documentation. Join our community on Matrix or Discord for support and discussions.

#fedidev #RFC9421 #HTTPSignatures #HTTPMessageSignatures #CloudflareWorkers

Fedify: an ActivityPub server framework

@fedify@hollo.social

🌐 Cloudflare Workers support

Fedify 1.6 introduces first-class support for Cloudflare Workers, enabling #serverless deployment of #ActivityPub applications at the edge.

New components

WorkersKvStore: A key–value store implementation using Cloudflare's KV API for persistent storage in Workers environments
WorkersMessageQueue: A message queue implementation leveraging Cloudflare Queues for reliable message processing

Key features

Seamless integration with #Cloudflare's serverless runtime
Automatic handling of queue message processing through Workers' queue() method
Support for Node.js compatibility flag required for Fedify's cryptographic operations
Manual queue processing via Federation.processQueuedTask() method

For a complete working example, see the Cloudflare Workers example in the Fedify repository.

🏗️ Federation builder pattern

Fedify 1.6 introduces the FederationBuilder class and createFederationBuilder() function to support deferred federation instantiation. This pattern provides several benefits:

Deferred instantiation: Set up dispatchers and listeners before creating the federation object
Better code organization: Avoid circular dependencies and improve project structure
Cloudflare #Workers compatibility: Accommodates binding-based architectures where resources are passed as arguments rather than globals
Modular setup: Build complex federations piece by piece before instantiation

The builder pattern is particularly useful for large applications and environments like Cloudflare Workers where configuration data is only available at runtime.

🔐 HTTP Message Signatures (RFC 9421)

Fedify 1.6 implements the official HTTP Message Signatures standard (RFC 9421) specification, the final revision of the HTTP Signatures specification.

Double-knocking mechanism

To ensure maximum compatibility across the fediverse, Fedify 1.6 introduces an intelligent double-knocking mechanism:

Primary attempt: RFC 9421 (HTTP Message Signatures) for modern implementations
Fallback: Draft cavage version for legacy compatibility
Adaptive caching: The system remembers which version each server supports to optimize future requests

This approach ensures seamless communication with both modern and legacy ActivityPub implementations while positioning Fedify at the forefront of security standards.

Interoperability testing

The RFC 9421 implementation has been thoroughly tested for interoperability with existing ActivityPub implementations that support RFC 9421 signature verification:

Mitra 4.4.0: Successfully verified Fedify-generated RFC 9421 signatures
Mastodon 4.4.0 development version: Tested RFC 9421 signature verification against Fedify's implementation (refer to Mastodon PR #34814, though Mastodon 4.4.0 has not yet been released)

🔍 WebFinger enhancements

Dedicated WebFinger lookup

🛠 Context API improvements

Context data replacement

🚀 Migration considerations

Backward compatibility

Fedify 1.6 maintains full backward compatibility with existing applications. The new HTTP Message Signatures and double-knocking mechanisms work transparently without requiring any code changes.

Node.js version requirement

New deployment options

For new deployments, consider leveraging Cloudflare Workers support for:

Global edge deployment with low latency
Serverless scaling and automatic resource management
Integration with Cloudflare's ecosystem of services

🎯 Looking forward

For detailed migration guides, API documentation, and examples, please visit the Fedify documentation. Join our community on Matrix or Discord for support and discussions.

#fedidev #RFC9421 #HTTPSignatures #HTTPMessageSignatures #CloudflareWorkers

Fedify: an ActivityPub server framework

@fedify@hollo.social

🌐 Cloudflare Workers support

Fedify 1.6 introduces first-class support for Cloudflare Workers, enabling #serverless deployment of #ActivityPub applications at the edge.

New components

WorkersKvStore: A key–value store implementation using Cloudflare's KV API for persistent storage in Workers environments
WorkersMessageQueue: A message queue implementation leveraging Cloudflare Queues for reliable message processing

Key features

Seamless integration with #Cloudflare's serverless runtime
Automatic handling of queue message processing through Workers' queue() method
Support for Node.js compatibility flag required for Fedify's cryptographic operations
Manual queue processing via Federation.processQueuedTask() method

For a complete working example, see the Cloudflare Workers example in the Fedify repository.

🏗️ Federation builder pattern

Fedify 1.6 introduces the FederationBuilder class and createFederationBuilder() function to support deferred federation instantiation. This pattern provides several benefits:

Deferred instantiation: Set up dispatchers and listeners before creating the federation object
Better code organization: Avoid circular dependencies and improve project structure
Cloudflare #Workers compatibility: Accommodates binding-based architectures where resources are passed as arguments rather than globals
Modular setup: Build complex federations piece by piece before instantiation

The builder pattern is particularly useful for large applications and environments like Cloudflare Workers where configuration data is only available at runtime.

🔐 HTTP Message Signatures (RFC 9421)

Fedify 1.6 implements the official HTTP Message Signatures standard (RFC 9421) specification, the final revision of the HTTP Signatures specification.

Double-knocking mechanism

To ensure maximum compatibility across the fediverse, Fedify 1.6 introduces an intelligent double-knocking mechanism:

Primary attempt: RFC 9421 (HTTP Message Signatures) for modern implementations
Fallback: Draft cavage version for legacy compatibility
Adaptive caching: The system remembers which version each server supports to optimize future requests

This approach ensures seamless communication with both modern and legacy ActivityPub implementations while positioning Fedify at the forefront of security standards.

Interoperability testing

The RFC 9421 implementation has been thoroughly tested for interoperability with existing ActivityPub implementations that support RFC 9421 signature verification:

Mitra 4.4.0: Successfully verified Fedify-generated RFC 9421 signatures
Mastodon 4.4.0 development version: Tested RFC 9421 signature verification against Fedify's implementation (refer to Mastodon PR #34814, though Mastodon 4.4.0 has not yet been released)

🔍 WebFinger enhancements

Dedicated WebFinger lookup

🛠 Context API improvements

Context data replacement

🚀 Migration considerations

Backward compatibility

Fedify 1.6 maintains full backward compatibility with existing applications. The new HTTP Message Signatures and double-knocking mechanisms work transparently without requiring any code changes.

Node.js version requirement

New deployment options

For new deployments, consider leveraging Cloudflare Workers support for:

Global edge deployment with low latency
Serverless scaling and automatic resource management
Integration with Cloudflare's ecosystem of services

🎯 Looking forward

For detailed migration guides, API documentation, and examples, please visit the Fedify documentation. Join our community on Matrix or Discord for support and discussions.

#fedidev #RFC9421 #HTTPSignatures #HTTPMessageSignatures #CloudflareWorkers

Fedify: an ActivityPub server framework

@fedify@hollo.social

🌐 Cloudflare Workers support

Fedify 1.6 introduces first-class support for Cloudflare Workers, enabling #serverless deployment of #ActivityPub applications at the edge.

New components

WorkersKvStore: A key–value store implementation using Cloudflare's KV API for persistent storage in Workers environments
WorkersMessageQueue: A message queue implementation leveraging Cloudflare Queues for reliable message processing

Key features

Seamless integration with #Cloudflare's serverless runtime
Automatic handling of queue message processing through Workers' queue() method
Support for Node.js compatibility flag required for Fedify's cryptographic operations
Manual queue processing via Federation.processQueuedTask() method

For a complete working example, see the Cloudflare Workers example in the Fedify repository.

🏗️ Federation builder pattern

Fedify 1.6 introduces the FederationBuilder class and createFederationBuilder() function to support deferred federation instantiation. This pattern provides several benefits:

Deferred instantiation: Set up dispatchers and listeners before creating the federation object
Better code organization: Avoid circular dependencies and improve project structure
Cloudflare #Workers compatibility: Accommodates binding-based architectures where resources are passed as arguments rather than globals
Modular setup: Build complex federations piece by piece before instantiation

The builder pattern is particularly useful for large applications and environments like Cloudflare Workers where configuration data is only available at runtime.

🔐 HTTP Message Signatures (RFC 9421)

Fedify 1.6 implements the official HTTP Message Signatures standard (RFC 9421) specification, the final revision of the HTTP Signatures specification.

Double-knocking mechanism

To ensure maximum compatibility across the fediverse, Fedify 1.6 introduces an intelligent double-knocking mechanism:

Primary attempt: RFC 9421 (HTTP Message Signatures) for modern implementations
Fallback: Draft cavage version for legacy compatibility
Adaptive caching: The system remembers which version each server supports to optimize future requests

This approach ensures seamless communication with both modern and legacy ActivityPub implementations while positioning Fedify at the forefront of security standards.

Interoperability testing

The RFC 9421 implementation has been thoroughly tested for interoperability with existing ActivityPub implementations that support RFC 9421 signature verification:

Mitra 4.4.0: Successfully verified Fedify-generated RFC 9421 signatures
Mastodon 4.4.0 development version: Tested RFC 9421 signature verification against Fedify's implementation (refer to Mastodon PR #34814, though Mastodon 4.4.0 has not yet been released)

🔍 WebFinger enhancements

Dedicated WebFinger lookup

🛠 Context API improvements

Context data replacement

🚀 Migration considerations

Backward compatibility

Fedify 1.6 maintains full backward compatibility with existing applications. The new HTTP Message Signatures and double-knocking mechanisms work transparently without requiring any code changes.

Node.js version requirement

New deployment options

For new deployments, consider leveraging Cloudflare Workers support for:

Global edge deployment with low latency
Serverless scaling and automatic resource management
Integration with Cloudflare's ecosystem of services

🎯 Looking forward

For detailed migration guides, API documentation, and examples, please visit the Fedify documentation. Join our community on Matrix or Discord for support and discussions.

#fedidev #RFC9421 #HTTPSignatures #HTTPMessageSignatures #CloudflareWorkers

Fedify: an ActivityPub server framework

@fedify@hollo.social

🌐 Cloudflare Workers support

Fedify 1.6 introduces first-class support for Cloudflare Workers, enabling #serverless deployment of #ActivityPub applications at the edge.

New components

WorkersKvStore: A key–value store implementation using Cloudflare's KV API for persistent storage in Workers environments
WorkersMessageQueue: A message queue implementation leveraging Cloudflare Queues for reliable message processing

Key features

Seamless integration with #Cloudflare's serverless runtime
Automatic handling of queue message processing through Workers' queue() method
Support for Node.js compatibility flag required for Fedify's cryptographic operations
Manual queue processing via Federation.processQueuedTask() method

For a complete working example, see the Cloudflare Workers example in the Fedify repository.

🏗️ Federation builder pattern

Fedify 1.6 introduces the FederationBuilder class and createFederationBuilder() function to support deferred federation instantiation. This pattern provides several benefits:

Deferred instantiation: Set up dispatchers and listeners before creating the federation object
Better code organization: Avoid circular dependencies and improve project structure
Cloudflare #Workers compatibility: Accommodates binding-based architectures where resources are passed as arguments rather than globals
Modular setup: Build complex federations piece by piece before instantiation

The builder pattern is particularly useful for large applications and environments like Cloudflare Workers where configuration data is only available at runtime.

🔐 HTTP Message Signatures (RFC 9421)

Fedify 1.6 implements the official HTTP Message Signatures standard (RFC 9421) specification, the final revision of the HTTP Signatures specification.

Double-knocking mechanism

To ensure maximum compatibility across the fediverse, Fedify 1.6 introduces an intelligent double-knocking mechanism:

Primary attempt: RFC 9421 (HTTP Message Signatures) for modern implementations
Fallback: Draft cavage version for legacy compatibility
Adaptive caching: The system remembers which version each server supports to optimize future requests

This approach ensures seamless communication with both modern and legacy ActivityPub implementations while positioning Fedify at the forefront of security standards.

Interoperability testing

The RFC 9421 implementation has been thoroughly tested for interoperability with existing ActivityPub implementations that support RFC 9421 signature verification:

Mitra 4.4.0: Successfully verified Fedify-generated RFC 9421 signatures
Mastodon 4.4.0 development version: Tested RFC 9421 signature verification against Fedify's implementation (refer to Mastodon PR #34814, though Mastodon 4.4.0 has not yet been released)

🔍 WebFinger enhancements

Dedicated WebFinger lookup

🛠 Context API improvements

Context data replacement

🚀 Migration considerations

Backward compatibility

Fedify 1.6 maintains full backward compatibility with existing applications. The new HTTP Message Signatures and double-knocking mechanisms work transparently without requiring any code changes.

Node.js version requirement

New deployment options

For new deployments, consider leveraging Cloudflare Workers support for:

Global edge deployment with low latency
Serverless scaling and automatic resource management
Integration with Cloudflare's ecosystem of services

🎯 Looking forward

For detailed migration guides, API documentation, and examples, please visit the Fedify documentation. Join our community on Matrix or Discord for support and discussions.

#fedidev #RFC9421 #HTTPSignatures #HTTPMessageSignatures #CloudflareWorkers

Fedify: an ActivityPub server framework

@fedify@hollo.social

🌐 Cloudflare Workers support

Fedify 1.6 introduces first-class support for Cloudflare Workers, enabling #serverless deployment of #ActivityPub applications at the edge.

New components

WorkersKvStore: A key–value store implementation using Cloudflare's KV API for persistent storage in Workers environments
WorkersMessageQueue: A message queue implementation leveraging Cloudflare Queues for reliable message processing

Key features

Seamless integration with #Cloudflare's serverless runtime
Automatic handling of queue message processing through Workers' queue() method
Support for Node.js compatibility flag required for Fedify's cryptographic operations
Manual queue processing via Federation.processQueuedTask() method

For a complete working example, see the Cloudflare Workers example in the Fedify repository.

🏗️ Federation builder pattern

Fedify 1.6 introduces the FederationBuilder class and createFederationBuilder() function to support deferred federation instantiation. This pattern provides several benefits:

Deferred instantiation: Set up dispatchers and listeners before creating the federation object
Better code organization: Avoid circular dependencies and improve project structure
Cloudflare #Workers compatibility: Accommodates binding-based architectures where resources are passed as arguments rather than globals
Modular setup: Build complex federations piece by piece before instantiation

The builder pattern is particularly useful for large applications and environments like Cloudflare Workers where configuration data is only available at runtime.

🔐 HTTP Message Signatures (RFC 9421)

Fedify 1.6 implements the official HTTP Message Signatures standard (RFC 9421) specification, the final revision of the HTTP Signatures specification.

Double-knocking mechanism

To ensure maximum compatibility across the fediverse, Fedify 1.6 introduces an intelligent double-knocking mechanism:

Primary attempt: RFC 9421 (HTTP Message Signatures) for modern implementations
Fallback: Draft cavage version for legacy compatibility
Adaptive caching: The system remembers which version each server supports to optimize future requests

This approach ensures seamless communication with both modern and legacy ActivityPub implementations while positioning Fedify at the forefront of security standards.

Interoperability testing

The RFC 9421 implementation has been thoroughly tested for interoperability with existing ActivityPub implementations that support RFC 9421 signature verification:

Mitra 4.4.0: Successfully verified Fedify-generated RFC 9421 signatures
Mastodon 4.4.0 development version: Tested RFC 9421 signature verification against Fedify's implementation (refer to Mastodon PR #34814, though Mastodon 4.4.0 has not yet been released)

🔍 WebFinger enhancements

Dedicated WebFinger lookup

🛠 Context API improvements

Context data replacement

🚀 Migration considerations

Backward compatibility

Fedify 1.6 maintains full backward compatibility with existing applications. The new HTTP Message Signatures and double-knocking mechanisms work transparently without requiring any code changes.

Node.js version requirement

New deployment options

For new deployments, consider leveraging Cloudflare Workers support for:

Global edge deployment with low latency
Serverless scaling and automatic resource management
Integration with Cloudflare's ecosystem of services

🎯 Looking forward

For detailed migration guides, API documentation, and examples, please visit the Fedify documentation. Join our community on Matrix or Discord for support and discussions.

#fedidev #RFC9421 #HTTPSignatures #HTTPMessageSignatures #CloudflareWorkers

Fedify: an ActivityPub server framework

@fedify@hollo.social

🌐 Cloudflare Workers support

Fedify 1.6 introduces first-class support for Cloudflare Workers, enabling #serverless deployment of #ActivityPub applications at the edge.

New components

WorkersKvStore: A key–value store implementation using Cloudflare's KV API for persistent storage in Workers environments
WorkersMessageQueue: A message queue implementation leveraging Cloudflare Queues for reliable message processing

Key features

Seamless integration with #Cloudflare's serverless runtime
Automatic handling of queue message processing through Workers' queue() method
Support for Node.js compatibility flag required for Fedify's cryptographic operations
Manual queue processing via Federation.processQueuedTask() method

For a complete working example, see the Cloudflare Workers example in the Fedify repository.

🏗️ Federation builder pattern

Fedify 1.6 introduces the FederationBuilder class and createFederationBuilder() function to support deferred federation instantiation. This pattern provides several benefits:

Deferred instantiation: Set up dispatchers and listeners before creating the federation object
Better code organization: Avoid circular dependencies and improve project structure
Cloudflare #Workers compatibility: Accommodates binding-based architectures where resources are passed as arguments rather than globals
Modular setup: Build complex federations piece by piece before instantiation

The builder pattern is particularly useful for large applications and environments like Cloudflare Workers where configuration data is only available at runtime.

🔐 HTTP Message Signatures (RFC 9421)

Fedify 1.6 implements the official HTTP Message Signatures standard (RFC 9421) specification, the final revision of the HTTP Signatures specification.

Double-knocking mechanism

To ensure maximum compatibility across the fediverse, Fedify 1.6 introduces an intelligent double-knocking mechanism:

Primary attempt: RFC 9421 (HTTP Message Signatures) for modern implementations
Fallback: Draft cavage version for legacy compatibility
Adaptive caching: The system remembers which version each server supports to optimize future requests

This approach ensures seamless communication with both modern and legacy ActivityPub implementations while positioning Fedify at the forefront of security standards.

Interoperability testing

The RFC 9421 implementation has been thoroughly tested for interoperability with existing ActivityPub implementations that support RFC 9421 signature verification:

Mitra 4.4.0: Successfully verified Fedify-generated RFC 9421 signatures
Mastodon 4.4.0 development version: Tested RFC 9421 signature verification against Fedify's implementation (refer to Mastodon PR #34814, though Mastodon 4.4.0 has not yet been released)

🔍 WebFinger enhancements

Dedicated WebFinger lookup

🛠 Context API improvements

Context data replacement

🚀 Migration considerations

Backward compatibility

Fedify 1.6 maintains full backward compatibility with existing applications. The new HTTP Message Signatures and double-knocking mechanisms work transparently without requiring any code changes.

Node.js version requirement

New deployment options

For new deployments, consider leveraging Cloudflare Workers support for:

Global edge deployment with low latency
Serverless scaling and automatic resource management
Integration with Cloudflare's ecosystem of services

Hollo

@hollo@hollo.social

Introducing #Hollo. Hollo is an #ActivityPub-enabled single-user microblogging software. Although it's for a single user, it also supports creating and running multiple accounts for different topics.

Oh, and Hollo is built using #Bun and #Fedify.

Fedify: an ActivityPub server framework

@fedify@hollo.social

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

🎉 #Cloudflare #Workers support is now complete! After implementing the test infrastructure, core module, examples, and comprehensive documentation, #Fedify can now run on Cloudflare Workers.

What's included:

@fedify/fedify/x/cfworkers module with WorkersKvStore and WorkersMessageQueue
Complete documentation covering Workers-specific patterns and constraints
Working example deployed to production
Integration with Cloudflare KV and Queues

Try it now: Available in the development release v1.6.1-dev.876+7b07d213:

This will be included in the upcoming Fedify 1.6 stable release. Thank you to everyone who requested this feature and provided feedback throughout the implementation!

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

🎉 #Cloudflare #Workers support is now complete! After implementing the test infrastructure, core module, examples, and comprehensive documentation, #Fedify can now run on Cloudflare Workers.

What's included:

@fedify/fedify/x/cfworkers module with WorkersKvStore and WorkersMessageQueue
Complete documentation covering Workers-specific patterns and constraints
Working example deployed to production
Integration with Cloudflare KV and Queues

Try it now: Available in the development release v1.6.1-dev.876+7b07d213:

This will be included in the upcoming Fedify 1.6 stable release. Thank you to everyone who requested this feature and provided feedback throughout the implementation!

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

🎉 #Cloudflare #Workers support is now complete! After implementing the test infrastructure, core module, examples, and comprehensive documentation, #Fedify can now run on Cloudflare Workers.

What's included:

@fedify/fedify/x/cfworkers module with WorkersKvStore and WorkersMessageQueue
Complete documentation covering Workers-specific patterns and constraints
Working example deployed to production
Integration with Cloudflare KV and Queues

Try it now: Available in the development release v1.6.1-dev.876+7b07d213:

This will be included in the upcoming Fedify 1.6 stable release. Thank you to everyone who requested this feature and provided feedback throughout the implementation!

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

🎉 #Cloudflare #Workers support is now complete! After implementing the test infrastructure, core module, examples, and comprehensive documentation, #Fedify can now run on Cloudflare Workers.

What's included:

@fedify/fedify/x/cfworkers module with WorkersKvStore and WorkersMessageQueue
Complete documentation covering Workers-specific patterns and constraints
Working example deployed to production
Integration with Cloudflare KV and Queues

Try it now: Available in the development release v1.6.1-dev.876+7b07d213:

This will be included in the upcoming Fedify 1.6 stable release. Thank you to everyone who requested this feature and provided feedback throughout the implementation!

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

🎉 #Cloudflare #Workers support is now complete! After implementing the test infrastructure, core module, examples, and comprehensive documentation, #Fedify can now run on Cloudflare Workers.

What's included:

@fedify/fedify/x/cfworkers module with WorkersKvStore and WorkersMessageQueue
Complete documentation covering Workers-specific patterns and constraints
Working example deployed to production
Integration with Cloudflare KV and Queues

Try it now: Available in the development release v1.6.1-dev.876+7b07d213:

This will be included in the upcoming Fedify 1.6 stable release. Thank you to everyone who requested this feature and provided feedback throughout the implementation!

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

🎉 #Cloudflare #Workers support is now complete! After implementing the test infrastructure, core module, examples, and comprehensive documentation, #Fedify can now run on Cloudflare Workers.

What's included:

@fedify/fedify/x/cfworkers module with WorkersKvStore and WorkersMessageQueue
Complete documentation covering Workers-specific patterns and constraints
Working example deployed to production
Integration with Cloudflare KV and Queues

Try it now: Available in the development release v1.6.1-dev.876+7b07d213:

This will be included in the upcoming Fedify 1.6 stable release. Thank you to everyone who requested this feature and provided feedback throughout the implementation!

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

🎉 #Cloudflare #Workers support is now complete! After implementing the test infrastructure, core module, examples, and comprehensive documentation, #Fedify can now run on Cloudflare Workers.

What's included:

@fedify/fedify/x/cfworkers module with WorkersKvStore and WorkersMessageQueue
Complete documentation covering Workers-specific patterns and constraints
Working example deployed to production
Integration with Cloudflare KV and Queues

Try it now: Available in the development release v1.6.1-dev.876+7b07d213:

This will be included in the upcoming Fedify 1.6 stable release. Thank you to everyone who requested this feature and provided feedback throughout the implementation!

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

🎉 #Cloudflare #Workers support is now complete! After implementing the test infrastructure, core module, examples, and comprehensive documentation, #Fedify can now run on Cloudflare Workers.

What's included:

@fedify/fedify/x/cfworkers module with WorkersKvStore and WorkersMessageQueue
Complete documentation covering Workers-specific patterns and constraints
Working example deployed to production
Integration with Cloudflare KV and Queues

Try it now: Available in the development release v1.6.1-dev.876+7b07d213:

This will be included in the upcoming Fedify 1.6 stable release. Thank you to everyone who requested this feature and provided feedback throughout the implementation!

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

🎉 #Cloudflare #Workers support is now complete! After implementing the test infrastructure, core module, examples, and comprehensive documentation, #Fedify can now run on Cloudflare Workers.

What's included:

@fedify/fedify/x/cfworkers module with WorkersKvStore and WorkersMessageQueue
Complete documentation covering Workers-specific patterns and constraints
Working example deployed to production
Integration with Cloudflare KV and Queues

Try it now: Available in the development release v1.6.1-dev.876+7b07d213:

This will be included in the upcoming Fedify 1.6 stable release. Thank you to everyone who requested this feature and provided feedback throughout the implementation!

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

🎉 #Cloudflare #Workers support is now complete! After implementing the test infrastructure, core module, examples, and comprehensive documentation, #Fedify can now run on Cloudflare Workers.

What's included:

@fedify/fedify/x/cfworkers module with WorkersKvStore and WorkersMessageQueue
Complete documentation covering Workers-specific patterns and constraints
Working example deployed to production
Integration with Cloudflare KV and Queues

Try it now: Available in the development release v1.6.1-dev.876+7b07d213:

This will be included in the upcoming Fedify 1.6 stable release. Thank you to everyone who requested this feature and provided feedback throughout the implementation!

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

If you're interested in building your own #ActivityPub server but don't know where to start, I recommend checking out #Fedify's #tutorial Creating your own federated microblog. It provides a comprehensive, step-by-step guide that walks you through building a fully functional federated application. Perfect for developers who want to dive into the #fediverse!

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

I deployed my first #Fedify application on Cloudflare Workers and saw it running smoothly. Now all that's left is the documentation!

RE: https://mastodon.social/@reiver/114590677447681643

洪民憙 (Hong Minhee)

Right now, I am using the "endpoints" field with the sub-field "inoutbox" to point to the WebSockets API end-point.

#ActivitySocket #GreatApe #Fediverse #FediDev #FediDevs #DeSo #FeSo #LoSo

ALT text details

{ "type": "Conference", "actor": "acct:reiver@mastodon.social", "endpoints": { "inoutbox": "wss://greatape.social/@reiver@mastodon.social/conf" }, "id": "https://greatape.social/@reiver@mastodon.social/conf", "name": "@reiver@mastodon.social — GreatApe" }

@reiver ⊼ (Charles)

@reiver@mastodon.social

This is how I am thinking about pointing to the GreatApe WebSocket API in the activity file.

The GreatApe WebSocket API — ActivitySocket ? — is sending ActivityPub activities over a WebSocket, along with some other stuff (such a queries, and commands).

Right now, I am using the "endpoints" field with the sub-field "inoutbox" to point to the WebSockets API end-point.

RE: https://mastodon.social/@reiver/114590677447681643

#ActivitySocket #GreatApe #Fediverse #FediDev #FediDevs #DeSo #FeSo #LoSo

ALT text details

@reiver ⊼ (Charles)

@reiver@mastodon.social · Reply to @reiver ⊼ (Charles) :batman:'s post

One thing that is interesting about the GreatApe WebSocket API is that —

Because the WebSocket can be both read from and written to — the WebSocket is in a sense both an ActivityPub outbox and an ActivityPub inbox at the same time.

RE: https://mastodon.social/@reiver/114585707207505158

#ActivitySocket #GreatApe #Fediverse #FediDev #FediDevs #DeSo #FeSo #LoSo

@reiver ⊼ (Charles)

@reiver@mastodon.social

GreatApe is a conferencing platform for the Fediverse and the Social Web — where an audience can listen & watch live, and can be invited to join the speakers on the stage.

GreatApe makes use of a WebSocket for communications.

I am working on turning the WebSocket API that @muhammadzaidali and @benyamin0 created into something more ActivityPub / ActivityStreams like.

Interestingly —

RE: https://mastodon.social/@reiver/114585707207505158

#ActivitySocket #GreatApe #Fediverse #FediDev #FediDevs #DeSo #FeSo #LoSo

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're planning to reorganize our #GitHub labels to better reflect #Fedify's project structure! 🏷️

Currently using GitHub's default labels, but we want something more tailored to our needs—like component-specific labels (vocab, federation, actor, etc.), runtime tags (Deno/Node/Bun), and #ActivityPub compatibility tracking.

The proposal includes hierarchical labeling with categories like:

type/ for bug, feature, documentation
component/ for different parts of Fedify
activitypub/ for interop issues with Mastodon, Misskey, etc.

We'd love your thoughts! What labels would be most helpful for contributors and maintainers?

Check out the full proposal: https://github.com/fedify-dev/fedify/issues/238.

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're planning to reorganize our #GitHub labels to better reflect #Fedify's project structure! 🏷️

The proposal includes hierarchical labeling with categories like:

type/ for bug, feature, documentation
component/ for different parts of Fedify
activitypub/ for interop issues with Mastodon, Misskey, etc.

We'd love your thoughts! What labels would be most helpful for contributors and maintainers?

Check out the full proposal: https://github.com/fedify-dev/fedify/issues/238.

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're planning to reorganize our #GitHub labels to better reflect #Fedify's project structure! 🏷️

The proposal includes hierarchical labeling with categories like:

type/ for bug, feature, documentation
component/ for different parts of Fedify
activitypub/ for interop issues with Mastodon, Misskey, etc.

We'd love your thoughts! What labels would be most helpful for contributors and maintainers?

Check out the full proposal: https://github.com/fedify-dev/fedify/issues/238.

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're planning to reorganize our #GitHub labels to better reflect #Fedify's project structure! 🏷️

The proposal includes hierarchical labeling with categories like:

type/ for bug, feature, documentation
component/ for different parts of Fedify
activitypub/ for interop issues with Mastodon, Misskey, etc.

We'd love your thoughts! What labels would be most helpful for contributors and maintainers?

Check out the full proposal: https://github.com/fedify-dev/fedify/issues/238.

Fedify: an ActivityPub server framework

@fedify@hollo.social

While #Fedify's #Vocabulary API provides comprehensive support for #ActivityPub and major vendor extensions, its code-generation approach makes runtime extensions challenging. However, the project welcomes contributions to expand the supported types and properties.

Fedify accepts vocabulary contributions when they meet any of these criteria:

Documented in FEP (Fediverse Enhancement Proposals) or equivalent specification
Already adopted by widely-used #fediverse implementations like Mastodon or Pleroma
Thoroughly discussed within the Fedify community (Discord, Matrix, GitHub Discussions)

Contributing new vocabulary is straightforward. The vocabulary definitions live in YAML files within the fedify/vocab/ directory. To add a new type, create a new .yaml file. To add properties to existing types, extend the properties section in the relevant .yaml file.

This approach ensures Fedify's vocabulary coverage grows with the fediverse ecosystem while maintaining type safety and comprehensive documentation. If you're working with custom ActivityPub extensions, consider contributing them upstream to benefit the entire community.

For detailed guidance on the contribution process, see the Extending the vocabulary section in Fedify's docs.

Fedify: an ActivityPub server framework

@fedify@hollo.social

Fedify accepts vocabulary contributions when they meet any of these criteria:

Documented in FEP (Fediverse Enhancement Proposals) or equivalent specification
Already adopted by widely-used #fediverse implementations like Mastodon or Pleroma
Thoroughly discussed within the Fedify community (Discord, Matrix, GitHub Discussions)

For detailed guidance on the contribution process, see the Extending the vocabulary section in Fedify's docs.

Fedify: an ActivityPub server framework

@fedify@hollo.social

Fedify accepts vocabulary contributions when they meet any of these criteria:

Documented in FEP (Fediverse Enhancement Proposals) or equivalent specification
Already adopted by widely-used #fediverse implementations like Mastodon or Pleroma
Thoroughly discussed within the Fedify community (Discord, Matrix, GitHub Discussions)

For detailed guidance on the contribution process, see the Extending the vocabulary section in Fedify's docs.

Fedify: an ActivityPub server framework

@fedify@hollo.social

Fedify accepts vocabulary contributions when they meet any of these criteria:

Documented in FEP (Fediverse Enhancement Proposals) or equivalent specification
Already adopted by widely-used #fediverse implementations like Mastodon or Pleroma
Thoroughly discussed within the Fedify community (Discord, Matrix, GitHub Discussions)

For detailed guidance on the contribution process, see the Extending the vocabulary section in Fedify's docs.

Fedify: an ActivityPub server framework

@fedify@hollo.social

Fedify accepts vocabulary contributions when they meet any of these criteria:

Documented in FEP (Fediverse Enhancement Proposals) or equivalent specification
Already adopted by widely-used #fediverse implementations like Mastodon or Pleroma
Thoroughly discussed within the Fedify community (Discord, Matrix, GitHub Discussions)

For detailed guidance on the contribution process, see the Extending the vocabulary section in Fedify's docs.

#fedidev #FediDevKR #opensource

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Had a wonderful time today at our second FediDev KR #sprint (@sprints.fedidev.kr) gathering at Turing's Apple (@TuringAppleDev) in #Seoul!

We spent the day contributing to various #fediverse open source projects including @fedify, @hollo, and Hackers' Pub. It was fantastic to see the community come together to build and improve tools for the decentralized social web.

Our participants made some great contributions, and you can read all about what we accomplished in today's blog post.

Looking forward to our next sprint!

ALT text details

A hand holding a 3D-printed keychain featuring the Fedify dinosaur mascot logo in blue and white colors. The keychain is packaged in a clear plastic bag with Korean text indicating it's from the FediDev KR Second Sprint on May 24, 2025. The background shows laptops and stickers on a table, suggesting a coding workspace at the sprint event.

https://mastodon.social/@reiver/114558438172850892

Jeff Sikes

@box464@mastodon.social

GreatApe, a federated live video / audio platform, is hosting an event right now! Give it a go, help test it out.

https://mastodon.social/@reiver/114558438172850892

Jeff Sikes

@box464@mastodon.social

GreatApe, a federated live video / audio platform, is hosting an event right now! Give it a go, help test it out.

#SocialWeb #Release #FediDev #Fediverse #SocialMedia #Mastodon #Channelorg #Newsmast

Newsmast

@newsmast@newsmast.social

Exciting update 👉 We're inviting a handful of select users to https://Channel.org now 🎉

https://Channel.org aims to bring together knowledge across the open social web, whilst offering organisations the ability to build a social home instead of renting from Big Tech dictators.

If you'd like to join the beta waitlist, let us know at support@channel.org

ALT text details

A graphic alert reading: Channel.org BETA release. Invite only access now live

Newsmast

@newsmast@newsmast.social

Exciting update 👉 We're inviting a handful of select users to https://Channel.org now 🎉

https://Channel.org aims to bring together knowledge across the open social web, whilst offering organisations the ability to build a social home instead of renting from Big Tech dictators.

If you'd like to join the beta waitlist, let us know at support@channel.org

#SocialWeb #Release #FediDev #Fediverse #SocialMedia #Mastodon #Channelorg #Newsmast

ALT text details

A graphic alert reading: Channel.org BETA release. Invite only access now live

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

@box464@mastodon.social

PieFed adds PassKeys! As in, log in only with your passkey. Not just as a 2FA addition to your username/password.

https://piefed.social/post/762082

#ActivityPub #FediDev #PieFed

Strypey

@strypey@mastodon.nzoss.nz

How hard would it be for a fediverse app to give me a daily or weekly notification about each of my saved drafts? So I can start a reply, decide it needs more thought, save it, and get reminded of it.

Bonus points for being able to schedule a reminder notification for each saved post. A day for this one, a week for this one, and so on.

#fediverse #FediverseIdeas #FediDev

@hongminhee@hollo.social

I've been thinking about client-server interactions in the #fediverse. #ActivityPub #C2S isn't widely used, and most clients rely on Mastodon-compatible APIs instead.

What if we created a new standardized API based on GraphQL + Relay for client-server communication, while keeping ActivityPub for server-to-server federation?

Would this be valuable to our community? What challenges do you see? How might we handle backward compatibility? And should this be formalized as an FEP?

Curious what others think about this approach.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social · Reply to 洪民憙 (Hong Minhee)'s post

Okay, I've just deployed a bleeding edge #Fedify, which implements both RFC 9421 and double-knocking, to Hackers' Pub. If you'd like to test your implementations against a real server, please give it a try! (If you want to create an account, let me know—I can invite you.)

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

I'm exploring a new idea called FediOTP (codename): an authentication system that uses #ActivityPub DMs to deliver one-time passwords, allowing any #fediverse account to authenticate with web services. Unlike current solutions that rely on specific APIs (#Mastodon, #Misskey), this would work with any ActivityPub-compatible server, increasing interoperability across the fediverse. Would love to hear your thoughts on potential challenges or use cases for this approach.

Looking for #ActivityPub implementations with #RFC9421 support! 🔍

As mentioned in the Fedify announcement below, I've implemented RFC 9421 (HTTP Message Signatures) and need to verify its interoperability with other ActivityPub implementations.

The challenge is that most major ActivityPub projects don't seem to have full RFC 9421 implementations in production yet. If you're working on an ActivityPub project that:

has implemented RFC 9421 (even in a development branch)
is currently implementing it
has plans to implement it soon

Please reach out! I'd love to collaborate on interoperability testing to ensure our implementations work properly with each other before merging this into #Fedify's main branch.

Any leads or connections would be greatly appreciated! 🙏

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're excited to announce that we've implemented RFC 9421 (HTTP Message Signatures) in #Fedify, complete with our double-knocking mechanism to maintain backward compatibility with the draft cavage version.

This implementation includes both signature generation and verification, meaning #RFC9421 is used when both sending and receiving activities. While we haven't merged the RFC 9421 implementation branch yet, we're currently conducting interoperability tests with development versions of Mastodon and other #ActivityPub implementations. Once these tests confirm compatibility, we'll proceed with the merge.

As noted in the attached docs, although RFC 9421 is the final and official standard for HTTP Signatures, the draft cavage version remains widely used across the #fediverse. Our double-knocking mechanism ensures maximum compatibility by trying the RFC 9421 version first, then falling back to draft cavage if needed.

Currently, we support RSA-PKCS#1-v1.5 key pairs for generating HTTP Message Signatures, with plans to expand to other signature types in future releases.

We look forward to contributing to a more standardized and secure fediverse!

ALT text details

HTTP Message Signatures This API is available since Fedify 1.6.0. RFC 9421, also known as HTTP Message Signatures, is the final revision of the HTTP Signatures specification. Although it is the official standard, it is not widely used in the fediverse yet. As of May 2025, major ActivityPub implementations, such as Mastodon, et al., still rely on the draft cavage version of HTTP Signatures for signing portable activities. Fedify automatically signs activities with the sender's private key if the actor keys dispatcher is set and the actor has any RSA-PKCS#1-v1.5 key pair. If there are multiple key pairs, Fedify selects the first RSA-PKCS#1-v1.5 key pair among them. NOTE Although HTTP Message Signatures support other than RSA-PKCS#1-v1.5, Fedify currently supports only RSA-PKCS#1-v1.5 key pairs for generating HTTP Message Signatures. This limitation will be lifted in the future releases.

ALT text details

Double-knocking HTTP Signatures This API is available since Fedify 1.6.0. As you read above, there are two revisions of HTTP Signatures: the draft cavage version and the RFC 9421 version. The draft cavage version is declared as obsolete, but it is still widely used in the fediverse, and many ActivityPub implementations still rely on it. On the other hand, the RFC 9421 version is the official standard, but it is not widely used yet. To support both versions of HTTP Signatures, Fedify uses the double-knocking mechanism: trying one version, then falling back to another if rejected. If it's the first encounter with the recipient server, Fedify tries the RFC 9421 version first, and if it fails, it falls back to the draft cavage version. If the recipient server accepts the RFC 9421 version, Fedify remembers it and uses the RFC 9421 version for the next time. If the recipient server rejects the RFC 9421 version, Fedify falls back to the draft cavage version and remembers it for the next time.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Looking for #ActivityPub implementations with #RFC9421 support! 🔍

As mentioned in the Fedify announcement below, I've implemented RFC 9421 (HTTP Message Signatures) and need to verify its interoperability with other ActivityPub implementations.

The challenge is that most major ActivityPub projects don't seem to have full RFC 9421 implementations in production yet. If you're working on an ActivityPub project that:

has implemented RFC 9421 (even in a development branch)
is currently implementing it
has plans to implement it soon

Please reach out! I'd love to collaborate on interoperability testing to ensure our implementations work properly with each other before merging this into #Fedify's main branch.

Any leads or connections would be greatly appreciated! 🙏

Fedify: an ActivityPub server framework

@fedify@hollo.social

Currently, we support RSA-PKCS#1-v1.5 key pairs for generating HTTP Message Signatures, with plans to expand to other signature types in future releases.

We look forward to contributing to a more standardized and secure fediverse!

ALT text details

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Looking for #ActivityPub implementations with #RFC9421 support! 🔍

As mentioned in the Fedify announcement below, I've implemented RFC 9421 (HTTP Message Signatures) and need to verify its interoperability with other ActivityPub implementations.

The challenge is that most major ActivityPub projects don't seem to have full RFC 9421 implementations in production yet. If you're working on an ActivityPub project that:

has implemented RFC 9421 (even in a development branch)
is currently implementing it
has plans to implement it soon

Please reach out! I'd love to collaborate on interoperability testing to ensure our implementations work properly with each other before merging this into #Fedify's main branch.

Any leads or connections would be greatly appreciated! 🙏

Fedify: an ActivityPub server framework

@fedify@hollo.social

Currently, we support RSA-PKCS#1-v1.5 key pairs for generating HTTP Message Signatures, with plans to expand to other signature types in future releases.

We look forward to contributing to a more standardized and secure fediverse!

ALT text details

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Looking for #ActivityPub implementations with #RFC9421 support! 🔍

As mentioned in the Fedify announcement below, I've implemented RFC 9421 (HTTP Message Signatures) and need to verify its interoperability with other ActivityPub implementations.

The challenge is that most major ActivityPub projects don't seem to have full RFC 9421 implementations in production yet. If you're working on an ActivityPub project that:

has implemented RFC 9421 (even in a development branch)
is currently implementing it
has plans to implement it soon

Please reach out! I'd love to collaborate on interoperability testing to ensure our implementations work properly with each other before merging this into #Fedify's main branch.

Any leads or connections would be greatly appreciated! 🙏

Fedify: an ActivityPub server framework

@fedify@hollo.social

Currently, we support RSA-PKCS#1-v1.5 key pairs for generating HTTP Message Signatures, with plans to expand to other signature types in future releases.

We look forward to contributing to a more standardized and secure fediverse!

ALT text details

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Looking for #ActivityPub implementations with #RFC9421 support! 🔍

As mentioned in the Fedify announcement below, I've implemented RFC 9421 (HTTP Message Signatures) and need to verify its interoperability with other ActivityPub implementations.

The challenge is that most major ActivityPub projects don't seem to have full RFC 9421 implementations in production yet. If you're working on an ActivityPub project that:

has implemented RFC 9421 (even in a development branch)
is currently implementing it
has plans to implement it soon

Please reach out! I'd love to collaborate on interoperability testing to ensure our implementations work properly with each other before merging this into #Fedify's main branch.

Any leads or connections would be greatly appreciated! 🙏

Fedify: an ActivityPub server framework

@fedify@hollo.social

Currently, we support RSA-PKCS#1-v1.5 key pairs for generating HTTP Message Signatures, with plans to expand to other signature types in future releases.

We look forward to contributing to a more standardized and secure fediverse!

ALT text details

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Looking for #ActivityPub implementations with #RFC9421 support! 🔍

As mentioned in the Fedify announcement below, I've implemented RFC 9421 (HTTP Message Signatures) and need to verify its interoperability with other ActivityPub implementations.

The challenge is that most major ActivityPub projects don't seem to have full RFC 9421 implementations in production yet. If you're working on an ActivityPub project that:

has implemented RFC 9421 (even in a development branch)
is currently implementing it
has plans to implement it soon

Please reach out! I'd love to collaborate on interoperability testing to ensure our implementations work properly with each other before merging this into #Fedify's main branch.

Any leads or connections would be greatly appreciated! 🙏

Fedify: an ActivityPub server framework

@fedify@hollo.social

Currently, we support RSA-PKCS#1-v1.5 key pairs for generating HTTP Message Signatures, with plans to expand to other signature types in future releases.

We look forward to contributing to a more standardized and secure fediverse!

ALT text details

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Looking for #ActivityPub implementations with #RFC9421 support! 🔍

As mentioned in the Fedify announcement below, I've implemented RFC 9421 (HTTP Message Signatures) and need to verify its interoperability with other ActivityPub implementations.

The challenge is that most major ActivityPub projects don't seem to have full RFC 9421 implementations in production yet. If you're working on an ActivityPub project that:

has implemented RFC 9421 (even in a development branch)
is currently implementing it
has plans to implement it soon

Please reach out! I'd love to collaborate on interoperability testing to ensure our implementations work properly with each other before merging this into #Fedify's main branch.

Any leads or connections would be greatly appreciated! 🙏

Fedify: an ActivityPub server framework

@fedify@hollo.social

Currently, we support RSA-PKCS#1-v1.5 key pairs for generating HTTP Message Signatures, with plans to expand to other signature types in future releases.

We look forward to contributing to a more standardized and secure fediverse!

ALT text details

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Looking for #ActivityPub implementations with #RFC9421 support! 🔍

As mentioned in the Fedify announcement below, I've implemented RFC 9421 (HTTP Message Signatures) and need to verify its interoperability with other ActivityPub implementations.

The challenge is that most major ActivityPub projects don't seem to have full RFC 9421 implementations in production yet. If you're working on an ActivityPub project that:

has implemented RFC 9421 (even in a development branch)
is currently implementing it
has plans to implement it soon

Please reach out! I'd love to collaborate on interoperability testing to ensure our implementations work properly with each other before merging this into #Fedify's main branch.

Any leads or connections would be greatly appreciated! 🙏

Fedify: an ActivityPub server framework

@fedify@hollo.social

Currently, we support RSA-PKCS#1-v1.5 key pairs for generating HTTP Message Signatures, with plans to expand to other signature types in future releases.

We look forward to contributing to a more standardized and secure fediverse!

ALT text details

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Looking for #ActivityPub implementations with #RFC9421 support! 🔍

As mentioned in the Fedify announcement below, I've implemented RFC 9421 (HTTP Message Signatures) and need to verify its interoperability with other ActivityPub implementations.

The challenge is that most major ActivityPub projects don't seem to have full RFC 9421 implementations in production yet. If you're working on an ActivityPub project that:

has implemented RFC 9421 (even in a development branch)
is currently implementing it
has plans to implement it soon

Please reach out! I'd love to collaborate on interoperability testing to ensure our implementations work properly with each other before merging this into #Fedify's main branch.

Any leads or connections would be greatly appreciated! 🙏

Fedify: an ActivityPub server framework

@fedify@hollo.social

Currently, we support RSA-PKCS#1-v1.5 key pairs for generating HTTP Message Signatures, with plans to expand to other signature types in future releases.

We look forward to contributing to a more standardized and secure fediverse!

ALT text details

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Looking for #ActivityPub implementations with #RFC9421 support! 🔍

As mentioned in the Fedify announcement below, I've implemented RFC 9421 (HTTP Message Signatures) and need to verify its interoperability with other ActivityPub implementations.

The challenge is that most major ActivityPub projects don't seem to have full RFC 9421 implementations in production yet. If you're working on an ActivityPub project that:

has implemented RFC 9421 (even in a development branch)
is currently implementing it
has plans to implement it soon

Please reach out! I'd love to collaborate on interoperability testing to ensure our implementations work properly with each other before merging this into #Fedify's main branch.

Any leads or connections would be greatly appreciated! 🙏

Fedify: an ActivityPub server framework

@fedify@hollo.social

Currently, we support RSA-PKCS#1-v1.5 key pairs for generating HTTP Message Signatures, with plans to expand to other signature types in future releases.

We look forward to contributing to a more standardized and secure fediverse!

ALT text details

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Looking for #ActivityPub implementations with #RFC9421 support! 🔍

As mentioned in the Fedify announcement below, I've implemented RFC 9421 (HTTP Message Signatures) and need to verify its interoperability with other ActivityPub implementations.

The challenge is that most major ActivityPub projects don't seem to have full RFC 9421 implementations in production yet. If you're working on an ActivityPub project that:

has implemented RFC 9421 (even in a development branch)
is currently implementing it
has plans to implement it soon

Please reach out! I'd love to collaborate on interoperability testing to ensure our implementations work properly with each other before merging this into #Fedify's main branch.

Any leads or connections would be greatly appreciated! 🙏

Fedify: an ActivityPub server framework

@fedify@hollo.social

Currently, we support RSA-PKCS#1-v1.5 key pairs for generating HTTP Message Signatures, with plans to expand to other signature types in future releases.

We look forward to contributing to a more standardized and secure fediverse!

ALT text details

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Looking for #ActivityPub implementations with #RFC9421 support! 🔍

As mentioned in the Fedify announcement below, I've implemented RFC 9421 (HTTP Message Signatures) and need to verify its interoperability with other ActivityPub implementations.

The challenge is that most major ActivityPub projects don't seem to have full RFC 9421 implementations in production yet. If you're working on an ActivityPub project that:

has implemented RFC 9421 (even in a development branch)
is currently implementing it
has plans to implement it soon

Please reach out! I'd love to collaborate on interoperability testing to ensure our implementations work properly with each other before merging this into #Fedify's main branch.

Any leads or connections would be greatly appreciated! 🙏

Fedify: an ActivityPub server framework

@fedify@hollo.social

Currently, we support RSA-PKCS#1-v1.5 key pairs for generating HTTP Message Signatures, with plans to expand to other signature types in future releases.

We look forward to contributing to a more standardized and secure fediverse!

ALT text details

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Looking for #ActivityPub implementations with #RFC9421 support! 🔍

As mentioned in the Fedify announcement below, I've implemented RFC 9421 (HTTP Message Signatures) and need to verify its interoperability with other ActivityPub implementations.

The challenge is that most major ActivityPub projects don't seem to have full RFC 9421 implementations in production yet. If you're working on an ActivityPub project that:

has implemented RFC 9421 (even in a development branch)
is currently implementing it
has plans to implement it soon

Please reach out! I'd love to collaborate on interoperability testing to ensure our implementations work properly with each other before merging this into #Fedify's main branch.

Any leads or connections would be greatly appreciated! 🙏

Fedify: an ActivityPub server framework

@fedify@hollo.social

Currently, we support RSA-PKCS#1-v1.5 key pairs for generating HTTP Message Signatures, with plans to expand to other signature types in future releases.

We look forward to contributing to a more standardized and secure fediverse!

ALT text details

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Looking for #ActivityPub implementations with #RFC9421 support! 🔍

As mentioned in the Fedify announcement below, I've implemented RFC 9421 (HTTP Message Signatures) and need to verify its interoperability with other ActivityPub implementations.

The challenge is that most major ActivityPub projects don't seem to have full RFC 9421 implementations in production yet. If you're working on an ActivityPub project that:

has implemented RFC 9421 (even in a development branch)
is currently implementing it
has plans to implement it soon

Please reach out! I'd love to collaborate on interoperability testing to ensure our implementations work properly with each other before merging this into #Fedify's main branch.

Any leads or connections would be greatly appreciated! 🙏

Fedify: an ActivityPub server framework

@fedify@hollo.social

Currently, we support RSA-PKCS#1-v1.5 key pairs for generating HTTP Message Signatures, with plans to expand to other signature types in future releases.

We look forward to contributing to a more standardized and secure fediverse!

ALT text details

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Looking for #ActivityPub implementations with #RFC9421 support! 🔍

As mentioned in the Fedify announcement below, I've implemented RFC 9421 (HTTP Message Signatures) and need to verify its interoperability with other ActivityPub implementations.

The challenge is that most major ActivityPub projects don't seem to have full RFC 9421 implementations in production yet. If you're working on an ActivityPub project that:

has implemented RFC 9421 (even in a development branch)
is currently implementing it
has plans to implement it soon

Please reach out! I'd love to collaborate on interoperability testing to ensure our implementations work properly with each other before merging this into #Fedify's main branch.

Any leads or connections would be greatly appreciated! 🙏

Fedify: an ActivityPub server framework

@fedify@hollo.social

Currently, we support RSA-PKCS#1-v1.5 key pairs for generating HTTP Message Signatures, with plans to expand to other signature types in future releases.

We look forward to contributing to a more standardized and secure fediverse!

ALT text details

Fedify: an ActivityPub server framework

@fedify@hollo.social

Currently, we support RSA-PKCS#1-v1.5 key pairs for generating HTTP Message Signatures, with plans to expand to other signature types in future releases.

We look forward to contributing to a more standardized and secure fediverse!

ALT text details

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Looking for #ActivityPub implementations with #RFC9421 support! 🔍

As mentioned in the Fedify announcement below, I've implemented RFC 9421 (HTTP Message Signatures) and need to verify its interoperability with other ActivityPub implementations.

The challenge is that most major ActivityPub projects don't seem to have full RFC 9421 implementations in production yet. If you're working on an ActivityPub project that:

has implemented RFC 9421 (even in a development branch)
is currently implementing it
has plans to implement it soon

Please reach out! I'd love to collaborate on interoperability testing to ensure our implementations work properly with each other before merging this into #Fedify's main branch.

Any leads or connections would be greatly appreciated! 🙏

Fedify: an ActivityPub server framework

@fedify@hollo.social

Currently, we support RSA-PKCS#1-v1.5 key pairs for generating HTTP Message Signatures, with plans to expand to other signature types in future releases.

We look forward to contributing to a more standardized and secure fediverse!

ALT text details

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Looking for #ActivityPub implementations with #RFC9421 support! 🔍

As mentioned in the Fedify announcement below, I've implemented RFC 9421 (HTTP Message Signatures) and need to verify its interoperability with other ActivityPub implementations.

The challenge is that most major ActivityPub projects don't seem to have full RFC 9421 implementations in production yet. If you're working on an ActivityPub project that:

has implemented RFC 9421 (even in a development branch)
is currently implementing it
has plans to implement it soon

Please reach out! I'd love to collaborate on interoperability testing to ensure our implementations work properly with each other before merging this into #Fedify's main branch.

Any leads or connections would be greatly appreciated! 🙏

Fedify: an ActivityPub server framework

@fedify@hollo.social

Currently, we support RSA-PKCS#1-v1.5 key pairs for generating HTTP Message Signatures, with plans to expand to other signature types in future releases.

We look forward to contributing to a more standardized and secure fediverse!

ALT text details

Fedify: an ActivityPub server framework

@fedify@hollo.social

Currently, we support RSA-PKCS#1-v1.5 key pairs for generating HTTP Message Signatures, with plans to expand to other signature types in future releases.

We look forward to contributing to a more standardized and secure fediverse!

ALT text details

Fedify: an ActivityPub server framework

@fedify@hollo.social

Currently, we support RSA-PKCS#1-v1.5 key pairs for generating HTTP Message Signatures, with plans to expand to other signature types in future releases.

We look forward to contributing to a more standardized and secure fediverse!

ALT text details

Fedify: an ActivityPub server framework

@fedify@hollo.social

Currently, we support RSA-PKCS#1-v1.5 key pairs for generating HTTP Message Signatures, with plans to expand to other signature types in future releases.

We look forward to contributing to a more standardized and secure fediverse!

ALT text details

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Looking for #ActivityPub implementations with #RFC9421 support! 🔍

As mentioned in the Fedify announcement below, I've implemented RFC 9421 (HTTP Message Signatures) and need to verify its interoperability with other ActivityPub implementations.

The challenge is that most major ActivityPub projects don't seem to have full RFC 9421 implementations in production yet. If you're working on an ActivityPub project that:

has implemented RFC 9421 (even in a development branch)
is currently implementing it
has plans to implement it soon

Please reach out! I'd love to collaborate on interoperability testing to ensure our implementations work properly with each other before merging this into #Fedify's main branch.

Any leads or connections would be greatly appreciated! 🙏

Fedify: an ActivityPub server framework

@fedify@hollo.social

Currently, we support RSA-PKCS#1-v1.5 key pairs for generating HTTP Message Signatures, with plans to expand to other signature types in future releases.

We look forward to contributing to a more standardized and secure fediverse!

ALT text details

Fedify: an ActivityPub server framework

@fedify@hollo.social

Currently, we support RSA-PKCS#1-v1.5 key pairs for generating HTTP Message Signatures, with plans to expand to other signature types in future releases.

We look forward to contributing to a more standardized and secure fediverse!

ALT text details

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Looking for #ActivityPub implementations with #RFC9421 support! 🔍

As mentioned in the Fedify announcement below, I've implemented RFC 9421 (HTTP Message Signatures) and need to verify its interoperability with other ActivityPub implementations.

The challenge is that most major ActivityPub projects don't seem to have full RFC 9421 implementations in production yet. If you're working on an ActivityPub project that:

has implemented RFC 9421 (even in a development branch)
is currently implementing it
has plans to implement it soon

Please reach out! I'd love to collaborate on interoperability testing to ensure our implementations work properly with each other before merging this into #Fedify's main branch.

Any leads or connections would be greatly appreciated! 🙏

Fedify: an ActivityPub server framework

@fedify@hollo.social

Currently, we support RSA-PKCS#1-v1.5 key pairs for generating HTTP Message Signatures, with plans to expand to other signature types in future releases.

We look forward to contributing to a more standardized and secure fediverse!

ALT text details

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Looking for #ActivityPub implementations with #RFC9421 support! 🔍

As mentioned in the Fedify announcement below, I've implemented RFC 9421 (HTTP Message Signatures) and need to verify its interoperability with other ActivityPub implementations.

The challenge is that most major ActivityPub projects don't seem to have full RFC 9421 implementations in production yet. If you're working on an ActivityPub project that:

has implemented RFC 9421 (even in a development branch)
is currently implementing it
has plans to implement it soon

We look forward to contributing to a more standardized and secure fediverse!

#fediverse #FediverseIdeas #FediDev

@liaizon@social.wake.st

Doing some fediverse research and discovered that @tkithrta is attempting to "implement #ActivityPub using 16 different web frameworks" in a project called #StrawberryFields
https://gitlab.com/acefed #fediverse #fedidev

Strypey

@strypey@mastodon.nzoss.nz

Bonus points for being able to schedule a reminder notification for each saved post. A day for this one, a week for this one, and so on.

@moshidon

Kidiatoliny Gonçalves

@kidiatoliny@mastodon.social

Hunter has just received its first sponsor!

This is a meaningful milestone that helps us keep building with independence and community values at the core.

Try it live: https://devhunter.cv

#HunterPlatform #OpenWeb #FediDev #IndieHackers

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

After reviewing FEP-5624: Per-object reply control policies and GoToSocial's interaction policy spec, I find myself leaning toward the latter for long-term considerations, though both have merit.

FEP-5624 is admirably focused and simpler to implement, which I appreciate. However, #GoToSocial's approach seems to offer some architectural advantages:

The three-tier permission model (allow/require approval/deny) feels more flexible than binary allow/deny
Separating approval objects from interactions appears more secure against forgery
The explicit handling of edge cases (mentioned users, post authors) provides clearer semantics
The extensible framework allows for handling diverse interaction types, not just replies

I wonder if creating an #FEP that extracts GoToSocial's interaction policy design into a standalone standard might be worthwhile. It could potentially serve as a more comprehensive foundation for access control in #ActivityPub.

This is merely my initial impression though. I'd be curious to hear other developers' perspectives on these approaches.

#FEP5624 #fedidev #fediverse #replycontrol #interactionpolicy

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

After reviewing FEP-5624: Per-object reply control policies and GoToSocial's interaction policy spec, I find myself leaning toward the latter for long-term considerations, though both have merit.

FEP-5624 is admirably focused and simpler to implement, which I appreciate. However, #GoToSocial's approach seems to offer some architectural advantages:

The three-tier permission model (allow/require approval/deny) feels more flexible than binary allow/deny
Separating approval objects from interactions appears more secure against forgery
The explicit handling of edge cases (mentioned users, post authors) provides clearer semantics
The extensible framework allows for handling diverse interaction types, not just replies

This is merely my initial impression though. I'd be curious to hear other developers' perspectives on these approaches.

#FEP5624 #fedidev #fediverse #replycontrol #interactionpolicy

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

After reviewing FEP-5624: Per-object reply control policies and GoToSocial's interaction policy spec, I find myself leaning toward the latter for long-term considerations, though both have merit.

FEP-5624 is admirably focused and simpler to implement, which I appreciate. However, #GoToSocial's approach seems to offer some architectural advantages:

The three-tier permission model (allow/require approval/deny) feels more flexible than binary allow/deny
Separating approval objects from interactions appears more secure against forgery
The explicit handling of edge cases (mentioned users, post authors) provides clearer semantics
The extensible framework allows for handling diverse interaction types, not just replies

This is merely my initial impression though. I'd be curious to hear other developers' perspectives on these approaches.

#FEP5624 #fedidev #fediverse #replycontrol #interactionpolicy

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

After reviewing FEP-5624: Per-object reply control policies and GoToSocial's interaction policy spec, I find myself leaning toward the latter for long-term considerations, though both have merit.

FEP-5624 is admirably focused and simpler to implement, which I appreciate. However, #GoToSocial's approach seems to offer some architectural advantages:

The three-tier permission model (allow/require approval/deny) feels more flexible than binary allow/deny
Separating approval objects from interactions appears more secure against forgery
The explicit handling of edge cases (mentioned users, post authors) provides clearer semantics
The extensible framework allows for handling diverse interaction types, not just replies

This is merely my initial impression though. I'd be curious to hear other developers' perspectives on these approaches.

#FEP5624 #fedidev #fediverse #replycontrol #interactionpolicy

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

After reviewing FEP-5624: Per-object reply control policies and GoToSocial's interaction policy spec, I find myself leaning toward the latter for long-term considerations, though both have merit.

FEP-5624 is admirably focused and simpler to implement, which I appreciate. However, #GoToSocial's approach seems to offer some architectural advantages:

The three-tier permission model (allow/require approval/deny) feels more flexible than binary allow/deny
Separating approval objects from interactions appears more secure against forgery
The explicit handling of edge cases (mentioned users, post authors) provides clearer semantics
The extensible framework allows for handling diverse interaction types, not just replies

This is merely my initial impression though. I'd be curious to hear other developers' perspectives on these approaches.

#FEP5624 #fedidev #fediverse #replycontrol #interactionpolicy

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

After reviewing FEP-5624: Per-object reply control policies and GoToSocial's interaction policy spec, I find myself leaning toward the latter for long-term considerations, though both have merit.

FEP-5624 is admirably focused and simpler to implement, which I appreciate. However, #GoToSocial's approach seems to offer some architectural advantages:

The three-tier permission model (allow/require approval/deny) feels more flexible than binary allow/deny
Separating approval objects from interactions appears more secure against forgery
The explicit handling of edge cases (mentioned users, post authors) provides clearer semantics
The extensible framework allows for handling diverse interaction types, not just replies

This is merely my initial impression though. I'd be curious to hear other developers' perspectives on these approaches.

#FEP5624 #fedidev #fediverse #replycontrol #interactionpolicy

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

After reviewing FEP-5624: Per-object reply control policies and GoToSocial's interaction policy spec, I find myself leaning toward the latter for long-term considerations, though both have merit.

FEP-5624 is admirably focused and simpler to implement, which I appreciate. However, #GoToSocial's approach seems to offer some architectural advantages:

The three-tier permission model (allow/require approval/deny) feels more flexible than binary allow/deny
Separating approval objects from interactions appears more secure against forgery
The explicit handling of edge cases (mentioned users, post authors) provides clearer semantics
The extensible framework allows for handling diverse interaction types, not just replies

This is merely my initial impression though. I'd be curious to hear other developers' perspectives on these approaches.

#FEP5624 #fedidev #fediverse #replycontrol #interactionpolicy

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

I've been wrestling with implementing #multilingual content support in Hackers' Pub, our #ActivityPub-powered platform for software engineers.

While ActivityPub theoretically supports multilingual content through the contentMap property, the reality is that most server implementations (Mastodon, Misskey, etc.) don't properly handle this content as of April 2025. This creates a significant challenge for us.

We want our users to share their knowledge in multiple languages, but we need to ensure compatibility with existing ActivityPub servers. I'm considering several approaches:

Creating separate posts for each language with clear language indicators, linking them through inReplyTo relationships (so translations appear as replies to the original post)
Using the primary language in content while storing translations in contentMap
Adding "View in other languages" links at the bottom of each post

Implementing inline language dividers that degrade gracefully on non-supporting servers, for example:

<div lang="en">
  <h3>English</h3>
  <p>This is the English content…</p>
</div>
<hr>
<div lang="ko">
  <h3>한국어</h3>
  <p>한국어 내용입니다…</p>
</div>

I'm leaning toward a hybrid approach—showing content in the user's preferred language when possible while providing easy access to other language versions.

Has anyone tackled this problem effectively? I'd love to hear about your experiences or ideas for making multilingual content work well in the fediverse, especially when dealing with server implementations that don't fully support ActivityPub's multilingual features.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Ayo Ayco

@ayo@ayco.io

Hey fedi devss! (Hints & boosts appreciated)

Mastodon API question — which instance/server API says where the URL redirects when there is no signed in user?

For example:
1. https://social.ayco.io goes to my profile; but
2. https://fosstodon.org goes to the explore tab

I am looking for the info via REST API

#askMastodon #fedidev

Ayo Ayco

@ayo@ayco.io

Hey fedi devss! (Hints & boosts appreciated)

Mastodon API question — which instance/server API says where the URL redirects when there is no signed in user?

For example:
1. https://social.ayco.io goes to my profile; but
2. https://fosstodon.org goes to the explore tab

We're pleased to announce the release of BotKit 0.2.0! For those new to our project, #BotKit is a #TypeScript framework for creating standalone #ActivityPub bots that can interact with Mastodon, Misskey, and other #fediverse platforms without the constraints of these existing platforms.

This release marks an important step in our journey to make fediverse bot development more accessible and powerful, introducing several features that our community has been requesting.

The Journey to Better Bot Interactions

In building BotKit, we've always focused on making bots more expressive and interactive. With version 0.2.0, we're taking this to the next level by bringing the social aspects of the fediverse to your bots.

Expressing Your Bot's Personality with Custom Emojis

One of the most requested features has been #custom_emoji support. Now your bots can truly express their personality with unique visuals that make their messages stand out.

// Define custom emojis for your bot
const emojis = bot.addCustomEmojis({
  botkit: { 
    file: `${import.meta.dirname}/images/botkit.png`, 
    type: "image/png" 
  },
  fedify: { 
    url: "https://fedify.dev/logo.png", 
    type: "image/png" 
  }
});

// Use these custom emojis in your messages
await session.publish(
  text`BotKit ${customEmoji(emojis.botkit)} is powered by Fedify ${customEmoji(emojis.fedify)}`
);

With this new API, you can:

Add custom emojis to your bot with Bot.addCustomEmojis()
Include these emojis in messages with the customEmoji() function
Use the text tagged template with Fedify Emoji objects

Engaging Through Reactions

Communication isn't just about posting messages—it's also about responding to others. The new reaction system creates natural interaction points between your bot and its followers:

// React to a message with a standard Unicode emoji
await message.react(emoji`👍`);

// Or use one of your custom emojis as a reaction
await message.react(emojis.botkit);

// Create a responsive bot that acknowledges reactions
bot.onReact = async (session, reaction) => {
  await session.publish(
    text`Thanks for reacting with ${reaction.emoji} to my message, ${reaction.actor}!`,
    { visibility: "direct" }
  );
};

This feature allows your bot to:

React to messages with Unicode emojis using Message.react()
React with the custom emojis you've defined
Handle reaction events with Bot.onReact and Bot.onUnreact handlers

Conversations Through Quotes

Discussions often involve referencing what others have said. Our new #quote support enables more cohesive conversation threads:

// Quote another message in your bot's post
await session.publish(
  text`Responding to this interesting point...`,
  { quoteTarget: originalMessage }
);

// Handle when users quote your bot's messages
bot.onQuote = async (session, quoteMessage) => {
  await session.publish(
    text`Thanks for sharing my thoughts, ${quoteMessage.actor}!`,
    { visibility: "direct" }
  );
};

With quote support, your bot can:

Quote messages with quoteTarget option
Access quoted messages via Message.quoteTarget
Handle quote events with the new Bot.onQuote event handler

Visual Enhancements

Because communication is visual too, we've improved how your bot presents itself:

Image attachments now properly display in the web interface
Your bot's content looks better and provides a richer experience

Behind the Scenes: Enhanced Activity Propagation

We've also improved how activities propagate through the fediverse:

More precise propagation of replies, shares, updates, and deletes
Activities are now properly sent to the original message authors

These improvements ensure your bot's interactions are consistent and reliable across different fediverse platforms.

Taking Your First Steps with BotKit 0.2.0

Ready to experience these new features? BotKit 0.2.0 is available on JSR and can be installed with a simple command:

deno add jsr:@fedify/botkit@0.2.0

Since BotKit uses the Temporal API (which is still evolving in JavaScript), remember to enable it in your deno.json:

{
  "imports": {
    "@fedify/botkit": "jsr:@fedify/botkit@0.2.0"
  },
  "unstable": ["temporal"]
}

With these simple steps, you're ready to create or upgrade your fediverse bot with our latest features.

Looking Forward

BotKit 0.2.0 represents our ongoing commitment to making fediverse bot development accessible, powerful, and enjoyable. We believe these new features will help your bots become more engaging and interactive members of the fediverse community.

For complete docs and more examples, visit our docs site.

Thank you to everyone who contributed to this release through feedback, feature requests, and code contributions. The BotKit community continues to grow, and we're excited to see what you'll create!

BotKit is powered by Fedify, a lower-level framework for creating ActivityPub server applications.

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

もしかしたらご存じないかもしれませんが、Fedifyには DiscordとMatrixのコミュニティがあります。ここでは、サポートを受けたり、機能について議論したり、ActivityPubやフェデレーテッドソーシャルネットワークについて話し合うことができます。

Matrixスペース：#fedify:matrix.org
Discordサーバー：https://discord.gg/bhtwpzURwd

お好みのコミュニティにご参加ください。どちらのチャンネルでも、Fedifyやフェデレーション関連のトピックについて活発な議論が行われています。

#Fedify #fedidev #ActivityPub #Discord #Matrix #디스코드 #매트릭스

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

혹시 모르고 계셨다면, Fedify는 Discord와 Matrix 커뮤니티를 운영하고 있습니다. 이곳에서 도움을 받거나, 기능에 대해 논의하거나, ActivityPub와 연합 소셜 네트워크에 대해 대화를 나눌 수 있습니다.

Matrix 스페이스: #fedify:matrix.org
Discord 서버: https://discord.gg/bhtwpzURwd

여러분의 선호도에 따라 어느 커뮤니티든 참여해 주세요. 두 채널 모두 Fedify와 연합 관련 주제에 대한 활발한 논의가 이루어지고 있습니다.

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

Matrixスペース：#fedify:matrix.org
Discordサーバー：https://discord.gg/bhtwpzURwd

#Fedify #fedidev #ActivityPub #Discord #Matrix #디스코드 #매트릭스

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

Matrix 스페이스: #fedify:matrix.org
Discord 서버: https://discord.gg/bhtwpzURwd

여러분의 선호도에 따라 어느 커뮤니티든 참여해 주세요. 두 채널 모두 Fedify와 연합 관련 주제에 대한 활발한 논의가 이루어지고 있습니다.

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

Matrixスペース：#fedify:matrix.org
Discordサーバー：https://discord.gg/bhtwpzURwd

#Fedify #fedidev #ActivityPub #Discord #Matrix #디스코드 #매트릭스

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

Matrix 스페이스: #fedify:matrix.org
Discord 서버: https://discord.gg/bhtwpzURwd

여러분의 선호도에 따라 어느 커뮤니티든 참여해 주세요. 두 채널 모두 Fedify와 연합 관련 주제에 대한 활발한 논의가 이루어지고 있습니다.

Fedify: an ActivityPub server framework

@fedify@hollo.social

📣 Exciting news! Fedify CLI is now available via Homebrew!

If you're using #Homebrew on macOS or #Linuxbrew on Linux, you can now install our CLI toolchain with a simple command:

brew install fedify

This makes it even easier to get started with building your federated server app. Try it out and let us know what you think!

BotKit by Fedify

@botkit@hollo.social · Reply to BotKit by Fedify :botkit:'s post

BotKit 0.2.0のリリース

BotKit 0.2.0をリリースしました！BotKitを初めて知る方のために簡単に説明すると、BotKitはTypeScriptで開発されたスタンドアロンのActivityPubボットフレームワークです。Mastodon、Misskeyなどさまざまなフェディバース（#fediverse）のプラットフォームと連携でき、既存プラットフォームの制約なしに自由にボットを作成できます。

このリリースは、フェディバースにおけるボット開発をより簡単で強力にするための旅の重要な一歩であり、コミュニティから要望のあった機能を多数導入しています。

より良いボットインタラクションへの旅

BotKitの開発において、私たちは常にボットをより表現力豊かでインタラクティブにすることに焦点を当ててきました。バージョン0.2.0では、フェディバースの社会的側面をボットに取り入れることで、さらに一歩前進しました。

カスタム絵文字でボットの個性を表現

最も要望の多かった機能の一つがカスタム絵文字のサポートです。これにより、ボットは独自の視覚要素でメッセージを目立たせ、自分だけの個性を表現できるようになりました。

// ボット用のカスタム絵文字を定義
const emojis = bot.addCustomEmojis({
  botkit: { 
    file: `${import.meta.dirname}/images/botkit.png`, 
    type: "image/png" 
  },
  fedify: { 
    url: "https://fedify.dev/logo.png", 
    type: "image/png" 
  }
});

// メッセージにカスタム絵文字を使用
await session.publish(
  text`BotKit ${customEmoji(emojis.botkit)}は、Fedify ${customEmoji(emojis.fedify)}によって支えられています`
);

この新しいAPIでは、次のことが可能になりました。

Bot.addCustomEmojis()でボットにカスタム絵文字を追加
customEmoji()関数でメッセージに絵文字を含める
FedifyのEmojiオブジェクトをtextタグテンプレートで使用する

リアクションによるコミュニケーション

コミュニケーションは単にメッセージを投稿するだけではありません。他の人のメッセージに反応することも重要です。新しいリアクションシステムは、ボットとフォロワーの間に自然な交流ポイントを作り出します。

// 標準のUnicode絵文字でメッセージにリアクション
await message.react(emoji`👍`);

// または定義したカスタム絵文字でリアクション
await message.react(emojis.botkit);

// リアクションを認識して応答するボットを作成
bot.onReact = async (session, reaction) => {
  await session.publish(
    text`${reaction.actor}さん、私のメッセージに${reaction.emoji}でリアクションしてくれてありがとうございます！`,
    { visibility: "direct" }
  );
};

この機能により、ボットは次のことができるようになりました。

Message.react()を使用してUnicode絵文字でメッセージにリアクション
定義したカスタム絵文字でリアクション
Bot.onReactとBot.onUnreactハンドラーでリアクションイベントを処理

引用による会話

議論では、他の人が言ったことを参照する必要がしばしばあります。新しい引用機能により、より結束力のある会話スレッドを作成できます。

// ボットの投稿で他のメッセージを引用
await session.publish(
  text`この興味深い視点について答えます...`,
  { quoteTarget: originalMessage }
);

// ユーザーがボットのメッセージを引用した場合の処理
bot.onQuote = async (session, quoteMessage) => {
  await session.publish(
    text`${quoteMessage.actor}さん、私の考えを共有してくれてありがとうございます！`,
    { visibility: "direct" }
  );
};

引用機能により、ボットは次のことができるようになりました。

quoteTargetオプションでメッセージを引用
Message.quoteTargetを通じて引用されたメッセージにアクセス
新しいBot.onQuoteイベントハンドラーで引用イベントを処理

視覚的な改善

コミュニケーションには視覚的要素も重要なため、ボットの表現方法を改善しました。

ウェブインターフェースで画像添付ファイルが正しく表示されるようになりました
ボットのコンテンツがより見やすくなり、豊かな体験を提供します

内部改善：活動の伝播の強化

フェディバースでの活動が伝播する方法も改善されました。

返信、共有、更新、削除のより正確な伝播
元のメッセージ作成者に活動が適切に送信されます

これらの改善により、様々なフェディバースプラットフォームでのボットの相互作用が一貫性と信頼性を持つようになります。

BotKit 0.2.0で最初の一歩を踏み出す

これらの新機能を体験してみたいですか？BotKit 0.2.0はJSRで利用可能で、簡単なコマンドでインストールできます。

deno add jsr:@fedify/botkit@0.2.0

BotKitはTemporal API（JavaScriptではまだ試験的な機能）を使用するため、deno.jsonでこれを有効にする必要があります。

{
  "imports": {
    "@fedify/botkit": "jsr:@fedify/botkit@0.2.0"
  },
  "unstable": ["temporal"]
}

これらの簡単なステップで、最新機能を使ってフェディバースボットを作成またはアップグレードする準備が整いました。

今後の展望

#BotKit 0.2.0は、フェディバースボット開発をアクセスしやすく、強力かつ楽しいものにするための私たちの継続的な取り組みを示しています。これらの新機能が、皆さんのボットをフェディバースコミュニティでより魅力的でインタラクティブなメンバーにするのに役立つと信じています。

完全なドキュメントと詳細な例については、私たちのドキュメントサイトをご覧ください。

フィードバック、機能リクエスト、コード貢献を通じてこのリリースに貢献してくださったすべての方々に感謝します。BotKitコミュニティは成長を続けており、皆さんが作成するものを楽しみにしています！

BotKitは、ActivityPubサーバーアプリケーションを作成するための低レベルフレームワークFedifyによって支えられています。

#fedidev #커모지 #커스텀_이모지 #에모지_반응 #이모지_반응 #에모지_리액션 #이모지_리액션

BotKit by Fedify

@botkit@hollo.social · Reply to BotKit by Fedify :botkit:'s post

BotKit 0.2.0 릴리스

BotKit 0.2.0 버전이 릴리스되었습니다! BotKit을 처음 접하시는 분들을 위해 간단히 소개하자면, BotKit은 TypeScript로 개발된 독립형 #ActivityPub 봇 프레임워크입니다. Mastodon, Misskey 등 다양한 #연합우주(#fediverse) 플랫폼과 상호작용할 수 있으며, 기존 플랫폼의 제약에서 벗어나 자유롭게 봇을 만들 수 있습니다.

이번 릴리스는 연합우주 봇 개발을 더 쉽고 강력하게 만들기 위한 여정에서 중요한 발걸음입니다. 커뮤니티에서 요청해 왔던 여러 기능들을 새롭게 선보입니다.

더 나은 봇 상호작용을 위한 여정

BotKit을 개발하면서 우리는 항상 봇이 더 표현력 있고 상호작용이 풍부하도록 만드는 데 집중해 왔습니다. 0.2.0 버전에서는 연합우주의 사회적 측면을 봇에 접목시켜 한 단계 더 발전시켰습니다.

커스텀 에모지로 봇의 개성 표현하기

가장 많이 요청받았던 기능 중 하나가 #커스텀_에모지 지원입니다. 이제 봇은 독특한 시각적 요소로 메시지를 돋보이게 하며 자신만의 개성을 표현할 수 있습니다.

// 봇의 커스텀 에모지 정의하기
const emojis = bot.addCustomEmojis({
  botkit: { 
    file: `${import.meta.dirname}/images/botkit.png`, 
    type: "image/png" 
  },
  fedify: { 
    url: "https://fedify.dev/logo.png", 
    type: "image/png" 
  }
});

// 메시지에 커스텀 에모지 사용하기
await session.publish(
  text`BotKit ${customEmoji(emojis.botkit)}은 Fedify ${customEmoji(emojis.fedify)}의 지원을 받습니다`
);

이 새로운 API를 통해 다음과 같은 기능을 사용할 수 있습니다.

Bot.addCustomEmojis()로 봇에 커스텀 에모지 추가하기
customEmoji() 함수로 메시지에 에모지 포함하기
Fedify의 Emoji 객체를 text 태그 템플릿에서 사용하기

반응을 통한 소통

소통은 단순히 메시지를 게시하는 것만이 아닙니다. 다른 사람의 메시지에 반응하는 것도 중요합니다. 새로운 반응 시스템은 봇과 팔로워 사이에 자연스러운 상호작용 지점을 만들어 줍니다.

// 표준 유니코드 에모지로 메시지에 반응하기
await message.react(emoji`👍`);

// 또는 정의한 커스텀 에모지로 반응하기
await message.react(emojis.botkit);

// 반응을 인식하고 응답하는 봇 만들기
bot.onReact = async (session, reaction) => {
  await session.publish(
    text`${reaction.actor}님, 제 메시지에 ${reaction.emoji} 반응을 남겨주셔서 감사합니다!`,
    { visibility: "direct" }
  );
};

이 기능을 통해 봇은 다음과 같은 작업을 수행할 수 있습니다.

Message.react()를 사용하여 유니코드 에모지로 메시지에 반응하기
정의한 커스텀 에모지로 반응하기
Bot.onReact와 Bot.onUnreact 핸들러로 반응 이벤트 처리하기

인용을 통한 대화

토론에서는 종종 다른 사람이 말한 내용을 참조해야 할 때가 있습니다. 새로운 #인용 기능은 더 응집력 있는 대화 스레드를 만들어 줍니다.

// 봇의 게시물에서 다른 메시지 인용하기
await session.publish(
  text`이 흥미로운 관점에 대한 답변입니다...`,
  { quoteTarget: originalMessage }
);

// 사용자가 봇의 메시지를 인용할 때 처리하기
bot.onQuote = async (session, quoteMessage) => {
  await session.publish(
    text`${quoteMessage.actor}님, 제 생각을 공유해 주셔서 감사합니다!`,
    { visibility: "direct" }
  );
};

인용 기능을 통해 봇은 다음과 같은 작업을 수행할 수 있습니다.

quoteTarget 옵션으로 메시지 인용하기
Message.quoteTarget을 통해 인용된 메시지에 접근하기
새로운 Bot.onQuote 이벤트 핸들러로 인용 이벤트 처리하기

시각적 개선

소통은 시각적인 요소도 중요하기 때문에 봇의 표현 방식을 개선했습니다.

웹 인터페이스에서 이미지 첨부파일이 제대로 표시됩니다
봇의 콘텐츠가 더 보기 좋아지고 풍부한 경험을 제공합니다

내부 개선: 향상된 액티비티 전파

연합우주에서 액티비티가 전파되는 방식도 개선했습니다.

답글, 공유, 업데이트, 삭제의 더 정확한 전파
원본 메시지 작성자에게 액티비티가 제대로 전송됩니다

이러한 개선 사항은 다양한 연합우주 플랫폼에서 봇의 상호작용이 일관되고 안정적으로 이루어지도록 보장합니다.

BotKit 0.2.0으로 첫 걸음 떼기

이러한 새로운 기능을 경험해 보고 싶으신가요? BotKit 0.2.0은 JSR에서 받을 수 있으며 간단한 명령어로 설치할 수 있습니다.

deno add jsr:@fedify/botkit@0.2.0

BotKit은 Temporal API(JavaScript에서 아직 시범적인 기능)를 사용하므로 deno.json에서 이를 활성화해야 합니다.

{
  "imports": {
    "@fedify/botkit": "jsr:@fedify/botkit@0.2.0"
  },
  "unstable": ["temporal"]
}

이 간단한 단계를 통해 최신 기능으로 연합우주 봇을 만들거나 업그레이드할 준비가 완료되었습니다.

앞으로의 전망

BotKit 0.2.0은 연합우주 봇 개발을 접근하기 쉽고, 강력하며, 즐겁게 만들기 위한 우리의 지속적인 노력을 보여줍니다. 이러한 새로운 기능들이 여러분의 봇이 연합우주 커뮤니티에서 더 매력적이고 상호작용이 풍부한 구성원이 되는 데 도움이 될 것이라고 믿습니다.

전체 문서와 더 많은 예제는 저희 문서 사이트에서 확인하실 수 있습니다.

피드백, 기능 요청, 코드 기여를 통해 이번 릴리스에 도움을 주신 모든 분들께 감사드립니다. BotKit 커뮤니티는 계속 성장하고 있으며, 여러분이 만들어낼 작품들을 기대합니다!

BotKit은 ActivityPub 서버 애플리케이션을 만들기 위한 하위 레벨 프레임워크인 Fedify의 지원을 받습니다.

BotKit by Fedify

@botkit@hollo.social

BotKit 0.2.0 Released

This release marks an important step in our journey to make fediverse bot development more accessible and powerful, introducing several features that our community has been requesting.

The Journey to Better Bot Interactions

Expressing Your Bot's Personality with Custom Emojis

One of the most requested features has been #custom_emoji support. Now your bots can truly express their personality with unique visuals that make their messages stand out.

// Define custom emojis for your bot
const emojis = bot.addCustomEmojis({
  botkit: { 
    file: `${import.meta.dirname}/images/botkit.png`, 
    type: "image/png" 
  },
  fedify: { 
    url: "https://fedify.dev/logo.png", 
    type: "image/png" 
  }
});

// Use these custom emojis in your messages
await session.publish(
  text`BotKit ${customEmoji(emojis.botkit)} is powered by Fedify ${customEmoji(emojis.fedify)}`
);

With this new API, you can:

Add custom emojis to your bot with Bot.addCustomEmojis()
Include these emojis in messages with the customEmoji() function
Use the text tagged template with Fedify Emoji objects

Engaging Through Reactions

Communication isn't just about posting messages—it's also about responding to others. The new reaction system creates natural interaction points between your bot and its followers:

// React to a message with a standard Unicode emoji
await message.react(emoji`👍`);

// Or use one of your custom emojis as a reaction
await message.react(emojis.botkit);

// Create a responsive bot that acknowledges reactions
bot.onReact = async (session, reaction) => {
  await session.publish(
    text`Thanks for reacting with ${reaction.emoji} to my message, ${reaction.actor}!`,
    { visibility: "direct" }
  );
};

This feature allows your bot to:

React to messages with Unicode emojis using Message.react()
React with the custom emojis you've defined
Handle reaction events with Bot.onReact and Bot.onUnreact handlers

Conversations Through Quotes

Discussions often involve referencing what others have said. Our new #quote support enables more cohesive conversation threads:

// Quote another message in your bot's post
await session.publish(
  text`Responding to this interesting point...`,
  { quoteTarget: originalMessage }
);

// Handle when users quote your bot's messages
bot.onQuote = async (session, quoteMessage) => {
  await session.publish(
    text`Thanks for sharing my thoughts, ${quoteMessage.actor}!`,
    { visibility: "direct" }
  );
};

With quote support, your bot can:

Quote messages with quoteTarget option
Access quoted messages via Message.quoteTarget
Handle quote events with the new Bot.onQuote event handler

Visual Enhancements

Because communication is visual too, we've improved how your bot presents itself:

Image attachments now properly display in the web interface
Your bot's content looks better and provides a richer experience

Behind the Scenes: Enhanced Activity Propagation

We've also improved how activities propagate through the fediverse:

More precise propagation of replies, shares, updates, and deletes
Activities are now properly sent to the original message authors

These improvements ensure your bot's interactions are consistent and reliable across different fediverse platforms.

Taking Your First Steps with BotKit 0.2.0

Ready to experience these new features? BotKit 0.2.0 is available on JSR and can be installed with a simple command:

deno add jsr:@fedify/botkit@0.2.0

Since BotKit uses the Temporal API (which is still evolving in JavaScript), remember to enable it in your deno.json:

{
  "imports": {
    "@fedify/botkit": "jsr:@fedify/botkit@0.2.0"
  },
  "unstable": ["temporal"]
}

With these simple steps, you're ready to create or upgrade your fediverse bot with our latest features.

Looking Forward

For complete docs and more examples, visit our docs site.

Thank you to everyone who contributed to this release through feedback, feature requests, and code contributions. The BotKit community continues to grow, and we're excited to see what you'll create!

BotKit is powered by Fedify, a lower-level framework for creating ActivityPub server applications.

Fedify: an ActivityPub server framework

@fedify@hollo.social

Hey folks! We're excited to share a preview of a new API coming in #Fedify 1.6 that should make structuring larger federated apps much cleaner: FederationBuilder.

As your Fedify applications grow, you might encounter circular dependency issues when registering dispatchers and listeners across multiple files. The new FederationBuilder pattern helps solve this by separating the configuration phase from instantiation.

Instead of this:

// federation.ts
import { createFederation } from "@fedify/fedify";

export const federation = createFederation<AppContext>({
  kv: new DbKvStore(), 
  queue: new RedisMessageQueue(),
  // Other options...
});

// Now we need to import this federation instance in other files
// to register dispatchers and listeners...

You can now do this:

// builder.ts
import { createFederationBuilder } from "@fedify/fedify";

export const builder = createFederationBuilder<AppContext>();

// other files can import and configure this builder...

// actors.ts
import { builder } from "./builder.ts";
import { Person } from "@fedify/fedify";

builder.setActorDispatcher("/users/{handle}", async (ctx, handle) => {
  // Actor implementation
});

// inbox.ts
import { builder } from "./builder.ts";
import { Follow } from "@fedify/fedify";

builder.setInboxListeners("/users/{handle}/inbox", "/inbox")
  .on(Follow, async (ctx, follow) => {
    // Follow handling
  });

// main.ts — Only create the Federation instance at startup
import { builder } from "./builder.ts";

// Build the Federation object with actual dependencies
export const federation = await builder.build({
  kv: new DbKvStore(),
  queue: new RedisMessageQueue(),
  // Other options...
});

This pattern helps avoid circular dependencies and makes your code more modular. Each part of your app can configure the builder without needing the actual Federation instance.

The full documentation will be available when 1.6 is released, but we wanted to share this early with our community. Looking forward to your feedback when it lands!

Want to try it right now? You can install the development version from JSR or npm:

# Deno
deno add jsr:@fedify/fedify@1.6.0-dev.777+1206cb01

# Node.js
npm add @fedify/fedify@1.6.0-dev.777

# Bun
bun add @fedify/fedify@1.6.0-dev.777

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

// federation.ts
import { createFederation } from "@fedify/fedify";

export const federation = createFederation<AppContext>({
  kv: new DbKvStore(), 
  queue: new RedisMessageQueue(),
  // Other options...
});

// Now we need to import this federation instance in other files
// to register dispatchers and listeners...

You can now do this:

// builder.ts
import { createFederationBuilder } from "@fedify/fedify";

export const builder = createFederationBuilder<AppContext>();

// other files can import and configure this builder...

// actors.ts
import { builder } from "./builder.ts";
import { Person } from "@fedify/fedify";

builder.setActorDispatcher("/users/{handle}", async (ctx, handle) => {
  // Actor implementation
});

// inbox.ts
import { builder } from "./builder.ts";
import { Follow } from "@fedify/fedify";

builder.setInboxListeners("/users/{handle}/inbox", "/inbox")
  .on(Follow, async (ctx, follow) => {
    // Follow handling
  });

// main.ts — Only create the Federation instance at startup
import { builder } from "./builder.ts";

// Build the Federation object with actual dependencies
export const federation = await builder.build({
  kv: new DbKvStore(),
  queue: new RedisMessageQueue(),
  // Other options...
});

This pattern helps avoid circular dependencies and makes your code more modular. Each part of your app can configure the builder without needing the actual Federation instance.

The full documentation will be available when 1.6 is released, but we wanted to share this early with our community. Looking forward to your feedback when it lands!

Want to try it right now? You can install the development version from JSR or npm:

# Deno
deno add jsr:@fedify/fedify@1.6.0-dev.777+1206cb01

# Node.js
npm add @fedify/fedify@1.6.0-dev.777

# Bun
bun add @fedify/fedify@1.6.0-dev.777

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

I've been reflecting lately on projects like @fedify, @hollo, and @botkit. Sometimes I wonder if I'm solving problems that very few people actually need solved. How many developers truly want to build their own #ActivityPub server from scratch?

It feels a bit like inventing shoes that let people walk on their hands all day. Would there be a viable market? How many would actually buy them?

That's the sense I get with these projects. They do have users who find them tremendously valuable, but the total user base is inherently limited. The tools serve an important function for a small audience of specialized developers.

There are moments when my motivation wavers. When the user community consists of just a handful of enthusiastic supporters, it's sometimes difficult to maintain momentum and justify the ongoing investment of time and energy.

And yet, there's something meaningful about creating specialized tools that solve complex problems well, even if they're only used by a few. Perhaps that's enough.

Fedify: an ActivityPub server framework

@fedify@hollo.social

Hey folks! We're excited to share a preview of a new API coming in #Fedify 1.6 that should make structuring larger federated apps much cleaner: FederationBuilder.

Instead of this:

// federation.ts
import { createFederation } from "@fedify/fedify";

export const federation = createFederation<AppContext>({
  kv: new DbKvStore(), 
  queue: new RedisMessageQueue(),
  // Other options...
});

// Now we need to import this federation instance in other files
// to register dispatchers and listeners...

You can now do this:

// builder.ts
import { createFederationBuilder } from "@fedify/fedify";

export const builder = createFederationBuilder<AppContext>();

// other files can import and configure this builder...

// actors.ts
import { builder } from "./builder.ts";
import { Person } from "@fedify/fedify";

builder.setActorDispatcher("/users/{handle}", async (ctx, handle) => {
  // Actor implementation
});

// inbox.ts
import { builder } from "./builder.ts";
import { Follow } from "@fedify/fedify";

builder.setInboxListeners("/users/{handle}/inbox", "/inbox")
  .on(Follow, async (ctx, follow) => {
    // Follow handling
  });

// main.ts — Only create the Federation instance at startup
import { builder } from "./builder.ts";

// Build the Federation object with actual dependencies
export const federation = await builder.build({
  kv: new DbKvStore(),
  queue: new RedisMessageQueue(),
  // Other options...
});

This pattern helps avoid circular dependencies and makes your code more modular. Each part of your app can configure the builder without needing the actual Federation instance.

The full documentation will be available when 1.6 is released, but we wanted to share this early with our community. Looking forward to your feedback when it lands!

Want to try it right now? You can install the development version from JSR or npm:

# Deno
deno add jsr:@fedify/fedify@1.6.0-dev.777+1206cb01

# Node.js
npm add @fedify/fedify@1.6.0-dev.777

# Bun
bun add @fedify/fedify@1.6.0-dev.777

Fedify: an ActivityPub server framework

@fedify@hollo.social

Hey folks! We're excited to share a preview of a new API coming in #Fedify 1.6 that should make structuring larger federated apps much cleaner: FederationBuilder.

Instead of this:

// federation.ts
import { createFederation } from "@fedify/fedify";

export const federation = createFederation<AppContext>({
  kv: new DbKvStore(), 
  queue: new RedisMessageQueue(),
  // Other options...
});

// Now we need to import this federation instance in other files
// to register dispatchers and listeners...

You can now do this:

// builder.ts
import { createFederationBuilder } from "@fedify/fedify";

export const builder = createFederationBuilder<AppContext>();

// other files can import and configure this builder...

// actors.ts
import { builder } from "./builder.ts";
import { Person } from "@fedify/fedify";

builder.setActorDispatcher("/users/{handle}", async (ctx, handle) => {
  // Actor implementation
});

// inbox.ts
import { builder } from "./builder.ts";
import { Follow } from "@fedify/fedify";

builder.setInboxListeners("/users/{handle}/inbox", "/inbox")
  .on(Follow, async (ctx, follow) => {
    // Follow handling
  });

// main.ts — Only create the Federation instance at startup
import { builder } from "./builder.ts";

// Build the Federation object with actual dependencies
export const federation = await builder.build({
  kv: new DbKvStore(),
  queue: new RedisMessageQueue(),
  // Other options...
});

This pattern helps avoid circular dependencies and makes your code more modular. Each part of your app can configure the builder without needing the actual Federation instance.

The full documentation will be available when 1.6 is released, but we wanted to share this early with our community. Looking forward to your feedback when it lands!

Want to try it right now? You can install the development version from JSR or npm:

# Deno
deno add jsr:@fedify/fedify@1.6.0-dev.777+1206cb01

# Node.js
npm add @fedify/fedify@1.6.0-dev.777

# Bun
bun add @fedify/fedify@1.6.0-dev.777

Fedify: an ActivityPub server framework

@fedify@hollo.social

Hey folks! We're excited to share a preview of a new API coming in #Fedify 1.6 that should make structuring larger federated apps much cleaner: FederationBuilder.

Instead of this:

// federation.ts
import { createFederation } from "@fedify/fedify";

export const federation = createFederation<AppContext>({
  kv: new DbKvStore(), 
  queue: new RedisMessageQueue(),
  // Other options...
});

// Now we need to import this federation instance in other files
// to register dispatchers and listeners...

You can now do this:

// builder.ts
import { createFederationBuilder } from "@fedify/fedify";

export const builder = createFederationBuilder<AppContext>();

// other files can import and configure this builder...

// actors.ts
import { builder } from "./builder.ts";
import { Person } from "@fedify/fedify";

builder.setActorDispatcher("/users/{handle}", async (ctx, handle) => {
  // Actor implementation
});

// inbox.ts
import { builder } from "./builder.ts";
import { Follow } from "@fedify/fedify";

builder.setInboxListeners("/users/{handle}/inbox", "/inbox")
  .on(Follow, async (ctx, follow) => {
    // Follow handling
  });

// main.ts — Only create the Federation instance at startup
import { builder } from "./builder.ts";

// Build the Federation object with actual dependencies
export const federation = await builder.build({
  kv: new DbKvStore(),
  queue: new RedisMessageQueue(),
  // Other options...
});

This pattern helps avoid circular dependencies and makes your code more modular. Each part of your app can configure the builder without needing the actual Federation instance.

The full documentation will be available when 1.6 is released, but we wanted to share this early with our community. Looking forward to your feedback when it lands!

Want to try it right now? You can install the development version from JSR or npm:

# Deno
deno add jsr:@fedify/fedify@1.6.0-dev.777+1206cb01

# Node.js
npm add @fedify/fedify@1.6.0-dev.777

# Bun
bun add @fedify/fedify@1.6.0-dev.777

Fedify: an ActivityPub server framework

@fedify@hollo.social

Hey folks! We're excited to share a preview of a new API coming in #Fedify 1.6 that should make structuring larger federated apps much cleaner: FederationBuilder.

Instead of this:

// federation.ts
import { createFederation } from "@fedify/fedify";

export const federation = createFederation<AppContext>({
  kv: new DbKvStore(), 
  queue: new RedisMessageQueue(),
  // Other options...
});

// Now we need to import this federation instance in other files
// to register dispatchers and listeners...

You can now do this:

// builder.ts
import { createFederationBuilder } from "@fedify/fedify";

export const builder = createFederationBuilder<AppContext>();

// other files can import and configure this builder...

// actors.ts
import { builder } from "./builder.ts";
import { Person } from "@fedify/fedify";

builder.setActorDispatcher("/users/{handle}", async (ctx, handle) => {
  // Actor implementation
});

// inbox.ts
import { builder } from "./builder.ts";
import { Follow } from "@fedify/fedify";

builder.setInboxListeners("/users/{handle}/inbox", "/inbox")
  .on(Follow, async (ctx, follow) => {
    // Follow handling
  });

// main.ts — Only create the Federation instance at startup
import { builder } from "./builder.ts";

// Build the Federation object with actual dependencies
export const federation = await builder.build({
  kv: new DbKvStore(),
  queue: new RedisMessageQueue(),
  // Other options...
});

This pattern helps avoid circular dependencies and makes your code more modular. Each part of your app can configure the builder without needing the actual Federation instance.

The full documentation will be available when 1.6 is released, but we wanted to share this early with our community. Looking forward to your feedback when it lands!

Want to try it right now? You can install the development version from JSR or npm:

# Deno
deno add jsr:@fedify/fedify@1.6.0-dev.777+1206cb01

# Node.js
npm add @fedify/fedify@1.6.0-dev.777

# Bun
bun add @fedify/fedify@1.6.0-dev.777

Fedify: an ActivityPub server framework

@fedify@hollo.social

Hey folks! We're excited to share a preview of a new API coming in #Fedify 1.6 that should make structuring larger federated apps much cleaner: FederationBuilder.

Instead of this:

// federation.ts
import { createFederation } from "@fedify/fedify";

export const federation = createFederation<AppContext>({
  kv: new DbKvStore(), 
  queue: new RedisMessageQueue(),
  // Other options...
});

// Now we need to import this federation instance in other files
// to register dispatchers and listeners...

You can now do this:

// builder.ts
import { createFederationBuilder } from "@fedify/fedify";

export const builder = createFederationBuilder<AppContext>();

// other files can import and configure this builder...

// actors.ts
import { builder } from "./builder.ts";
import { Person } from "@fedify/fedify";

builder.setActorDispatcher("/users/{handle}", async (ctx, handle) => {
  // Actor implementation
});

// inbox.ts
import { builder } from "./builder.ts";
import { Follow } from "@fedify/fedify";

builder.setInboxListeners("/users/{handle}/inbox", "/inbox")
  .on(Follow, async (ctx, follow) => {
    // Follow handling
  });

// main.ts — Only create the Federation instance at startup
import { builder } from "./builder.ts";

// Build the Federation object with actual dependencies
export const federation = await builder.build({
  kv: new DbKvStore(),
  queue: new RedisMessageQueue(),
  // Other options...
});

This pattern helps avoid circular dependencies and makes your code more modular. Each part of your app can configure the builder without needing the actual Federation instance.

The full documentation will be available when 1.6 is released, but we wanted to share this early with our community. Looking forward to your feedback when it lands!

Want to try it right now? You can install the development version from JSR or npm:

# Deno
deno add jsr:@fedify/fedify@1.6.0-dev.777+1206cb01

# Node.js
npm add @fedify/fedify@1.6.0-dev.777

# Bun
bun add @fedify/fedify@1.6.0-dev.777

Fedify: an ActivityPub server framework

@fedify@hollo.social

Hey folks! We're excited to share a preview of a new API coming in #Fedify 1.6 that should make structuring larger federated apps much cleaner: FederationBuilder.

Instead of this:

// federation.ts
import { createFederation } from "@fedify/fedify";

export const federation = createFederation<AppContext>({
  kv: new DbKvStore(), 
  queue: new RedisMessageQueue(),
  // Other options...
});

// Now we need to import this federation instance in other files
// to register dispatchers and listeners...

You can now do this:

// builder.ts
import { createFederationBuilder } from "@fedify/fedify";

export const builder = createFederationBuilder<AppContext>();

// other files can import and configure this builder...

// actors.ts
import { builder } from "./builder.ts";
import { Person } from "@fedify/fedify";

builder.setActorDispatcher("/users/{handle}", async (ctx, handle) => {
  // Actor implementation
});

// inbox.ts
import { builder } from "./builder.ts";
import { Follow } from "@fedify/fedify";

builder.setInboxListeners("/users/{handle}/inbox", "/inbox")
  .on(Follow, async (ctx, follow) => {
    // Follow handling
  });

// main.ts — Only create the Federation instance at startup
import { builder } from "./builder.ts";

// Build the Federation object with actual dependencies
export const federation = await builder.build({
  kv: new DbKvStore(),
  queue: new RedisMessageQueue(),
  // Other options...
});

This pattern helps avoid circular dependencies and makes your code more modular. Each part of your app can configure the builder without needing the actual Federation instance.

The full documentation will be available when 1.6 is released, but we wanted to share this early with our community. Looking forward to your feedback when it lands!

Want to try it right now? You can install the development version from JSR or npm:

# Deno
deno add jsr:@fedify/fedify@1.6.0-dev.777+1206cb01

# Node.js
npm add @fedify/fedify@1.6.0-dev.777

# Bun
bun add @fedify/fedify@1.6.0-dev.777

Fedify: an ActivityPub server framework

@fedify@hollo.social

Hey folks! We're excited to share a preview of a new API coming in #Fedify 1.6 that should make structuring larger federated apps much cleaner: FederationBuilder.

Instead of this:

// federation.ts
import { createFederation } from "@fedify/fedify";

export const federation = createFederation<AppContext>({
  kv: new DbKvStore(), 
  queue: new RedisMessageQueue(),
  // Other options...
});

// Now we need to import this federation instance in other files
// to register dispatchers and listeners...

You can now do this:

// builder.ts
import { createFederationBuilder } from "@fedify/fedify";

export const builder = createFederationBuilder<AppContext>();

// other files can import and configure this builder...

// actors.ts
import { builder } from "./builder.ts";
import { Person } from "@fedify/fedify";

builder.setActorDispatcher("/users/{handle}", async (ctx, handle) => {
  // Actor implementation
});

// inbox.ts
import { builder } from "./builder.ts";
import { Follow } from "@fedify/fedify";

builder.setInboxListeners("/users/{handle}/inbox", "/inbox")
  .on(Follow, async (ctx, follow) => {
    // Follow handling
  });

// main.ts — Only create the Federation instance at startup
import { builder } from "./builder.ts";

// Build the Federation object with actual dependencies
export const federation = await builder.build({
  kv: new DbKvStore(),
  queue: new RedisMessageQueue(),
  // Other options...
});

This pattern helps avoid circular dependencies and makes your code more modular. Each part of your app can configure the builder without needing the actual Federation instance.

The full documentation will be available when 1.6 is released, but we wanted to share this early with our community. Looking forward to your feedback when it lands!

Want to try it right now? You can install the development version from JSR or npm:

# Deno
deno add jsr:@fedify/fedify@1.6.0-dev.777+1206cb01

# Node.js
npm add @fedify/fedify@1.6.0-dev.777

# Bun
bun add @fedify/fedify@1.6.0-dev.777

Fedify: an ActivityPub server framework

@fedify@hollo.social

Hey folks! We're excited to share a preview of a new API coming in #Fedify 1.6 that should make structuring larger federated apps much cleaner: FederationBuilder.

Instead of this:

// federation.ts
import { createFederation } from "@fedify/fedify";

export const federation = createFederation<AppContext>({
  kv: new DbKvStore(), 
  queue: new RedisMessageQueue(),
  // Other options...
});

// Now we need to import this federation instance in other files
// to register dispatchers and listeners...

You can now do this:

// builder.ts
import { createFederationBuilder } from "@fedify/fedify";

export const builder = createFederationBuilder<AppContext>();

// other files can import and configure this builder...

// actors.ts
import { builder } from "./builder.ts";
import { Person } from "@fedify/fedify";

builder.setActorDispatcher("/users/{handle}", async (ctx, handle) => {
  // Actor implementation
});

// inbox.ts
import { builder } from "./builder.ts";
import { Follow } from "@fedify/fedify";

builder.setInboxListeners("/users/{handle}/inbox", "/inbox")
  .on(Follow, async (ctx, follow) => {
    // Follow handling
  });

// main.ts — Only create the Federation instance at startup
import { builder } from "./builder.ts";

// Build the Federation object with actual dependencies
export const federation = await builder.build({
  kv: new DbKvStore(),
  queue: new RedisMessageQueue(),
  // Other options...
});

This pattern helps avoid circular dependencies and makes your code more modular. Each part of your app can configure the builder without needing the actual Federation instance.

The full documentation will be available when 1.6 is released, but we wanted to share this early with our community. Looking forward to your feedback when it lands!

Want to try it right now? You can install the development version from JSR or npm:

# Deno
deno add jsr:@fedify/fedify@1.6.0-dev.777+1206cb01

# Node.js
npm add @fedify/fedify@1.6.0-dev.777

# Bun
bun add @fedify/fedify@1.6.0-dev.777

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

As someone who has developed several #ActivityPub software implementations (Fedify, Hollo, BotKit, and Hackers' Pub), I believe one of the most frustrating features to implement in the #fediverse is #custom_emoji.

The challenges are numerous:

First, there's no standardization. ActivityPub specifications don't define how custom emoji should work, leading to inconsistent implementations across different servers like Mastodon and Misskey.

Rendering is particularly problematic. Emojis must display properly across different contexts (in text, as reactions, in emoji pickers) while maintaining quality at various sizes. Animated emojis add another layer of complexity.

Perhaps most concerning is the poor #accessibility. Most implementations simply use the emoji code (like :party_blob:) as the alt text, which provides no meaningful information to screen reader users (in particular, non-English speakers) about what the emoji actually depicts or means.

What really dampens my motivation to implement this feature is knowing I'm investing significant effort into something that ultimately creates accessibility barriers. It's disheartening to work hard on a feature that excludes part of the community.

Fedify: an ActivityPub server framework

@fedify@hollo.social

Hey folks! We're excited to share a preview of a new API coming in #Fedify 1.6 that should make structuring larger federated apps much cleaner: FederationBuilder.

Instead of this:

// federation.ts
import { createFederation } from "@fedify/fedify";

export const federation = createFederation<AppContext>({
  kv: new DbKvStore(), 
  queue: new RedisMessageQueue(),
  // Other options...
});

// Now we need to import this federation instance in other files
// to register dispatchers and listeners...

You can now do this:

// builder.ts
import { createFederationBuilder } from "@fedify/fedify";

export const builder = createFederationBuilder<AppContext>();

// other files can import and configure this builder...

// actors.ts
import { builder } from "./builder.ts";
import { Person } from "@fedify/fedify";

builder.setActorDispatcher("/users/{handle}", async (ctx, handle) => {
  // Actor implementation
});

// inbox.ts
import { builder } from "./builder.ts";
import { Follow } from "@fedify/fedify";

builder.setInboxListeners("/users/{handle}/inbox", "/inbox")
  .on(Follow, async (ctx, follow) => {
    // Follow handling
  });

// main.ts — Only create the Federation instance at startup
import { builder } from "./builder.ts";

// Build the Federation object with actual dependencies
export const federation = await builder.build({
  kv: new DbKvStore(),
  queue: new RedisMessageQueue(),
  // Other options...
});

This pattern helps avoid circular dependencies and makes your code more modular. Each part of your app can configure the builder without needing the actual Federation instance.

The full documentation will be available when 1.6 is released, but we wanted to share this early with our community. Looking forward to your feedback when it lands!

Want to try it right now? You can install the development version from JSR or npm:

# Deno
deno add jsr:@fedify/fedify@1.6.0-dev.777+1206cb01

# Node.js
npm add @fedify/fedify@1.6.0-dev.777

# Bun
bun add @fedify/fedify@1.6.0-dev.777

Fedify: an ActivityPub server framework

@fedify@hollo.social

Hey folks! We're excited to share a preview of a new API coming in #Fedify 1.6 that should make structuring larger federated apps much cleaner: FederationBuilder.

Instead of this:

// federation.ts
import { createFederation } from "@fedify/fedify";

export const federation = createFederation<AppContext>({
  kv: new DbKvStore(), 
  queue: new RedisMessageQueue(),
  // Other options...
});

// Now we need to import this federation instance in other files
// to register dispatchers and listeners...

You can now do this:

// builder.ts
import { createFederationBuilder } from "@fedify/fedify";

export const builder = createFederationBuilder<AppContext>();

// other files can import and configure this builder...

// actors.ts
import { builder } from "./builder.ts";
import { Person } from "@fedify/fedify";

builder.setActorDispatcher("/users/{handle}", async (ctx, handle) => {
  // Actor implementation
});

// inbox.ts
import { builder } from "./builder.ts";
import { Follow } from "@fedify/fedify";

builder.setInboxListeners("/users/{handle}/inbox", "/inbox")
  .on(Follow, async (ctx, follow) => {
    // Follow handling
  });

// main.ts — Only create the Federation instance at startup
import { builder } from "./builder.ts";

// Build the Federation object with actual dependencies
export const federation = await builder.build({
  kv: new DbKvStore(),
  queue: new RedisMessageQueue(),
  // Other options...
});

This pattern helps avoid circular dependencies and makes your code more modular. Each part of your app can configure the builder without needing the actual Federation instance.

The full documentation will be available when 1.6 is released, but we wanted to share this early with our community. Looking forward to your feedback when it lands!

Want to try it right now? You can install the development version from JSR or npm:

# Deno
deno add jsr:@fedify/fedify@1.6.0-dev.777+1206cb01

# Node.js
npm add @fedify/fedify@1.6.0-dev.777

# Bun
bun add @fedify/fedify@1.6.0-dev.777

Fedify: an ActivityPub server framework

@fedify@hollo.social

Hey folks! We're excited to share a preview of a new API coming in #Fedify 1.6 that should make structuring larger federated apps much cleaner: FederationBuilder.

Instead of this:

// federation.ts
import { createFederation } from "@fedify/fedify";

export const federation = createFederation<AppContext>({
  kv: new DbKvStore(), 
  queue: new RedisMessageQueue(),
  // Other options...
});

// Now we need to import this federation instance in other files
// to register dispatchers and listeners...

You can now do this:

// builder.ts
import { createFederationBuilder } from "@fedify/fedify";

export const builder = createFederationBuilder<AppContext>();

// other files can import and configure this builder...

// actors.ts
import { builder } from "./builder.ts";
import { Person } from "@fedify/fedify";

builder.setActorDispatcher("/users/{handle}", async (ctx, handle) => {
  // Actor implementation
});

// inbox.ts
import { builder } from "./builder.ts";
import { Follow } from "@fedify/fedify";

builder.setInboxListeners("/users/{handle}/inbox", "/inbox")
  .on(Follow, async (ctx, follow) => {
    // Follow handling
  });

// main.ts — Only create the Federation instance at startup
import { builder } from "./builder.ts";

// Build the Federation object with actual dependencies
export const federation = await builder.build({
  kv: new DbKvStore(),
  queue: new RedisMessageQueue(),
  // Other options...
});

This pattern helps avoid circular dependencies and makes your code more modular. Each part of your app can configure the builder without needing the actual Federation instance.

The full documentation will be available when 1.6 is released, but we wanted to share this early with our community. Looking forward to your feedback when it lands!

Want to try it right now? You can install the development version from JSR or npm:

# Deno
deno add jsr:@fedify/fedify@1.6.0-dev.777+1206cb01

# Node.js
npm add @fedify/fedify@1.6.0-dev.777

# Bun
bun add @fedify/fedify@1.6.0-dev.777

Fedify: an ActivityPub server framework

@fedify@hollo.social

Hey folks! We're excited to share a preview of a new API coming in #Fedify 1.6 that should make structuring larger federated apps much cleaner: FederationBuilder.

Instead of this:

// federation.ts
import { createFederation } from "@fedify/fedify";

export const federation = createFederation<AppContext>({
  kv: new DbKvStore(), 
  queue: new RedisMessageQueue(),
  // Other options...
});

// Now we need to import this federation instance in other files
// to register dispatchers and listeners...

You can now do this:

// builder.ts
import { createFederationBuilder } from "@fedify/fedify";

export const builder = createFederationBuilder<AppContext>();

// other files can import and configure this builder...

// actors.ts
import { builder } from "./builder.ts";
import { Person } from "@fedify/fedify";

builder.setActorDispatcher("/users/{handle}", async (ctx, handle) => {
  // Actor implementation
});

// inbox.ts
import { builder } from "./builder.ts";
import { Follow } from "@fedify/fedify";

builder.setInboxListeners("/users/{handle}/inbox", "/inbox")
  .on(Follow, async (ctx, follow) => {
    // Follow handling
  });

// main.ts — Only create the Federation instance at startup
import { builder } from "./builder.ts";

// Build the Federation object with actual dependencies
export const federation = await builder.build({
  kv: new DbKvStore(),
  queue: new RedisMessageQueue(),
  // Other options...
});

This pattern helps avoid circular dependencies and makes your code more modular. Each part of your app can configure the builder without needing the actual Federation instance.

The full documentation will be available when 1.6 is released, but we wanted to share this early with our community. Looking forward to your feedback when it lands!

Want to try it right now? You can install the development version from JSR or npm:

# Deno
deno add jsr:@fedify/fedify@1.6.0-dev.777+1206cb01

# Node.js
npm add @fedify/fedify@1.6.0-dev.777

# Bun
bun add @fedify/fedify@1.6.0-dev.777

Fedify: an ActivityPub server framework

@fedify@hollo.social

Hey folks! We're excited to share a preview of a new API coming in #Fedify 1.6 that should make structuring larger federated apps much cleaner: FederationBuilder.

Instead of this:

// federation.ts
import { createFederation } from "@fedify/fedify";

export const federation = createFederation<AppContext>({
  kv: new DbKvStore(), 
  queue: new RedisMessageQueue(),
  // Other options...
});

// Now we need to import this federation instance in other files
// to register dispatchers and listeners...

You can now do this:

// builder.ts
import { createFederationBuilder } from "@fedify/fedify";

export const builder = createFederationBuilder<AppContext>();

// other files can import and configure this builder...

// actors.ts
import { builder } from "./builder.ts";
import { Person } from "@fedify/fedify";

builder.setActorDispatcher("/users/{handle}", async (ctx, handle) => {
  // Actor implementation
});

// inbox.ts
import { builder } from "./builder.ts";
import { Follow } from "@fedify/fedify";

builder.setInboxListeners("/users/{handle}/inbox", "/inbox")
  .on(Follow, async (ctx, follow) => {
    // Follow handling
  });

// main.ts — Only create the Federation instance at startup
import { builder } from "./builder.ts";

// Build the Federation object with actual dependencies
export const federation = await builder.build({
  kv: new DbKvStore(),
  queue: new RedisMessageQueue(),
  // Other options...
});

This pattern helps avoid circular dependencies and makes your code more modular. Each part of your app can configure the builder without needing the actual Federation instance.

The full documentation will be available when 1.6 is released, but we wanted to share this early with our community. Looking forward to your feedback when it lands!

Want to try it right now? You can install the development version from JSR or npm:

# Deno
deno add jsr:@fedify/fedify@1.6.0-dev.777+1206cb01

# Node.js
npm add @fedify/fedify@1.6.0-dev.777

# Bun
bun add @fedify/fedify@1.6.0-dev.777

Fedify: an ActivityPub server framework

@fedify@hollo.social

Hey folks! We're excited to share a preview of a new API coming in #Fedify 1.6 that should make structuring larger federated apps much cleaner: FederationBuilder.

Instead of this:

// federation.ts
import { createFederation } from "@fedify/fedify";

export const federation = createFederation<AppContext>({
  kv: new DbKvStore(), 
  queue: new RedisMessageQueue(),
  // Other options...
});

// Now we need to import this federation instance in other files
// to register dispatchers and listeners...

You can now do this:

// builder.ts
import { createFederationBuilder } from "@fedify/fedify";

export const builder = createFederationBuilder<AppContext>();

// other files can import and configure this builder...

// actors.ts
import { builder } from "./builder.ts";
import { Person } from "@fedify/fedify";

builder.setActorDispatcher("/users/{handle}", async (ctx, handle) => {
  // Actor implementation
});

// inbox.ts
import { builder } from "./builder.ts";
import { Follow } from "@fedify/fedify";

builder.setInboxListeners("/users/{handle}/inbox", "/inbox")
  .on(Follow, async (ctx, follow) => {
    // Follow handling
  });

// main.ts — Only create the Federation instance at startup
import { builder } from "./builder.ts";

// Build the Federation object with actual dependencies
export const federation = await builder.build({
  kv: new DbKvStore(),
  queue: new RedisMessageQueue(),
  // Other options...
});

This pattern helps avoid circular dependencies and makes your code more modular. Each part of your app can configure the builder without needing the actual Federation instance.

The full documentation will be available when 1.6 is released, but we wanted to share this early with our community. Looking forward to your feedback when it lands!

Want to try it right now? You can install the development version from JSR or npm:

# Deno
deno add jsr:@fedify/fedify@1.6.0-dev.777+1206cb01

# Node.js
npm add @fedify/fedify@1.6.0-dev.777

# Bun
bun add @fedify/fedify@1.6.0-dev.777

BotKit by Fedify

@botkit@hollo.social · Reply to BotKit by Fedify :botkit:'s post

BotKit 0.2.0のリリース

より良いボットインタラクションへの旅

カスタム絵文字でボットの個性を表現

// ボット用のカスタム絵文字を定義
const emojis = bot.addCustomEmojis({
  botkit: { 
    file: `${import.meta.dirname}/images/botkit.png`, 
    type: "image/png" 
  },
  fedify: { 
    url: "https://fedify.dev/logo.png", 
    type: "image/png" 
  }
});

// メッセージにカスタム絵文字を使用
await session.publish(
  text`BotKit ${customEmoji(emojis.botkit)}は、Fedify ${customEmoji(emojis.fedify)}によって支えられています`
);

この新しいAPIでは、次のことが可能になりました。

Bot.addCustomEmojis()でボットにカスタム絵文字を追加
customEmoji()関数でメッセージに絵文字を含める
FedifyのEmojiオブジェクトをtextタグテンプレートで使用する

リアクションによるコミュニケーション

// 標準のUnicode絵文字でメッセージにリアクション
await message.react(emoji`👍`);

// または定義したカスタム絵文字でリアクション
await message.react(emojis.botkit);

// リアクションを認識して応答するボットを作成
bot.onReact = async (session, reaction) => {
  await session.publish(
    text`${reaction.actor}さん、私のメッセージに${reaction.emoji}でリアクションしてくれてありがとうございます！`,
    { visibility: "direct" }
  );
};

この機能により、ボットは次のことができるようになりました。

Message.react()を使用してUnicode絵文字でメッセージにリアクション
定義したカスタム絵文字でリアクション
Bot.onReactとBot.onUnreactハンドラーでリアクションイベントを処理

引用による会話

議論では、他の人が言ったことを参照する必要がしばしばあります。新しい引用機能により、より結束力のある会話スレッドを作成できます。

// ボットの投稿で他のメッセージを引用
await session.publish(
  text`この興味深い視点について答えます...`,
  { quoteTarget: originalMessage }
);

// ユーザーがボットのメッセージを引用した場合の処理
bot.onQuote = async (session, quoteMessage) => {
  await session.publish(
    text`${quoteMessage.actor}さん、私の考えを共有してくれてありがとうございます！`,
    { visibility: "direct" }
  );
};

引用機能により、ボットは次のことができるようになりました。

quoteTargetオプションでメッセージを引用
Message.quoteTargetを通じて引用されたメッセージにアクセス
新しいBot.onQuoteイベントハンドラーで引用イベントを処理

視覚的な改善

コミュニケーションには視覚的要素も重要なため、ボットの表現方法を改善しました。

ウェブインターフェースで画像添付ファイルが正しく表示されるようになりました
ボットのコンテンツがより見やすくなり、豊かな体験を提供します

内部改善：活動の伝播の強化

フェディバースでの活動が伝播する方法も改善されました。

返信、共有、更新、削除のより正確な伝播
元のメッセージ作成者に活動が適切に送信されます

これらの改善により、様々なフェディバースプラットフォームでのボットの相互作用が一貫性と信頼性を持つようになります。

BotKit 0.2.0で最初の一歩を踏み出す

これらの新機能を体験してみたいですか？BotKit 0.2.0はJSRで利用可能で、簡単なコマンドでインストールできます。

deno add jsr:@fedify/botkit@0.2.0

BotKitはTemporal API（JavaScriptではまだ試験的な機能）を使用するため、deno.jsonでこれを有効にする必要があります。

{
  "imports": {
    "@fedify/botkit": "jsr:@fedify/botkit@0.2.0"
  },
  "unstable": ["temporal"]
}

これらの簡単なステップで、最新機能を使ってフェディバースボットを作成またはアップグレードする準備が整いました。

今後の展望

完全なドキュメントと詳細な例については、私たちのドキュメントサイトをご覧ください。

BotKitは、ActivityPubサーバーアプリケーションを作成するための低レベルフレームワークFedifyによって支えられています。

BotKit by Fedify

@botkit@hollo.social · Reply to BotKit by Fedify :botkit:'s post

BotKit 0.2.0のリリース

より良いボットインタラクションへの旅

カスタム絵文字でボットの個性を表現

// ボット用のカスタム絵文字を定義
const emojis = bot.addCustomEmojis({
  botkit: { 
    file: `${import.meta.dirname}/images/botkit.png`, 
    type: "image/png" 
  },
  fedify: { 
    url: "https://fedify.dev/logo.png", 
    type: "image/png" 
  }
});

// メッセージにカスタム絵文字を使用
await session.publish(
  text`BotKit ${customEmoji(emojis.botkit)}は、Fedify ${customEmoji(emojis.fedify)}によって支えられています`
);

この新しいAPIでは、次のことが可能になりました。

Bot.addCustomEmojis()でボットにカスタム絵文字を追加
customEmoji()関数でメッセージに絵文字を含める
FedifyのEmojiオブジェクトをtextタグテンプレートで使用する

リアクションによるコミュニケーション

// 標準のUnicode絵文字でメッセージにリアクション
await message.react(emoji`👍`);

// または定義したカスタム絵文字でリアクション
await message.react(emojis.botkit);

// リアクションを認識して応答するボットを作成
bot.onReact = async (session, reaction) => {
  await session.publish(
    text`${reaction.actor}さん、私のメッセージに${reaction.emoji}でリアクションしてくれてありがとうございます！`,
    { visibility: "direct" }
  );
};

この機能により、ボットは次のことができるようになりました。

Message.react()を使用してUnicode絵文字でメッセージにリアクション
定義したカスタム絵文字でリアクション
Bot.onReactとBot.onUnreactハンドラーでリアクションイベントを処理

引用による会話

議論では、他の人が言ったことを参照する必要がしばしばあります。新しい引用機能により、より結束力のある会話スレッドを作成できます。

// ボットの投稿で他のメッセージを引用
await session.publish(
  text`この興味深い視点について答えます...`,
  { quoteTarget: originalMessage }
);

// ユーザーがボットのメッセージを引用した場合の処理
bot.onQuote = async (session, quoteMessage) => {
  await session.publish(
    text`${quoteMessage.actor}さん、私の考えを共有してくれてありがとうございます！`,
    { visibility: "direct" }
  );
};

引用機能により、ボットは次のことができるようになりました。

quoteTargetオプションでメッセージを引用
Message.quoteTargetを通じて引用されたメッセージにアクセス
新しいBot.onQuoteイベントハンドラーで引用イベントを処理

視覚的な改善

コミュニケーションには視覚的要素も重要なため、ボットの表現方法を改善しました。

ウェブインターフェースで画像添付ファイルが正しく表示されるようになりました
ボットのコンテンツがより見やすくなり、豊かな体験を提供します

内部改善：活動の伝播の強化

フェディバースでの活動が伝播する方法も改善されました。

返信、共有、更新、削除のより正確な伝播
元のメッセージ作成者に活動が適切に送信されます

これらの改善により、様々なフェディバースプラットフォームでのボットの相互作用が一貫性と信頼性を持つようになります。

BotKit 0.2.0で最初の一歩を踏み出す

これらの新機能を体験してみたいですか？BotKit 0.2.0はJSRで利用可能で、簡単なコマンドでインストールできます。

deno add jsr:@fedify/botkit@0.2.0

BotKitはTemporal API（JavaScriptではまだ試験的な機能）を使用するため、deno.jsonでこれを有効にする必要があります。

{
  "imports": {
    "@fedify/botkit": "jsr:@fedify/botkit@0.2.0"
  },
  "unstable": ["temporal"]
}

これらの簡単なステップで、最新機能を使ってフェディバースボットを作成またはアップグレードする準備が整いました。

@reiver@mastodon.social · Reply to @reiver ⊼ (Charles) :batman:'s post

A HEALTH-CHECK URL would, for example, make sure:

• the web-server is up,
• the database connection is fine,
• maybe query one or more important tables to make sure that still works,
• make sure any 3rd party APIs are working,
• etc.

If any of those things has a problem, then it would return "500 Internal Server Error".

Else (if everything was fine then) it would return "200 OK".

@reiver ⊼ (Charles)

@reiver@mastodon.social

A lot of Fediverse software has a HEALTH-CHECK URL.

But not all Fediverse does.

It would be better if ALL Fediverse software had a HEALTH-CHECK URL.

...

A HEALTH-CHECK URL is a special URL that tell others if the system is running properly.

It would return "200 OK" if everything is fine. And return "500 Internal Server Error" if there is a problem

...

A HEALTH-CHECK URL is important to those who actual run and administrate Fediverse servers

BotKit by Fedify

@botkit@hollo.social

BotKit 0.2.0 Released

This release marks an important step in our journey to make fediverse bot development more accessible and powerful, introducing several features that our community has been requesting.

The Journey to Better Bot Interactions

Expressing Your Bot's Personality with Custom Emojis

One of the most requested features has been #custom_emoji support. Now your bots can truly express their personality with unique visuals that make their messages stand out.

// Define custom emojis for your bot
const emojis = bot.addCustomEmojis({
  botkit: { 
    file: `${import.meta.dirname}/images/botkit.png`, 
    type: "image/png" 
  },
  fedify: { 
    url: "https://fedify.dev/logo.png", 
    type: "image/png" 
  }
});

// Use these custom emojis in your messages
await session.publish(
  text`BotKit ${customEmoji(emojis.botkit)} is powered by Fedify ${customEmoji(emojis.fedify)}`
);

With this new API, you can:

Add custom emojis to your bot with Bot.addCustomEmojis()
Include these emojis in messages with the customEmoji() function
Use the text tagged template with Fedify Emoji objects

Engaging Through Reactions

Communication isn't just about posting messages—it's also about responding to others. The new reaction system creates natural interaction points between your bot and its followers:

// React to a message with a standard Unicode emoji
await message.react(emoji`👍`);

// Or use one of your custom emojis as a reaction
await message.react(emojis.botkit);

// Create a responsive bot that acknowledges reactions
bot.onReact = async (session, reaction) => {
  await session.publish(
    text`Thanks for reacting with ${reaction.emoji} to my message, ${reaction.actor}!`,
    { visibility: "direct" }
  );
};

This feature allows your bot to:

React to messages with Unicode emojis using Message.react()
React with the custom emojis you've defined
Handle reaction events with Bot.onReact and Bot.onUnreact handlers

Conversations Through Quotes

Discussions often involve referencing what others have said. Our new #quote support enables more cohesive conversation threads:

// Quote another message in your bot's post
await session.publish(
  text`Responding to this interesting point...`,
  { quoteTarget: originalMessage }
);

// Handle when users quote your bot's messages
bot.onQuote = async (session, quoteMessage) => {
  await session.publish(
    text`Thanks for sharing my thoughts, ${quoteMessage.actor}!`,
    { visibility: "direct" }
  );
};

With quote support, your bot can:

Quote messages with quoteTarget option
Access quoted messages via Message.quoteTarget
Handle quote events with the new Bot.onQuote event handler

Visual Enhancements

Because communication is visual too, we've improved how your bot presents itself:

Image attachments now properly display in the web interface
Your bot's content looks better and provides a richer experience

Behind the Scenes: Enhanced Activity Propagation

We've also improved how activities propagate through the fediverse:

More precise propagation of replies, shares, updates, and deletes
Activities are now properly sent to the original message authors

These improvements ensure your bot's interactions are consistent and reliable across different fediverse platforms.

Taking Your First Steps with BotKit 0.2.0

Ready to experience these new features? BotKit 0.2.0 is available on JSR and can be installed with a simple command:

deno add jsr:@fedify/botkit@0.2.0

Since BotKit uses the Temporal API (which is still evolving in JavaScript), remember to enable it in your deno.json:

{
  "imports": {
    "@fedify/botkit": "jsr:@fedify/botkit@0.2.0"
  },
  "unstable": ["temporal"]
}

With these simple steps, you're ready to create or upgrade your fediverse bot with our latest features.

Looking Forward

For complete docs and more examples, visit our docs site.

Thank you to everyone who contributed to this release through feedback, feature requests, and code contributions. The BotKit community continues to grow, and we're excited to see what you'll create!

BotKit is powered by Fedify, a lower-level framework for creating ActivityPub server applications.

BotKit by Fedify

@botkit@hollo.social

BotKit 0.2.0 Released

This release marks an important step in our journey to make fediverse bot development more accessible and powerful, introducing several features that our community has been requesting.

The Journey to Better Bot Interactions

Expressing Your Bot's Personality with Custom Emojis

One of the most requested features has been #custom_emoji support. Now your bots can truly express their personality with unique visuals that make their messages stand out.

// Define custom emojis for your bot
const emojis = bot.addCustomEmojis({
  botkit: { 
    file: `${import.meta.dirname}/images/botkit.png`, 
    type: "image/png" 
  },
  fedify: { 
    url: "https://fedify.dev/logo.png", 
    type: "image/png" 
  }
});

// Use these custom emojis in your messages
await session.publish(
  text`BotKit ${customEmoji(emojis.botkit)} is powered by Fedify ${customEmoji(emojis.fedify)}`
);

With this new API, you can:

Add custom emojis to your bot with Bot.addCustomEmojis()
Include these emojis in messages with the customEmoji() function
Use the text tagged template with Fedify Emoji objects

Engaging Through Reactions

Communication isn't just about posting messages—it's also about responding to others. The new reaction system creates natural interaction points between your bot and its followers:

// React to a message with a standard Unicode emoji
await message.react(emoji`👍`);

// Or use one of your custom emojis as a reaction
await message.react(emojis.botkit);

// Create a responsive bot that acknowledges reactions
bot.onReact = async (session, reaction) => {
  await session.publish(
    text`Thanks for reacting with ${reaction.emoji} to my message, ${reaction.actor}!`,
    { visibility: "direct" }
  );
};

This feature allows your bot to:

React to messages with Unicode emojis using Message.react()
React with the custom emojis you've defined
Handle reaction events with Bot.onReact and Bot.onUnreact handlers

Conversations Through Quotes

Discussions often involve referencing what others have said. Our new #quote support enables more cohesive conversation threads:

// Quote another message in your bot's post
await session.publish(
  text`Responding to this interesting point...`,
  { quoteTarget: originalMessage }
);

// Handle when users quote your bot's messages
bot.onQuote = async (session, quoteMessage) => {
  await session.publish(
    text`Thanks for sharing my thoughts, ${quoteMessage.actor}!`,
    { visibility: "direct" }
  );
};

With quote support, your bot can:

Quote messages with quoteTarget option
Access quoted messages via Message.quoteTarget
Handle quote events with the new Bot.onQuote event handler

Visual Enhancements

Because communication is visual too, we've improved how your bot presents itself:

Image attachments now properly display in the web interface
Your bot's content looks better and provides a richer experience

Behind the Scenes: Enhanced Activity Propagation

We've also improved how activities propagate through the fediverse:

More precise propagation of replies, shares, updates, and deletes
Activities are now properly sent to the original message authors

These improvements ensure your bot's interactions are consistent and reliable across different fediverse platforms.

Taking Your First Steps with BotKit 0.2.0

Ready to experience these new features? BotKit 0.2.0 is available on JSR and can be installed with a simple command:

deno add jsr:@fedify/botkit@0.2.0

Since BotKit uses the Temporal API (which is still evolving in JavaScript), remember to enable it in your deno.json:

{
  "imports": {
    "@fedify/botkit": "jsr:@fedify/botkit@0.2.0"
  },
  "unstable": ["temporal"]
}

With these simple steps, you're ready to create or upgrade your fediverse bot with our latest features.

Looking Forward

For complete docs and more examples, visit our docs site.

Thank you to everyone who contributed to this release through feedback, feature requests, and code contributions. The BotKit community continues to grow, and we're excited to see what you'll create!

BotKit is powered by Fedify, a lower-level framework for creating ActivityPub server applications.

@reiver ⊼ (Charles)

@reiver@mastodon.social · Reply to @reiver ⊼ (Charles) :batman:'s post

A HEALTH-CHECK URL would, for example, make sure:

• the web-server is up,
• the database connection is fine,
• maybe query one or more important tables to make sure that still works,
• make sure any 3rd party APIs are working,
• etc.

If any of those things has a problem, then it would return "500 Internal Server Error".

Else (if everything was fine then) it would return "200 OK".

@reiver ⊼ (Charles)

@reiver@mastodon.social

A lot of Fediverse software has a HEALTH-CHECK URL.

But not all Fediverse does.

It would be better if ALL Fediverse software had a HEALTH-CHECK URL.

...

A HEALTH-CHECK URL is a special URL that tell others if the system is running properly.

It would return "200 OK" if everything is fine. And return "500 Internal Server Error" if there is a problem

...

A HEALTH-CHECK URL is important to those who actual run and administrate Fediverse servers

BotKit by Fedify

@botkit@hollo.social

BotKit 0.2.0 Released

This release marks an important step in our journey to make fediverse bot development more accessible and powerful, introducing several features that our community has been requesting.

The Journey to Better Bot Interactions

Expressing Your Bot's Personality with Custom Emojis

One of the most requested features has been #custom_emoji support. Now your bots can truly express their personality with unique visuals that make their messages stand out.

// Define custom emojis for your bot
const emojis = bot.addCustomEmojis({
  botkit: { 
    file: `${import.meta.dirname}/images/botkit.png`, 
    type: "image/png" 
  },
  fedify: { 
    url: "https://fedify.dev/logo.png", 
    type: "image/png" 
  }
});

// Use these custom emojis in your messages
await session.publish(
  text`BotKit ${customEmoji(emojis.botkit)} is powered by Fedify ${customEmoji(emojis.fedify)}`
);

With this new API, you can:

Add custom emojis to your bot with Bot.addCustomEmojis()
Include these emojis in messages with the customEmoji() function
Use the text tagged template with Fedify Emoji objects

Engaging Through Reactions

Communication isn't just about posting messages—it's also about responding to others. The new reaction system creates natural interaction points between your bot and its followers:

// React to a message with a standard Unicode emoji
await message.react(emoji`👍`);

// Or use one of your custom emojis as a reaction
await message.react(emojis.botkit);

// Create a responsive bot that acknowledges reactions
bot.onReact = async (session, reaction) => {
  await session.publish(
    text`Thanks for reacting with ${reaction.emoji} to my message, ${reaction.actor}!`,
    { visibility: "direct" }
  );
};

This feature allows your bot to:

React to messages with Unicode emojis using Message.react()
React with the custom emojis you've defined
Handle reaction events with Bot.onReact and Bot.onUnreact handlers

Conversations Through Quotes

Discussions often involve referencing what others have said. Our new #quote support enables more cohesive conversation threads:

// Quote another message in your bot's post
await session.publish(
  text`Responding to this interesting point...`,
  { quoteTarget: originalMessage }
);

// Handle when users quote your bot's messages
bot.onQuote = async (session, quoteMessage) => {
  await session.publish(
    text`Thanks for sharing my thoughts, ${quoteMessage.actor}!`,
    { visibility: "direct" }
  );
};

With quote support, your bot can:

Quote messages with quoteTarget option
Access quoted messages via Message.quoteTarget
Handle quote events with the new Bot.onQuote event handler

Visual Enhancements

Because communication is visual too, we've improved how your bot presents itself:

Image attachments now properly display in the web interface
Your bot's content looks better and provides a richer experience

Behind the Scenes: Enhanced Activity Propagation

We've also improved how activities propagate through the fediverse:

More precise propagation of replies, shares, updates, and deletes
Activities are now properly sent to the original message authors

These improvements ensure your bot's interactions are consistent and reliable across different fediverse platforms.

Taking Your First Steps with BotKit 0.2.0

Ready to experience these new features? BotKit 0.2.0 is available on JSR and can be installed with a simple command:

deno add jsr:@fedify/botkit@0.2.0

Since BotKit uses the Temporal API (which is still evolving in JavaScript), remember to enable it in your deno.json:

{
  "imports": {
    "@fedify/botkit": "jsr:@fedify/botkit@0.2.0"
  },
  "unstable": ["temporal"]
}

With these simple steps, you're ready to create or upgrade your fediverse bot with our latest features.

Looking Forward

For complete docs and more examples, visit our docs site.

Thank you to everyone who contributed to this release through feedback, feature requests, and code contributions. The BotKit community continues to grow, and we're excited to see what you'll create!

BotKit is powered by Fedify, a lower-level framework for creating ActivityPub server applications.

BotKit by Fedify

@botkit@hollo.social

BotKit 0.2.0 Released

This release marks an important step in our journey to make fediverse bot development more accessible and powerful, introducing several features that our community has been requesting.

The Journey to Better Bot Interactions

Expressing Your Bot's Personality with Custom Emojis

One of the most requested features has been #custom_emoji support. Now your bots can truly express their personality with unique visuals that make their messages stand out.

// Define custom emojis for your bot
const emojis = bot.addCustomEmojis({
  botkit: { 
    file: `${import.meta.dirname}/images/botkit.png`, 
    type: "image/png" 
  },
  fedify: { 
    url: "https://fedify.dev/logo.png", 
    type: "image/png" 
  }
});

// Use these custom emojis in your messages
await session.publish(
  text`BotKit ${customEmoji(emojis.botkit)} is powered by Fedify ${customEmoji(emojis.fedify)}`
);

With this new API, you can:

Add custom emojis to your bot with Bot.addCustomEmojis()
Include these emojis in messages with the customEmoji() function
Use the text tagged template with Fedify Emoji objects

Engaging Through Reactions

Communication isn't just about posting messages—it's also about responding to others. The new reaction system creates natural interaction points between your bot and its followers:

// React to a message with a standard Unicode emoji
await message.react(emoji`👍`);

// Or use one of your custom emojis as a reaction
await message.react(emojis.botkit);

// Create a responsive bot that acknowledges reactions
bot.onReact = async (session, reaction) => {
  await session.publish(
    text`Thanks for reacting with ${reaction.emoji} to my message, ${reaction.actor}!`,
    { visibility: "direct" }
  );
};

This feature allows your bot to:

React to messages with Unicode emojis using Message.react()
React with the custom emojis you've defined
Handle reaction events with Bot.onReact and Bot.onUnreact handlers

Conversations Through Quotes

Discussions often involve referencing what others have said. Our new #quote support enables more cohesive conversation threads:

// Quote another message in your bot's post
await session.publish(
  text`Responding to this interesting point...`,
  { quoteTarget: originalMessage }
);

// Handle when users quote your bot's messages
bot.onQuote = async (session, quoteMessage) => {
  await session.publish(
    text`Thanks for sharing my thoughts, ${quoteMessage.actor}!`,
    { visibility: "direct" }
  );
};

With quote support, your bot can:

Quote messages with quoteTarget option
Access quoted messages via Message.quoteTarget
Handle quote events with the new Bot.onQuote event handler

Visual Enhancements

Because communication is visual too, we've improved how your bot presents itself:

Image attachments now properly display in the web interface
Your bot's content looks better and provides a richer experience

Behind the Scenes: Enhanced Activity Propagation

We've also improved how activities propagate through the fediverse:

More precise propagation of replies, shares, updates, and deletes
Activities are now properly sent to the original message authors

These improvements ensure your bot's interactions are consistent and reliable across different fediverse platforms.

Taking Your First Steps with BotKit 0.2.0

Ready to experience these new features? BotKit 0.2.0 is available on JSR and can be installed with a simple command:

deno add jsr:@fedify/botkit@0.2.0

Since BotKit uses the Temporal API (which is still evolving in JavaScript), remember to enable it in your deno.json:

{
  "imports": {
    "@fedify/botkit": "jsr:@fedify/botkit@0.2.0"
  },
  "unstable": ["temporal"]
}

With these simple steps, you're ready to create or upgrade your fediverse bot with our latest features.

Looking Forward

For complete docs and more examples, visit our docs site.

Thank you to everyone who contributed to this release through feedback, feature requests, and code contributions. The BotKit community continues to grow, and we're excited to see what you'll create!

BotKit is powered by Fedify, a lower-level framework for creating ActivityPub server applications.

BotKit by Fedify

@botkit@hollo.social

BotKit 0.2.0 Released

This release marks an important step in our journey to make fediverse bot development more accessible and powerful, introducing several features that our community has been requesting.

The Journey to Better Bot Interactions

Expressing Your Bot's Personality with Custom Emojis

One of the most requested features has been #custom_emoji support. Now your bots can truly express their personality with unique visuals that make their messages stand out.

// Define custom emojis for your bot
const emojis = bot.addCustomEmojis({
  botkit: { 
    file: `${import.meta.dirname}/images/botkit.png`, 
    type: "image/png" 
  },
  fedify: { 
    url: "https://fedify.dev/logo.png", 
    type: "image/png" 
  }
});

// Use these custom emojis in your messages
await session.publish(
  text`BotKit ${customEmoji(emojis.botkit)} is powered by Fedify ${customEmoji(emojis.fedify)}`
);

With this new API, you can:

Add custom emojis to your bot with Bot.addCustomEmojis()
Include these emojis in messages with the customEmoji() function
Use the text tagged template with Fedify Emoji objects

Engaging Through Reactions

Communication isn't just about posting messages—it's also about responding to others. The new reaction system creates natural interaction points between your bot and its followers:

// React to a message with a standard Unicode emoji
await message.react(emoji`👍`);

// Or use one of your custom emojis as a reaction
await message.react(emojis.botkit);

// Create a responsive bot that acknowledges reactions
bot.onReact = async (session, reaction) => {
  await session.publish(
    text`Thanks for reacting with ${reaction.emoji} to my message, ${reaction.actor}!`,
    { visibility: "direct" }
  );
};

This feature allows your bot to:

React to messages with Unicode emojis using Message.react()
React with the custom emojis you've defined
Handle reaction events with Bot.onReact and Bot.onUnreact handlers

Conversations Through Quotes

Discussions often involve referencing what others have said. Our new #quote support enables more cohesive conversation threads:

// Quote another message in your bot's post
await session.publish(
  text`Responding to this interesting point...`,
  { quoteTarget: originalMessage }
);

// Handle when users quote your bot's messages
bot.onQuote = async (session, quoteMessage) => {
  await session.publish(
    text`Thanks for sharing my thoughts, ${quoteMessage.actor}!`,
    { visibility: "direct" }
  );
};

With quote support, your bot can:

Quote messages with quoteTarget option
Access quoted messages via Message.quoteTarget
Handle quote events with the new Bot.onQuote event handler

Visual Enhancements

Because communication is visual too, we've improved how your bot presents itself:

Image attachments now properly display in the web interface
Your bot's content looks better and provides a richer experience

Behind the Scenes: Enhanced Activity Propagation

We've also improved how activities propagate through the fediverse:

More precise propagation of replies, shares, updates, and deletes
Activities are now properly sent to the original message authors

These improvements ensure your bot's interactions are consistent and reliable across different fediverse platforms.

Taking Your First Steps with BotKit 0.2.0

Ready to experience these new features? BotKit 0.2.0 is available on JSR and can be installed with a simple command:

deno add jsr:@fedify/botkit@0.2.0

Since BotKit uses the Temporal API (which is still evolving in JavaScript), remember to enable it in your deno.json:

{
  "imports": {
    "@fedify/botkit": "jsr:@fedify/botkit@0.2.0"
  },
  "unstable": ["temporal"]
}

With these simple steps, you're ready to create or upgrade your fediverse bot with our latest features.

Looking Forward

For complete docs and more examples, visit our docs site.

Thank you to everyone who contributed to this release through feedback, feature requests, and code contributions. The BotKit community continues to grow, and we're excited to see what you'll create!

BotKit is powered by Fedify, a lower-level framework for creating ActivityPub server applications.

BotKit by Fedify

@botkit@hollo.social · Reply to BotKit by Fedify :botkit:'s post

BotKit 0.2.0のリリース

より良いボットインタラクションへの旅

カスタム絵文字でボットの個性を表現

// ボット用のカスタム絵文字を定義
const emojis = bot.addCustomEmojis({
  botkit: { 
    file: `${import.meta.dirname}/images/botkit.png`, 
    type: "image/png" 
  },
  fedify: { 
    url: "https://fedify.dev/logo.png", 
    type: "image/png" 
  }
});

// メッセージにカスタム絵文字を使用
await session.publish(
  text`BotKit ${customEmoji(emojis.botkit)}は、Fedify ${customEmoji(emojis.fedify)}によって支えられています`
);

この新しいAPIでは、次のことが可能になりました。

Bot.addCustomEmojis()でボットにカスタム絵文字を追加
customEmoji()関数でメッセージに絵文字を含める
FedifyのEmojiオブジェクトをtextタグテンプレートで使用する

リアクションによるコミュニケーション

// 標準のUnicode絵文字でメッセージにリアクション
await message.react(emoji`👍`);

// または定義したカスタム絵文字でリアクション
await message.react(emojis.botkit);

// リアクションを認識して応答するボットを作成
bot.onReact = async (session, reaction) => {
  await session.publish(
    text`${reaction.actor}さん、私のメッセージに${reaction.emoji}でリアクションしてくれてありがとうございます！`,
    { visibility: "direct" }
  );
};

この機能により、ボットは次のことができるようになりました。

Message.react()を使用してUnicode絵文字でメッセージにリアクション
定義したカスタム絵文字でリアクション
Bot.onReactとBot.onUnreactハンドラーでリアクションイベントを処理

引用による会話

議論では、他の人が言ったことを参照する必要がしばしばあります。新しい引用機能により、より結束力のある会話スレッドを作成できます。

// ボットの投稿で他のメッセージを引用
await session.publish(
  text`この興味深い視点について答えます...`,
  { quoteTarget: originalMessage }
);

// ユーザーがボットのメッセージを引用した場合の処理
bot.onQuote = async (session, quoteMessage) => {
  await session.publish(
    text`${quoteMessage.actor}さん、私の考えを共有してくれてありがとうございます！`,
    { visibility: "direct" }
  );
};

引用機能により、ボットは次のことができるようになりました。

quoteTargetオプションでメッセージを引用
Message.quoteTargetを通じて引用されたメッセージにアクセス
新しいBot.onQuoteイベントハンドラーで引用イベントを処理

視覚的な改善

コミュニケーションには視覚的要素も重要なため、ボットの表現方法を改善しました。

ウェブインターフェースで画像添付ファイルが正しく表示されるようになりました
ボットのコンテンツがより見やすくなり、豊かな体験を提供します

内部改善：活動の伝播の強化

フェディバースでの活動が伝播する方法も改善されました。

返信、共有、更新、削除のより正確な伝播
元のメッセージ作成者に活動が適切に送信されます

これらの改善により、様々なフェディバースプラットフォームでのボットの相互作用が一貫性と信頼性を持つようになります。

BotKit 0.2.0で最初の一歩を踏み出す

これらの新機能を体験してみたいですか？BotKit 0.2.0はJSRで利用可能で、簡単なコマンドでインストールできます。

deno add jsr:@fedify/botkit@0.2.0

BotKitはTemporal API（JavaScriptではまだ試験的な機能）を使用するため、deno.jsonでこれを有効にする必要があります。

{
  "imports": {
    "@fedify/botkit": "jsr:@fedify/botkit@0.2.0"
  },
  "unstable": ["temporal"]
}

これらの簡単なステップで、最新機能を使ってフェディバースボットを作成またはアップグレードする準備が整いました。

今後の展望

完全なドキュメントと詳細な例については、私たちのドキュメントサイトをご覧ください。

BotKitは、ActivityPubサーバーアプリケーションを作成するための低レベルフレームワークFedifyによって支えられています。

BotKit by Fedify

@botkit@hollo.social · Reply to BotKit by Fedify :botkit:'s post

BotKit 0.2.0のリリース

より良いボットインタラクションへの旅

カスタム絵文字でボットの個性を表現

// ボット用のカスタム絵文字を定義
const emojis = bot.addCustomEmojis({
  botkit: { 
    file: `${import.meta.dirname}/images/botkit.png`, 
    type: "image/png" 
  },
  fedify: { 
    url: "https://fedify.dev/logo.png", 
    type: "image/png" 
  }
});

// メッセージにカスタム絵文字を使用
await session.publish(
  text`BotKit ${customEmoji(emojis.botkit)}は、Fedify ${customEmoji(emojis.fedify)}によって支えられています`
);

この新しいAPIでは、次のことが可能になりました。

Bot.addCustomEmojis()でボットにカスタム絵文字を追加
customEmoji()関数でメッセージに絵文字を含める
FedifyのEmojiオブジェクトをtextタグテンプレートで使用する

リアクションによるコミュニケーション

// 標準のUnicode絵文字でメッセージにリアクション
await message.react(emoji`👍`);

// または定義したカスタム絵文字でリアクション
await message.react(emojis.botkit);

// リアクションを認識して応答するボットを作成
bot.onReact = async (session, reaction) => {
  await session.publish(
    text`${reaction.actor}さん、私のメッセージに${reaction.emoji}でリアクションしてくれてありがとうございます！`,
    { visibility: "direct" }
  );
};

この機能により、ボットは次のことができるようになりました。

Message.react()を使用してUnicode絵文字でメッセージにリアクション
定義したカスタム絵文字でリアクション
Bot.onReactとBot.onUnreactハンドラーでリアクションイベントを処理

引用による会話

議論では、他の人が言ったことを参照する必要がしばしばあります。新しい引用機能により、より結束力のある会話スレッドを作成できます。

// ボットの投稿で他のメッセージを引用
await session.publish(
  text`この興味深い視点について答えます...`,
  { quoteTarget: originalMessage }
);

// ユーザーがボットのメッセージを引用した場合の処理
bot.onQuote = async (session, quoteMessage) => {
  await session.publish(
    text`${quoteMessage.actor}さん、私の考えを共有してくれてありがとうございます！`,
    { visibility: "direct" }
  );
};

引用機能により、ボットは次のことができるようになりました。

quoteTargetオプションでメッセージを引用
Message.quoteTargetを通じて引用されたメッセージにアクセス
新しいBot.onQuoteイベントハンドラーで引用イベントを処理

視覚的な改善

コミュニケーションには視覚的要素も重要なため、ボットの表現方法を改善しました。

ウェブインターフェースで画像添付ファイルが正しく表示されるようになりました
ボットのコンテンツがより見やすくなり、豊かな体験を提供します

内部改善：活動の伝播の強化

フェディバースでの活動が伝播する方法も改善されました。

返信、共有、更新、削除のより正確な伝播
元のメッセージ作成者に活動が適切に送信されます

これらの改善により、様々なフェディバースプラットフォームでのボットの相互作用が一貫性と信頼性を持つようになります。

BotKit 0.2.0で最初の一歩を踏み出す

これらの新機能を体験してみたいですか？BotKit 0.2.0はJSRで利用可能で、簡単なコマンドでインストールできます。

deno add jsr:@fedify/botkit@0.2.0

BotKitはTemporal API（JavaScriptではまだ試験的な機能）を使用するため、deno.jsonでこれを有効にする必要があります。

{
  "imports": {
    "@fedify/botkit": "jsr:@fedify/botkit@0.2.0"
  },
  "unstable": ["temporal"]
}

これらの簡単なステップで、最新機能を使ってフェディバースボットを作成またはアップグレードする準備が整いました。

今後の展望

完全なドキュメントと詳細な例については、私たちのドキュメントサイトをご覧ください。

BotKitは、ActivityPubサーバーアプリケーションを作成するための低レベルフレームワークFedifyによって支えられています。

BotKit by Fedify

@botkit@hollo.social · Reply to BotKit by Fedify :botkit:'s post

BotKit 0.2.0のリリース

より良いボットインタラクションへの旅

カスタム絵文字でボットの個性を表現

// ボット用のカスタム絵文字を定義
const emojis = bot.addCustomEmojis({
  botkit: { 
    file: `${import.meta.dirname}/images/botkit.png`, 
    type: "image/png" 
  },
  fedify: { 
    url: "https://fedify.dev/logo.png", 
    type: "image/png" 
  }
});

// メッセージにカスタム絵文字を使用
await session.publish(
  text`BotKit ${customEmoji(emojis.botkit)}は、Fedify ${customEmoji(emojis.fedify)}によって支えられています`
);

この新しいAPIでは、次のことが可能になりました。

Bot.addCustomEmojis()でボットにカスタム絵文字を追加
customEmoji()関数でメッセージに絵文字を含める
FedifyのEmojiオブジェクトをtextタグテンプレートで使用する

リアクションによるコミュニケーション

// 標準のUnicode絵文字でメッセージにリアクション
await message.react(emoji`👍`);

// または定義したカスタム絵文字でリアクション
await message.react(emojis.botkit);

// リアクションを認識して応答するボットを作成
bot.onReact = async (session, reaction) => {
  await session.publish(
    text`${reaction.actor}さん、私のメッセージに${reaction.emoji}でリアクションしてくれてありがとうございます！`,
    { visibility: "direct" }
  );
};

この機能により、ボットは次のことができるようになりました。

Message.react()を使用してUnicode絵文字でメッセージにリアクション
定義したカスタム絵文字でリアクション
Bot.onReactとBot.onUnreactハンドラーでリアクションイベントを処理

引用による会話

議論では、他の人が言ったことを参照する必要がしばしばあります。新しい引用機能により、より結束力のある会話スレッドを作成できます。

// ボットの投稿で他のメッセージを引用
await session.publish(
  text`この興味深い視点について答えます...`,
  { quoteTarget: originalMessage }
);

// ユーザーがボットのメッセージを引用した場合の処理
bot.onQuote = async (session, quoteMessage) => {
  await session.publish(
    text`${quoteMessage.actor}さん、私の考えを共有してくれてありがとうございます！`,
    { visibility: "direct" }
  );
};

引用機能により、ボットは次のことができるようになりました。

quoteTargetオプションでメッセージを引用
Message.quoteTargetを通じて引用されたメッセージにアクセス
新しいBot.onQuoteイベントハンドラーで引用イベントを処理

視覚的な改善

コミュニケーションには視覚的要素も重要なため、ボットの表現方法を改善しました。

ウェブインターフェースで画像添付ファイルが正しく表示されるようになりました
ボットのコンテンツがより見やすくなり、豊かな体験を提供します

内部改善：活動の伝播の強化

フェディバースでの活動が伝播する方法も改善されました。

返信、共有、更新、削除のより正確な伝播
元のメッセージ作成者に活動が適切に送信されます

これらの改善により、様々なフェディバースプラットフォームでのボットの相互作用が一貫性と信頼性を持つようになります。

BotKit 0.2.0で最初の一歩を踏み出す

これらの新機能を体験してみたいですか？BotKit 0.2.0はJSRで利用可能で、簡単なコマンドでインストールできます。

deno add jsr:@fedify/botkit@0.2.0

BotKitはTemporal API（JavaScriptではまだ試験的な機能）を使用するため、deno.jsonでこれを有効にする必要があります。

{
  "imports": {
    "@fedify/botkit": "jsr:@fedify/botkit@0.2.0"
  },
  "unstable": ["temporal"]
}

これらの簡単なステップで、最新機能を使ってフェディバースボットを作成またはアップグレードする準備が整いました。

今後の展望

完全なドキュメントと詳細な例については、私たちのドキュメントサイトをご覧ください。

BotKitは、ActivityPubサーバーアプリケーションを作成するための低レベルフレームワークFedifyによって支えられています。

#fedidev #커모지 #커스텀_이모지 #에모지_반응 #이모지_반응 #에모지_리액션 #이모지_리액션

BotKit by Fedify

@botkit@hollo.social · Reply to BotKit by Fedify :botkit:'s post

BotKit 0.2.0 릴리스

더 나은 봇 상호작용을 위한 여정

커스텀 에모지로 봇의 개성 표현하기

// 봇의 커스텀 에모지 정의하기
const emojis = bot.addCustomEmojis({
  botkit: { 
    file: `${import.meta.dirname}/images/botkit.png`, 
    type: "image/png" 
  },
  fedify: { 
    url: "https://fedify.dev/logo.png", 
    type: "image/png" 
  }
});

// 메시지에 커스텀 에모지 사용하기
await session.publish(
  text`BotKit ${customEmoji(emojis.botkit)}은 Fedify ${customEmoji(emojis.fedify)}의 지원을 받습니다`
);

이 새로운 API를 통해 다음과 같은 기능을 사용할 수 있습니다.

Bot.addCustomEmojis()로 봇에 커스텀 에모지 추가하기
customEmoji() 함수로 메시지에 에모지 포함하기
Fedify의 Emoji 객체를 text 태그 템플릿에서 사용하기

반응을 통한 소통

// 표준 유니코드 에모지로 메시지에 반응하기
await message.react(emoji`👍`);

// 또는 정의한 커스텀 에모지로 반응하기
await message.react(emojis.botkit);

// 반응을 인식하고 응답하는 봇 만들기
bot.onReact = async (session, reaction) => {
  await session.publish(
    text`${reaction.actor}님, 제 메시지에 ${reaction.emoji} 반응을 남겨주셔서 감사합니다!`,
    { visibility: "direct" }
  );
};

이 기능을 통해 봇은 다음과 같은 작업을 수행할 수 있습니다.

Message.react()를 사용하여 유니코드 에모지로 메시지에 반응하기
정의한 커스텀 에모지로 반응하기
Bot.onReact와 Bot.onUnreact 핸들러로 반응 이벤트 처리하기

인용을 통한 대화

토론에서는 종종 다른 사람이 말한 내용을 참조해야 할 때가 있습니다. 새로운 #인용 기능은 더 응집력 있는 대화 스레드를 만들어 줍니다.

// 봇의 게시물에서 다른 메시지 인용하기
await session.publish(
  text`이 흥미로운 관점에 대한 답변입니다...`,
  { quoteTarget: originalMessage }
);

// 사용자가 봇의 메시지를 인용할 때 처리하기
bot.onQuote = async (session, quoteMessage) => {
  await session.publish(
    text`${quoteMessage.actor}님, 제 생각을 공유해 주셔서 감사합니다!`,
    { visibility: "direct" }
  );
};

인용 기능을 통해 봇은 다음과 같은 작업을 수행할 수 있습니다.

quoteTarget 옵션으로 메시지 인용하기
Message.quoteTarget을 통해 인용된 메시지에 접근하기
새로운 Bot.onQuote 이벤트 핸들러로 인용 이벤트 처리하기

시각적 개선

소통은 시각적인 요소도 중요하기 때문에 봇의 표현 방식을 개선했습니다.

웹 인터페이스에서 이미지 첨부파일이 제대로 표시됩니다
봇의 콘텐츠가 더 보기 좋아지고 풍부한 경험을 제공합니다

내부 개선: 향상된 액티비티 전파

연합우주에서 액티비티가 전파되는 방식도 개선했습니다.

답글, 공유, 업데이트, 삭제의 더 정확한 전파
원본 메시지 작성자에게 액티비티가 제대로 전송됩니다

이러한 개선 사항은 다양한 연합우주 플랫폼에서 봇의 상호작용이 일관되고 안정적으로 이루어지도록 보장합니다.

BotKit 0.2.0으로 첫 걸음 떼기

이러한 새로운 기능을 경험해 보고 싶으신가요? BotKit 0.2.0은 JSR에서 받을 수 있으며 간단한 명령어로 설치할 수 있습니다.

deno add jsr:@fedify/botkit@0.2.0

BotKit은 Temporal API(JavaScript에서 아직 시범적인 기능)를 사용하므로 deno.json에서 이를 활성화해야 합니다.

{
  "imports": {
    "@fedify/botkit": "jsr:@fedify/botkit@0.2.0"
  },
  "unstable": ["temporal"]
}

이 간단한 단계를 통해 최신 기능으로 연합우주 봇을 만들거나 업그레이드할 준비가 완료되었습니다.

앞으로의 전망

전체 문서와 더 많은 예제는 저희 문서 사이트에서 확인하실 수 있습니다.

BotKit은 ActivityPub 서버 애플리케이션을 만들기 위한 하위 레벨 프레임워크인 Fedify의 지원을 받습니다.

BotKit by Fedify

@botkit@hollo.social

BotKit 0.2.0 Released

This release marks an important step in our journey to make fediverse bot development more accessible and powerful, introducing several features that our community has been requesting.

The Journey to Better Bot Interactions

Expressing Your Bot's Personality with Custom Emojis

One of the most requested features has been #custom_emoji support. Now your bots can truly express their personality with unique visuals that make their messages stand out.

// Define custom emojis for your bot
const emojis = bot.addCustomEmojis({
  botkit: { 
    file: `${import.meta.dirname}/images/botkit.png`, 
    type: "image/png" 
  },
  fedify: { 
    url: "https://fedify.dev/logo.png", 
    type: "image/png" 
  }
});

// Use these custom emojis in your messages
await session.publish(
  text`BotKit ${customEmoji(emojis.botkit)} is powered by Fedify ${customEmoji(emojis.fedify)}`
);

With this new API, you can:

Add custom emojis to your bot with Bot.addCustomEmojis()
Include these emojis in messages with the customEmoji() function
Use the text tagged template with Fedify Emoji objects

Engaging Through Reactions

Communication isn't just about posting messages—it's also about responding to others. The new reaction system creates natural interaction points between your bot and its followers:

// React to a message with a standard Unicode emoji
await message.react(emoji`👍`);

// Or use one of your custom emojis as a reaction
await message.react(emojis.botkit);

// Create a responsive bot that acknowledges reactions
bot.onReact = async (session, reaction) => {
  await session.publish(
    text`Thanks for reacting with ${reaction.emoji} to my message, ${reaction.actor}!`,
    { visibility: "direct" }
  );
};

This feature allows your bot to:

React to messages with Unicode emojis using Message.react()
React with the custom emojis you've defined
Handle reaction events with Bot.onReact and Bot.onUnreact handlers

Conversations Through Quotes

Discussions often involve referencing what others have said. Our new #quote support enables more cohesive conversation threads:

// Quote another message in your bot's post
await session.publish(
  text`Responding to this interesting point...`,
  { quoteTarget: originalMessage }
);

// Handle when users quote your bot's messages
bot.onQuote = async (session, quoteMessage) => {
  await session.publish(
    text`Thanks for sharing my thoughts, ${quoteMessage.actor}!`,
    { visibility: "direct" }
  );
};

With quote support, your bot can:

Quote messages with quoteTarget option
Access quoted messages via Message.quoteTarget
Handle quote events with the new Bot.onQuote event handler

Visual Enhancements

Because communication is visual too, we've improved how your bot presents itself:

Image attachments now properly display in the web interface
Your bot's content looks better and provides a richer experience

Behind the Scenes: Enhanced Activity Propagation

We've also improved how activities propagate through the fediverse:

More precise propagation of replies, shares, updates, and deletes
Activities are now properly sent to the original message authors

These improvements ensure your bot's interactions are consistent and reliable across different fediverse platforms.

Taking Your First Steps with BotKit 0.2.0

Ready to experience these new features? BotKit 0.2.0 is available on JSR and can be installed with a simple command:

deno add jsr:@fedify/botkit@0.2.0

Since BotKit uses the Temporal API (which is still evolving in JavaScript), remember to enable it in your deno.json:

{
  "imports": {
    "@fedify/botkit": "jsr:@fedify/botkit@0.2.0"
  },
  "unstable": ["temporal"]
}

With these simple steps, you're ready to create or upgrade your fediverse bot with our latest features.

Looking Forward

For complete docs and more examples, visit our docs site.

Thank you to everyone who contributed to this release through feedback, feature requests, and code contributions. The BotKit community continues to grow, and we're excited to see what you'll create!

BotKit is powered by Fedify, a lower-level framework for creating ActivityPub server applications.

BotKit by Fedify

@botkit@hollo.social

BotKit 0.2.0 Released

This release marks an important step in our journey to make fediverse bot development more accessible and powerful, introducing several features that our community has been requesting.

The Journey to Better Bot Interactions

Expressing Your Bot's Personality with Custom Emojis

One of the most requested features has been #custom_emoji support. Now your bots can truly express their personality with unique visuals that make their messages stand out.

// Define custom emojis for your bot
const emojis = bot.addCustomEmojis({
  botkit: { 
    file: `${import.meta.dirname}/images/botkit.png`, 
    type: "image/png" 
  },
  fedify: { 
    url: "https://fedify.dev/logo.png", 
    type: "image/png" 
  }
});

// Use these custom emojis in your messages
await session.publish(
  text`BotKit ${customEmoji(emojis.botkit)} is powered by Fedify ${customEmoji(emojis.fedify)}`
);

With this new API, you can:

Add custom emojis to your bot with Bot.addCustomEmojis()
Include these emojis in messages with the customEmoji() function
Use the text tagged template with Fedify Emoji objects

Engaging Through Reactions

Communication isn't just about posting messages—it's also about responding to others. The new reaction system creates natural interaction points between your bot and its followers:

// React to a message with a standard Unicode emoji
await message.react(emoji`👍`);

// Or use one of your custom emojis as a reaction
await message.react(emojis.botkit);

// Create a responsive bot that acknowledges reactions
bot.onReact = async (session, reaction) => {
  await session.publish(
    text`Thanks for reacting with ${reaction.emoji} to my message, ${reaction.actor}!`,
    { visibility: "direct" }
  );
};

This feature allows your bot to:

React to messages with Unicode emojis using Message.react()
React with the custom emojis you've defined
Handle reaction events with Bot.onReact and Bot.onUnreact handlers

Conversations Through Quotes

Discussions often involve referencing what others have said. Our new #quote support enables more cohesive conversation threads:

// Quote another message in your bot's post
await session.publish(
  text`Responding to this interesting point...`,
  { quoteTarget: originalMessage }
);

// Handle when users quote your bot's messages
bot.onQuote = async (session, quoteMessage) => {
  await session.publish(
    text`Thanks for sharing my thoughts, ${quoteMessage.actor}!`,
    { visibility: "direct" }
  );
};

With quote support, your bot can:

Quote messages with quoteTarget option
Access quoted messages via Message.quoteTarget
Handle quote events with the new Bot.onQuote event handler

Visual Enhancements

Because communication is visual too, we've improved how your bot presents itself:

Image attachments now properly display in the web interface
Your bot's content looks better and provides a richer experience

Behind the Scenes: Enhanced Activity Propagation

We've also improved how activities propagate through the fediverse:

More precise propagation of replies, shares, updates, and deletes
Activities are now properly sent to the original message authors

These improvements ensure your bot's interactions are consistent and reliable across different fediverse platforms.

Taking Your First Steps with BotKit 0.2.0

Ready to experience these new features? BotKit 0.2.0 is available on JSR and can be installed with a simple command:

deno add jsr:@fedify/botkit@0.2.0

Since BotKit uses the Temporal API (which is still evolving in JavaScript), remember to enable it in your deno.json:

{
  "imports": {
    "@fedify/botkit": "jsr:@fedify/botkit@0.2.0"
  },
  "unstable": ["temporal"]
}

With these simple steps, you're ready to create or upgrade your fediverse bot with our latest features.

Looking Forward

For complete docs and more examples, visit our docs site.

Thank you to everyone who contributed to this release through feedback, feature requests, and code contributions. The BotKit community continues to grow, and we're excited to see what you'll create!

BotKit is powered by Fedify, a lower-level framework for creating ActivityPub server applications.

BotKit by Fedify

@botkit@hollo.social

Coming soon in #BotKit 0.2.0: Native #quote post support!

We're excited to share a preview of the upcoming quoting features in BotKit 0.2.0. This update will make it easier for your bots to engage with quoted content across the fediverse.

The quoting feature set includes:

Detecting when someone quotes your bot's posts with the new Bot.onQuote event handler
Accessing quoted content through the Message.quoteTarget property
Creating quote posts using the quoteTarget option in Session.publish() and Message.reply() methods

Here's a quick example of how you can use the quote detection:

bot.onQuote = async (session, quote) => {
  // The quote parameter is a Message object representing the post that quoted your bot
  await quote.reply(text`Thanks for quoting my post, ${quote.actor}!`);
  
  // You can access the original quoted message
  const originalPost = quote.quoteTarget;
  console.log(`Original message: ${originalPost?.text}`);
};

And creating quote posts is just as simple:

// Quote in a new post
await session.publish(
  text`I'm quoting this interesting message!`,
  { quoteTarget: someMessage }
);

// Or quote in a reply
await message.reply(
  text`Interesting point! I'm quoting another relevant post here.`,
  { quoteTarget: anotherMessage }
);

Remember that quoting behavior may vary across different #ActivityPub implementations—some platforms like Misskey display quotes prominently, while others like Mastodon might implement them differently.

Want to try these features right now? You can install the development version from JSR:

deno add jsr:@fedify/botkit@0.2.0-dev.90+d6ab4bdc

We're looking forward to seeing how you use these quoting capabilities in your bots!

Fedify: an ActivityPub server framework

@fedify@hollo.social

In case you weren't aware, #Fedify has both #Discord and #Matrix communities where you can get help, discuss features, or just chat about #ActivityPub and federated social networks.

Matrix space: #fedify:matrix.org
Discord server: https://discord.gg/bhtwpzURwd

Feel free to join either community based on your preference. Both channels have active discussions about Fedify and federation topics.

BotKit by Fedify

@botkit@hollo.social · Reply to BotKit by Fedify :botkit:'s post

BotKit 0.2.0のリリース

より良いボットインタラクションへの旅

カスタム絵文字でボットの個性を表現

// ボット用のカスタム絵文字を定義
const emojis = bot.addCustomEmojis({
  botkit: { 
    file: `${import.meta.dirname}/images/botkit.png`, 
    type: "image/png" 
  },
  fedify: { 
    url: "https://fedify.dev/logo.png", 
    type: "image/png" 
  }
});

// メッセージにカスタム絵文字を使用
await session.publish(
  text`BotKit ${customEmoji(emojis.botkit)}は、Fedify ${customEmoji(emojis.fedify)}によって支えられています`
);

この新しいAPIでは、次のことが可能になりました。

Bot.addCustomEmojis()でボットにカスタム絵文字を追加
customEmoji()関数でメッセージに絵文字を含める
FedifyのEmojiオブジェクトをtextタグテンプレートで使用する

リアクションによるコミュニケーション

// 標準のUnicode絵文字でメッセージにリアクション
await message.react(emoji`👍`);

// または定義したカスタム絵文字でリアクション
await message.react(emojis.botkit);

// リアクションを認識して応答するボットを作成
bot.onReact = async (session, reaction) => {
  await session.publish(
    text`${reaction.actor}さん、私のメッセージに${reaction.emoji}でリアクションしてくれてありがとうございます！`,
    { visibility: "direct" }
  );
};

この機能により、ボットは次のことができるようになりました。

Message.react()を使用してUnicode絵文字でメッセージにリアクション
定義したカスタム絵文字でリアクション
Bot.onReactとBot.onUnreactハンドラーでリアクションイベントを処理

引用による会話

議論では、他の人が言ったことを参照する必要がしばしばあります。新しい引用機能により、より結束力のある会話スレッドを作成できます。

// ボットの投稿で他のメッセージを引用
await session.publish(
  text`この興味深い視点について答えます...`,
  { quoteTarget: originalMessage }
);

// ユーザーがボットのメッセージを引用した場合の処理
bot.onQuote = async (session, quoteMessage) => {
  await session.publish(
    text`${quoteMessage.actor}さん、私の考えを共有してくれてありがとうございます！`,
    { visibility: "direct" }
  );
};

引用機能により、ボットは次のことができるようになりました。

quoteTargetオプションでメッセージを引用
Message.quoteTargetを通じて引用されたメッセージにアクセス
新しいBot.onQuoteイベントハンドラーで引用イベントを処理

視覚的な改善

コミュニケーションには視覚的要素も重要なため、ボットの表現方法を改善しました。

ウェブインターフェースで画像添付ファイルが正しく表示されるようになりました
ボットのコンテンツがより見やすくなり、豊かな体験を提供します

内部改善：活動の伝播の強化

フェディバースでの活動が伝播する方法も改善されました。

返信、共有、更新、削除のより正確な伝播
元のメッセージ作成者に活動が適切に送信されます

これらの改善により、様々なフェディバースプラットフォームでのボットの相互作用が一貫性と信頼性を持つようになります。

BotKit 0.2.0で最初の一歩を踏み出す

これらの新機能を体験してみたいですか？BotKit 0.2.0はJSRで利用可能で、簡単なコマンドでインストールできます。

deno add jsr:@fedify/botkit@0.2.0

BotKitはTemporal API（JavaScriptではまだ試験的な機能）を使用するため、deno.jsonでこれを有効にする必要があります。

{
  "imports": {
    "@fedify/botkit": "jsr:@fedify/botkit@0.2.0"
  },
  "unstable": ["temporal"]
}

これらの簡単なステップで、最新機能を使ってフェディバースボットを作成またはアップグレードする準備が整いました。

今後の展望

完全なドキュメントと詳細な例については、私たちのドキュメントサイトをご覧ください。

BotKitは、ActivityPubサーバーアプリケーションを作成するための低レベルフレームワークFedifyによって支えられています。

BotKit by Fedify

@botkit@hollo.social

BotKit 0.2.0 Released

This release marks an important step in our journey to make fediverse bot development more accessible and powerful, introducing several features that our community has been requesting.

The Journey to Better Bot Interactions

Expressing Your Bot's Personality with Custom Emojis

One of the most requested features has been #custom_emoji support. Now your bots can truly express their personality with unique visuals that make their messages stand out.

// Define custom emojis for your bot
const emojis = bot.addCustomEmojis({
  botkit: { 
    file: `${import.meta.dirname}/images/botkit.png`, 
    type: "image/png" 
  },
  fedify: { 
    url: "https://fedify.dev/logo.png", 
    type: "image/png" 
  }
});

// Use these custom emojis in your messages
await session.publish(
  text`BotKit ${customEmoji(emojis.botkit)} is powered by Fedify ${customEmoji(emojis.fedify)}`
);

With this new API, you can:

Add custom emojis to your bot with Bot.addCustomEmojis()
Include these emojis in messages with the customEmoji() function
Use the text tagged template with Fedify Emoji objects

Engaging Through Reactions

Communication isn't just about posting messages—it's also about responding to others. The new reaction system creates natural interaction points between your bot and its followers:

// React to a message with a standard Unicode emoji
await message.react(emoji`👍`);

// Or use one of your custom emojis as a reaction
await message.react(emojis.botkit);

// Create a responsive bot that acknowledges reactions
bot.onReact = async (session, reaction) => {
  await session.publish(
    text`Thanks for reacting with ${reaction.emoji} to my message, ${reaction.actor}!`,
    { visibility: "direct" }
  );
};

This feature allows your bot to:

React to messages with Unicode emojis using Message.react()
React with the custom emojis you've defined
Handle reaction events with Bot.onReact and Bot.onUnreact handlers

Conversations Through Quotes

Discussions often involve referencing what others have said. Our new #quote support enables more cohesive conversation threads:

// Quote another message in your bot's post
await session.publish(
  text`Responding to this interesting point...`,
  { quoteTarget: originalMessage }
);

// Handle when users quote your bot's messages
bot.onQuote = async (session, quoteMessage) => {
  await session.publish(
    text`Thanks for sharing my thoughts, ${quoteMessage.actor}!`,
    { visibility: "direct" }
  );
};

With quote support, your bot can:

Quote messages with quoteTarget option
Access quoted messages via Message.quoteTarget
Handle quote events with the new Bot.onQuote event handler

Visual Enhancements

Because communication is visual too, we've improved how your bot presents itself:

Image attachments now properly display in the web interface
Your bot's content looks better and provides a richer experience

Behind the Scenes: Enhanced Activity Propagation

We've also improved how activities propagate through the fediverse:

More precise propagation of replies, shares, updates, and deletes
Activities are now properly sent to the original message authors

These improvements ensure your bot's interactions are consistent and reliable across different fediverse platforms.

Taking Your First Steps with BotKit 0.2.0

Ready to experience these new features? BotKit 0.2.0 is available on JSR and can be installed with a simple command:

deno add jsr:@fedify/botkit@0.2.0

Since BotKit uses the Temporal API (which is still evolving in JavaScript), remember to enable it in your deno.json:

{
  "imports": {
    "@fedify/botkit": "jsr:@fedify/botkit@0.2.0"
  },
  "unstable": ["temporal"]
}

With these simple steps, you're ready to create or upgrade your fediverse bot with our latest features.

Looking Forward

For complete docs and more examples, visit our docs site.

Thank you to everyone who contributed to this release through feedback, feature requests, and code contributions. The BotKit community continues to grow, and we're excited to see what you'll create!

BotKit is powered by Fedify, a lower-level framework for creating ActivityPub server applications.

#fedidev #커모지 #커스텀_이모지 #에모지_반응 #이모지_반응 #에모지_리액션 #이모지_리액션

BotKit by Fedify

@botkit@hollo.social · Reply to BotKit by Fedify :botkit:'s post

BotKit 0.2.0 릴리스

더 나은 봇 상호작용을 위한 여정

커스텀 에모지로 봇의 개성 표현하기

// 봇의 커스텀 에모지 정의하기
const emojis = bot.addCustomEmojis({
  botkit: { 
    file: `${import.meta.dirname}/images/botkit.png`, 
    type: "image/png" 
  },
  fedify: { 
    url: "https://fedify.dev/logo.png", 
    type: "image/png" 
  }
});

// 메시지에 커스텀 에모지 사용하기
await session.publish(
  text`BotKit ${customEmoji(emojis.botkit)}은 Fedify ${customEmoji(emojis.fedify)}의 지원을 받습니다`
);

이 새로운 API를 통해 다음과 같은 기능을 사용할 수 있습니다.

Bot.addCustomEmojis()로 봇에 커스텀 에모지 추가하기
customEmoji() 함수로 메시지에 에모지 포함하기
Fedify의 Emoji 객체를 text 태그 템플릿에서 사용하기

반응을 통한 소통

// 표준 유니코드 에모지로 메시지에 반응하기
await message.react(emoji`👍`);

// 또는 정의한 커스텀 에모지로 반응하기
await message.react(emojis.botkit);

// 반응을 인식하고 응답하는 봇 만들기
bot.onReact = async (session, reaction) => {
  await session.publish(
    text`${reaction.actor}님, 제 메시지에 ${reaction.emoji} 반응을 남겨주셔서 감사합니다!`,
    { visibility: "direct" }
  );
};

이 기능을 통해 봇은 다음과 같은 작업을 수행할 수 있습니다.

Message.react()를 사용하여 유니코드 에모지로 메시지에 반응하기
정의한 커스텀 에모지로 반응하기
Bot.onReact와 Bot.onUnreact 핸들러로 반응 이벤트 처리하기

인용을 통한 대화

토론에서는 종종 다른 사람이 말한 내용을 참조해야 할 때가 있습니다. 새로운 #인용 기능은 더 응집력 있는 대화 스레드를 만들어 줍니다.

// 봇의 게시물에서 다른 메시지 인용하기
await session.publish(
  text`이 흥미로운 관점에 대한 답변입니다...`,
  { quoteTarget: originalMessage }
);

// 사용자가 봇의 메시지를 인용할 때 처리하기
bot.onQuote = async (session, quoteMessage) => {
  await session.publish(
    text`${quoteMessage.actor}님, 제 생각을 공유해 주셔서 감사합니다!`,
    { visibility: "direct" }
  );
};

인용 기능을 통해 봇은 다음과 같은 작업을 수행할 수 있습니다.

quoteTarget 옵션으로 메시지 인용하기
Message.quoteTarget을 통해 인용된 메시지에 접근하기
새로운 Bot.onQuote 이벤트 핸들러로 인용 이벤트 처리하기

시각적 개선

소통은 시각적인 요소도 중요하기 때문에 봇의 표현 방식을 개선했습니다.

웹 인터페이스에서 이미지 첨부파일이 제대로 표시됩니다
봇의 콘텐츠가 더 보기 좋아지고 풍부한 경험을 제공합니다

내부 개선: 향상된 액티비티 전파

연합우주에서 액티비티가 전파되는 방식도 개선했습니다.

답글, 공유, 업데이트, 삭제의 더 정확한 전파
원본 메시지 작성자에게 액티비티가 제대로 전송됩니다

이러한 개선 사항은 다양한 연합우주 플랫폼에서 봇의 상호작용이 일관되고 안정적으로 이루어지도록 보장합니다.

BotKit 0.2.0으로 첫 걸음 떼기

이러한 새로운 기능을 경험해 보고 싶으신가요? BotKit 0.2.0은 JSR에서 받을 수 있으며 간단한 명령어로 설치할 수 있습니다.

deno add jsr:@fedify/botkit@0.2.0

BotKit은 Temporal API(JavaScript에서 아직 시범적인 기능)를 사용하므로 deno.json에서 이를 활성화해야 합니다.

{
  "imports": {
    "@fedify/botkit": "jsr:@fedify/botkit@0.2.0"
  },
  "unstable": ["temporal"]
}

이 간단한 단계를 통해 최신 기능으로 연합우주 봇을 만들거나 업그레이드할 준비가 완료되었습니다.

앞으로의 전망

전체 문서와 더 많은 예제는 저희 문서 사이트에서 확인하실 수 있습니다.

BotKit은 ActivityPub 서버 애플리케이션을 만들기 위한 하위 레벨 프레임워크인 Fedify의 지원을 받습니다.

BotKit by Fedify

@botkit@hollo.social · Reply to BotKit by Fedify :botkit:'s post

BotKit 0.2.0のリリース

より良いボットインタラクションへの旅

カスタム絵文字でボットの個性を表現

// ボット用のカスタム絵文字を定義
const emojis = bot.addCustomEmojis({
  botkit: { 
    file: `${import.meta.dirname}/images/botkit.png`, 
    type: "image/png" 
  },
  fedify: { 
    url: "https://fedify.dev/logo.png", 
    type: "image/png" 
  }
});

// メッセージにカスタム絵文字を使用
await session.publish(
  text`BotKit ${customEmoji(emojis.botkit)}は、Fedify ${customEmoji(emojis.fedify)}によって支えられています`
);

この新しいAPIでは、次のことが可能になりました。

Bot.addCustomEmojis()でボットにカスタム絵文字を追加
customEmoji()関数でメッセージに絵文字を含める
FedifyのEmojiオブジェクトをtextタグテンプレートで使用する

リアクションによるコミュニケーション

// 標準のUnicode絵文字でメッセージにリアクション
await message.react(emoji`👍`);

// または定義したカスタム絵文字でリアクション
await message.react(emojis.botkit);

// リアクションを認識して応答するボットを作成
bot.onReact = async (session, reaction) => {
  await session.publish(
    text`${reaction.actor}さん、私のメッセージに${reaction.emoji}でリアクションしてくれてありがとうございます！`,
    { visibility: "direct" }
  );
};

この機能により、ボットは次のことができるようになりました。

Message.react()を使用してUnicode絵文字でメッセージにリアクション
定義したカスタム絵文字でリアクション
Bot.onReactとBot.onUnreactハンドラーでリアクションイベントを処理

引用による会話

議論では、他の人が言ったことを参照する必要がしばしばあります。新しい引用機能により、より結束力のある会話スレッドを作成できます。

// ボットの投稿で他のメッセージを引用
await session.publish(
  text`この興味深い視点について答えます...`,
  { quoteTarget: originalMessage }
);

// ユーザーがボットのメッセージを引用した場合の処理
bot.onQuote = async (session, quoteMessage) => {
  await session.publish(
    text`${quoteMessage.actor}さん、私の考えを共有してくれてありがとうございます！`,
    { visibility: "direct" }
  );
};

引用機能により、ボットは次のことができるようになりました。

quoteTargetオプションでメッセージを引用
Message.quoteTargetを通じて引用されたメッセージにアクセス
新しいBot.onQuoteイベントハンドラーで引用イベントを処理

視覚的な改善

コミュニケーションには視覚的要素も重要なため、ボットの表現方法を改善しました。

ウェブインターフェースで画像添付ファイルが正しく表示されるようになりました
ボットのコンテンツがより見やすくなり、豊かな体験を提供します

内部改善：活動の伝播の強化

フェディバースでの活動が伝播する方法も改善されました。

返信、共有、更新、削除のより正確な伝播
元のメッセージ作成者に活動が適切に送信されます

これらの改善により、様々なフェディバースプラットフォームでのボットの相互作用が一貫性と信頼性を持つようになります。

BotKit 0.2.0で最初の一歩を踏み出す

これらの新機能を体験してみたいですか？BotKit 0.2.0はJSRで利用可能で、簡単なコマンドでインストールできます。

deno add jsr:@fedify/botkit@0.2.0

BotKitはTemporal API（JavaScriptではまだ試験的な機能）を使用するため、deno.jsonでこれを有効にする必要があります。

{
  "imports": {
    "@fedify/botkit": "jsr:@fedify/botkit@0.2.0"
  },
  "unstable": ["temporal"]
}

これらの簡単なステップで、最新機能を使ってフェディバースボットを作成またはアップグレードする準備が整いました。

今後の展望

完全なドキュメントと詳細な例については、私たちのドキュメントサイトをご覧ください。

BotKitは、ActivityPubサーバーアプリケーションを作成するための低レベルフレームワークFedifyによって支えられています。

BotKit by Fedify

@botkit@hollo.social

BotKit 0.2.0 Released

This release marks an important step in our journey to make fediverse bot development more accessible and powerful, introducing several features that our community has been requesting.

The Journey to Better Bot Interactions

Expressing Your Bot's Personality with Custom Emojis

One of the most requested features has been #custom_emoji support. Now your bots can truly express their personality with unique visuals that make their messages stand out.

// Define custom emojis for your bot
const emojis = bot.addCustomEmojis({
  botkit: { 
    file: `${import.meta.dirname}/images/botkit.png`, 
    type: "image/png" 
  },
  fedify: { 
    url: "https://fedify.dev/logo.png", 
    type: "image/png" 
  }
});

// Use these custom emojis in your messages
await session.publish(
  text`BotKit ${customEmoji(emojis.botkit)} is powered by Fedify ${customEmoji(emojis.fedify)}`
);

With this new API, you can:

Add custom emojis to your bot with Bot.addCustomEmojis()
Include these emojis in messages with the customEmoji() function
Use the text tagged template with Fedify Emoji objects

Engaging Through Reactions

Communication isn't just about posting messages—it's also about responding to others. The new reaction system creates natural interaction points between your bot and its followers:

// React to a message with a standard Unicode emoji
await message.react(emoji`👍`);

// Or use one of your custom emojis as a reaction
await message.react(emojis.botkit);

// Create a responsive bot that acknowledges reactions
bot.onReact = async (session, reaction) => {
  await session.publish(
    text`Thanks for reacting with ${reaction.emoji} to my message, ${reaction.actor}!`,
    { visibility: "direct" }
  );
};

This feature allows your bot to:

React to messages with Unicode emojis using Message.react()
React with the custom emojis you've defined
Handle reaction events with Bot.onReact and Bot.onUnreact handlers

Conversations Through Quotes

Discussions often involve referencing what others have said. Our new #quote support enables more cohesive conversation threads:

// Quote another message in your bot's post
await session.publish(
  text`Responding to this interesting point...`,
  { quoteTarget: originalMessage }
);

// Handle when users quote your bot's messages
bot.onQuote = async (session, quoteMessage) => {
  await session.publish(
    text`Thanks for sharing my thoughts, ${quoteMessage.actor}!`,
    { visibility: "direct" }
  );
};

With quote support, your bot can:

Quote messages with quoteTarget option
Access quoted messages via Message.quoteTarget
Handle quote events with the new Bot.onQuote event handler

Visual Enhancements

Because communication is visual too, we've improved how your bot presents itself:

Image attachments now properly display in the web interface
Your bot's content looks better and provides a richer experience

Behind the Scenes: Enhanced Activity Propagation

We've also improved how activities propagate through the fediverse:

More precise propagation of replies, shares, updates, and deletes
Activities are now properly sent to the original message authors

These improvements ensure your bot's interactions are consistent and reliable across different fediverse platforms.

Taking Your First Steps with BotKit 0.2.0

Ready to experience these new features? BotKit 0.2.0 is available on JSR and can be installed with a simple command:

deno add jsr:@fedify/botkit@0.2.0

Since BotKit uses the Temporal API (which is still evolving in JavaScript), remember to enable it in your deno.json:

{
  "imports": {
    "@fedify/botkit": "jsr:@fedify/botkit@0.2.0"
  },
  "unstable": ["temporal"]
}

With these simple steps, you're ready to create or upgrade your fediverse bot with our latest features.

Looking Forward

For complete docs and more examples, visit our docs site.

Thank you to everyone who contributed to this release through feedback, feature requests, and code contributions. The BotKit community continues to grow, and we're excited to see what you'll create!

BotKit is powered by Fedify, a lower-level framework for creating ActivityPub server applications.

BotKit by Fedify

@botkit@hollo.social

BotKit 0.2.0 Released

This release marks an important step in our journey to make fediverse bot development more accessible and powerful, introducing several features that our community has been requesting.

The Journey to Better Bot Interactions

Expressing Your Bot's Personality with Custom Emojis

One of the most requested features has been #custom_emoji support. Now your bots can truly express their personality with unique visuals that make their messages stand out.

// Define custom emojis for your bot
const emojis = bot.addCustomEmojis({
  botkit: { 
    file: `${import.meta.dirname}/images/botkit.png`, 
    type: "image/png" 
  },
  fedify: { 
    url: "https://fedify.dev/logo.png", 
    type: "image/png" 
  }
});

// Use these custom emojis in your messages
await session.publish(
  text`BotKit ${customEmoji(emojis.botkit)} is powered by Fedify ${customEmoji(emojis.fedify)}`
);

With this new API, you can:

Add custom emojis to your bot with Bot.addCustomEmojis()
Include these emojis in messages with the customEmoji() function
Use the text tagged template with Fedify Emoji objects

Engaging Through Reactions

Communication isn't just about posting messages—it's also about responding to others. The new reaction system creates natural interaction points between your bot and its followers:

// React to a message with a standard Unicode emoji
await message.react(emoji`👍`);

// Or use one of your custom emojis as a reaction
await message.react(emojis.botkit);

// Create a responsive bot that acknowledges reactions
bot.onReact = async (session, reaction) => {
  await session.publish(
    text`Thanks for reacting with ${reaction.emoji} to my message, ${reaction.actor}!`,
    { visibility: "direct" }
  );
};

This feature allows your bot to:

React to messages with Unicode emojis using Message.react()
React with the custom emojis you've defined
Handle reaction events with Bot.onReact and Bot.onUnreact handlers

Conversations Through Quotes

Discussions often involve referencing what others have said. Our new #quote support enables more cohesive conversation threads:

// Quote another message in your bot's post
await session.publish(
  text`Responding to this interesting point...`,
  { quoteTarget: originalMessage }
);

// Handle when users quote your bot's messages
bot.onQuote = async (session, quoteMessage) => {
  await session.publish(
    text`Thanks for sharing my thoughts, ${quoteMessage.actor}!`,
    { visibility: "direct" }
  );
};

With quote support, your bot can:

Quote messages with quoteTarget option
Access quoted messages via Message.quoteTarget
Handle quote events with the new Bot.onQuote event handler

Visual Enhancements

Because communication is visual too, we've improved how your bot presents itself:

Image attachments now properly display in the web interface
Your bot's content looks better and provides a richer experience

Behind the Scenes: Enhanced Activity Propagation

We've also improved how activities propagate through the fediverse:

More precise propagation of replies, shares, updates, and deletes
Activities are now properly sent to the original message authors

These improvements ensure your bot's interactions are consistent and reliable across different fediverse platforms.

Taking Your First Steps with BotKit 0.2.0

Ready to experience these new features? BotKit 0.2.0 is available on JSR and can be installed with a simple command:

deno add jsr:@fedify/botkit@0.2.0

Since BotKit uses the Temporal API (which is still evolving in JavaScript), remember to enable it in your deno.json:

{
  "imports": {
    "@fedify/botkit": "jsr:@fedify/botkit@0.2.0"
  },
  "unstable": ["temporal"]
}

With these simple steps, you're ready to create or upgrade your fediverse bot with our latest features.

Looking Forward

For complete docs and more examples, visit our docs site.

Thank you to everyone who contributed to this release through feedback, feature requests, and code contributions. The BotKit community continues to grow, and we're excited to see what you'll create!

BotKit is powered by Fedify, a lower-level framework for creating ActivityPub server applications.

BotKit by Fedify

@botkit@hollo.social

BotKit 0.2.0 Released

This release marks an important step in our journey to make fediverse bot development more accessible and powerful, introducing several features that our community has been requesting.

The Journey to Better Bot Interactions

Expressing Your Bot's Personality with Custom Emojis

One of the most requested features has been #custom_emoji support. Now your bots can truly express their personality with unique visuals that make their messages stand out.

// Define custom emojis for your bot
const emojis = bot.addCustomEmojis({
  botkit: { 
    file: `${import.meta.dirname}/images/botkit.png`, 
    type: "image/png" 
  },
  fedify: { 
    url: "https://fedify.dev/logo.png", 
    type: "image/png" 
  }
});

// Use these custom emojis in your messages
await session.publish(
  text`BotKit ${customEmoji(emojis.botkit)} is powered by Fedify ${customEmoji(emojis.fedify)}`
);

With this new API, you can:

Add custom emojis to your bot with Bot.addCustomEmojis()
Include these emojis in messages with the customEmoji() function
Use the text tagged template with Fedify Emoji objects

Engaging Through Reactions

Communication isn't just about posting messages—it's also about responding to others. The new reaction system creates natural interaction points between your bot and its followers:

// React to a message with a standard Unicode emoji
await message.react(emoji`👍`);

// Or use one of your custom emojis as a reaction
await message.react(emojis.botkit);

// Create a responsive bot that acknowledges reactions
bot.onReact = async (session, reaction) => {
  await session.publish(
    text`Thanks for reacting with ${reaction.emoji} to my message, ${reaction.actor}!`,
    { visibility: "direct" }
  );
};

This feature allows your bot to:

React to messages with Unicode emojis using Message.react()
React with the custom emojis you've defined
Handle reaction events with Bot.onReact and Bot.onUnreact handlers

Conversations Through Quotes

Discussions often involve referencing what others have said. Our new #quote support enables more cohesive conversation threads:

// Quote another message in your bot's post
await session.publish(
  text`Responding to this interesting point...`,
  { quoteTarget: originalMessage }
);

// Handle when users quote your bot's messages
bot.onQuote = async (session, quoteMessage) => {
  await session.publish(
    text`Thanks for sharing my thoughts, ${quoteMessage.actor}!`,
    { visibility: "direct" }
  );
};

With quote support, your bot can:

Quote messages with quoteTarget option
Access quoted messages via Message.quoteTarget
Handle quote events with the new Bot.onQuote event handler

Visual Enhancements

Because communication is visual too, we've improved how your bot presents itself:

Image attachments now properly display in the web interface
Your bot's content looks better and provides a richer experience

Behind the Scenes: Enhanced Activity Propagation

We've also improved how activities propagate through the fediverse:

More precise propagation of replies, shares, updates, and deletes
Activities are now properly sent to the original message authors

These improvements ensure your bot's interactions are consistent and reliable across different fediverse platforms.

Taking Your First Steps with BotKit 0.2.0

Ready to experience these new features? BotKit 0.2.0 is available on JSR and can be installed with a simple command:

deno add jsr:@fedify/botkit@0.2.0

Since BotKit uses the Temporal API (which is still evolving in JavaScript), remember to enable it in your deno.json:

{
  "imports": {
    "@fedify/botkit": "jsr:@fedify/botkit@0.2.0"
  },
  "unstable": ["temporal"]
}

With these simple steps, you're ready to create or upgrade your fediverse bot with our latest features.

Looking Forward

For complete docs and more examples, visit our docs site.

Thank you to everyone who contributed to this release through feedback, feature requests, and code contributions. The BotKit community continues to grow, and we're excited to see what you'll create!

BotKit is powered by Fedify, a lower-level framework for creating ActivityPub server applications.

BotKit by Fedify

@botkit@hollo.social · Reply to BotKit by Fedify :botkit:'s post

BotKit 0.2.0のリリース

より良いボットインタラクションへの旅

カスタム絵文字でボットの個性を表現

// ボット用のカスタム絵文字を定義
const emojis = bot.addCustomEmojis({
  botkit: { 
    file: `${import.meta.dirname}/images/botkit.png`, 
    type: "image/png" 
  },
  fedify: { 
    url: "https://fedify.dev/logo.png", 
    type: "image/png" 
  }
});

// メッセージにカスタム絵文字を使用
await session.publish(
  text`BotKit ${customEmoji(emojis.botkit)}は、Fedify ${customEmoji(emojis.fedify)}によって支えられています`
);

この新しいAPIでは、次のことが可能になりました。

Bot.addCustomEmojis()でボットにカスタム絵文字を追加
customEmoji()関数でメッセージに絵文字を含める
FedifyのEmojiオブジェクトをtextタグテンプレートで使用する

リアクションによるコミュニケーション

// 標準のUnicode絵文字でメッセージにリアクション
await message.react(emoji`👍`);

// または定義したカスタム絵文字でリアクション
await message.react(emojis.botkit);

// リアクションを認識して応答するボットを作成
bot.onReact = async (session, reaction) => {
  await session.publish(
    text`${reaction.actor}さん、私のメッセージに${reaction.emoji}でリアクションしてくれてありがとうございます！`,
    { visibility: "direct" }
  );
};

この機能により、ボットは次のことができるようになりました。

Message.react()を使用してUnicode絵文字でメッセージにリアクション
定義したカスタム絵文字でリアクション
Bot.onReactとBot.onUnreactハンドラーでリアクションイベントを処理

引用による会話

議論では、他の人が言ったことを参照する必要がしばしばあります。新しい引用機能により、より結束力のある会話スレッドを作成できます。

// ボットの投稿で他のメッセージを引用
await session.publish(
  text`この興味深い視点について答えます...`,
  { quoteTarget: originalMessage }
);

// ユーザーがボットのメッセージを引用した場合の処理
bot.onQuote = async (session, quoteMessage) => {
  await session.publish(
    text`${quoteMessage.actor}さん、私の考えを共有してくれてありがとうございます！`,
    { visibility: "direct" }
  );
};

引用機能により、ボットは次のことができるようになりました。

quoteTargetオプションでメッセージを引用
Message.quoteTargetを通じて引用されたメッセージにアクセス
新しいBot.onQuoteイベントハンドラーで引用イベントを処理

視覚的な改善

コミュニケーションには視覚的要素も重要なため、ボットの表現方法を改善しました。

ウェブインターフェースで画像添付ファイルが正しく表示されるようになりました
ボットのコンテンツがより見やすくなり、豊かな体験を提供します

内部改善：活動の伝播の強化

フェディバースでの活動が伝播する方法も改善されました。

返信、共有、更新、削除のより正確な伝播
元のメッセージ作成者に活動が適切に送信されます

これらの改善により、様々なフェディバースプラットフォームでのボットの相互作用が一貫性と信頼性を持つようになります。

BotKit 0.2.0で最初の一歩を踏み出す

これらの新機能を体験してみたいですか？BotKit 0.2.0はJSRで利用可能で、簡単なコマンドでインストールできます。

deno add jsr:@fedify/botkit@0.2.0

BotKitはTemporal API（JavaScriptではまだ試験的な機能）を使用するため、deno.jsonでこれを有効にする必要があります。

{
  "imports": {
    "@fedify/botkit": "jsr:@fedify/botkit@0.2.0"
  },
  "unstable": ["temporal"]
}

これらの簡単なステップで、最新機能を使ってフェディバースボットを作成またはアップグレードする準備が整いました。

今後の展望

完全なドキュメントと詳細な例については、私たちのドキュメントサイトをご覧ください。

BotKitは、ActivityPubサーバーアプリケーションを作成するための低レベルフレームワークFedifyによって支えられています。

#fedidev #커모지 #커스텀_이모지 #에모지_반응 #이모지_반응 #에모지_리액션 #이모지_리액션

BotKit by Fedify

@botkit@hollo.social · Reply to BotKit by Fedify :botkit:'s post

BotKit 0.2.0 릴리스

더 나은 봇 상호작용을 위한 여정

커스텀 에모지로 봇의 개성 표현하기

// 봇의 커스텀 에모지 정의하기
const emojis = bot.addCustomEmojis({
  botkit: { 
    file: `${import.meta.dirname}/images/botkit.png`, 
    type: "image/png" 
  },
  fedify: { 
    url: "https://fedify.dev/logo.png", 
    type: "image/png" 
  }
});

// 메시지에 커스텀 에모지 사용하기
await session.publish(
  text`BotKit ${customEmoji(emojis.botkit)}은 Fedify ${customEmoji(emojis.fedify)}의 지원을 받습니다`
);

이 새로운 API를 통해 다음과 같은 기능을 사용할 수 있습니다.

Bot.addCustomEmojis()로 봇에 커스텀 에모지 추가하기
customEmoji() 함수로 메시지에 에모지 포함하기
Fedify의 Emoji 객체를 text 태그 템플릿에서 사용하기

반응을 통한 소통

// 표준 유니코드 에모지로 메시지에 반응하기
await message.react(emoji`👍`);

// 또는 정의한 커스텀 에모지로 반응하기
await message.react(emojis.botkit);

// 반응을 인식하고 응답하는 봇 만들기
bot.onReact = async (session, reaction) => {
  await session.publish(
    text`${reaction.actor}님, 제 메시지에 ${reaction.emoji} 반응을 남겨주셔서 감사합니다!`,
    { visibility: "direct" }
  );
};

이 기능을 통해 봇은 다음과 같은 작업을 수행할 수 있습니다.

Message.react()를 사용하여 유니코드 에모지로 메시지에 반응하기
정의한 커스텀 에모지로 반응하기
Bot.onReact와 Bot.onUnreact 핸들러로 반응 이벤트 처리하기

인용을 통한 대화

토론에서는 종종 다른 사람이 말한 내용을 참조해야 할 때가 있습니다. 새로운 #인용 기능은 더 응집력 있는 대화 스레드를 만들어 줍니다.

// 봇의 게시물에서 다른 메시지 인용하기
await session.publish(
  text`이 흥미로운 관점에 대한 답변입니다...`,
  { quoteTarget: originalMessage }
);

// 사용자가 봇의 메시지를 인용할 때 처리하기
bot.onQuote = async (session, quoteMessage) => {
  await session.publish(
    text`${quoteMessage.actor}님, 제 생각을 공유해 주셔서 감사합니다!`,
    { visibility: "direct" }
  );
};

인용 기능을 통해 봇은 다음과 같은 작업을 수행할 수 있습니다.

quoteTarget 옵션으로 메시지 인용하기
Message.quoteTarget을 통해 인용된 메시지에 접근하기
새로운 Bot.onQuote 이벤트 핸들러로 인용 이벤트 처리하기

시각적 개선

소통은 시각적인 요소도 중요하기 때문에 봇의 표현 방식을 개선했습니다.

웹 인터페이스에서 이미지 첨부파일이 제대로 표시됩니다
봇의 콘텐츠가 더 보기 좋아지고 풍부한 경험을 제공합니다

내부 개선: 향상된 액티비티 전파

연합우주에서 액티비티가 전파되는 방식도 개선했습니다.

답글, 공유, 업데이트, 삭제의 더 정확한 전파
원본 메시지 작성자에게 액티비티가 제대로 전송됩니다

이러한 개선 사항은 다양한 연합우주 플랫폼에서 봇의 상호작용이 일관되고 안정적으로 이루어지도록 보장합니다.

BotKit 0.2.0으로 첫 걸음 떼기

이러한 새로운 기능을 경험해 보고 싶으신가요? BotKit 0.2.0은 JSR에서 받을 수 있으며 간단한 명령어로 설치할 수 있습니다.

deno add jsr:@fedify/botkit@0.2.0

BotKit은 Temporal API(JavaScript에서 아직 시범적인 기능)를 사용하므로 deno.json에서 이를 활성화해야 합니다.

{
  "imports": {
    "@fedify/botkit": "jsr:@fedify/botkit@0.2.0"
  },
  "unstable": ["temporal"]
}

이 간단한 단계를 통해 최신 기능으로 연합우주 봇을 만들거나 업그레이드할 준비가 완료되었습니다.

앞으로의 전망

전체 문서와 더 많은 예제는 저희 문서 사이트에서 확인하실 수 있습니다.

BotKit은 ActivityPub 서버 애플리케이션을 만들기 위한 하위 레벨 프레임워크인 Fedify의 지원을 받습니다.

BotKit by Fedify

@botkit@hollo.social

BotKit 0.2.0 Released

This release marks an important step in our journey to make fediverse bot development more accessible and powerful, introducing several features that our community has been requesting.

The Journey to Better Bot Interactions

Expressing Your Bot's Personality with Custom Emojis

One of the most requested features has been #custom_emoji support. Now your bots can truly express their personality with unique visuals that make their messages stand out.

// Define custom emojis for your bot
const emojis = bot.addCustomEmojis({
  botkit: { 
    file: `${import.meta.dirname}/images/botkit.png`, 
    type: "image/png" 
  },
  fedify: { 
    url: "https://fedify.dev/logo.png", 
    type: "image/png" 
  }
});

// Use these custom emojis in your messages
await session.publish(
  text`BotKit ${customEmoji(emojis.botkit)} is powered by Fedify ${customEmoji(emojis.fedify)}`
);

With this new API, you can:

Add custom emojis to your bot with Bot.addCustomEmojis()
Include these emojis in messages with the customEmoji() function
Use the text tagged template with Fedify Emoji objects

Engaging Through Reactions

Communication isn't just about posting messages—it's also about responding to others. The new reaction system creates natural interaction points between your bot and its followers:

// React to a message with a standard Unicode emoji
await message.react(emoji`👍`);

// Or use one of your custom emojis as a reaction
await message.react(emojis.botkit);

// Create a responsive bot that acknowledges reactions
bot.onReact = async (session, reaction) => {
  await session.publish(
    text`Thanks for reacting with ${reaction.emoji} to my message, ${reaction.actor}!`,
    { visibility: "direct" }
  );
};

This feature allows your bot to:

React to messages with Unicode emojis using Message.react()
React with the custom emojis you've defined
Handle reaction events with Bot.onReact and Bot.onUnreact handlers

Conversations Through Quotes

Discussions often involve referencing what others have said. Our new #quote support enables more cohesive conversation threads:

// Quote another message in your bot's post
await session.publish(
  text`Responding to this interesting point...`,
  { quoteTarget: originalMessage }
);

// Handle when users quote your bot's messages
bot.onQuote = async (session, quoteMessage) => {
  await session.publish(
    text`Thanks for sharing my thoughts, ${quoteMessage.actor}!`,
    { visibility: "direct" }
  );
};

With quote support, your bot can:

Quote messages with quoteTarget option
Access quoted messages via Message.quoteTarget
Handle quote events with the new Bot.onQuote event handler

Visual Enhancements

Because communication is visual too, we've improved how your bot presents itself:

Image attachments now properly display in the web interface
Your bot's content looks better and provides a richer experience

Behind the Scenes: Enhanced Activity Propagation

We've also improved how activities propagate through the fediverse:

More precise propagation of replies, shares, updates, and deletes
Activities are now properly sent to the original message authors

These improvements ensure your bot's interactions are consistent and reliable across different fediverse platforms.

Taking Your First Steps with BotKit 0.2.0

Ready to experience these new features? BotKit 0.2.0 is available on JSR and can be installed with a simple command:

deno add jsr:@fedify/botkit@0.2.0

Since BotKit uses the Temporal API (which is still evolving in JavaScript), remember to enable it in your deno.json:

{
  "imports": {
    "@fedify/botkit": "jsr:@fedify/botkit@0.2.0"
  },
  "unstable": ["temporal"]
}

With these simple steps, you're ready to create or upgrade your fediverse bot with our latest features.

Looking Forward

For complete docs and more examples, visit our docs site.

Thank you to everyone who contributed to this release through feedback, feature requests, and code contributions. The BotKit community continues to grow, and we're excited to see what you'll create!

BotKit is powered by Fedify, a lower-level framework for creating ActivityPub server applications.

BotKit by Fedify

@botkit@hollo.social · Reply to BotKit by Fedify :botkit:'s post

BotKit 0.2.0のリリース

より良いボットインタラクションへの旅

カスタム絵文字でボットの個性を表現

// ボット用のカスタム絵文字を定義
const emojis = bot.addCustomEmojis({
  botkit: { 
    file: `${import.meta.dirname}/images/botkit.png`, 
    type: "image/png" 
  },
  fedify: { 
    url: "https://fedify.dev/logo.png", 
    type: "image/png" 
  }
});

// メッセージにカスタム絵文字を使用
await session.publish(
  text`BotKit ${customEmoji(emojis.botkit)}は、Fedify ${customEmoji(emojis.fedify)}によって支えられています`
);

この新しいAPIでは、次のことが可能になりました。

Bot.addCustomEmojis()でボットにカスタム絵文字を追加
customEmoji()関数でメッセージに絵文字を含める
FedifyのEmojiオブジェクトをtextタグテンプレートで使用する

リアクションによるコミュニケーション

// 標準のUnicode絵文字でメッセージにリアクション
await message.react(emoji`👍`);

// または定義したカスタム絵文字でリアクション
await message.react(emojis.botkit);

// リアクションを認識して応答するボットを作成
bot.onReact = async (session, reaction) => {
  await session.publish(
    text`${reaction.actor}さん、私のメッセージに${reaction.emoji}でリアクションしてくれてありがとうございます！`,
    { visibility: "direct" }
  );
};

この機能により、ボットは次のことができるようになりました。

Message.react()を使用してUnicode絵文字でメッセージにリアクション
定義したカスタム絵文字でリアクション
Bot.onReactとBot.onUnreactハンドラーでリアクションイベントを処理

引用による会話

議論では、他の人が言ったことを参照する必要がしばしばあります。新しい引用機能により、より結束力のある会話スレッドを作成できます。

// ボットの投稿で他のメッセージを引用
await session.publish(
  text`この興味深い視点について答えます...`,
  { quoteTarget: originalMessage }
);

// ユーザーがボットのメッセージを引用した場合の処理
bot.onQuote = async (session, quoteMessage) => {
  await session.publish(
    text`${quoteMessage.actor}さん、私の考えを共有してくれてありがとうございます！`,
    { visibility: "direct" }
  );
};

引用機能により、ボットは次のことができるようになりました。

quoteTargetオプションでメッセージを引用
Message.quoteTargetを通じて引用されたメッセージにアクセス
新しいBot.onQuoteイベントハンドラーで引用イベントを処理

視覚的な改善

コミュニケーションには視覚的要素も重要なため、ボットの表現方法を改善しました。

ウェブインターフェースで画像添付ファイルが正しく表示されるようになりました
ボットのコンテンツがより見やすくなり、豊かな体験を提供します

内部改善：活動の伝播の強化

フェディバースでの活動が伝播する方法も改善されました。

返信、共有、更新、削除のより正確な伝播
元のメッセージ作成者に活動が適切に送信されます

これらの改善により、様々なフェディバースプラットフォームでのボットの相互作用が一貫性と信頼性を持つようになります。

BotKit 0.2.0で最初の一歩を踏み出す

これらの新機能を体験してみたいですか？BotKit 0.2.0はJSRで利用可能で、簡単なコマンドでインストールできます。

deno add jsr:@fedify/botkit@0.2.0

BotKitはTemporal API（JavaScriptではまだ試験的な機能）を使用するため、deno.jsonでこれを有効にする必要があります。

{
  "imports": {
    "@fedify/botkit": "jsr:@fedify/botkit@0.2.0"
  },
  "unstable": ["temporal"]
}

これらの簡単なステップで、最新機能を使ってフェディバースボットを作成またはアップグレードする準備が整いました。

今後の展望

完全なドキュメントと詳細な例については、私たちのドキュメントサイトをご覧ください。

BotKitは、ActivityPubサーバーアプリケーションを作成するための低レベルフレームワークFedifyによって支えられています。

#fedidev #커모지 #커스텀_이모지 #에모지_반응 #이모지_반응 #에모지_리액션 #이모지_리액션

BotKit by Fedify

@botkit@hollo.social · Reply to BotKit by Fedify :botkit:'s post

BotKit 0.2.0 릴리스

더 나은 봇 상호작용을 위한 여정

커스텀 에모지로 봇의 개성 표현하기

// 봇의 커스텀 에모지 정의하기
const emojis = bot.addCustomEmojis({
  botkit: { 
    file: `${import.meta.dirname}/images/botkit.png`, 
    type: "image/png" 
  },
  fedify: { 
    url: "https://fedify.dev/logo.png", 
    type: "image/png" 
  }
});

// 메시지에 커스텀 에모지 사용하기
await session.publish(
  text`BotKit ${customEmoji(emojis.botkit)}은 Fedify ${customEmoji(emojis.fedify)}의 지원을 받습니다`
);

이 새로운 API를 통해 다음과 같은 기능을 사용할 수 있습니다.

Bot.addCustomEmojis()로 봇에 커스텀 에모지 추가하기
customEmoji() 함수로 메시지에 에모지 포함하기
Fedify의 Emoji 객체를 text 태그 템플릿에서 사용하기

반응을 통한 소통

// 표준 유니코드 에모지로 메시지에 반응하기
await message.react(emoji`👍`);

// 또는 정의한 커스텀 에모지로 반응하기
await message.react(emojis.botkit);

// 반응을 인식하고 응답하는 봇 만들기
bot.onReact = async (session, reaction) => {
  await session.publish(
    text`${reaction.actor}님, 제 메시지에 ${reaction.emoji} 반응을 남겨주셔서 감사합니다!`,
    { visibility: "direct" }
  );
};

이 기능을 통해 봇은 다음과 같은 작업을 수행할 수 있습니다.

Message.react()를 사용하여 유니코드 에모지로 메시지에 반응하기
정의한 커스텀 에모지로 반응하기
Bot.onReact와 Bot.onUnreact 핸들러로 반응 이벤트 처리하기

인용을 통한 대화

토론에서는 종종 다른 사람이 말한 내용을 참조해야 할 때가 있습니다. 새로운 #인용 기능은 더 응집력 있는 대화 스레드를 만들어 줍니다.

// 봇의 게시물에서 다른 메시지 인용하기
await session.publish(
  text`이 흥미로운 관점에 대한 답변입니다...`,
  { quoteTarget: originalMessage }
);

// 사용자가 봇의 메시지를 인용할 때 처리하기
bot.onQuote = async (session, quoteMessage) => {
  await session.publish(
    text`${quoteMessage.actor}님, 제 생각을 공유해 주셔서 감사합니다!`,
    { visibility: "direct" }
  );
};

인용 기능을 통해 봇은 다음과 같은 작업을 수행할 수 있습니다.

quoteTarget 옵션으로 메시지 인용하기
Message.quoteTarget을 통해 인용된 메시지에 접근하기
새로운 Bot.onQuote 이벤트 핸들러로 인용 이벤트 처리하기

시각적 개선

소통은 시각적인 요소도 중요하기 때문에 봇의 표현 방식을 개선했습니다.

웹 인터페이스에서 이미지 첨부파일이 제대로 표시됩니다
봇의 콘텐츠가 더 보기 좋아지고 풍부한 경험을 제공합니다

내부 개선: 향상된 액티비티 전파

연합우주에서 액티비티가 전파되는 방식도 개선했습니다.

답글, 공유, 업데이트, 삭제의 더 정확한 전파
원본 메시지 작성자에게 액티비티가 제대로 전송됩니다

이러한 개선 사항은 다양한 연합우주 플랫폼에서 봇의 상호작용이 일관되고 안정적으로 이루어지도록 보장합니다.

BotKit 0.2.0으로 첫 걸음 떼기

이러한 새로운 기능을 경험해 보고 싶으신가요? BotKit 0.2.0은 JSR에서 받을 수 있으며 간단한 명령어로 설치할 수 있습니다.

deno add jsr:@fedify/botkit@0.2.0

BotKit은 Temporal API(JavaScript에서 아직 시범적인 기능)를 사용하므로 deno.json에서 이를 활성화해야 합니다.

{
  "imports": {
    "@fedify/botkit": "jsr:@fedify/botkit@0.2.0"
  },
  "unstable": ["temporal"]
}

이 간단한 단계를 통해 최신 기능으로 연합우주 봇을 만들거나 업그레이드할 준비가 완료되었습니다.

앞으로의 전망

전체 문서와 더 많은 예제는 저희 문서 사이트에서 확인하실 수 있습니다.

BotKit은 ActivityPub 서버 애플리케이션을 만들기 위한 하위 레벨 프레임워크인 Fedify의 지원을 받습니다.

BotKit by Fedify

@botkit@hollo.social

BotKit 0.2.0 Released

This release marks an important step in our journey to make fediverse bot development more accessible and powerful, introducing several features that our community has been requesting.

The Journey to Better Bot Interactions

Expressing Your Bot's Personality with Custom Emojis

One of the most requested features has been #custom_emoji support. Now your bots can truly express their personality with unique visuals that make their messages stand out.

// Define custom emojis for your bot
const emojis = bot.addCustomEmojis({
  botkit: { 
    file: `${import.meta.dirname}/images/botkit.png`, 
    type: "image/png" 
  },
  fedify: { 
    url: "https://fedify.dev/logo.png", 
    type: "image/png" 
  }
});

// Use these custom emojis in your messages
await session.publish(
  text`BotKit ${customEmoji(emojis.botkit)} is powered by Fedify ${customEmoji(emojis.fedify)}`
);

With this new API, you can:

Add custom emojis to your bot with Bot.addCustomEmojis()
Include these emojis in messages with the customEmoji() function
Use the text tagged template with Fedify Emoji objects

Engaging Through Reactions

Communication isn't just about posting messages—it's also about responding to others. The new reaction system creates natural interaction points between your bot and its followers:

// React to a message with a standard Unicode emoji
await message.react(emoji`👍`);

// Or use one of your custom emojis as a reaction
await message.react(emojis.botkit);

// Create a responsive bot that acknowledges reactions
bot.onReact = async (session, reaction) => {
  await session.publish(
    text`Thanks for reacting with ${reaction.emoji} to my message, ${reaction.actor}!`,
    { visibility: "direct" }
  );
};

This feature allows your bot to:

React to messages with Unicode emojis using Message.react()
React with the custom emojis you've defined
Handle reaction events with Bot.onReact and Bot.onUnreact handlers

Conversations Through Quotes

Discussions often involve referencing what others have said. Our new #quote support enables more cohesive conversation threads:

// Quote another message in your bot's post
await session.publish(
  text`Responding to this interesting point...`,
  { quoteTarget: originalMessage }
);

// Handle when users quote your bot's messages
bot.onQuote = async (session, quoteMessage) => {
  await session.publish(
    text`Thanks for sharing my thoughts, ${quoteMessage.actor}!`,
    { visibility: "direct" }
  );
};

With quote support, your bot can:

Quote messages with quoteTarget option
Access quoted messages via Message.quoteTarget
Handle quote events with the new Bot.onQuote event handler

Visual Enhancements

Because communication is visual too, we've improved how your bot presents itself:

Image attachments now properly display in the web interface
Your bot's content looks better and provides a richer experience

Behind the Scenes: Enhanced Activity Propagation

We've also improved how activities propagate through the fediverse:

More precise propagation of replies, shares, updates, and deletes
Activities are now properly sent to the original message authors

These improvements ensure your bot's interactions are consistent and reliable across different fediverse platforms.

Taking Your First Steps with BotKit 0.2.0

Ready to experience these new features? BotKit 0.2.0 is available on JSR and can be installed with a simple command:

deno add jsr:@fedify/botkit@0.2.0

Since BotKit uses the Temporal API (which is still evolving in JavaScript), remember to enable it in your deno.json:

{
  "imports": {
    "@fedify/botkit": "jsr:@fedify/botkit@0.2.0"
  },
  "unstable": ["temporal"]
}

With these simple steps, you're ready to create or upgrade your fediverse bot with our latest features.

Looking Forward

For complete docs and more examples, visit our docs site.

Thank you to everyone who contributed to this release through feedback, feature requests, and code contributions. The BotKit community continues to grow, and we're excited to see what you'll create!

BotKit is powered by Fedify, a lower-level framework for creating ActivityPub server applications.

BotKit by Fedify

@botkit@hollo.social

Coming soon in #BotKit 0.2.0: Native #quote post support!

We're excited to share a preview of the upcoming quoting features in BotKit 0.2.0. This update will make it easier for your bots to engage with quoted content across the fediverse.

The quoting feature set includes:

Detecting when someone quotes your bot's posts with the new Bot.onQuote event handler
Accessing quoted content through the Message.quoteTarget property
Creating quote posts using the quoteTarget option in Session.publish() and Message.reply() methods

Here's a quick example of how you can use the quote detection:

bot.onQuote = async (session, quote) => {
  // The quote parameter is a Message object representing the post that quoted your bot
  await quote.reply(text`Thanks for quoting my post, ${quote.actor}!`);
  
  // You can access the original quoted message
  const originalPost = quote.quoteTarget;
  console.log(`Original message: ${originalPost?.text}`);
};

And creating quote posts is just as simple:

// Quote in a new post
await session.publish(
  text`I'm quoting this interesting message!`,
  { quoteTarget: someMessage }
);

// Or quote in a reply
await message.reply(
  text`Interesting point! I'm quoting another relevant post here.`,
  { quoteTarget: anotherMessage }
);

Want to try these features right now? You can install the development version from JSR:

deno add jsr:@fedify/botkit@0.2.0-dev.90+d6ab4bdc

We're looking forward to seeing how you use these quoting capabilities in your bots!

BotKit by Fedify

@botkit@hollo.social

Coming soon in #BotKit 0.2.0: Native #quote post support!

We're excited to share a preview of the upcoming quoting features in BotKit 0.2.0. This update will make it easier for your bots to engage with quoted content across the fediverse.

The quoting feature set includes:

Detecting when someone quotes your bot's posts with the new Bot.onQuote event handler
Accessing quoted content through the Message.quoteTarget property
Creating quote posts using the quoteTarget option in Session.publish() and Message.reply() methods

Here's a quick example of how you can use the quote detection:

bot.onQuote = async (session, quote) => {
  // The quote parameter is a Message object representing the post that quoted your bot
  await quote.reply(text`Thanks for quoting my post, ${quote.actor}!`);
  
  // You can access the original quoted message
  const originalPost = quote.quoteTarget;
  console.log(`Original message: ${originalPost?.text}`);
};

And creating quote posts is just as simple:

// Quote in a new post
await session.publish(
  text`I'm quoting this interesting message!`,
  { quoteTarget: someMessage }
);

// Or quote in a reply
await message.reply(
  text`Interesting point! I'm quoting another relevant post here.`,
  { quoteTarget: anotherMessage }
);

Want to try these features right now? You can install the development version from JSR:

deno add jsr:@fedify/botkit@0.2.0-dev.90+d6ab4bdc

We're looking forward to seeing how you use these quoting capabilities in your bots!

BotKit by Fedify

@botkit@hollo.social

Coming soon in #BotKit 0.2.0: Native #quote post support!

We're excited to share a preview of the upcoming quoting features in BotKit 0.2.0. This update will make it easier for your bots to engage with quoted content across the fediverse.

The quoting feature set includes:

Detecting when someone quotes your bot's posts with the new Bot.onQuote event handler
Accessing quoted content through the Message.quoteTarget property
Creating quote posts using the quoteTarget option in Session.publish() and Message.reply() methods

Here's a quick example of how you can use the quote detection:

bot.onQuote = async (session, quote) => {
  // The quote parameter is a Message object representing the post that quoted your bot
  await quote.reply(text`Thanks for quoting my post, ${quote.actor}!`);
  
  // You can access the original quoted message
  const originalPost = quote.quoteTarget;
  console.log(`Original message: ${originalPost?.text}`);
};

And creating quote posts is just as simple:

// Quote in a new post
await session.publish(
  text`I'm quoting this interesting message!`,
  { quoteTarget: someMessage }
);

// Or quote in a reply
await message.reply(
  text`Interesting point! I'm quoting another relevant post here.`,
  { quoteTarget: anotherMessage }
);

Want to try these features right now? You can install the development version from JSR:

deno add jsr:@fedify/botkit@0.2.0-dev.90+d6ab4bdc

We're looking forward to seeing how you use these quoting capabilities in your bots!

BotKit by Fedify

@botkit@hollo.social

Coming soon in #BotKit 0.2.0: Native #quote post support!

We're excited to share a preview of the upcoming quoting features in BotKit 0.2.0. This update will make it easier for your bots to engage with quoted content across the fediverse.

The quoting feature set includes:

Detecting when someone quotes your bot's posts with the new Bot.onQuote event handler
Accessing quoted content through the Message.quoteTarget property
Creating quote posts using the quoteTarget option in Session.publish() and Message.reply() methods

Here's a quick example of how you can use the quote detection:

bot.onQuote = async (session, quote) => {
  // The quote parameter is a Message object representing the post that quoted your bot
  await quote.reply(text`Thanks for quoting my post, ${quote.actor}!`);
  
  // You can access the original quoted message
  const originalPost = quote.quoteTarget;
  console.log(`Original message: ${originalPost?.text}`);
};

And creating quote posts is just as simple:

// Quote in a new post
await session.publish(
  text`I'm quoting this interesting message!`,
  { quoteTarget: someMessage }
);

// Or quote in a reply
await message.reply(
  text`Interesting point! I'm quoting another relevant post here.`,
  { quoteTarget: anotherMessage }
);

Want to try these features right now? You can install the development version from JSR:

deno add jsr:@fedify/botkit@0.2.0-dev.90+d6ab4bdc

We're looking forward to seeing how you use these quoting capabilities in your bots!

BotKit by Fedify

@botkit@hollo.social

Coming soon in #BotKit 0.2.0: Native #quote post support!

We're excited to share a preview of the upcoming quoting features in BotKit 0.2.0. This update will make it easier for your bots to engage with quoted content across the fediverse.

The quoting feature set includes:

Detecting when someone quotes your bot's posts with the new Bot.onQuote event handler
Accessing quoted content through the Message.quoteTarget property
Creating quote posts using the quoteTarget option in Session.publish() and Message.reply() methods

Here's a quick example of how you can use the quote detection:

bot.onQuote = async (session, quote) => {
  // The quote parameter is a Message object representing the post that quoted your bot
  await quote.reply(text`Thanks for quoting my post, ${quote.actor}!`);
  
  // You can access the original quoted message
  const originalPost = quote.quoteTarget;
  console.log(`Original message: ${originalPost?.text}`);
};

And creating quote posts is just as simple:

// Quote in a new post
await session.publish(
  text`I'm quoting this interesting message!`,
  { quoteTarget: someMessage }
);

// Or quote in a reply
await message.reply(
  text`Interesting point! I'm quoting another relevant post here.`,
  { quoteTarget: anotherMessage }
);

Want to try these features right now? You can install the development version from JSR:

deno add jsr:@fedify/botkit@0.2.0-dev.90+d6ab4bdc

We're looking forward to seeing how you use these quoting capabilities in your bots!

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

I've been considering what to add in the next version of BotKit (v0.2.0) and wanted to share my current plans. After reviewing feedback and examining the #ActivityPub ecosystem, I've identified three key features that would significantly enhance the framework's capabilities:

Custom emoji support. This would allow bots to use server-defined custom emojis in their messages, making communication more expressive and allowing better integration with instance culture.
Emoji reactions. I plan to implement both sending and receiving emoji reactions to messages. This provides a lightweight interaction model that many users prefer for simple acknowledgments or responses. This would manifest as new event handlers (like Bot.onReaction) and methods (like Message.react()).
Quote posts. The ability to reference other posts with commentary is an important discourse feature in the fediverse. Supporting both sending quotes and detecting when bot posts have been quoted would enable more sophisticated conversational patterns.

These additions should make #BotKit more capable while maintaining its simple, developer-friendly API. I expect implementation to involve extending the Message class and adding new Text processing capabilities, all while keeping backward compatibility with existing bots. Having built both Hollo and Hackers' Pub, I already have deep familiarity with how various ActivityPub implementations handle these features across the fediverse. I welcome any community feedback on priorities or implementation details before I begin coding.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

The challenges are numerous:

First, there's no standardization. ActivityPub specifications don't define how custom emoji should work, leading to inconsistent implementations across different servers like Mastodon and Misskey.

BotKit by Fedify

@botkit@hollo.social

We're excited to introduce emoji reactions in the upcoming #BotKit 0.2.0 release!

With the new Message.react() method, your bot can now react to messages using standard Unicode #emojis:

await message.react(emoji`👍`);

#Custom_emoji support is also included, allowing your bot to react with server-specific emojis:

const emojis = bot.addCustomEmojis({
  // Use a remote image URL:
  yesBlob: {
    url: "https://cdn3.emoji.gg/emojis/68238-yesblob.png",
    mediaType: "image/png",
  },
  // Use a local image file:
  noBlob: {
    file: `${import.meta.dirname}/emojis/no_blob.png`,
    mediaType: "image/webp",
  },
});

await message.react(emojis.yesBlob);

Reactions can be removed using the AuthorizedReaction.unreact() method:

const reaction = await message.react(emoji`❤️`);
await reaction.unreact();

Want to try these features now? You can install the development version from JSR today:

deno add jsr:@fedify/botkit@0.2.0-dev.84+c997c6a6

We're looking forward to seeing how your bots express themselves with this new feature!

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Custom emoji support. This would allow bots to use server-defined custom emojis in their messages, making communication more expressive and allowing better integration with instance culture.
Emoji reactions. I plan to implement both sending and receiving emoji reactions to messages. This provides a lightweight interaction model that many users prefer for simple acknowledgments or responses. This would manifest as new event handlers (like Bot.onReaction) and methods (like Message.react()).
Quote posts. The ability to reference other posts with commentary is an important discourse feature in the fediverse. Supporting both sending quotes and detecting when bot posts have been quoted would enable more sophisticated conversational patterns.

Fedify: an ActivityPub server framework

@fedify@hollo.social

In case you weren't aware, #Fedify has both #Discord and #Matrix communities where you can get help, discuss features, or just chat about #ActivityPub and federated social networks.

Matrix space: #fedify:matrix.org
Discord server: https://discord.gg/bhtwpzURwd

Feel free to join either community based on your preference. Both channels have active discussions about Fedify and federation topics.

BotKit by Fedify

@botkit@hollo.social

We're excited to introduce emoji reactions in the upcoming #BotKit 0.2.0 release!

With the new Message.react() method, your bot can now react to messages using standard Unicode #emojis:

await message.react(emoji`👍`);

#Custom_emoji support is also included, allowing your bot to react with server-specific emojis:

const emojis = bot.addCustomEmojis({
  // Use a remote image URL:
  yesBlob: {
    url: "https://cdn3.emoji.gg/emojis/68238-yesblob.png",
    mediaType: "image/png",
  },
  // Use a local image file:
  noBlob: {
    file: `${import.meta.dirname}/emojis/no_blob.png`,
    mediaType: "image/webp",
  },
});

await message.react(emojis.yesBlob);

Reactions can be removed using the AuthorizedReaction.unreact() method:

const reaction = await message.react(emoji`❤️`);
await reaction.unreact();

Want to try these features now? You can install the development version from JSR today:

deno add jsr:@fedify/botkit@0.2.0-dev.84+c997c6a6

We're looking forward to seeing how your bots express themselves with this new feature!

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Custom emoji support. This would allow bots to use server-defined custom emojis in their messages, making communication more expressive and allowing better integration with instance culture.
Emoji reactions. I plan to implement both sending and receiving emoji reactions to messages. This provides a lightweight interaction model that many users prefer for simple acknowledgments or responses. This would manifest as new event handlers (like Bot.onReaction) and methods (like Message.react()).
Quote posts. The ability to reference other posts with commentary is an important discourse feature in the fediverse. Supporting both sending quotes and detecting when bot posts have been quoted would enable more sophisticated conversational patterns.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Custom emoji support. This would allow bots to use server-defined custom emojis in their messages, making communication more expressive and allowing better integration with instance culture.
Emoji reactions. I plan to implement both sending and receiving emoji reactions to messages. This provides a lightweight interaction model that many users prefer for simple acknowledgments or responses. This would manifest as new event handlers (like Bot.onReaction) and methods (like Message.react()).
Quote posts. The ability to reference other posts with commentary is an important discourse feature in the fediverse. Supporting both sending quotes and detecting when bot posts have been quoted would enable more sophisticated conversational patterns.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Custom emoji support. This would allow bots to use server-defined custom emojis in their messages, making communication more expressive and allowing better integration with instance culture.
Emoji reactions. I plan to implement both sending and receiving emoji reactions to messages. This provides a lightweight interaction model that many users prefer for simple acknowledgments or responses. This would manifest as new event handlers (like Bot.onReaction) and methods (like Message.react()).
Quote posts. The ability to reference other posts with commentary is an important discourse feature in the fediverse. Supporting both sending quotes and detecting when bot posts have been quoted would enable more sophisticated conversational patterns.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Custom emoji support. This would allow bots to use server-defined custom emojis in their messages, making communication more expressive and allowing better integration with instance culture.
Emoji reactions. I plan to implement both sending and receiving emoji reactions to messages. This provides a lightweight interaction model that many users prefer for simple acknowledgments or responses. This would manifest as new event handlers (like Bot.onReaction) and methods (like Message.react()).
Quote posts. The ability to reference other posts with commentary is an important discourse feature in the fediverse. Supporting both sending quotes and detecting when bot posts have been quoted would enable more sophisticated conversational patterns.

BotKit by Fedify

@botkit@hollo.social

We're excited to introduce emoji reactions in the upcoming #BotKit 0.2.0 release!

With the new Message.react() method, your bot can now react to messages using standard Unicode #emojis:

await message.react(emoji`👍`);

#Custom_emoji support is also included, allowing your bot to react with server-specific emojis:

const emojis = bot.addCustomEmojis({
  // Use a remote image URL:
  yesBlob: {
    url: "https://cdn3.emoji.gg/emojis/68238-yesblob.png",
    mediaType: "image/png",
  },
  // Use a local image file:
  noBlob: {
    file: `${import.meta.dirname}/emojis/no_blob.png`,
    mediaType: "image/webp",
  },
});

await message.react(emojis.yesBlob);

Reactions can be removed using the AuthorizedReaction.unreact() method:

const reaction = await message.react(emoji`❤️`);
await reaction.unreact();

Want to try these features now? You can install the development version from JSR today:

deno add jsr:@fedify/botkit@0.2.0-dev.84+c997c6a6

We're looking forward to seeing how your bots express themselves with this new feature!

BotKit by Fedify

@botkit@hollo.social

We're excited to introduce emoji reactions in the upcoming #BotKit 0.2.0 release!

With the new Message.react() method, your bot can now react to messages using standard Unicode #emojis:

await message.react(emoji`👍`);

#Custom_emoji support is also included, allowing your bot to react with server-specific emojis:

const emojis = bot.addCustomEmojis({
  // Use a remote image URL:
  yesBlob: {
    url: "https://cdn3.emoji.gg/emojis/68238-yesblob.png",
    mediaType: "image/png",
  },
  // Use a local image file:
  noBlob: {
    file: `${import.meta.dirname}/emojis/no_blob.png`,
    mediaType: "image/webp",
  },
});

await message.react(emojis.yesBlob);

Reactions can be removed using the AuthorizedReaction.unreact() method:

const reaction = await message.react(emoji`❤️`);
await reaction.unreact();

Want to try these features now? You can install the development version from JSR today:

deno add jsr:@fedify/botkit@0.2.0-dev.84+c997c6a6

We're looking forward to seeing how your bots express themselves with this new feature!

BotKit by Fedify

@botkit@hollo.social

We're excited to introduce emoji reactions in the upcoming #BotKit 0.2.0 release!

With the new Message.react() method, your bot can now react to messages using standard Unicode #emojis:

await message.react(emoji`👍`);

#Custom_emoji support is also included, allowing your bot to react with server-specific emojis:

const emojis = bot.addCustomEmojis({
  // Use a remote image URL:
  yesBlob: {
    url: "https://cdn3.emoji.gg/emojis/68238-yesblob.png",
    mediaType: "image/png",
  },
  // Use a local image file:
  noBlob: {
    file: `${import.meta.dirname}/emojis/no_blob.png`,
    mediaType: "image/webp",
  },
});

await message.react(emojis.yesBlob);

Reactions can be removed using the AuthorizedReaction.unreact() method:

const reaction = await message.react(emoji`❤️`);
await reaction.unreact();

Want to try these features now? You can install the development version from JSR today:

deno add jsr:@fedify/botkit@0.2.0-dev.84+c997c6a6

We're looking forward to seeing how your bots express themselves with this new feature!

BotKit by Fedify

@botkit@hollo.social

We're excited to announce that #BotKit 0.2.0 will introduce custom emoji support! This feature allows your bots to express themselves with more personality and engagement.

What's included:

Add custom emojis to your bot with Bot.addCustomEmojis()
Use emoji in messages with the customEmoji() function
Support for both local image files and remote URLs as emoji sources
Full integration with BotKit's text formatting system

Simple example:

// Define custom emojis
const emojis = bot.addCustomEmojis({
  botkit: { file: "./botkit.png", type: "image/png" },
  fedify: { url: "https://fedify.dev/logo.png", type: "image/png" }
});

// Use in messages
await session.publish(
  text`Hello world! ${customEmoji(emojis.botkit)}`
);

Want to try it early? You can install the development version from JSR today:

deno add jsr:@fedify/botkit@0.2.0-dev.82+8a0438e6

BotKit by Fedify

@botkit@hollo.social

We're excited to announce that #BotKit 0.2.0 will introduce custom emoji support! This feature allows your bots to express themselves with more personality and engagement.

What's included:

Add custom emojis to your bot with Bot.addCustomEmojis()
Use emoji in messages with the customEmoji() function
Support for both local image files and remote URLs as emoji sources
Full integration with BotKit's text formatting system

Simple example:

// Define custom emojis
const emojis = bot.addCustomEmojis({
  botkit: { file: "./botkit.png", type: "image/png" },
  fedify: { url: "https://fedify.dev/logo.png", type: "image/png" }
});

// Use in messages
await session.publish(
  text`Hello world! ${customEmoji(emojis.botkit)}`
);

Want to try it early? You can install the development version from JSR today:

deno add jsr:@fedify/botkit@0.2.0-dev.82+8a0438e6

BotKit by Fedify

@botkit@hollo.social

We're excited to announce that #BotKit 0.2.0 will introduce custom emoji support! This feature allows your bots to express themselves with more personality and engagement.

What's included:

Add custom emojis to your bot with Bot.addCustomEmojis()
Use emoji in messages with the customEmoji() function
Support for both local image files and remote URLs as emoji sources
Full integration with BotKit's text formatting system

Simple example:

// Define custom emojis
const emojis = bot.addCustomEmojis({
  botkit: { file: "./botkit.png", type: "image/png" },
  fedify: { url: "https://fedify.dev/logo.png", type: "image/png" }
});

// Use in messages
await session.publish(
  text`Hello world! ${customEmoji(emojis.botkit)}`
);

Want to try it early? You can install the development version from JSR today:

deno add jsr:@fedify/botkit@0.2.0-dev.82+8a0438e6

BotKit by Fedify

@botkit@hollo.social

We're excited to announce that #BotKit 0.2.0 will introduce custom emoji support! This feature allows your bots to express themselves with more personality and engagement.

What's included:

Add custom emojis to your bot with Bot.addCustomEmojis()
Use emoji in messages with the customEmoji() function
Support for both local image files and remote URLs as emoji sources
Full integration with BotKit's text formatting system

Simple example:

// Define custom emojis
const emojis = bot.addCustomEmojis({
  botkit: { file: "./botkit.png", type: "image/png" },
  fedify: { url: "https://fedify.dev/logo.png", type: "image/png" }
});

// Use in messages
await session.publish(
  text`Hello world! ${customEmoji(emojis.botkit)}`
);

Want to try it early? You can install the development version from JSR today:

deno add jsr:@fedify/botkit@0.2.0-dev.82+8a0438e6

Fedify: an ActivityPub server framework

@fedify@hollo.social

In case you weren't aware, #Fedify has both #Discord and #Matrix communities where you can get help, discuss features, or just chat about #ActivityPub and federated social networks.

Matrix space: #fedify:matrix.org
Discord server: https://discord.gg/bhtwpzURwd

Feel free to join either community based on your preference. Both channels have active discussions about Fedify and federation topics.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

The challenges are numerous:

First, there's no standardization. ActivityPub specifications don't define how custom emoji should work, leading to inconsistent implementations across different servers like Mastodon and Misskey.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

The challenges are numerous:

First, there's no standardization. ActivityPub specifications don't define how custom emoji should work, leading to inconsistent implementations across different servers like Mastodon and Misskey.

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

Matrixスペース：#fedify:matrix.org
Discordサーバー：https://discord.gg/bhtwpzURwd

Fedify: an ActivityPub server framework

@fedify@hollo.social

In case you weren't aware, #Fedify has both #Discord and #Matrix communities where you can get help, discuss features, or just chat about #ActivityPub and federated social networks.

Matrix space: #fedify:matrix.org
Discord server: https://discord.gg/bhtwpzURwd

Feel free to join either community based on your preference. Both channels have active discussions about Fedify and federation topics.

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

Matrixスペース：#fedify:matrix.org
Discordサーバー：https://discord.gg/bhtwpzURwd

Fedify: an ActivityPub server framework

@fedify@hollo.social

In case you weren't aware, #Fedify has both #Discord and #Matrix communities where you can get help, discuss features, or just chat about #ActivityPub and federated social networks.

Matrix space: #fedify:matrix.org
Discord server: https://discord.gg/bhtwpzURwd

Feel free to join either community based on your preference. Both channels have active discussions about Fedify and federation topics.

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

Matrixスペース：#fedify:matrix.org
Discordサーバー：https://discord.gg/bhtwpzURwd

#Fedify #fedidev #ActivityPub #Discord #Matrix #디스코드 #매트릭스

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

Matrix 스페이스: #fedify:matrix.org
Discord 서버: https://discord.gg/bhtwpzURwd

여러분의 선호도에 따라 어느 커뮤니티든 참여해 주세요. 두 채널 모두 Fedify와 연합 관련 주제에 대한 활발한 논의가 이루어지고 있습니다.

Fedify: an ActivityPub server framework

@fedify@hollo.social

In case you weren't aware, #Fedify has both #Discord and #Matrix communities where you can get help, discuss features, or just chat about #ActivityPub and federated social networks.

Matrix space: #fedify:matrix.org
Discord server: https://discord.gg/bhtwpzURwd

Feel free to join either community based on your preference. Both channels have active discussions about Fedify and federation topics.

Fedify: an ActivityPub server framework

@fedify@hollo.social

In case you weren't aware, #Fedify has both #Discord and #Matrix communities where you can get help, discuss features, or just chat about #ActivityPub and federated social networks.

Matrix space: #fedify:matrix.org
Discord server: https://discord.gg/bhtwpzURwd

Feel free to join either community based on your preference. Both channels have active discussions about Fedify and federation topics.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Custom emoji support. This would allow bots to use server-defined custom emojis in their messages, making communication more expressive and allowing better integration with instance culture.
Emoji reactions. I plan to implement both sending and receiving emoji reactions to messages. This provides a lightweight interaction model that many users prefer for simple acknowledgments or responses. This would manifest as new event handlers (like Bot.onReaction) and methods (like Message.react()).
Quote posts. The ability to reference other posts with commentary is an important discourse feature in the fediverse. Supporting both sending quotes and detecting when bot posts have been quoted would enable more sophisticated conversational patterns.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Custom emoji support. This would allow bots to use server-defined custom emojis in their messages, making communication more expressive and allowing better integration with instance culture.
Emoji reactions. I plan to implement both sending and receiving emoji reactions to messages. This provides a lightweight interaction model that many users prefer for simple acknowledgments or responses. This would manifest as new event handlers (like Bot.onReaction) and methods (like Message.react()).
Quote posts. The ability to reference other posts with commentary is an important discourse feature in the fediverse. Supporting both sending quotes and detecting when bot posts have been quoted would enable more sophisticated conversational patterns.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Custom emoji support. This would allow bots to use server-defined custom emojis in their messages, making communication more expressive and allowing better integration with instance culture.
Emoji reactions. I plan to implement both sending and receiving emoji reactions to messages. This provides a lightweight interaction model that many users prefer for simple acknowledgments or responses. This would manifest as new event handlers (like Bot.onReaction) and methods (like Message.react()).
Quote posts. The ability to reference other posts with commentary is an important discourse feature in the fediverse. Supporting both sending quotes and detecting when bot posts have been quoted would enable more sophisticated conversational patterns.

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

I've been wrestling with implementing #multilingual content support in Hackers' Pub, our #ActivityPub-powered platform for software engineers.

We want our users to share their knowledge in multiple languages, but we need to ensure compatibility with existing ActivityPub servers. I'm considering several approaches:

Creating separate posts for each language with clear language indicators, linking them through inReplyTo relationships (so translations appear as replies to the original post)
Using the primary language in content while storing translations in contentMap
Adding "View in other languages" links at the bottom of each post

Implementing inline language dividers that degrade gracefully on non-supporting servers, for example:

<div lang="en">
  <h3>English</h3>
  <p>This is the English content…</p>
</div>
<hr>
<div lang="ko">
  <h3>한국어</h3>
  <p>한국어 내용입니다…</p>
</div>

I'm leaning toward a hybrid approach—showing content in the user's preferred language when possible while providing easy access to other language versions.

wakest ⁂

@liaizon@social.wake.st

Before I go though and file my own issue for this, does anyone know whats up with @peertube's support for remote edits / updates of comments/replies? It seems like its not implemented and I didn't find any issues filed for this which seemed strange to me. Maybe I am overlooking something? #fedidev

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Custom emoji support. This would allow bots to use server-defined custom emojis in their messages, making communication more expressive and allowing better integration with instance culture.
Emoji reactions. I plan to implement both sending and receiving emoji reactions to messages. This provides a lightweight interaction model that many users prefer for simple acknowledgments or responses. This would manifest as new event handlers (like Bot.onReaction) and methods (like Message.react()).
Quote posts. The ability to reference other posts with commentary is an important discourse feature in the fediverse. Supporting both sending quotes and detecting when bot posts have been quoted would enable more sophisticated conversational patterns.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Custom emoji support. This would allow bots to use server-defined custom emojis in their messages, making communication more expressive and allowing better integration with instance culture.
Emoji reactions. I plan to implement both sending and receiving emoji reactions to messages. This provides a lightweight interaction model that many users prefer for simple acknowledgments or responses. This would manifest as new event handlers (like Bot.onReaction) and methods (like Message.react()).
Quote posts. The ability to reference other posts with commentary is an important discourse feature in the fediverse. Supporting both sending quotes and detecting when bot posts have been quoted would enable more sophisticated conversational patterns.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Custom emoji support. This would allow bots to use server-defined custom emojis in their messages, making communication more expressive and allowing better integration with instance culture.
Emoji reactions. I plan to implement both sending and receiving emoji reactions to messages. This provides a lightweight interaction model that many users prefer for simple acknowledgments or responses. This would manifest as new event handlers (like Bot.onReaction) and methods (like Message.react()).
Quote posts. The ability to reference other posts with commentary is an important discourse feature in the fediverse. Supporting both sending quotes and detecting when bot posts have been quoted would enable more sophisticated conversational patterns.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Custom emoji support. This would allow bots to use server-defined custom emojis in their messages, making communication more expressive and allowing better integration with instance culture.
Emoji reactions. I plan to implement both sending and receiving emoji reactions to messages. This provides a lightweight interaction model that many users prefer for simple acknowledgments or responses. This would manifest as new event handlers (like Bot.onReaction) and methods (like Message.react()).
Quote posts. The ability to reference other posts with commentary is an important discourse feature in the fediverse. Supporting both sending quotes and detecting when bot posts have been quoted would enable more sophisticated conversational patterns.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Custom emoji support. This would allow bots to use server-defined custom emojis in their messages, making communication more expressive and allowing better integration with instance culture.
Emoji reactions. I plan to implement both sending and receiving emoji reactions to messages. This provides a lightweight interaction model that many users prefer for simple acknowledgments or responses. This would manifest as new event handlers (like Bot.onReaction) and methods (like Message.react()).
Quote posts. The ability to reference other posts with commentary is an important discourse feature in the fediverse. Supporting both sending quotes and detecting when bot posts have been quoted would enable more sophisticated conversational patterns.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Custom emoji support. This would allow bots to use server-defined custom emojis in their messages, making communication more expressive and allowing better integration with instance culture.
Emoji reactions. I plan to implement both sending and receiving emoji reactions to messages. This provides a lightweight interaction model that many users prefer for simple acknowledgments or responses. This would manifest as new event handlers (like Bot.onReaction) and methods (like Message.react()).
Quote posts. The ability to reference other posts with commentary is an important discourse feature in the fediverse. Supporting both sending quotes and detecting when bot posts have been quoted would enable more sophisticated conversational patterns.

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

I've been wrestling with implementing #multilingual content support in Hackers' Pub, our #ActivityPub-powered platform for software engineers.

We want our users to share their knowledge in multiple languages, but we need to ensure compatibility with existing ActivityPub servers. I'm considering several approaches:

Creating separate posts for each language with clear language indicators, linking them through inReplyTo relationships (so translations appear as replies to the original post)
Using the primary language in content while storing translations in contentMap
Adding "View in other languages" links at the bottom of each post

Implementing inline language dividers that degrade gracefully on non-supporting servers, for example:

<div lang="en">
  <h3>English</h3>
  <p>This is the English content…</p>
</div>
<hr>
<div lang="ko">
  <h3>한국어</h3>
  <p>한국어 내용입니다…</p>
</div>

I'm leaning toward a hybrid approach—showing content in the user's preferred language when possible while providing easy access to other language versions.

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

I've been wrestling with implementing #multilingual content support in Hackers' Pub, our #ActivityPub-powered platform for software engineers.

We want our users to share their knowledge in multiple languages, but we need to ensure compatibility with existing ActivityPub servers. I'm considering several approaches:

Creating separate posts for each language with clear language indicators, linking them through inReplyTo relationships (so translations appear as replies to the original post)
Using the primary language in content while storing translations in contentMap
Adding "View in other languages" links at the bottom of each post

Implementing inline language dividers that degrade gracefully on non-supporting servers, for example:

<div lang="en">
  <h3>English</h3>
  <p>This is the English content…</p>
</div>
<hr>
<div lang="ko">
  <h3>한국어</h3>
  <p>한국어 내용입니다…</p>
</div>

I'm leaning toward a hybrid approach—showing content in the user's preferred language when possible while providing easy access to other language versions.

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

I've been wrestling with implementing #multilingual content support in Hackers' Pub, our #ActivityPub-powered platform for software engineers.

We want our users to share their knowledge in multiple languages, but we need to ensure compatibility with existing ActivityPub servers. I'm considering several approaches:

Creating separate posts for each language with clear language indicators, linking them through inReplyTo relationships (so translations appear as replies to the original post)
Using the primary language in content while storing translations in contentMap
Adding "View in other languages" links at the bottom of each post

Implementing inline language dividers that degrade gracefully on non-supporting servers, for example:

<div lang="en">
  <h3>English</h3>
  <p>This is the English content…</p>
</div>
<hr>
<div lang="ko">
  <h3>한국어</h3>
  <p>한국어 내용입니다…</p>
</div>

I'm leaning toward a hybrid approach—showing content in the user's preferred language when possible while providing easy access to other language versions.

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

I've been wrestling with implementing #multilingual content support in Hackers' Pub, our #ActivityPub-powered platform for software engineers.

We want our users to share their knowledge in multiple languages, but we need to ensure compatibility with existing ActivityPub servers. I'm considering several approaches:

Creating separate posts for each language with clear language indicators, linking them through inReplyTo relationships (so translations appear as replies to the original post)
Using the primary language in content while storing translations in contentMap
Adding "View in other languages" links at the bottom of each post

Implementing inline language dividers that degrade gracefully on non-supporting servers, for example:

<div lang="en">
  <h3>English</h3>
  <p>This is the English content…</p>
</div>
<hr>
<div lang="ko">
  <h3>한국어</h3>
  <p>한국어 내용입니다…</p>
</div>

I'm leaning toward a hybrid approach—showing content in the user's preferred language when possible while providing easy access to other language versions.

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

I've been wrestling with implementing #multilingual content support in Hackers' Pub, our #ActivityPub-powered platform for software engineers.

We want our users to share their knowledge in multiple languages, but we need to ensure compatibility with existing ActivityPub servers. I'm considering several approaches:

Creating separate posts for each language with clear language indicators, linking them through inReplyTo relationships (so translations appear as replies to the original post)
Using the primary language in content while storing translations in contentMap
Adding "View in other languages" links at the bottom of each post

Implementing inline language dividers that degrade gracefully on non-supporting servers, for example:

<div lang="en">
  <h3>English</h3>
  <p>This is the English content…</p>
</div>
<hr>
<div lang="ko">
  <h3>한국어</h3>
  <p>한국어 내용입니다…</p>
</div>

I'm leaning toward a hybrid approach—showing content in the user's preferred language when possible while providing easy access to other language versions.

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

I've been wrestling with implementing #multilingual content support in Hackers' Pub, our #ActivityPub-powered platform for software engineers.

We want our users to share their knowledge in multiple languages, but we need to ensure compatibility with existing ActivityPub servers. I'm considering several approaches:

Creating separate posts for each language with clear language indicators, linking them through inReplyTo relationships (so translations appear as replies to the original post)
Using the primary language in content while storing translations in contentMap
Adding "View in other languages" links at the bottom of each post

Implementing inline language dividers that degrade gracefully on non-supporting servers, for example:

<div lang="en">
  <h3>English</h3>
  <p>This is the English content…</p>
</div>
<hr>
<div lang="ko">
  <h3>한국어</h3>
  <p>한국어 내용입니다…</p>
</div>

I'm leaning toward a hybrid approach—showing content in the user's preferred language when possible while providing easy access to other language versions.

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

I've been wrestling with implementing #multilingual content support in Hackers' Pub, our #ActivityPub-powered platform for software engineers.

We want our users to share their knowledge in multiple languages, but we need to ensure compatibility with existing ActivityPub servers. I'm considering several approaches:

Creating separate posts for each language with clear language indicators, linking them through inReplyTo relationships (so translations appear as replies to the original post)
Using the primary language in content while storing translations in contentMap
Adding "View in other languages" links at the bottom of each post

Implementing inline language dividers that degrade gracefully on non-supporting servers, for example:

<div lang="en">
  <h3>English</h3>
  <p>This is the English content…</p>
</div>
<hr>
<div lang="ko">
  <h3>한국어</h3>
  <p>한국어 내용입니다…</p>
</div>

I'm leaning toward a hybrid approach—showing content in the user's preferred language when possible while providing easy access to other language versions.

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

I've been wrestling with implementing #multilingual content support in Hackers' Pub, our #ActivityPub-powered platform for software engineers.

We want our users to share their knowledge in multiple languages, but we need to ensure compatibility with existing ActivityPub servers. I'm considering several approaches:

Creating separate posts for each language with clear language indicators, linking them through inReplyTo relationships (so translations appear as replies to the original post)
Using the primary language in content while storing translations in contentMap
Adding "View in other languages" links at the bottom of each post

Implementing inline language dividers that degrade gracefully on non-supporting servers, for example:

<div lang="en">
  <h3>English</h3>
  <p>This is the English content…</p>
</div>
<hr>
<div lang="ko">
  <h3>한국어</h3>
  <p>한국어 내용입니다…</p>
</div>

I'm leaning toward a hybrid approach—showing content in the user's preferred language when possible while providing easy access to other language versions.

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

I've been wrestling with implementing #multilingual content support in Hackers' Pub, our #ActivityPub-powered platform for software engineers.

We want our users to share their knowledge in multiple languages, but we need to ensure compatibility with existing ActivityPub servers. I'm considering several approaches:

Creating separate posts for each language with clear language indicators, linking them through inReplyTo relationships (so translations appear as replies to the original post)
Using the primary language in content while storing translations in contentMap
Adding "View in other languages" links at the bottom of each post

Implementing inline language dividers that degrade gracefully on non-supporting servers, for example:

<div lang="en">
  <h3>English</h3>
  <p>This is the English content…</p>
</div>
<hr>
<div lang="ko">
  <h3>한국어</h3>
  <p>한국어 내용입니다…</p>
</div>

I'm leaning toward a hybrid approach—showing content in the user's preferred language when possible while providing easy access to other language versions.

https://hackers.pub/@hongminhee/2025/why-use-fedify

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Don't build #ActivityPub from scratch! It's complex. See why using the #Fedify framework is the smarter way to develop for the fediverse in my new post:

#FediLUG #Fedify #Hollo #ActivityPub #フェディバース #fediverse #fedidev

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

So, you're captivated by the fediverse—the decentralized social web powered by protocols like ActivityPub. Maybe you're dreaming of building the next great federated app, a unique space connected to Mastodon, Lemmy, Pixelfed, and more. The temptation to dive deep and implement ActivityPub yourself, from the ground up, is strong. Total control, right? Understanding every byte? Sounds cool!

But hold on a sec. Before you embark on that epic quest, let's talk reality. Implementing ActivityPub correctly isn't just one task; it's like juggling several complex standards while riding a unicycle… blindfolded. It’s hard.

That's where Fedify comes in. It's a TypeScript framework designed to handle the gnarliest parts of ActivityPub development, letting you focus on what makes your app special, not reinventing the federation wheel.

This post will break down the common headaches of DIY ActivityPub implementation and show how Fedify acts as the super-powered pain reliever, starting with the very foundation of how data is represented.

Challenge #1: Data Modeling—Speaking ActivityStreams & JSON-LD Fluently

At its core, ActivityPub relies on the ActivityStreams 2.0 vocabulary to describe actions and objects, and it uses JSON-LD as the syntax to encode this vocabulary. While powerful, this combination introduces significant complexity right from the start.

First, understanding and correctly using the vast ActivityStreams vocabulary itself is a hurdle. You need to model everything—posts (Note, Article), profiles (Person, Organization), actions (Create, Follow, Like, Announce)—using the precise terms and properties defined in the specification. Manual JSON construction is tedious and prone to errors.

Second, JSON-LD, the encoding layer, has specific rules that make direct JSON manipulation surprisingly tricky:

Missing vs. Empty Array: In JSON-LD, a property being absent is often semantically identical to it being present with an empty array. Your application logic needs to treat these cases equally when checking for values. For example, these two Note objects mean the same thing regarding the name property:
```
// No name property
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "…"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "name": [],
  "content": "…"
}
```
Single Value vs. Array: Similarly, a property holding a single value directly is often equivalent to it holding a single-element array containing that value. Your code must anticipate both representations for the same meaning, like for the content property here:
```
// Single value
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "Hello"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": ["Hello"]
}
```

Object Reference vs. Embedded Object: Properties can contain either the full JSON-LD object embedded directly or just a URI string referencing that object. Your application needs to be prepared to fetch the object's data if only a URI is given (a process called dereferencing). These two Announce activities are semantically equivalent (assuming the URIs resolve correctly):

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // Embedded objects:
  "actor": {
    "type": "Person",
    "id": "http://sally.example.org/",
    "name": "Sally"
  },
  "object": {
    "type": "Arrive",
    "id": "https://sally.example.com/arrive",
    /* ... */
  }
}

// Equivalent to:
{
  "@context":
  "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // URI references:
  "actor": "http://sally.example.org/",
  "object": "https://sally.example.com/arrive"
}

Attempting to manually handle all these vocabulary rules and JSON-LD variations consistently across your application inevitably leads to verbose, complex, and fragile code, ripe for subtle bugs that break federation.

Fedify tackles this entire data modeling challenge with its comprehensive, type-safe Activity Vocabulary API. It provides TypeScript classes for ActivityStreams types and common extensions, giving you autocompletion and compile-time safety. Crucially, these classes internally manage all the tricky JSON-LD nuances. Fedify's property accessors present a consistent interface—non-functional properties (like tags) always return arrays, functional properties (like content) always return single values or null. It handles object references versus embedded objects seamlessly through dereferencing accessors (like activity.getActor()) which automatically fetch remote objects via URI when needed—a feature known as property hydration. With Fedify, you work with a clean, predictable TypeScript API, letting the framework handle the messy details of AS vocabulary and JSON-LD encoding.

Challenge #2: Discovery & Identity—Finding Your Actors

Once you can model data, you need to make your actors discoverable. This primarily involves the WebFinger protocol (RFC 7033). You'd need to build a server endpoint at /.well-known/webfinger capable of parsing resource queries (like acct: URIs), validating the requested domain against your server, and responding with a precisely formatted JSON Resource Descriptor (JRD). This JRD must include specific links, like a self link pointing to the actor's ActivityPub ID using the correct media type. Getting any part of this wrong can make your actors invisible.

Fedify simplifies this significantly. It automatically handles WebFinger requests based on the actor information you provide through its setActorDispatcher() method. Fedify generates the correct JRD response. If you need more advanced control, like mapping user-facing handles to internal identifiers, you can easily register mapHandle() or mapAlias() callbacks. You focus on defining your actors; Fedify handles making them discoverable.

// Example: Define how to find actors
federation.setActorDispatcher(
  "/users/{username}",
  async (ctx, username) => { /* ... */ }
);
// Now GET /.well-known/webfinger?resource=acct:username@your.domain just works!

Challenge #3: Core ActivityPub Mechanics—Handling Requests and Collections

Serving actor profiles requires careful content negotiation. A request for an actor's ID needs JSON-LD for machine clients (Accept: application/activity+json) but HTML for browsers (Accept: text/html). Handling incoming activities at the inbox endpoint involves validating POST requests, verifying cryptographic signatures, parsing the payload, preventing duplicates (idempotency), and routing based on activity type. Implementing collections (outbox, followers, etc.) with correct pagination adds another layer.

Fedify streamlines all of this. Its core request handler (via Federation.fetch() or framework adapters like @fedify/express) manages content negotiation. You define actors with setActorDispatcher() and web pages with your framework (Hono, Express, SvelteKit, etc.)—Fedify routes appropriately. For the inbox, setInboxListeners() lets you define handlers per activity type (e.g., .on(Follow, ...)), while Fedify automatically handles validation, signature verification, parsing, and idempotency checks using its KV Store. Collection implementation is simplified via dispatchers (e.g., setFollowersDispatcher()); you provide logic to fetch a page of data, and Fedify constructs the correct Collection or CollectionPage with pagination.

// Define inbox handlers
federation.setInboxListeners("/inbox", "/users/{handle}/inbox")
  .on(Follow, async (ctx, follow) => { /* Handle follow */ })
  .on(Undo, async (ctx, undo) => { /* Handle undo */ });

// Define followers collection logic
federation.setFollowersDispatcher(
  "/users/{handle}/followers",
  async (ctx, handle, cursor) => { /* ... */ }
);

Challenge #4: Reliable Delivery & Asynchronous Processing—Sending Activities Robustly

Sending an activity requires more than a simple POST. Networks fail, servers go down. You need robust failure handling and retry logic (ideally with backoff). Processing incoming activities synchronously can block your server. Efficiently broadcasting to many followers (fan-out) requires background processing and using shared inboxes where possible.

Fedify addresses reliability and scalability using its MessageQueue abstraction. When configured (highly recommended), Context.sendActivity() enqueues delivery tasks. Background workers handle sending with automatic retries based on configurable policies (like outboxRetryPolicy). Fedify supports various queue backends (Deno KV, Redis, PostgreSQL, AMQP). For high-traffic fan-out, Fedify uses an optimized two-stage mechanism to distribute the load efficiently.

// Configure Fedify with a persistent queue (e.g., Deno KV)
const federation = createFederation({
  queue: new DenoKvMessageQueue(/* ... */),
  // ...
});
// Sending is now reliable and non-blocking
await ctx.sendActivity({ handle: "myUser" }, recipient, someActivity);

Challenge #5: Security—Avoiding Common Pitfalls

Securing an ActivityPub server is critical. You need to implement HTTP Signatures (draft-cavage-http-signatures-12) for server-to-server authentication—a complex process. You might also need Linked Data Signatures (LDS) or Object Integrity Proofs (OIP) based on FEP-8b32 for data integrity and compatibility. Managing cryptographic keys securely is essential. Lastly, fetching remote resources risks Server-Side Request Forgery (SSRF) if not validated properly.

Fedify is designed with security in mind. It automatically handles the creation and verification of HTTP Signatures, LDS, and OIP, provided you supply keys via setKeyPairsDispatcher(). It includes key management utilities. Crucially, Fedify's default document loader includes built-in SSRF protection, blocking requests to private IPs unless explicitly allowed.

Challenge #6: Interoperability & Maintenance—Playing Nicely with Others

The fediverse is diverse. Different servers have quirks. Ensuring compatibility requires testing and adaptation. Standards evolve with new Federation Enhancement Proposals (FEPs). You also need protocols like NodeInfo to advertise server capabilities.

Fedify aims for broad interoperability and is actively maintained. It includes features like ActivityTransformers to smooth over implementation differences. NodeInfo support is built-in via setNodeInfoDispatcher().

Challenge #7: Developer Experience—Actually Building Your App

Beyond the protocol, building any server involves setup, testing, and debugging. With federation, debugging becomes harder—was the message malformed? Was the signature wrong? Is the remote server down? Is it a compatibility quirk? Good tooling is essential.

Fedify enhances the developer experience significantly. Being built with TypeScript, it offers excellent type safety and editor auto-completion. The fedify CLI is a powerful companion designed to streamline common development tasks.

You can quickly scaffold a new project tailored to your chosen runtime and web framework using fedify init.

For debugging interactions and verifying data, fedify lookup is invaluable. It lets you inspect how any remote actor or object appears from the outside by performing WebFinger discovery and fetching the object's data. Fedify then displays the parsed object structure and properties directly in your terminal. For example, running:

$ fedify lookup @fedify-example@fedify-blog.deno.dev

Will first show progress messages and then output the structured representation of the actor, similar to this:

// Output of fedify lookup command (shows parsed object structure)
Person {
  id: URL "https://fedify-blog.deno.dev/users/fedify-example",
  name: "Fedify Example Blog",
  published: 2024-03-03T13:18:11.857Z, // Simplified timestamp
  summary: "This blog is powered by Fedify, a fediverse server framework.",
  url: URL "https://fedify-blog.deno.dev/",
  preferredUsername: "fedify-example",
  publicKey: CryptographicKey {
    id: URL "https://fedify-blog.deno.dev/users/fedify-example#main-key",
    owner: URL "https://fedify-blog.deno.dev/users/fedify-example",
    publicKey: CryptoKey { /* ... CryptoKey details ... */ }
  },
  // ... other properties like inbox, outbox, followers, endpoints ...
}

This allows you to easily check how data is structured or troubleshoot why an interaction might be failing by seeing the actual properties Fedify parsed.

Testing outgoing activities from your application during development is made much easier with fedify inbox. Running the command starts a temporary local server that acts as a publicly accessible inbox, displaying key information about the temporary actor it creates for receiving messages:

$ fedify inbox
✔ The ephemeral ActivityPub server is up and running: https://<unique_id>.lhr.life/
✔ Sent follow request to @<some_test_account>@activitypub.academy.
╭───────────────┬─────────────────────────────────────────╮
│ Actor handle: │ i@<unique_id>.lhr.life                  │
├───────────────┼─────────────────────────────────────────┤
│   Actor URI:  │ https://<unique_id>.lhr.life/i          │
├───────────────┼─────────────────────────────────────────┤
│  Actor inbox: │ https://<unique_id>.lhr.life/i/inbox    │
├───────────────┼─────────────────────────────────────────┤
│ Shared inbox: │ https://<unique_id>.lhr.life/inbox      │
╰───────────────┴─────────────────────────────────────────╯

Web interface available at: http://localhost:8000/

You then configure your developing application to send an activity to the Actor inbox or Shared inbox URI provided. When an activity arrives, fedify inbox only prints a summary table to your console indicating that a request was received:

╭────────────────┬─────────────────────────────────────╮
│     Request #: │ 2                                   │
├────────────────┼─────────────────────────────────────┤
│ Activity type: │ Follow                              │
├────────────────┼─────────────────────────────────────┤
│  HTTP request: │ POST /i/inbox                       │
├────────────────┼─────────────────────────────────────┤
│ HTTP response: │ 202                                 │
├────────────────┼─────────────────────────────────────┤
│       Details  │ https://<unique_id>.lhr.life/r/2    │
╰────────────────┴─────────────────────────────────────╯

Crucially, the detailed information about the received request—including the full headers (like Signature), the request body (the Activity JSON), and the signature verification status—is only available in the web interface provided by fedify inbox. This web UI allows you to thoroughly inspect incoming activities during development.

Screenshot of the Fedify Inbox web interface showing received activities and their details. — The Fedify Inbox web UI is where you view detailed activity information.

When you need to test interactions with the live fediverse from your local machine beyond just sending, fedify tunnel can securely expose your entire local development server temporarily. This suite of tools significantly eases the process of building and debugging federated applications.

Conclusion: Build Features, Not Plumbing

Implementing the ActivityPub suite of protocols from scratch is an incredibly complex and time-consuming undertaking. It involves deep dives into multiple technical specifications, cryptographic signing, security hardening, and navigating the nuances of a diverse ecosystem. While educational, it dramatically slows down the process of building the actual, unique features of your federated application.

Fedify offers a well-architected, secure, and type-safe foundation, handling the intricacies of federation for you—data modeling, discovery, core mechanics, delivery, security, and interoperability. It lets you focus on your application's unique value and user experience. Stop wrestling with low-level protocol details and start building your vision for the fediverse faster and more reliably. Give Fedify a try!

Getting started is straightforward. First, install the Fedify CLI using your preferred method. Once installed, create a new project template by running fedify init your-project-name.

Check out the Fedify tutorials and Fedify manual to learn more. Happy federating!

洪民憙 (Hong Minhee)

@hongminhee@hollo.social · Reply to 洪民憙 (Hong Minhee)'s post

国漢文混用体からHolloまで

本日、第8回FediLUG勉強会で「国漢文混用体からHolloまで」というタイトルで発表をしてきました。

私がなぜActivityPubサーバーフレームワークのFedifyと、シングルユーザー向けActivityPubサーバーのHolloを開発する事に成ったのか、その旅路を共有しました。

実は全ての始まりは、韓国語の「国漢文混用体」（漢字ハングル混じり文）に「振りハングル」を付けたいという単純な願いからでした。この小さな目標が、最終的にFedifyとHolloという二つのプロジェクトへと発展したのです。

興味のある方は、発表スライドをご覧ください：「国漢文混用体からHolloまで」（Speaker Deck）

洪民憙 (Hong Minhee)

@hongminhee@hollo.social · Reply to 洪民憙 (Hong Minhee)'s post

国漢文混用体からHolloまで

本日、第8回FediLUG勉強会で「国漢文混用体からHolloまで」というタイトルで発表をしてきました。

興味のある方は、発表スライドをご覧ください：「国漢文混用体からHolloまで」（Speaker Deck）

#FediLUG #Fedify #Hollo #ActivityPub #フェディバース #fediverse #fedidev

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Don't build #ActivityPub from scratch! It's complex. See why using the #Fedify framework is the smarter way to develop for the fediverse in my new post:

https://hackers.pub/@hongminhee/2025/why-use-fedify

https://hackers.pub/@hongminhee/2025/why-use-fedify

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

Challenge #1: Data Modeling—Speaking ActivityStreams & JSON-LD Fluently

Second, JSON-LD, the encoding layer, has specific rules that make direct JSON manipulation surprisingly tricky:

Missing vs. Empty Array: In JSON-LD, a property being absent is often semantically identical to it being present with an empty array. Your application logic needs to treat these cases equally when checking for values. For example, these two Note objects mean the same thing regarding the name property:
```
// No name property
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "…"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "name": [],
  "content": "…"
}
```
Single Value vs. Array: Similarly, a property holding a single value directly is often equivalent to it holding a single-element array containing that value. Your code must anticipate both representations for the same meaning, like for the content property here:
```
// Single value
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "Hello"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": ["Hello"]
}
```

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // Embedded objects:
  "actor": {
    "type": "Person",
    "id": "http://sally.example.org/",
    "name": "Sally"
  },
  "object": {
    "type": "Arrive",
    "id": "https://sally.example.com/arrive",
    /* ... */
  }
}

// Equivalent to:
{
  "@context":
  "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // URI references:
  "actor": "http://sally.example.org/",
  "object": "https://sally.example.com/arrive"
}

Challenge #2: Discovery & Identity—Finding Your Actors

// Example: Define how to find actors
federation.setActorDispatcher(
  "/users/{username}",
  async (ctx, username) => { /* ... */ }
);
// Now GET /.well-known/webfinger?resource=acct:username@your.domain just works!

Challenge #3: Core ActivityPub Mechanics—Handling Requests and Collections

// Define inbox handlers
federation.setInboxListeners("/inbox", "/users/{handle}/inbox")
  .on(Follow, async (ctx, follow) => { /* Handle follow */ })
  .on(Undo, async (ctx, undo) => { /* Handle undo */ });

// Define followers collection logic
federation.setFollowersDispatcher(
  "/users/{handle}/followers",
  async (ctx, handle, cursor) => { /* ... */ }
);

Challenge #4: Reliable Delivery & Asynchronous Processing—Sending Activities Robustly

// Configure Fedify with a persistent queue (e.g., Deno KV)
const federation = createFederation({
  queue: new DenoKvMessageQueue(/* ... */),
  // ...
});
// Sending is now reliable and non-blocking
await ctx.sendActivity({ handle: "myUser" }, recipient, someActivity);

Challenge #5: Security—Avoiding Common Pitfalls

Challenge #6: Interoperability & Maintenance—Playing Nicely with Others

Challenge #7: Developer Experience—Actually Building Your App

You can quickly scaffold a new project tailored to your chosen runtime and web framework using fedify init.

$ fedify lookup @fedify-example@fedify-blog.deno.dev

Will first show progress messages and then output the structured representation of the actor, similar to this:

// Output of fedify lookup command (shows parsed object structure)
Person {
  id: URL "https://fedify-blog.deno.dev/users/fedify-example",
  name: "Fedify Example Blog",
  published: 2024-03-03T13:18:11.857Z, // Simplified timestamp
  summary: "This blog is powered by Fedify, a fediverse server framework.",
  url: URL "https://fedify-blog.deno.dev/",
  preferredUsername: "fedify-example",
  publicKey: CryptographicKey {
    id: URL "https://fedify-blog.deno.dev/users/fedify-example#main-key",
    owner: URL "https://fedify-blog.deno.dev/users/fedify-example",
    publicKey: CryptoKey { /* ... CryptoKey details ... */ }
  },
  // ... other properties like inbox, outbox, followers, endpoints ...
}

This allows you to easily check how data is structured or troubleshoot why an interaction might be failing by seeing the actual properties Fedify parsed.

$ fedify inbox
✔ The ephemeral ActivityPub server is up and running: https://<unique_id>.lhr.life/
✔ Sent follow request to @<some_test_account>@activitypub.academy.
╭───────────────┬─────────────────────────────────────────╮
│ Actor handle: │ i@<unique_id>.lhr.life                  │
├───────────────┼─────────────────────────────────────────┤
│   Actor URI:  │ https://<unique_id>.lhr.life/i          │
├───────────────┼─────────────────────────────────────────┤
│  Actor inbox: │ https://<unique_id>.lhr.life/i/inbox    │
├───────────────┼─────────────────────────────────────────┤
│ Shared inbox: │ https://<unique_id>.lhr.life/inbox      │
╰───────────────┴─────────────────────────────────────────╯

Web interface available at: http://localhost:8000/

╭────────────────┬─────────────────────────────────────╮
│     Request #: │ 2                                   │
├────────────────┼─────────────────────────────────────┤
│ Activity type: │ Follow                              │
├────────────────┼─────────────────────────────────────┤
│  HTTP request: │ POST /i/inbox                       │
├────────────────┼─────────────────────────────────────┤
│ HTTP response: │ 202                                 │
├────────────────┼─────────────────────────────────────┤
│       Details  │ https://<unique_id>.lhr.life/r/2    │
╰────────────────┴─────────────────────────────────────╯

Conclusion: Build Features, Not Plumbing

Getting started is straightforward. First, install the Fedify CLI using your preferred method. Once installed, create a new project template by running fedify init your-project-name.

Check out the Fedify tutorials and Fedify manual to learn more. Happy federating!

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Don't build #ActivityPub from scratch! It's complex. See why using the #Fedify framework is the smarter way to develop for the fediverse in my new post:

https://hackers.pub/@hongminhee/2025/why-use-fedify

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

Challenge #1: Data Modeling—Speaking ActivityStreams & JSON-LD Fluently

Second, JSON-LD, the encoding layer, has specific rules that make direct JSON manipulation surprisingly tricky:

Missing vs. Empty Array: In JSON-LD, a property being absent is often semantically identical to it being present with an empty array. Your application logic needs to treat these cases equally when checking for values. For example, these two Note objects mean the same thing regarding the name property:
```
// No name property
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "…"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "name": [],
  "content": "…"
}
```
Single Value vs. Array: Similarly, a property holding a single value directly is often equivalent to it holding a single-element array containing that value. Your code must anticipate both representations for the same meaning, like for the content property here:
```
// Single value
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "Hello"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": ["Hello"]
}
```

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // Embedded objects:
  "actor": {
    "type": "Person",
    "id": "http://sally.example.org/",
    "name": "Sally"
  },
  "object": {
    "type": "Arrive",
    "id": "https://sally.example.com/arrive",
    /* ... */
  }
}

// Equivalent to:
{
  "@context":
  "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // URI references:
  "actor": "http://sally.example.org/",
  "object": "https://sally.example.com/arrive"
}

Challenge #2: Discovery & Identity—Finding Your Actors

// Example: Define how to find actors
federation.setActorDispatcher(
  "/users/{username}",
  async (ctx, username) => { /* ... */ }
);
// Now GET /.well-known/webfinger?resource=acct:username@your.domain just works!

Challenge #3: Core ActivityPub Mechanics—Handling Requests and Collections

// Define inbox handlers
federation.setInboxListeners("/inbox", "/users/{handle}/inbox")
  .on(Follow, async (ctx, follow) => { /* Handle follow */ })
  .on(Undo, async (ctx, undo) => { /* Handle undo */ });

// Define followers collection logic
federation.setFollowersDispatcher(
  "/users/{handle}/followers",
  async (ctx, handle, cursor) => { /* ... */ }
);

Challenge #4: Reliable Delivery & Asynchronous Processing—Sending Activities Robustly

// Configure Fedify with a persistent queue (e.g., Deno KV)
const federation = createFederation({
  queue: new DenoKvMessageQueue(/* ... */),
  // ...
});
// Sending is now reliable and non-blocking
await ctx.sendActivity({ handle: "myUser" }, recipient, someActivity);

Challenge #5: Security—Avoiding Common Pitfalls

Challenge #6: Interoperability & Maintenance—Playing Nicely with Others

Challenge #7: Developer Experience—Actually Building Your App

You can quickly scaffold a new project tailored to your chosen runtime and web framework using fedify init.

$ fedify lookup @fedify-example@fedify-blog.deno.dev

Will first show progress messages and then output the structured representation of the actor, similar to this:

// Output of fedify lookup command (shows parsed object structure)
Person {
  id: URL "https://fedify-blog.deno.dev/users/fedify-example",
  name: "Fedify Example Blog",
  published: 2024-03-03T13:18:11.857Z, // Simplified timestamp
  summary: "This blog is powered by Fedify, a fediverse server framework.",
  url: URL "https://fedify-blog.deno.dev/",
  preferredUsername: "fedify-example",
  publicKey: CryptographicKey {
    id: URL "https://fedify-blog.deno.dev/users/fedify-example#main-key",
    owner: URL "https://fedify-blog.deno.dev/users/fedify-example",
    publicKey: CryptoKey { /* ... CryptoKey details ... */ }
  },
  // ... other properties like inbox, outbox, followers, endpoints ...
}

This allows you to easily check how data is structured or troubleshoot why an interaction might be failing by seeing the actual properties Fedify parsed.

$ fedify inbox
✔ The ephemeral ActivityPub server is up and running: https://<unique_id>.lhr.life/
✔ Sent follow request to @<some_test_account>@activitypub.academy.
╭───────────────┬─────────────────────────────────────────╮
│ Actor handle: │ i@<unique_id>.lhr.life                  │
├───────────────┼─────────────────────────────────────────┤
│   Actor URI:  │ https://<unique_id>.lhr.life/i          │
├───────────────┼─────────────────────────────────────────┤
│  Actor inbox: │ https://<unique_id>.lhr.life/i/inbox    │
├───────────────┼─────────────────────────────────────────┤
│ Shared inbox: │ https://<unique_id>.lhr.life/inbox      │
╰───────────────┴─────────────────────────────────────────╯

Web interface available at: http://localhost:8000/

╭────────────────┬─────────────────────────────────────╮
│     Request #: │ 2                                   │
├────────────────┼─────────────────────────────────────┤
│ Activity type: │ Follow                              │
├────────────────┼─────────────────────────────────────┤
│  HTTP request: │ POST /i/inbox                       │
├────────────────┼─────────────────────────────────────┤
│ HTTP response: │ 202                                 │
├────────────────┼─────────────────────────────────────┤
│       Details  │ https://<unique_id>.lhr.life/r/2    │
╰────────────────┴─────────────────────────────────────╯

Conclusion: Build Features, Not Plumbing

Getting started is straightforward. First, install the Fedify CLI using your preferred method. Once installed, create a new project template by running fedify init your-project-name.

Check out the Fedify tutorials and Fedify manual to learn more. Happy federating!

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Don't build #ActivityPub from scratch! It's complex. See why using the #Fedify framework is the smarter way to develop for the fediverse in my new post:

https://hackers.pub/@hongminhee/2025/why-use-fedify

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

Challenge #1: Data Modeling—Speaking ActivityStreams & JSON-LD Fluently

Second, JSON-LD, the encoding layer, has specific rules that make direct JSON manipulation surprisingly tricky:

Missing vs. Empty Array: In JSON-LD, a property being absent is often semantically identical to it being present with an empty array. Your application logic needs to treat these cases equally when checking for values. For example, these two Note objects mean the same thing regarding the name property:
```
// No name property
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "…"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "name": [],
  "content": "…"
}
```
Single Value vs. Array: Similarly, a property holding a single value directly is often equivalent to it holding a single-element array containing that value. Your code must anticipate both representations for the same meaning, like for the content property here:
```
// Single value
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "Hello"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": ["Hello"]
}
```

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // Embedded objects:
  "actor": {
    "type": "Person",
    "id": "http://sally.example.org/",
    "name": "Sally"
  },
  "object": {
    "type": "Arrive",
    "id": "https://sally.example.com/arrive",
    /* ... */
  }
}

// Equivalent to:
{
  "@context":
  "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // URI references:
  "actor": "http://sally.example.org/",
  "object": "https://sally.example.com/arrive"
}

Challenge #2: Discovery & Identity—Finding Your Actors

// Example: Define how to find actors
federation.setActorDispatcher(
  "/users/{username}",
  async (ctx, username) => { /* ... */ }
);
// Now GET /.well-known/webfinger?resource=acct:username@your.domain just works!

Challenge #3: Core ActivityPub Mechanics—Handling Requests and Collections

// Define inbox handlers
federation.setInboxListeners("/inbox", "/users/{handle}/inbox")
  .on(Follow, async (ctx, follow) => { /* Handle follow */ })
  .on(Undo, async (ctx, undo) => { /* Handle undo */ });

// Define followers collection logic
federation.setFollowersDispatcher(
  "/users/{handle}/followers",
  async (ctx, handle, cursor) => { /* ... */ }
);

Challenge #4: Reliable Delivery & Asynchronous Processing—Sending Activities Robustly

// Configure Fedify with a persistent queue (e.g., Deno KV)
const federation = createFederation({
  queue: new DenoKvMessageQueue(/* ... */),
  // ...
});
// Sending is now reliable and non-blocking
await ctx.sendActivity({ handle: "myUser" }, recipient, someActivity);

Challenge #5: Security—Avoiding Common Pitfalls

Challenge #6: Interoperability & Maintenance—Playing Nicely with Others

Challenge #7: Developer Experience—Actually Building Your App

You can quickly scaffold a new project tailored to your chosen runtime and web framework using fedify init.

$ fedify lookup @fedify-example@fedify-blog.deno.dev

Will first show progress messages and then output the structured representation of the actor, similar to this:

// Output of fedify lookup command (shows parsed object structure)
Person {
  id: URL "https://fedify-blog.deno.dev/users/fedify-example",
  name: "Fedify Example Blog",
  published: 2024-03-03T13:18:11.857Z, // Simplified timestamp
  summary: "This blog is powered by Fedify, a fediverse server framework.",
  url: URL "https://fedify-blog.deno.dev/",
  preferredUsername: "fedify-example",
  publicKey: CryptographicKey {
    id: URL "https://fedify-blog.deno.dev/users/fedify-example#main-key",
    owner: URL "https://fedify-blog.deno.dev/users/fedify-example",
    publicKey: CryptoKey { /* ... CryptoKey details ... */ }
  },
  // ... other properties like inbox, outbox, followers, endpoints ...
}

This allows you to easily check how data is structured or troubleshoot why an interaction might be failing by seeing the actual properties Fedify parsed.

$ fedify inbox
✔ The ephemeral ActivityPub server is up and running: https://<unique_id>.lhr.life/
✔ Sent follow request to @<some_test_account>@activitypub.academy.
╭───────────────┬─────────────────────────────────────────╮
│ Actor handle: │ i@<unique_id>.lhr.life                  │
├───────────────┼─────────────────────────────────────────┤
│   Actor URI:  │ https://<unique_id>.lhr.life/i          │
├───────────────┼─────────────────────────────────────────┤
│  Actor inbox: │ https://<unique_id>.lhr.life/i/inbox    │
├───────────────┼─────────────────────────────────────────┤
│ Shared inbox: │ https://<unique_id>.lhr.life/inbox      │
╰───────────────┴─────────────────────────────────────────╯

Web interface available at: http://localhost:8000/

╭────────────────┬─────────────────────────────────────╮
│     Request #: │ 2                                   │
├────────────────┼─────────────────────────────────────┤
│ Activity type: │ Follow                              │
├────────────────┼─────────────────────────────────────┤
│  HTTP request: │ POST /i/inbox                       │
├────────────────┼─────────────────────────────────────┤
│ HTTP response: │ 202                                 │
├────────────────┼─────────────────────────────────────┤
│       Details  │ https://<unique_id>.lhr.life/r/2    │
╰────────────────┴─────────────────────────────────────╯

Conclusion: Build Features, Not Plumbing

Getting started is straightforward. First, install the Fedify CLI using your preferred method. Once installed, create a new project template by running fedify init your-project-name.

Check out the Fedify tutorials and Fedify manual to learn more. Happy federating!

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Don't build #ActivityPub from scratch! It's complex. See why using the #Fedify framework is the smarter way to develop for the fediverse in my new post:

https://hackers.pub/@hongminhee/2025/why-use-fedify

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

Challenge #1: Data Modeling—Speaking ActivityStreams & JSON-LD Fluently

Second, JSON-LD, the encoding layer, has specific rules that make direct JSON manipulation surprisingly tricky:

Missing vs. Empty Array: In JSON-LD, a property being absent is often semantically identical to it being present with an empty array. Your application logic needs to treat these cases equally when checking for values. For example, these two Note objects mean the same thing regarding the name property:
```
// No name property
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "…"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "name": [],
  "content": "…"
}
```
Single Value vs. Array: Similarly, a property holding a single value directly is often equivalent to it holding a single-element array containing that value. Your code must anticipate both representations for the same meaning, like for the content property here:
```
// Single value
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "Hello"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": ["Hello"]
}
```

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // Embedded objects:
  "actor": {
    "type": "Person",
    "id": "http://sally.example.org/",
    "name": "Sally"
  },
  "object": {
    "type": "Arrive",
    "id": "https://sally.example.com/arrive",
    /* ... */
  }
}

// Equivalent to:
{
  "@context":
  "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // URI references:
  "actor": "http://sally.example.org/",
  "object": "https://sally.example.com/arrive"
}

Challenge #2: Discovery & Identity—Finding Your Actors

// Example: Define how to find actors
federation.setActorDispatcher(
  "/users/{username}",
  async (ctx, username) => { /* ... */ }
);
// Now GET /.well-known/webfinger?resource=acct:username@your.domain just works!

Challenge #3: Core ActivityPub Mechanics—Handling Requests and Collections

// Define inbox handlers
federation.setInboxListeners("/inbox", "/users/{handle}/inbox")
  .on(Follow, async (ctx, follow) => { /* Handle follow */ })
  .on(Undo, async (ctx, undo) => { /* Handle undo */ });

// Define followers collection logic
federation.setFollowersDispatcher(
  "/users/{handle}/followers",
  async (ctx, handle, cursor) => { /* ... */ }
);

Challenge #4: Reliable Delivery & Asynchronous Processing—Sending Activities Robustly

// Configure Fedify with a persistent queue (e.g., Deno KV)
const federation = createFederation({
  queue: new DenoKvMessageQueue(/* ... */),
  // ...
});
// Sending is now reliable and non-blocking
await ctx.sendActivity({ handle: "myUser" }, recipient, someActivity);

Challenge #5: Security—Avoiding Common Pitfalls

Challenge #6: Interoperability & Maintenance—Playing Nicely with Others

Challenge #7: Developer Experience—Actually Building Your App

You can quickly scaffold a new project tailored to your chosen runtime and web framework using fedify init.

$ fedify lookup @fedify-example@fedify-blog.deno.dev

Will first show progress messages and then output the structured representation of the actor, similar to this:

// Output of fedify lookup command (shows parsed object structure)
Person {
  id: URL "https://fedify-blog.deno.dev/users/fedify-example",
  name: "Fedify Example Blog",
  published: 2024-03-03T13:18:11.857Z, // Simplified timestamp
  summary: "This blog is powered by Fedify, a fediverse server framework.",
  url: URL "https://fedify-blog.deno.dev/",
  preferredUsername: "fedify-example",
  publicKey: CryptographicKey {
    id: URL "https://fedify-blog.deno.dev/users/fedify-example#main-key",
    owner: URL "https://fedify-blog.deno.dev/users/fedify-example",
    publicKey: CryptoKey { /* ... CryptoKey details ... */ }
  },
  // ... other properties like inbox, outbox, followers, endpoints ...
}

This allows you to easily check how data is structured or troubleshoot why an interaction might be failing by seeing the actual properties Fedify parsed.

$ fedify inbox
✔ The ephemeral ActivityPub server is up and running: https://<unique_id>.lhr.life/
✔ Sent follow request to @<some_test_account>@activitypub.academy.
╭───────────────┬─────────────────────────────────────────╮
│ Actor handle: │ i@<unique_id>.lhr.life                  │
├───────────────┼─────────────────────────────────────────┤
│   Actor URI:  │ https://<unique_id>.lhr.life/i          │
├───────────────┼─────────────────────────────────────────┤
│  Actor inbox: │ https://<unique_id>.lhr.life/i/inbox    │
├───────────────┼─────────────────────────────────────────┤
│ Shared inbox: │ https://<unique_id>.lhr.life/inbox      │
╰───────────────┴─────────────────────────────────────────╯

Web interface available at: http://localhost:8000/

╭────────────────┬─────────────────────────────────────╮
│     Request #: │ 2                                   │
├────────────────┼─────────────────────────────────────┤
│ Activity type: │ Follow                              │
├────────────────┼─────────────────────────────────────┤
│  HTTP request: │ POST /i/inbox                       │
├────────────────┼─────────────────────────────────────┤
│ HTTP response: │ 202                                 │
├────────────────┼─────────────────────────────────────┤
│       Details  │ https://<unique_id>.lhr.life/r/2    │
╰────────────────┴─────────────────────────────────────╯

Conclusion: Build Features, Not Plumbing

Getting started is straightforward. First, install the Fedify CLI using your preferred method. Once installed, create a new project template by running fedify init your-project-name.

Check out the Fedify tutorials and Fedify manual to learn more. Happy federating!

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Don't build #ActivityPub from scratch! It's complex. See why using the #Fedify framework is the smarter way to develop for the fediverse in my new post:

https://hackers.pub/@hongminhee/2025/why-use-fedify

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

Challenge #1: Data Modeling—Speaking ActivityStreams & JSON-LD Fluently

Second, JSON-LD, the encoding layer, has specific rules that make direct JSON manipulation surprisingly tricky:

Missing vs. Empty Array: In JSON-LD, a property being absent is often semantically identical to it being present with an empty array. Your application logic needs to treat these cases equally when checking for values. For example, these two Note objects mean the same thing regarding the name property:
```
// No name property
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "…"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "name": [],
  "content": "…"
}
```
Single Value vs. Array: Similarly, a property holding a single value directly is often equivalent to it holding a single-element array containing that value. Your code must anticipate both representations for the same meaning, like for the content property here:
```
// Single value
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "Hello"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": ["Hello"]
}
```

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // Embedded objects:
  "actor": {
    "type": "Person",
    "id": "http://sally.example.org/",
    "name": "Sally"
  },
  "object": {
    "type": "Arrive",
    "id": "https://sally.example.com/arrive",
    /* ... */
  }
}

// Equivalent to:
{
  "@context":
  "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // URI references:
  "actor": "http://sally.example.org/",
  "object": "https://sally.example.com/arrive"
}

Challenge #2: Discovery & Identity—Finding Your Actors

// Example: Define how to find actors
federation.setActorDispatcher(
  "/users/{username}",
  async (ctx, username) => { /* ... */ }
);
// Now GET /.well-known/webfinger?resource=acct:username@your.domain just works!

Challenge #3: Core ActivityPub Mechanics—Handling Requests and Collections

// Define inbox handlers
federation.setInboxListeners("/inbox", "/users/{handle}/inbox")
  .on(Follow, async (ctx, follow) => { /* Handle follow */ })
  .on(Undo, async (ctx, undo) => { /* Handle undo */ });

// Define followers collection logic
federation.setFollowersDispatcher(
  "/users/{handle}/followers",
  async (ctx, handle, cursor) => { /* ... */ }
);

Challenge #4: Reliable Delivery & Asynchronous Processing—Sending Activities Robustly

// Configure Fedify with a persistent queue (e.g., Deno KV)
const federation = createFederation({
  queue: new DenoKvMessageQueue(/* ... */),
  // ...
});
// Sending is now reliable and non-blocking
await ctx.sendActivity({ handle: "myUser" }, recipient, someActivity);

Challenge #5: Security—Avoiding Common Pitfalls

Challenge #6: Interoperability & Maintenance—Playing Nicely with Others

Challenge #7: Developer Experience—Actually Building Your App

You can quickly scaffold a new project tailored to your chosen runtime and web framework using fedify init.

$ fedify lookup @fedify-example@fedify-blog.deno.dev

Will first show progress messages and then output the structured representation of the actor, similar to this:

// Output of fedify lookup command (shows parsed object structure)
Person {
  id: URL "https://fedify-blog.deno.dev/users/fedify-example",
  name: "Fedify Example Blog",
  published: 2024-03-03T13:18:11.857Z, // Simplified timestamp
  summary: "This blog is powered by Fedify, a fediverse server framework.",
  url: URL "https://fedify-blog.deno.dev/",
  preferredUsername: "fedify-example",
  publicKey: CryptographicKey {
    id: URL "https://fedify-blog.deno.dev/users/fedify-example#main-key",
    owner: URL "https://fedify-blog.deno.dev/users/fedify-example",
    publicKey: CryptoKey { /* ... CryptoKey details ... */ }
  },
  // ... other properties like inbox, outbox, followers, endpoints ...
}

This allows you to easily check how data is structured or troubleshoot why an interaction might be failing by seeing the actual properties Fedify parsed.

$ fedify inbox
✔ The ephemeral ActivityPub server is up and running: https://<unique_id>.lhr.life/
✔ Sent follow request to @<some_test_account>@activitypub.academy.
╭───────────────┬─────────────────────────────────────────╮
│ Actor handle: │ i@<unique_id>.lhr.life                  │
├───────────────┼─────────────────────────────────────────┤
│   Actor URI:  │ https://<unique_id>.lhr.life/i          │
├───────────────┼─────────────────────────────────────────┤
│  Actor inbox: │ https://<unique_id>.lhr.life/i/inbox    │
├───────────────┼─────────────────────────────────────────┤
│ Shared inbox: │ https://<unique_id>.lhr.life/inbox      │
╰───────────────┴─────────────────────────────────────────╯

Web interface available at: http://localhost:8000/

╭────────────────┬─────────────────────────────────────╮
│     Request #: │ 2                                   │
├────────────────┼─────────────────────────────────────┤
│ Activity type: │ Follow                              │
├────────────────┼─────────────────────────────────────┤
│  HTTP request: │ POST /i/inbox                       │
├────────────────┼─────────────────────────────────────┤
│ HTTP response: │ 202                                 │
├────────────────┼─────────────────────────────────────┤
│       Details  │ https://<unique_id>.lhr.life/r/2    │
╰────────────────┴─────────────────────────────────────╯

Conclusion: Build Features, Not Plumbing

Getting started is straightforward. First, install the Fedify CLI using your preferred method. Once installed, create a new project template by running fedify init your-project-name.

Check out the Fedify tutorials and Fedify manual to learn more. Happy federating!

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Don't build #ActivityPub from scratch! It's complex. See why using the #Fedify framework is the smarter way to develop for the fediverse in my new post:

https://hackers.pub/@hongminhee/2025/why-use-fedify

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

Challenge #1: Data Modeling—Speaking ActivityStreams & JSON-LD Fluently

Second, JSON-LD, the encoding layer, has specific rules that make direct JSON manipulation surprisingly tricky:

Missing vs. Empty Array: In JSON-LD, a property being absent is often semantically identical to it being present with an empty array. Your application logic needs to treat these cases equally when checking for values. For example, these two Note objects mean the same thing regarding the name property:
```
// No name property
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "…"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "name": [],
  "content": "…"
}
```
Single Value vs. Array: Similarly, a property holding a single value directly is often equivalent to it holding a single-element array containing that value. Your code must anticipate both representations for the same meaning, like for the content property here:
```
// Single value
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "Hello"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": ["Hello"]
}
```

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // Embedded objects:
  "actor": {
    "type": "Person",
    "id": "http://sally.example.org/",
    "name": "Sally"
  },
  "object": {
    "type": "Arrive",
    "id": "https://sally.example.com/arrive",
    /* ... */
  }
}

// Equivalent to:
{
  "@context":
  "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // URI references:
  "actor": "http://sally.example.org/",
  "object": "https://sally.example.com/arrive"
}

Challenge #2: Discovery & Identity—Finding Your Actors

// Example: Define how to find actors
federation.setActorDispatcher(
  "/users/{username}",
  async (ctx, username) => { /* ... */ }
);
// Now GET /.well-known/webfinger?resource=acct:username@your.domain just works!

Challenge #3: Core ActivityPub Mechanics—Handling Requests and Collections

// Define inbox handlers
federation.setInboxListeners("/inbox", "/users/{handle}/inbox")
  .on(Follow, async (ctx, follow) => { /* Handle follow */ })
  .on(Undo, async (ctx, undo) => { /* Handle undo */ });

// Define followers collection logic
federation.setFollowersDispatcher(
  "/users/{handle}/followers",
  async (ctx, handle, cursor) => { /* ... */ }
);

Challenge #4: Reliable Delivery & Asynchronous Processing—Sending Activities Robustly

// Configure Fedify with a persistent queue (e.g., Deno KV)
const federation = createFederation({
  queue: new DenoKvMessageQueue(/* ... */),
  // ...
});
// Sending is now reliable and non-blocking
await ctx.sendActivity({ handle: "myUser" }, recipient, someActivity);

Challenge #5: Security—Avoiding Common Pitfalls

Challenge #6: Interoperability & Maintenance—Playing Nicely with Others

Challenge #7: Developer Experience—Actually Building Your App

You can quickly scaffold a new project tailored to your chosen runtime and web framework using fedify init.

$ fedify lookup @fedify-example@fedify-blog.deno.dev

Will first show progress messages and then output the structured representation of the actor, similar to this:

// Output of fedify lookup command (shows parsed object structure)
Person {
  id: URL "https://fedify-blog.deno.dev/users/fedify-example",
  name: "Fedify Example Blog",
  published: 2024-03-03T13:18:11.857Z, // Simplified timestamp
  summary: "This blog is powered by Fedify, a fediverse server framework.",
  url: URL "https://fedify-blog.deno.dev/",
  preferredUsername: "fedify-example",
  publicKey: CryptographicKey {
    id: URL "https://fedify-blog.deno.dev/users/fedify-example#main-key",
    owner: URL "https://fedify-blog.deno.dev/users/fedify-example",
    publicKey: CryptoKey { /* ... CryptoKey details ... */ }
  },
  // ... other properties like inbox, outbox, followers, endpoints ...
}

This allows you to easily check how data is structured or troubleshoot why an interaction might be failing by seeing the actual properties Fedify parsed.

$ fedify inbox
✔ The ephemeral ActivityPub server is up and running: https://<unique_id>.lhr.life/
✔ Sent follow request to @<some_test_account>@activitypub.academy.
╭───────────────┬─────────────────────────────────────────╮
│ Actor handle: │ i@<unique_id>.lhr.life                  │
├───────────────┼─────────────────────────────────────────┤
│   Actor URI:  │ https://<unique_id>.lhr.life/i          │
├───────────────┼─────────────────────────────────────────┤
│  Actor inbox: │ https://<unique_id>.lhr.life/i/inbox    │
├───────────────┼─────────────────────────────────────────┤
│ Shared inbox: │ https://<unique_id>.lhr.life/inbox      │
╰───────────────┴─────────────────────────────────────────╯

Web interface available at: http://localhost:8000/

╭────────────────┬─────────────────────────────────────╮
│     Request #: │ 2                                   │
├────────────────┼─────────────────────────────────────┤
│ Activity type: │ Follow                              │
├────────────────┼─────────────────────────────────────┤
│  HTTP request: │ POST /i/inbox                       │
├────────────────┼─────────────────────────────────────┤
│ HTTP response: │ 202                                 │
├────────────────┼─────────────────────────────────────┤
│       Details  │ https://<unique_id>.lhr.life/r/2    │
╰────────────────┴─────────────────────────────────────╯

Conclusion: Build Features, Not Plumbing

Getting started is straightforward. First, install the Fedify CLI using your preferred method. Once installed, create a new project template by running fedify init your-project-name.

Check out the Fedify tutorials and Fedify manual to learn more. Happy federating!

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Don't build #ActivityPub from scratch! It's complex. See why using the #Fedify framework is the smarter way to develop for the fediverse in my new post:

https://hackers.pub/@hongminhee/2025/why-use-fedify

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

Challenge #1: Data Modeling—Speaking ActivityStreams & JSON-LD Fluently

Second, JSON-LD, the encoding layer, has specific rules that make direct JSON manipulation surprisingly tricky:

Missing vs. Empty Array: In JSON-LD, a property being absent is often semantically identical to it being present with an empty array. Your application logic needs to treat these cases equally when checking for values. For example, these two Note objects mean the same thing regarding the name property:
```
// No name property
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "…"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "name": [],
  "content": "…"
}
```
Single Value vs. Array: Similarly, a property holding a single value directly is often equivalent to it holding a single-element array containing that value. Your code must anticipate both representations for the same meaning, like for the content property here:
```
// Single value
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "Hello"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": ["Hello"]
}
```

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // Embedded objects:
  "actor": {
    "type": "Person",
    "id": "http://sally.example.org/",
    "name": "Sally"
  },
  "object": {
    "type": "Arrive",
    "id": "https://sally.example.com/arrive",
    /* ... */
  }
}

// Equivalent to:
{
  "@context":
  "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // URI references:
  "actor": "http://sally.example.org/",
  "object": "https://sally.example.com/arrive"
}

Challenge #2: Discovery & Identity—Finding Your Actors

// Example: Define how to find actors
federation.setActorDispatcher(
  "/users/{username}",
  async (ctx, username) => { /* ... */ }
);
// Now GET /.well-known/webfinger?resource=acct:username@your.domain just works!

Challenge #3: Core ActivityPub Mechanics—Handling Requests and Collections

// Define inbox handlers
federation.setInboxListeners("/inbox", "/users/{handle}/inbox")
  .on(Follow, async (ctx, follow) => { /* Handle follow */ })
  .on(Undo, async (ctx, undo) => { /* Handle undo */ });

// Define followers collection logic
federation.setFollowersDispatcher(
  "/users/{handle}/followers",
  async (ctx, handle, cursor) => { /* ... */ }
);

Challenge #4: Reliable Delivery & Asynchronous Processing—Sending Activities Robustly

// Configure Fedify with a persistent queue (e.g., Deno KV)
const federation = createFederation({
  queue: new DenoKvMessageQueue(/* ... */),
  // ...
});
// Sending is now reliable and non-blocking
await ctx.sendActivity({ handle: "myUser" }, recipient, someActivity);

Challenge #5: Security—Avoiding Common Pitfalls

Challenge #6: Interoperability & Maintenance—Playing Nicely with Others

Challenge #7: Developer Experience—Actually Building Your App

You can quickly scaffold a new project tailored to your chosen runtime and web framework using fedify init.

$ fedify lookup @fedify-example@fedify-blog.deno.dev

Will first show progress messages and then output the structured representation of the actor, similar to this:

// Output of fedify lookup command (shows parsed object structure)
Person {
  id: URL "https://fedify-blog.deno.dev/users/fedify-example",
  name: "Fedify Example Blog",
  published: 2024-03-03T13:18:11.857Z, // Simplified timestamp
  summary: "This blog is powered by Fedify, a fediverse server framework.",
  url: URL "https://fedify-blog.deno.dev/",
  preferredUsername: "fedify-example",
  publicKey: CryptographicKey {
    id: URL "https://fedify-blog.deno.dev/users/fedify-example#main-key",
    owner: URL "https://fedify-blog.deno.dev/users/fedify-example",
    publicKey: CryptoKey { /* ... CryptoKey details ... */ }
  },
  // ... other properties like inbox, outbox, followers, endpoints ...
}

This allows you to easily check how data is structured or troubleshoot why an interaction might be failing by seeing the actual properties Fedify parsed.

$ fedify inbox
✔ The ephemeral ActivityPub server is up and running: https://<unique_id>.lhr.life/
✔ Sent follow request to @<some_test_account>@activitypub.academy.
╭───────────────┬─────────────────────────────────────────╮
│ Actor handle: │ i@<unique_id>.lhr.life                  │
├───────────────┼─────────────────────────────────────────┤
│   Actor URI:  │ https://<unique_id>.lhr.life/i          │
├───────────────┼─────────────────────────────────────────┤
│  Actor inbox: │ https://<unique_id>.lhr.life/i/inbox    │
├───────────────┼─────────────────────────────────────────┤
│ Shared inbox: │ https://<unique_id>.lhr.life/inbox      │
╰───────────────┴─────────────────────────────────────────╯

Web interface available at: http://localhost:8000/

╭────────────────┬─────────────────────────────────────╮
│     Request #: │ 2                                   │
├────────────────┼─────────────────────────────────────┤
│ Activity type: │ Follow                              │
├────────────────┼─────────────────────────────────────┤
│  HTTP request: │ POST /i/inbox                       │
├────────────────┼─────────────────────────────────────┤
│ HTTP response: │ 202                                 │
├────────────────┼─────────────────────────────────────┤
│       Details  │ https://<unique_id>.lhr.life/r/2    │
╰────────────────┴─────────────────────────────────────╯

Conclusion: Build Features, Not Plumbing

Getting started is straightforward. First, install the Fedify CLI using your preferred method. Once installed, create a new project template by running fedify init your-project-name.

Check out the Fedify tutorials and Fedify manual to learn more. Happy federating!

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

Challenge #1: Data Modeling—Speaking ActivityStreams & JSON-LD Fluently

Second, JSON-LD, the encoding layer, has specific rules that make direct JSON manipulation surprisingly tricky:

Missing vs. Empty Array: In JSON-LD, a property being absent is often semantically identical to it being present with an empty array. Your application logic needs to treat these cases equally when checking for values. For example, these two Note objects mean the same thing regarding the name property:
```
// No name property
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "…"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "name": [],
  "content": "…"
}
```
Single Value vs. Array: Similarly, a property holding a single value directly is often equivalent to it holding a single-element array containing that value. Your code must anticipate both representations for the same meaning, like for the content property here:
```
// Single value
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "Hello"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": ["Hello"]
}
```

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // Embedded objects:
  "actor": {
    "type": "Person",
    "id": "http://sally.example.org/",
    "name": "Sally"
  },
  "object": {
    "type": "Arrive",
    "id": "https://sally.example.com/arrive",
    /* ... */
  }
}

// Equivalent to:
{
  "@context":
  "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // URI references:
  "actor": "http://sally.example.org/",
  "object": "https://sally.example.com/arrive"
}

Challenge #2: Discovery & Identity—Finding Your Actors

// Example: Define how to find actors
federation.setActorDispatcher(
  "/users/{username}",
  async (ctx, username) => { /* ... */ }
);
// Now GET /.well-known/webfinger?resource=acct:username@your.domain just works!

Challenge #3: Core ActivityPub Mechanics—Handling Requests and Collections

// Define inbox handlers
federation.setInboxListeners("/inbox", "/users/{handle}/inbox")
  .on(Follow, async (ctx, follow) => { /* Handle follow */ })
  .on(Undo, async (ctx, undo) => { /* Handle undo */ });

// Define followers collection logic
federation.setFollowersDispatcher(
  "/users/{handle}/followers",
  async (ctx, handle, cursor) => { /* ... */ }
);

Challenge #4: Reliable Delivery & Asynchronous Processing—Sending Activities Robustly

// Configure Fedify with a persistent queue (e.g., Deno KV)
const federation = createFederation({
  queue: new DenoKvMessageQueue(/* ... */),
  // ...
});
// Sending is now reliable and non-blocking
await ctx.sendActivity({ handle: "myUser" }, recipient, someActivity);

Challenge #5: Security—Avoiding Common Pitfalls

Challenge #6: Interoperability & Maintenance—Playing Nicely with Others

Challenge #7: Developer Experience—Actually Building Your App

You can quickly scaffold a new project tailored to your chosen runtime and web framework using fedify init.

$ fedify lookup @fedify-example@fedify-blog.deno.dev

Will first show progress messages and then output the structured representation of the actor, similar to this:

// Output of fedify lookup command (shows parsed object structure)
Person {
  id: URL "https://fedify-blog.deno.dev/users/fedify-example",
  name: "Fedify Example Blog",
  published: 2024-03-03T13:18:11.857Z, // Simplified timestamp
  summary: "This blog is powered by Fedify, a fediverse server framework.",
  url: URL "https://fedify-blog.deno.dev/",
  preferredUsername: "fedify-example",
  publicKey: CryptographicKey {
    id: URL "https://fedify-blog.deno.dev/users/fedify-example#main-key",
    owner: URL "https://fedify-blog.deno.dev/users/fedify-example",
    publicKey: CryptoKey { /* ... CryptoKey details ... */ }
  },
  // ... other properties like inbox, outbox, followers, endpoints ...
}

This allows you to easily check how data is structured or troubleshoot why an interaction might be failing by seeing the actual properties Fedify parsed.

$ fedify inbox
✔ The ephemeral ActivityPub server is up and running: https://<unique_id>.lhr.life/
✔ Sent follow request to @<some_test_account>@activitypub.academy.
╭───────────────┬─────────────────────────────────────────╮
│ Actor handle: │ i@<unique_id>.lhr.life                  │
├───────────────┼─────────────────────────────────────────┤
│   Actor URI:  │ https://<unique_id>.lhr.life/i          │
├───────────────┼─────────────────────────────────────────┤
│  Actor inbox: │ https://<unique_id>.lhr.life/i/inbox    │
├───────────────┼─────────────────────────────────────────┤
│ Shared inbox: │ https://<unique_id>.lhr.life/inbox      │
╰───────────────┴─────────────────────────────────────────╯

Web interface available at: http://localhost:8000/

╭────────────────┬─────────────────────────────────────╮
│     Request #: │ 2                                   │
├────────────────┼─────────────────────────────────────┤
│ Activity type: │ Follow                              │
├────────────────┼─────────────────────────────────────┤
│  HTTP request: │ POST /i/inbox                       │
├────────────────┼─────────────────────────────────────┤
│ HTTP response: │ 202                                 │
├────────────────┼─────────────────────────────────────┤
│       Details  │ https://<unique_id>.lhr.life/r/2    │
╰────────────────┴─────────────────────────────────────╯

Conclusion: Build Features, Not Plumbing

Getting started is straightforward. First, install the Fedify CLI using your preferred method. Once installed, create a new project template by running fedify init your-project-name.

Check out the Fedify tutorials and Fedify manual to learn more. Happy federating!

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Don't build #ActivityPub from scratch! It's complex. See why using the #Fedify framework is the smarter way to develop for the fediverse in my new post:

https://hackers.pub/@hongminhee/2025/why-use-fedify

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

Challenge #1: Data Modeling—Speaking ActivityStreams & JSON-LD Fluently

Second, JSON-LD, the encoding layer, has specific rules that make direct JSON manipulation surprisingly tricky:

Missing vs. Empty Array: In JSON-LD, a property being absent is often semantically identical to it being present with an empty array. Your application logic needs to treat these cases equally when checking for values. For example, these two Note objects mean the same thing regarding the name property:
```
// No name property
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "…"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "name": [],
  "content": "…"
}
```
Single Value vs. Array: Similarly, a property holding a single value directly is often equivalent to it holding a single-element array containing that value. Your code must anticipate both representations for the same meaning, like for the content property here:
```
// Single value
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "Hello"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": ["Hello"]
}
```

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // Embedded objects:
  "actor": {
    "type": "Person",
    "id": "http://sally.example.org/",
    "name": "Sally"
  },
  "object": {
    "type": "Arrive",
    "id": "https://sally.example.com/arrive",
    /* ... */
  }
}

// Equivalent to:
{
  "@context":
  "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // URI references:
  "actor": "http://sally.example.org/",
  "object": "https://sally.example.com/arrive"
}

Challenge #2: Discovery & Identity—Finding Your Actors

// Example: Define how to find actors
federation.setActorDispatcher(
  "/users/{username}",
  async (ctx, username) => { /* ... */ }
);
// Now GET /.well-known/webfinger?resource=acct:username@your.domain just works!

Challenge #3: Core ActivityPub Mechanics—Handling Requests and Collections

// Define inbox handlers
federation.setInboxListeners("/inbox", "/users/{handle}/inbox")
  .on(Follow, async (ctx, follow) => { /* Handle follow */ })
  .on(Undo, async (ctx, undo) => { /* Handle undo */ });

// Define followers collection logic
federation.setFollowersDispatcher(
  "/users/{handle}/followers",
  async (ctx, handle, cursor) => { /* ... */ }
);

Challenge #4: Reliable Delivery & Asynchronous Processing—Sending Activities Robustly

// Configure Fedify with a persistent queue (e.g., Deno KV)
const federation = createFederation({
  queue: new DenoKvMessageQueue(/* ... */),
  // ...
});
// Sending is now reliable and non-blocking
await ctx.sendActivity({ handle: "myUser" }, recipient, someActivity);

Challenge #5: Security—Avoiding Common Pitfalls

Challenge #6: Interoperability & Maintenance—Playing Nicely with Others

Challenge #7: Developer Experience—Actually Building Your App

You can quickly scaffold a new project tailored to your chosen runtime and web framework using fedify init.

$ fedify lookup @fedify-example@fedify-blog.deno.dev

Will first show progress messages and then output the structured representation of the actor, similar to this:

// Output of fedify lookup command (shows parsed object structure)
Person {
  id: URL "https://fedify-blog.deno.dev/users/fedify-example",
  name: "Fedify Example Blog",
  published: 2024-03-03T13:18:11.857Z, // Simplified timestamp
  summary: "This blog is powered by Fedify, a fediverse server framework.",
  url: URL "https://fedify-blog.deno.dev/",
  preferredUsername: "fedify-example",
  publicKey: CryptographicKey {
    id: URL "https://fedify-blog.deno.dev/users/fedify-example#main-key",
    owner: URL "https://fedify-blog.deno.dev/users/fedify-example",
    publicKey: CryptoKey { /* ... CryptoKey details ... */ }
  },
  // ... other properties like inbox, outbox, followers, endpoints ...
}

This allows you to easily check how data is structured or troubleshoot why an interaction might be failing by seeing the actual properties Fedify parsed.

$ fedify inbox
✔ The ephemeral ActivityPub server is up and running: https://<unique_id>.lhr.life/
✔ Sent follow request to @<some_test_account>@activitypub.academy.
╭───────────────┬─────────────────────────────────────────╮
│ Actor handle: │ i@<unique_id>.lhr.life                  │
├───────────────┼─────────────────────────────────────────┤
│   Actor URI:  │ https://<unique_id>.lhr.life/i          │
├───────────────┼─────────────────────────────────────────┤
│  Actor inbox: │ https://<unique_id>.lhr.life/i/inbox    │
├───────────────┼─────────────────────────────────────────┤
│ Shared inbox: │ https://<unique_id>.lhr.life/inbox      │
╰───────────────┴─────────────────────────────────────────╯

Web interface available at: http://localhost:8000/

╭────────────────┬─────────────────────────────────────╮
│     Request #: │ 2                                   │
├────────────────┼─────────────────────────────────────┤
│ Activity type: │ Follow                              │
├────────────────┼─────────────────────────────────────┤
│  HTTP request: │ POST /i/inbox                       │
├────────────────┼─────────────────────────────────────┤
│ HTTP response: │ 202                                 │
├────────────────┼─────────────────────────────────────┤
│       Details  │ https://<unique_id>.lhr.life/r/2    │
╰────────────────┴─────────────────────────────────────╯

Conclusion: Build Features, Not Plumbing

Getting started is straightforward. First, install the Fedify CLI using your preferred method. Once installed, create a new project template by running fedify init your-project-name.

Check out the Fedify tutorials and Fedify manual to learn more. Happy federating!

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Don't build #ActivityPub from scratch! It's complex. See why using the #Fedify framework is the smarter way to develop for the fediverse in my new post:

https://hackers.pub/@hongminhee/2025/why-use-fedify

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

Challenge #1: Data Modeling—Speaking ActivityStreams & JSON-LD Fluently

Second, JSON-LD, the encoding layer, has specific rules that make direct JSON manipulation surprisingly tricky:

Missing vs. Empty Array: In JSON-LD, a property being absent is often semantically identical to it being present with an empty array. Your application logic needs to treat these cases equally when checking for values. For example, these two Note objects mean the same thing regarding the name property:
```
// No name property
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "…"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "name": [],
  "content": "…"
}
```
Single Value vs. Array: Similarly, a property holding a single value directly is often equivalent to it holding a single-element array containing that value. Your code must anticipate both representations for the same meaning, like for the content property here:
```
// Single value
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "Hello"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": ["Hello"]
}
```

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // Embedded objects:
  "actor": {
    "type": "Person",
    "id": "http://sally.example.org/",
    "name": "Sally"
  },
  "object": {
    "type": "Arrive",
    "id": "https://sally.example.com/arrive",
    /* ... */
  }
}

// Equivalent to:
{
  "@context":
  "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // URI references:
  "actor": "http://sally.example.org/",
  "object": "https://sally.example.com/arrive"
}

Challenge #2: Discovery & Identity—Finding Your Actors

// Example: Define how to find actors
federation.setActorDispatcher(
  "/users/{username}",
  async (ctx, username) => { /* ... */ }
);
// Now GET /.well-known/webfinger?resource=acct:username@your.domain just works!

Challenge #3: Core ActivityPub Mechanics—Handling Requests and Collections

// Define inbox handlers
federation.setInboxListeners("/inbox", "/users/{handle}/inbox")
  .on(Follow, async (ctx, follow) => { /* Handle follow */ })
  .on(Undo, async (ctx, undo) => { /* Handle undo */ });

// Define followers collection logic
federation.setFollowersDispatcher(
  "/users/{handle}/followers",
  async (ctx, handle, cursor) => { /* ... */ }
);

Challenge #4: Reliable Delivery & Asynchronous Processing—Sending Activities Robustly

// Configure Fedify with a persistent queue (e.g., Deno KV)
const federation = createFederation({
  queue: new DenoKvMessageQueue(/* ... */),
  // ...
});
// Sending is now reliable and non-blocking
await ctx.sendActivity({ handle: "myUser" }, recipient, someActivity);

Challenge #5: Security—Avoiding Common Pitfalls

Challenge #6: Interoperability & Maintenance—Playing Nicely with Others

Challenge #7: Developer Experience—Actually Building Your App

You can quickly scaffold a new project tailored to your chosen runtime and web framework using fedify init.

$ fedify lookup @fedify-example@fedify-blog.deno.dev

Will first show progress messages and then output the structured representation of the actor, similar to this:

// Output of fedify lookup command (shows parsed object structure)
Person {
  id: URL "https://fedify-blog.deno.dev/users/fedify-example",
  name: "Fedify Example Blog",
  published: 2024-03-03T13:18:11.857Z, // Simplified timestamp
  summary: "This blog is powered by Fedify, a fediverse server framework.",
  url: URL "https://fedify-blog.deno.dev/",
  preferredUsername: "fedify-example",
  publicKey: CryptographicKey {
    id: URL "https://fedify-blog.deno.dev/users/fedify-example#main-key",
    owner: URL "https://fedify-blog.deno.dev/users/fedify-example",
    publicKey: CryptoKey { /* ... CryptoKey details ... */ }
  },
  // ... other properties like inbox, outbox, followers, endpoints ...
}

This allows you to easily check how data is structured or troubleshoot why an interaction might be failing by seeing the actual properties Fedify parsed.

$ fedify inbox
✔ The ephemeral ActivityPub server is up and running: https://<unique_id>.lhr.life/
✔ Sent follow request to @<some_test_account>@activitypub.academy.
╭───────────────┬─────────────────────────────────────────╮
│ Actor handle: │ i@<unique_id>.lhr.life                  │
├───────────────┼─────────────────────────────────────────┤
│   Actor URI:  │ https://<unique_id>.lhr.life/i          │
├───────────────┼─────────────────────────────────────────┤
│  Actor inbox: │ https://<unique_id>.lhr.life/i/inbox    │
├───────────────┼─────────────────────────────────────────┤
│ Shared inbox: │ https://<unique_id>.lhr.life/inbox      │
╰───────────────┴─────────────────────────────────────────╯

Web interface available at: http://localhost:8000/

╭────────────────┬─────────────────────────────────────╮
│     Request #: │ 2                                   │
├────────────────┼─────────────────────────────────────┤
│ Activity type: │ Follow                              │
├────────────────┼─────────────────────────────────────┤
│  HTTP request: │ POST /i/inbox                       │
├────────────────┼─────────────────────────────────────┤
│ HTTP response: │ 202                                 │
├────────────────┼─────────────────────────────────────┤
│       Details  │ https://<unique_id>.lhr.life/r/2    │
╰────────────────┴─────────────────────────────────────╯

Conclusion: Build Features, Not Plumbing

Getting started is straightforward. First, install the Fedify CLI using your preferred method. Once installed, create a new project template by running fedify init your-project-name.

Check out the Fedify tutorials and Fedify manual to learn more. Happy federating!

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Don't build #ActivityPub from scratch! It's complex. See why using the #Fedify framework is the smarter way to develop for the fediverse in my new post:

https://hackers.pub/@hongminhee/2025/why-use-fedify

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

Challenge #1: Data Modeling—Speaking ActivityStreams & JSON-LD Fluently

Second, JSON-LD, the encoding layer, has specific rules that make direct JSON manipulation surprisingly tricky:

Missing vs. Empty Array: In JSON-LD, a property being absent is often semantically identical to it being present with an empty array. Your application logic needs to treat these cases equally when checking for values. For example, these two Note objects mean the same thing regarding the name property:
```
// No name property
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "…"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "name": [],
  "content": "…"
}
```
Single Value vs. Array: Similarly, a property holding a single value directly is often equivalent to it holding a single-element array containing that value. Your code must anticipate both representations for the same meaning, like for the content property here:
```
// Single value
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "Hello"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": ["Hello"]
}
```

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // Embedded objects:
  "actor": {
    "type": "Person",
    "id": "http://sally.example.org/",
    "name": "Sally"
  },
  "object": {
    "type": "Arrive",
    "id": "https://sally.example.com/arrive",
    /* ... */
  }
}

// Equivalent to:
{
  "@context":
  "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // URI references:
  "actor": "http://sally.example.org/",
  "object": "https://sally.example.com/arrive"
}

Challenge #2: Discovery & Identity—Finding Your Actors

// Example: Define how to find actors
federation.setActorDispatcher(
  "/users/{username}",
  async (ctx, username) => { /* ... */ }
);
// Now GET /.well-known/webfinger?resource=acct:username@your.domain just works!

Challenge #3: Core ActivityPub Mechanics—Handling Requests and Collections

// Define inbox handlers
federation.setInboxListeners("/inbox", "/users/{handle}/inbox")
  .on(Follow, async (ctx, follow) => { /* Handle follow */ })
  .on(Undo, async (ctx, undo) => { /* Handle undo */ });

// Define followers collection logic
federation.setFollowersDispatcher(
  "/users/{handle}/followers",
  async (ctx, handle, cursor) => { /* ... */ }
);

Challenge #4: Reliable Delivery & Asynchronous Processing—Sending Activities Robustly

// Configure Fedify with a persistent queue (e.g., Deno KV)
const federation = createFederation({
  queue: new DenoKvMessageQueue(/* ... */),
  // ...
});
// Sending is now reliable and non-blocking
await ctx.sendActivity({ handle: "myUser" }, recipient, someActivity);

Challenge #5: Security—Avoiding Common Pitfalls

Challenge #6: Interoperability & Maintenance—Playing Nicely with Others

Challenge #7: Developer Experience—Actually Building Your App

You can quickly scaffold a new project tailored to your chosen runtime and web framework using fedify init.

$ fedify lookup @fedify-example@fedify-blog.deno.dev

Will first show progress messages and then output the structured representation of the actor, similar to this:

// Output of fedify lookup command (shows parsed object structure)
Person {
  id: URL "https://fedify-blog.deno.dev/users/fedify-example",
  name: "Fedify Example Blog",
  published: 2024-03-03T13:18:11.857Z, // Simplified timestamp
  summary: "This blog is powered by Fedify, a fediverse server framework.",
  url: URL "https://fedify-blog.deno.dev/",
  preferredUsername: "fedify-example",
  publicKey: CryptographicKey {
    id: URL "https://fedify-blog.deno.dev/users/fedify-example#main-key",
    owner: URL "https://fedify-blog.deno.dev/users/fedify-example",
    publicKey: CryptoKey { /* ... CryptoKey details ... */ }
  },
  // ... other properties like inbox, outbox, followers, endpoints ...
}

This allows you to easily check how data is structured or troubleshoot why an interaction might be failing by seeing the actual properties Fedify parsed.

$ fedify inbox
✔ The ephemeral ActivityPub server is up and running: https://<unique_id>.lhr.life/
✔ Sent follow request to @<some_test_account>@activitypub.academy.
╭───────────────┬─────────────────────────────────────────╮
│ Actor handle: │ i@<unique_id>.lhr.life                  │
├───────────────┼─────────────────────────────────────────┤
│   Actor URI:  │ https://<unique_id>.lhr.life/i          │
├───────────────┼─────────────────────────────────────────┤
│  Actor inbox: │ https://<unique_id>.lhr.life/i/inbox    │
├───────────────┼─────────────────────────────────────────┤
│ Shared inbox: │ https://<unique_id>.lhr.life/inbox      │
╰───────────────┴─────────────────────────────────────────╯

Web interface available at: http://localhost:8000/

╭────────────────┬─────────────────────────────────────╮
│     Request #: │ 2                                   │
├────────────────┼─────────────────────────────────────┤
│ Activity type: │ Follow                              │
├────────────────┼─────────────────────────────────────┤
│  HTTP request: │ POST /i/inbox                       │
├────────────────┼─────────────────────────────────────┤
│ HTTP response: │ 202                                 │
├────────────────┼─────────────────────────────────────┤
│       Details  │ https://<unique_id>.lhr.life/r/2    │
╰────────────────┴─────────────────────────────────────╯

Conclusion: Build Features, Not Plumbing

Getting started is straightforward. First, install the Fedify CLI using your preferred method. Once installed, create a new project template by running fedify init your-project-name.

Check out the Fedify tutorials and Fedify manual to learn more. Happy federating!

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Don't build #ActivityPub from scratch! It's complex. See why using the #Fedify framework is the smarter way to develop for the fediverse in my new post:

https://hackers.pub/@hongminhee/2025/why-use-fedify

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

Challenge #1: Data Modeling—Speaking ActivityStreams & JSON-LD Fluently

Second, JSON-LD, the encoding layer, has specific rules that make direct JSON manipulation surprisingly tricky:

Missing vs. Empty Array: In JSON-LD, a property being absent is often semantically identical to it being present with an empty array. Your application logic needs to treat these cases equally when checking for values. For example, these two Note objects mean the same thing regarding the name property:
```
// No name property
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "…"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "name": [],
  "content": "…"
}
```
Single Value vs. Array: Similarly, a property holding a single value directly is often equivalent to it holding a single-element array containing that value. Your code must anticipate both representations for the same meaning, like for the content property here:
```
// Single value
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "Hello"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": ["Hello"]
}
```

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // Embedded objects:
  "actor": {
    "type": "Person",
    "id": "http://sally.example.org/",
    "name": "Sally"
  },
  "object": {
    "type": "Arrive",
    "id": "https://sally.example.com/arrive",
    /* ... */
  }
}

// Equivalent to:
{
  "@context":
  "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // URI references:
  "actor": "http://sally.example.org/",
  "object": "https://sally.example.com/arrive"
}

Challenge #2: Discovery & Identity—Finding Your Actors

// Example: Define how to find actors
federation.setActorDispatcher(
  "/users/{username}",
  async (ctx, username) => { /* ... */ }
);
// Now GET /.well-known/webfinger?resource=acct:username@your.domain just works!

Challenge #3: Core ActivityPub Mechanics—Handling Requests and Collections

// Define inbox handlers
federation.setInboxListeners("/inbox", "/users/{handle}/inbox")
  .on(Follow, async (ctx, follow) => { /* Handle follow */ })
  .on(Undo, async (ctx, undo) => { /* Handle undo */ });

// Define followers collection logic
federation.setFollowersDispatcher(
  "/users/{handle}/followers",
  async (ctx, handle, cursor) => { /* ... */ }
);

Challenge #4: Reliable Delivery & Asynchronous Processing—Sending Activities Robustly

// Configure Fedify with a persistent queue (e.g., Deno KV)
const federation = createFederation({
  queue: new DenoKvMessageQueue(/* ... */),
  // ...
});
// Sending is now reliable and non-blocking
await ctx.sendActivity({ handle: "myUser" }, recipient, someActivity);

Challenge #5: Security—Avoiding Common Pitfalls

Challenge #6: Interoperability & Maintenance—Playing Nicely with Others

Challenge #7: Developer Experience—Actually Building Your App

You can quickly scaffold a new project tailored to your chosen runtime and web framework using fedify init.

$ fedify lookup @fedify-example@fedify-blog.deno.dev

Will first show progress messages and then output the structured representation of the actor, similar to this:

// Output of fedify lookup command (shows parsed object structure)
Person {
  id: URL "https://fedify-blog.deno.dev/users/fedify-example",
  name: "Fedify Example Blog",
  published: 2024-03-03T13:18:11.857Z, // Simplified timestamp
  summary: "This blog is powered by Fedify, a fediverse server framework.",
  url: URL "https://fedify-blog.deno.dev/",
  preferredUsername: "fedify-example",
  publicKey: CryptographicKey {
    id: URL "https://fedify-blog.deno.dev/users/fedify-example#main-key",
    owner: URL "https://fedify-blog.deno.dev/users/fedify-example",
    publicKey: CryptoKey { /* ... CryptoKey details ... */ }
  },
  // ... other properties like inbox, outbox, followers, endpoints ...
}

This allows you to easily check how data is structured or troubleshoot why an interaction might be failing by seeing the actual properties Fedify parsed.

$ fedify inbox
✔ The ephemeral ActivityPub server is up and running: https://<unique_id>.lhr.life/
✔ Sent follow request to @<some_test_account>@activitypub.academy.
╭───────────────┬─────────────────────────────────────────╮
│ Actor handle: │ i@<unique_id>.lhr.life                  │
├───────────────┼─────────────────────────────────────────┤
│   Actor URI:  │ https://<unique_id>.lhr.life/i          │
├───────────────┼─────────────────────────────────────────┤
│  Actor inbox: │ https://<unique_id>.lhr.life/i/inbox    │
├───────────────┼─────────────────────────────────────────┤
│ Shared inbox: │ https://<unique_id>.lhr.life/inbox      │
╰───────────────┴─────────────────────────────────────────╯

Web interface available at: http://localhost:8000/

╭────────────────┬─────────────────────────────────────╮
│     Request #: │ 2                                   │
├────────────────┼─────────────────────────────────────┤
│ Activity type: │ Follow                              │
├────────────────┼─────────────────────────────────────┤
│  HTTP request: │ POST /i/inbox                       │
├────────────────┼─────────────────────────────────────┤
│ HTTP response: │ 202                                 │
├────────────────┼─────────────────────────────────────┤
│       Details  │ https://<unique_id>.lhr.life/r/2    │
╰────────────────┴─────────────────────────────────────╯

Conclusion: Build Features, Not Plumbing

Getting started is straightforward. First, install the Fedify CLI using your preferred method. Once installed, create a new project template by running fedify init your-project-name.

Check out the Fedify tutorials and Fedify manual to learn more. Happy federating!

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Don't build #ActivityPub from scratch! It's complex. See why using the #Fedify framework is the smarter way to develop for the fediverse in my new post:

https://hackers.pub/@hongminhee/2025/why-use-fedify

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

Challenge #1: Data Modeling—Speaking ActivityStreams & JSON-LD Fluently

Second, JSON-LD, the encoding layer, has specific rules that make direct JSON manipulation surprisingly tricky:

Missing vs. Empty Array: In JSON-LD, a property being absent is often semantically identical to it being present with an empty array. Your application logic needs to treat these cases equally when checking for values. For example, these two Note objects mean the same thing regarding the name property:
```
// No name property
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "…"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "name": [],
  "content": "…"
}
```
Single Value vs. Array: Similarly, a property holding a single value directly is often equivalent to it holding a single-element array containing that value. Your code must anticipate both representations for the same meaning, like for the content property here:
```
// Single value
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "Hello"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": ["Hello"]
}
```

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // Embedded objects:
  "actor": {
    "type": "Person",
    "id": "http://sally.example.org/",
    "name": "Sally"
  },
  "object": {
    "type": "Arrive",
    "id": "https://sally.example.com/arrive",
    /* ... */
  }
}

// Equivalent to:
{
  "@context":
  "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // URI references:
  "actor": "http://sally.example.org/",
  "object": "https://sally.example.com/arrive"
}

Challenge #2: Discovery & Identity—Finding Your Actors

// Example: Define how to find actors
federation.setActorDispatcher(
  "/users/{username}",
  async (ctx, username) => { /* ... */ }
);
// Now GET /.well-known/webfinger?resource=acct:username@your.domain just works!

Challenge #3: Core ActivityPub Mechanics—Handling Requests and Collections

// Define inbox handlers
federation.setInboxListeners("/inbox", "/users/{handle}/inbox")
  .on(Follow, async (ctx, follow) => { /* Handle follow */ })
  .on(Undo, async (ctx, undo) => { /* Handle undo */ });

// Define followers collection logic
federation.setFollowersDispatcher(
  "/users/{handle}/followers",
  async (ctx, handle, cursor) => { /* ... */ }
);

Challenge #4: Reliable Delivery & Asynchronous Processing—Sending Activities Robustly

// Configure Fedify with a persistent queue (e.g., Deno KV)
const federation = createFederation({
  queue: new DenoKvMessageQueue(/* ... */),
  // ...
});
// Sending is now reliable and non-blocking
await ctx.sendActivity({ handle: "myUser" }, recipient, someActivity);

Challenge #5: Security—Avoiding Common Pitfalls

Challenge #6: Interoperability & Maintenance—Playing Nicely with Others

Challenge #7: Developer Experience—Actually Building Your App

You can quickly scaffold a new project tailored to your chosen runtime and web framework using fedify init.

$ fedify lookup @fedify-example@fedify-blog.deno.dev

Will first show progress messages and then output the structured representation of the actor, similar to this:

// Output of fedify lookup command (shows parsed object structure)
Person {
  id: URL "https://fedify-blog.deno.dev/users/fedify-example",
  name: "Fedify Example Blog",
  published: 2024-03-03T13:18:11.857Z, // Simplified timestamp
  summary: "This blog is powered by Fedify, a fediverse server framework.",
  url: URL "https://fedify-blog.deno.dev/",
  preferredUsername: "fedify-example",
  publicKey: CryptographicKey {
    id: URL "https://fedify-blog.deno.dev/users/fedify-example#main-key",
    owner: URL "https://fedify-blog.deno.dev/users/fedify-example",
    publicKey: CryptoKey { /* ... CryptoKey details ... */ }
  },
  // ... other properties like inbox, outbox, followers, endpoints ...
}

This allows you to easily check how data is structured or troubleshoot why an interaction might be failing by seeing the actual properties Fedify parsed.

$ fedify inbox
✔ The ephemeral ActivityPub server is up and running: https://<unique_id>.lhr.life/
✔ Sent follow request to @<some_test_account>@activitypub.academy.
╭───────────────┬─────────────────────────────────────────╮
│ Actor handle: │ i@<unique_id>.lhr.life                  │
├───────────────┼─────────────────────────────────────────┤
│   Actor URI:  │ https://<unique_id>.lhr.life/i          │
├───────────────┼─────────────────────────────────────────┤
│  Actor inbox: │ https://<unique_id>.lhr.life/i/inbox    │
├───────────────┼─────────────────────────────────────────┤
│ Shared inbox: │ https://<unique_id>.lhr.life/inbox      │
╰───────────────┴─────────────────────────────────────────╯

Web interface available at: http://localhost:8000/

╭────────────────┬─────────────────────────────────────╮
│     Request #: │ 2                                   │
├────────────────┼─────────────────────────────────────┤
│ Activity type: │ Follow                              │
├────────────────┼─────────────────────────────────────┤
│  HTTP request: │ POST /i/inbox                       │
├────────────────┼─────────────────────────────────────┤
│ HTTP response: │ 202                                 │
├────────────────┼─────────────────────────────────────┤
│       Details  │ https://<unique_id>.lhr.life/r/2    │
╰────────────────┴─────────────────────────────────────╯

Conclusion: Build Features, Not Plumbing

Getting started is straightforward. First, install the Fedify CLI using your preferred method. Once installed, create a new project template by running fedify init your-project-name.

Check out the Fedify tutorials and Fedify manual to learn more. Happy federating!

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

Challenge #1: Data Modeling—Speaking ActivityStreams & JSON-LD Fluently

Second, JSON-LD, the encoding layer, has specific rules that make direct JSON manipulation surprisingly tricky:

Missing vs. Empty Array: In JSON-LD, a property being absent is often semantically identical to it being present with an empty array. Your application logic needs to treat these cases equally when checking for values. For example, these two Note objects mean the same thing regarding the name property:
```
// No name property
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "…"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "name": [],
  "content": "…"
}
```
Single Value vs. Array: Similarly, a property holding a single value directly is often equivalent to it holding a single-element array containing that value. Your code must anticipate both representations for the same meaning, like for the content property here:
```
// Single value
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "Hello"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": ["Hello"]
}
```

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // Embedded objects:
  "actor": {
    "type": "Person",
    "id": "http://sally.example.org/",
    "name": "Sally"
  },
  "object": {
    "type": "Arrive",
    "id": "https://sally.example.com/arrive",
    /* ... */
  }
}

// Equivalent to:
{
  "@context":
  "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // URI references:
  "actor": "http://sally.example.org/",
  "object": "https://sally.example.com/arrive"
}

Challenge #2: Discovery & Identity—Finding Your Actors

// Example: Define how to find actors
federation.setActorDispatcher(
  "/users/{username}",
  async (ctx, username) => { /* ... */ }
);
// Now GET /.well-known/webfinger?resource=acct:username@your.domain just works!

Challenge #3: Core ActivityPub Mechanics—Handling Requests and Collections

// Define inbox handlers
federation.setInboxListeners("/inbox", "/users/{handle}/inbox")
  .on(Follow, async (ctx, follow) => { /* Handle follow */ })
  .on(Undo, async (ctx, undo) => { /* Handle undo */ });

// Define followers collection logic
federation.setFollowersDispatcher(
  "/users/{handle}/followers",
  async (ctx, handle, cursor) => { /* ... */ }
);

Challenge #4: Reliable Delivery & Asynchronous Processing—Sending Activities Robustly

// Configure Fedify with a persistent queue (e.g., Deno KV)
const federation = createFederation({
  queue: new DenoKvMessageQueue(/* ... */),
  // ...
});
// Sending is now reliable and non-blocking
await ctx.sendActivity({ handle: "myUser" }, recipient, someActivity);

Challenge #5: Security—Avoiding Common Pitfalls

Challenge #6: Interoperability & Maintenance—Playing Nicely with Others

Challenge #7: Developer Experience—Actually Building Your App

You can quickly scaffold a new project tailored to your chosen runtime and web framework using fedify init.

$ fedify lookup @fedify-example@fedify-blog.deno.dev

Will first show progress messages and then output the structured representation of the actor, similar to this:

// Output of fedify lookup command (shows parsed object structure)
Person {
  id: URL "https://fedify-blog.deno.dev/users/fedify-example",
  name: "Fedify Example Blog",
  published: 2024-03-03T13:18:11.857Z, // Simplified timestamp
  summary: "This blog is powered by Fedify, a fediverse server framework.",
  url: URL "https://fedify-blog.deno.dev/",
  preferredUsername: "fedify-example",
  publicKey: CryptographicKey {
    id: URL "https://fedify-blog.deno.dev/users/fedify-example#main-key",
    owner: URL "https://fedify-blog.deno.dev/users/fedify-example",
    publicKey: CryptoKey { /* ... CryptoKey details ... */ }
  },
  // ... other properties like inbox, outbox, followers, endpoints ...
}

This allows you to easily check how data is structured or troubleshoot why an interaction might be failing by seeing the actual properties Fedify parsed.

$ fedify inbox
✔ The ephemeral ActivityPub server is up and running: https://<unique_id>.lhr.life/
✔ Sent follow request to @<some_test_account>@activitypub.academy.
╭───────────────┬─────────────────────────────────────────╮
│ Actor handle: │ i@<unique_id>.lhr.life                  │
├───────────────┼─────────────────────────────────────────┤
│   Actor URI:  │ https://<unique_id>.lhr.life/i          │
├───────────────┼─────────────────────────────────────────┤
│  Actor inbox: │ https://<unique_id>.lhr.life/i/inbox    │
├───────────────┼─────────────────────────────────────────┤
│ Shared inbox: │ https://<unique_id>.lhr.life/inbox      │
╰───────────────┴─────────────────────────────────────────╯

Web interface available at: http://localhost:8000/

╭────────────────┬─────────────────────────────────────╮
│     Request #: │ 2                                   │
├────────────────┼─────────────────────────────────────┤
│ Activity type: │ Follow                              │
├────────────────┼─────────────────────────────────────┤
│  HTTP request: │ POST /i/inbox                       │
├────────────────┼─────────────────────────────────────┤
│ HTTP response: │ 202                                 │
├────────────────┼─────────────────────────────────────┤
│       Details  │ https://<unique_id>.lhr.life/r/2    │
╰────────────────┴─────────────────────────────────────╯

Conclusion: Build Features, Not Plumbing

Getting started is straightforward. First, install the Fedify CLI using your preferred method. Once installed, create a new project template by running fedify init your-project-name.

Check out the Fedify tutorials and Fedify manual to learn more. Happy federating!

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Don't build #ActivityPub from scratch! It's complex. See why using the #Fedify framework is the smarter way to develop for the fediverse in my new post:

https://hackers.pub/@hongminhee/2025/why-use-fedify

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

Challenge #1: Data Modeling—Speaking ActivityStreams & JSON-LD Fluently

Second, JSON-LD, the encoding layer, has specific rules that make direct JSON manipulation surprisingly tricky:

Missing vs. Empty Array: In JSON-LD, a property being absent is often semantically identical to it being present with an empty array. Your application logic needs to treat these cases equally when checking for values. For example, these two Note objects mean the same thing regarding the name property:
```
// No name property
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "…"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "name": [],
  "content": "…"
}
```
Single Value vs. Array: Similarly, a property holding a single value directly is often equivalent to it holding a single-element array containing that value. Your code must anticipate both representations for the same meaning, like for the content property here:
```
// Single value
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "Hello"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": ["Hello"]
}
```

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // Embedded objects:
  "actor": {
    "type": "Person",
    "id": "http://sally.example.org/",
    "name": "Sally"
  },
  "object": {
    "type": "Arrive",
    "id": "https://sally.example.com/arrive",
    /* ... */
  }
}

// Equivalent to:
{
  "@context":
  "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // URI references:
  "actor": "http://sally.example.org/",
  "object": "https://sally.example.com/arrive"
}

Challenge #2: Discovery & Identity—Finding Your Actors

// Example: Define how to find actors
federation.setActorDispatcher(
  "/users/{username}",
  async (ctx, username) => { /* ... */ }
);
// Now GET /.well-known/webfinger?resource=acct:username@your.domain just works!

Challenge #3: Core ActivityPub Mechanics—Handling Requests and Collections

// Define inbox handlers
federation.setInboxListeners("/inbox", "/users/{handle}/inbox")
  .on(Follow, async (ctx, follow) => { /* Handle follow */ })
  .on(Undo, async (ctx, undo) => { /* Handle undo */ });

// Define followers collection logic
federation.setFollowersDispatcher(
  "/users/{handle}/followers",
  async (ctx, handle, cursor) => { /* ... */ }
);

Challenge #4: Reliable Delivery & Asynchronous Processing—Sending Activities Robustly

// Configure Fedify with a persistent queue (e.g., Deno KV)
const federation = createFederation({
  queue: new DenoKvMessageQueue(/* ... */),
  // ...
});
// Sending is now reliable and non-blocking
await ctx.sendActivity({ handle: "myUser" }, recipient, someActivity);

Challenge #5: Security—Avoiding Common Pitfalls

Challenge #6: Interoperability & Maintenance—Playing Nicely with Others

Challenge #7: Developer Experience—Actually Building Your App

You can quickly scaffold a new project tailored to your chosen runtime and web framework using fedify init.

$ fedify lookup @fedify-example@fedify-blog.deno.dev

Will first show progress messages and then output the structured representation of the actor, similar to this:

// Output of fedify lookup command (shows parsed object structure)
Person {
  id: URL "https://fedify-blog.deno.dev/users/fedify-example",
  name: "Fedify Example Blog",
  published: 2024-03-03T13:18:11.857Z, // Simplified timestamp
  summary: "This blog is powered by Fedify, a fediverse server framework.",
  url: URL "https://fedify-blog.deno.dev/",
  preferredUsername: "fedify-example",
  publicKey: CryptographicKey {
    id: URL "https://fedify-blog.deno.dev/users/fedify-example#main-key",
    owner: URL "https://fedify-blog.deno.dev/users/fedify-example",
    publicKey: CryptoKey { /* ... CryptoKey details ... */ }
  },
  // ... other properties like inbox, outbox, followers, endpoints ...
}

This allows you to easily check how data is structured or troubleshoot why an interaction might be failing by seeing the actual properties Fedify parsed.

$ fedify inbox
✔ The ephemeral ActivityPub server is up and running: https://<unique_id>.lhr.life/
✔ Sent follow request to @<some_test_account>@activitypub.academy.
╭───────────────┬─────────────────────────────────────────╮
│ Actor handle: │ i@<unique_id>.lhr.life                  │
├───────────────┼─────────────────────────────────────────┤
│   Actor URI:  │ https://<unique_id>.lhr.life/i          │
├───────────────┼─────────────────────────────────────────┤
│  Actor inbox: │ https://<unique_id>.lhr.life/i/inbox    │
├───────────────┼─────────────────────────────────────────┤
│ Shared inbox: │ https://<unique_id>.lhr.life/inbox      │
╰───────────────┴─────────────────────────────────────────╯

Web interface available at: http://localhost:8000/

╭────────────────┬─────────────────────────────────────╮
│     Request #: │ 2                                   │
├────────────────┼─────────────────────────────────────┤
│ Activity type: │ Follow                              │
├────────────────┼─────────────────────────────────────┤
│  HTTP request: │ POST /i/inbox                       │
├────────────────┼─────────────────────────────────────┤
│ HTTP response: │ 202                                 │
├────────────────┼─────────────────────────────────────┤
│       Details  │ https://<unique_id>.lhr.life/r/2    │
╰────────────────┴─────────────────────────────────────╯

Conclusion: Build Features, Not Plumbing

Getting started is straightforward. First, install the Fedify CLI using your preferred method. Once installed, create a new project template by running fedify init your-project-name.

Check out the Fedify tutorials and Fedify manual to learn more. Happy federating!

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Don't build #ActivityPub from scratch! It's complex. See why using the #Fedify framework is the smarter way to develop for the fediverse in my new post:

https://hackers.pub/@hongminhee/2025/why-use-fedify

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

Challenge #1: Data Modeling—Speaking ActivityStreams & JSON-LD Fluently

Second, JSON-LD, the encoding layer, has specific rules that make direct JSON manipulation surprisingly tricky:

Missing vs. Empty Array: In JSON-LD, a property being absent is often semantically identical to it being present with an empty array. Your application logic needs to treat these cases equally when checking for values. For example, these two Note objects mean the same thing regarding the name property:
```
// No name property
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "…"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "name": [],
  "content": "…"
}
```
Single Value vs. Array: Similarly, a property holding a single value directly is often equivalent to it holding a single-element array containing that value. Your code must anticipate both representations for the same meaning, like for the content property here:
```
// Single value
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "Hello"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": ["Hello"]
}
```

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // Embedded objects:
  "actor": {
    "type": "Person",
    "id": "http://sally.example.org/",
    "name": "Sally"
  },
  "object": {
    "type": "Arrive",
    "id": "https://sally.example.com/arrive",
    /* ... */
  }
}

// Equivalent to:
{
  "@context":
  "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // URI references:
  "actor": "http://sally.example.org/",
  "object": "https://sally.example.com/arrive"
}

Challenge #2: Discovery & Identity—Finding Your Actors

// Example: Define how to find actors
federation.setActorDispatcher(
  "/users/{username}",
  async (ctx, username) => { /* ... */ }
);
// Now GET /.well-known/webfinger?resource=acct:username@your.domain just works!

Challenge #3: Core ActivityPub Mechanics—Handling Requests and Collections

// Define inbox handlers
federation.setInboxListeners("/inbox", "/users/{handle}/inbox")
  .on(Follow, async (ctx, follow) => { /* Handle follow */ })
  .on(Undo, async (ctx, undo) => { /* Handle undo */ });

// Define followers collection logic
federation.setFollowersDispatcher(
  "/users/{handle}/followers",
  async (ctx, handle, cursor) => { /* ... */ }
);

Challenge #4: Reliable Delivery & Asynchronous Processing—Sending Activities Robustly

// Configure Fedify with a persistent queue (e.g., Deno KV)
const federation = createFederation({
  queue: new DenoKvMessageQueue(/* ... */),
  // ...
});
// Sending is now reliable and non-blocking
await ctx.sendActivity({ handle: "myUser" }, recipient, someActivity);

Challenge #5: Security—Avoiding Common Pitfalls

Challenge #6: Interoperability & Maintenance—Playing Nicely with Others

Challenge #7: Developer Experience—Actually Building Your App

You can quickly scaffold a new project tailored to your chosen runtime and web framework using fedify init.

$ fedify lookup @fedify-example@fedify-blog.deno.dev

Will first show progress messages and then output the structured representation of the actor, similar to this:

// Output of fedify lookup command (shows parsed object structure)
Person {
  id: URL "https://fedify-blog.deno.dev/users/fedify-example",
  name: "Fedify Example Blog",
  published: 2024-03-03T13:18:11.857Z, // Simplified timestamp
  summary: "This blog is powered by Fedify, a fediverse server framework.",
  url: URL "https://fedify-blog.deno.dev/",
  preferredUsername: "fedify-example",
  publicKey: CryptographicKey {
    id: URL "https://fedify-blog.deno.dev/users/fedify-example#main-key",
    owner: URL "https://fedify-blog.deno.dev/users/fedify-example",
    publicKey: CryptoKey { /* ... CryptoKey details ... */ }
  },
  // ... other properties like inbox, outbox, followers, endpoints ...
}

This allows you to easily check how data is structured or troubleshoot why an interaction might be failing by seeing the actual properties Fedify parsed.

$ fedify inbox
✔ The ephemeral ActivityPub server is up and running: https://<unique_id>.lhr.life/
✔ Sent follow request to @<some_test_account>@activitypub.academy.
╭───────────────┬─────────────────────────────────────────╮
│ Actor handle: │ i@<unique_id>.lhr.life                  │
├───────────────┼─────────────────────────────────────────┤
│   Actor URI:  │ https://<unique_id>.lhr.life/i          │
├───────────────┼─────────────────────────────────────────┤
│  Actor inbox: │ https://<unique_id>.lhr.life/i/inbox    │
├───────────────┼─────────────────────────────────────────┤
│ Shared inbox: │ https://<unique_id>.lhr.life/inbox      │
╰───────────────┴─────────────────────────────────────────╯

Web interface available at: http://localhost:8000/

╭────────────────┬─────────────────────────────────────╮
│     Request #: │ 2                                   │
├────────────────┼─────────────────────────────────────┤
│ Activity type: │ Follow                              │
├────────────────┼─────────────────────────────────────┤
│  HTTP request: │ POST /i/inbox                       │
├────────────────┼─────────────────────────────────────┤
│ HTTP response: │ 202                                 │
├────────────────┼─────────────────────────────────────┤
│       Details  │ https://<unique_id>.lhr.life/r/2    │
╰────────────────┴─────────────────────────────────────╯

Conclusion: Build Features, Not Plumbing

Getting started is straightforward. First, install the Fedify CLI using your preferred method. Once installed, create a new project template by running fedify init your-project-name.

Check out the Fedify tutorials and Fedify manual to learn more. Happy federating!

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Don't build #ActivityPub from scratch! It's complex. See why using the #Fedify framework is the smarter way to develop for the fediverse in my new post:

https://hackers.pub/@hongminhee/2025/why-use-fedify

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

Challenge #1: Data Modeling—Speaking ActivityStreams & JSON-LD Fluently

Second, JSON-LD, the encoding layer, has specific rules that make direct JSON manipulation surprisingly tricky:

Missing vs. Empty Array: In JSON-LD, a property being absent is often semantically identical to it being present with an empty array. Your application logic needs to treat these cases equally when checking for values. For example, these two Note objects mean the same thing regarding the name property:
```
// No name property
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "…"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "name": [],
  "content": "…"
}
```
Single Value vs. Array: Similarly, a property holding a single value directly is often equivalent to it holding a single-element array containing that value. Your code must anticipate both representations for the same meaning, like for the content property here:
```
// Single value
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "Hello"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": ["Hello"]
}
```

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // Embedded objects:
  "actor": {
    "type": "Person",
    "id": "http://sally.example.org/",
    "name": "Sally"
  },
  "object": {
    "type": "Arrive",
    "id": "https://sally.example.com/arrive",
    /* ... */
  }
}

// Equivalent to:
{
  "@context":
  "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // URI references:
  "actor": "http://sally.example.org/",
  "object": "https://sally.example.com/arrive"
}

Challenge #2: Discovery & Identity—Finding Your Actors

// Example: Define how to find actors
federation.setActorDispatcher(
  "/users/{username}",
  async (ctx, username) => { /* ... */ }
);
// Now GET /.well-known/webfinger?resource=acct:username@your.domain just works!

Challenge #3: Core ActivityPub Mechanics—Handling Requests and Collections

// Define inbox handlers
federation.setInboxListeners("/inbox", "/users/{handle}/inbox")
  .on(Follow, async (ctx, follow) => { /* Handle follow */ })
  .on(Undo, async (ctx, undo) => { /* Handle undo */ });

// Define followers collection logic
federation.setFollowersDispatcher(
  "/users/{handle}/followers",
  async (ctx, handle, cursor) => { /* ... */ }
);

Challenge #4: Reliable Delivery & Asynchronous Processing—Sending Activities Robustly

// Configure Fedify with a persistent queue (e.g., Deno KV)
const federation = createFederation({
  queue: new DenoKvMessageQueue(/* ... */),
  // ...
});
// Sending is now reliable and non-blocking
await ctx.sendActivity({ handle: "myUser" }, recipient, someActivity);

Challenge #5: Security—Avoiding Common Pitfalls

Challenge #6: Interoperability & Maintenance—Playing Nicely with Others

Challenge #7: Developer Experience—Actually Building Your App

You can quickly scaffold a new project tailored to your chosen runtime and web framework using fedify init.

$ fedify lookup @fedify-example@fedify-blog.deno.dev

Will first show progress messages and then output the structured representation of the actor, similar to this:

// Output of fedify lookup command (shows parsed object structure)
Person {
  id: URL "https://fedify-blog.deno.dev/users/fedify-example",
  name: "Fedify Example Blog",
  published: 2024-03-03T13:18:11.857Z, // Simplified timestamp
  summary: "This blog is powered by Fedify, a fediverse server framework.",
  url: URL "https://fedify-blog.deno.dev/",
  preferredUsername: "fedify-example",
  publicKey: CryptographicKey {
    id: URL "https://fedify-blog.deno.dev/users/fedify-example#main-key",
    owner: URL "https://fedify-blog.deno.dev/users/fedify-example",
    publicKey: CryptoKey { /* ... CryptoKey details ... */ }
  },
  // ... other properties like inbox, outbox, followers, endpoints ...
}

This allows you to easily check how data is structured or troubleshoot why an interaction might be failing by seeing the actual properties Fedify parsed.

$ fedify inbox
✔ The ephemeral ActivityPub server is up and running: https://<unique_id>.lhr.life/
✔ Sent follow request to @<some_test_account>@activitypub.academy.
╭───────────────┬─────────────────────────────────────────╮
│ Actor handle: │ i@<unique_id>.lhr.life                  │
├───────────────┼─────────────────────────────────────────┤
│   Actor URI:  │ https://<unique_id>.lhr.life/i          │
├───────────────┼─────────────────────────────────────────┤
│  Actor inbox: │ https://<unique_id>.lhr.life/i/inbox    │
├───────────────┼─────────────────────────────────────────┤
│ Shared inbox: │ https://<unique_id>.lhr.life/inbox      │
╰───────────────┴─────────────────────────────────────────╯

Web interface available at: http://localhost:8000/

╭────────────────┬─────────────────────────────────────╮
│     Request #: │ 2                                   │
├────────────────┼─────────────────────────────────────┤
│ Activity type: │ Follow                              │
├────────────────┼─────────────────────────────────────┤
│  HTTP request: │ POST /i/inbox                       │
├────────────────┼─────────────────────────────────────┤
│ HTTP response: │ 202                                 │
├────────────────┼─────────────────────────────────────┤
│       Details  │ https://<unique_id>.lhr.life/r/2    │
╰────────────────┴─────────────────────────────────────╯

Conclusion: Build Features, Not Plumbing

Getting started is straightforward. First, install the Fedify CLI using your preferred method. Once installed, create a new project template by running fedify init your-project-name.

Check out the Fedify tutorials and Fedify manual to learn more. Happy federating!

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

Challenge #1: Data Modeling—Speaking ActivityStreams & JSON-LD Fluently

Second, JSON-LD, the encoding layer, has specific rules that make direct JSON manipulation surprisingly tricky:

Missing vs. Empty Array: In JSON-LD, a property being absent is often semantically identical to it being present with an empty array. Your application logic needs to treat these cases equally when checking for values. For example, these two Note objects mean the same thing regarding the name property:
```
// No name property
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "…"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "name": [],
  "content": "…"
}
```
Single Value vs. Array: Similarly, a property holding a single value directly is often equivalent to it holding a single-element array containing that value. Your code must anticipate both representations for the same meaning, like for the content property here:
```
// Single value
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "Hello"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": ["Hello"]
}
```

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // Embedded objects:
  "actor": {
    "type": "Person",
    "id": "http://sally.example.org/",
    "name": "Sally"
  },
  "object": {
    "type": "Arrive",
    "id": "https://sally.example.com/arrive",
    /* ... */
  }
}

// Equivalent to:
{
  "@context":
  "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // URI references:
  "actor": "http://sally.example.org/",
  "object": "https://sally.example.com/arrive"
}

Challenge #2: Discovery & Identity—Finding Your Actors

// Example: Define how to find actors
federation.setActorDispatcher(
  "/users/{username}",
  async (ctx, username) => { /* ... */ }
);
// Now GET /.well-known/webfinger?resource=acct:username@your.domain just works!

Challenge #3: Core ActivityPub Mechanics—Handling Requests and Collections

// Define inbox handlers
federation.setInboxListeners("/inbox", "/users/{handle}/inbox")
  .on(Follow, async (ctx, follow) => { /* Handle follow */ })
  .on(Undo, async (ctx, undo) => { /* Handle undo */ });

// Define followers collection logic
federation.setFollowersDispatcher(
  "/users/{handle}/followers",
  async (ctx, handle, cursor) => { /* ... */ }
);

Challenge #4: Reliable Delivery & Asynchronous Processing—Sending Activities Robustly

// Configure Fedify with a persistent queue (e.g., Deno KV)
const federation = createFederation({
  queue: new DenoKvMessageQueue(/* ... */),
  // ...
});
// Sending is now reliable and non-blocking
await ctx.sendActivity({ handle: "myUser" }, recipient, someActivity);

Challenge #5: Security—Avoiding Common Pitfalls

Challenge #6: Interoperability & Maintenance—Playing Nicely with Others

Challenge #7: Developer Experience—Actually Building Your App

You can quickly scaffold a new project tailored to your chosen runtime and web framework using fedify init.

$ fedify lookup @fedify-example@fedify-blog.deno.dev

Will first show progress messages and then output the structured representation of the actor, similar to this:

// Output of fedify lookup command (shows parsed object structure)
Person {
  id: URL "https://fedify-blog.deno.dev/users/fedify-example",
  name: "Fedify Example Blog",
  published: 2024-03-03T13:18:11.857Z, // Simplified timestamp
  summary: "This blog is powered by Fedify, a fediverse server framework.",
  url: URL "https://fedify-blog.deno.dev/",
  preferredUsername: "fedify-example",
  publicKey: CryptographicKey {
    id: URL "https://fedify-blog.deno.dev/users/fedify-example#main-key",
    owner: URL "https://fedify-blog.deno.dev/users/fedify-example",
    publicKey: CryptoKey { /* ... CryptoKey details ... */ }
  },
  // ... other properties like inbox, outbox, followers, endpoints ...
}

This allows you to easily check how data is structured or troubleshoot why an interaction might be failing by seeing the actual properties Fedify parsed.

$ fedify inbox
✔ The ephemeral ActivityPub server is up and running: https://<unique_id>.lhr.life/
✔ Sent follow request to @<some_test_account>@activitypub.academy.
╭───────────────┬─────────────────────────────────────────╮
│ Actor handle: │ i@<unique_id>.lhr.life                  │
├───────────────┼─────────────────────────────────────────┤
│   Actor URI:  │ https://<unique_id>.lhr.life/i          │
├───────────────┼─────────────────────────────────────────┤
│  Actor inbox: │ https://<unique_id>.lhr.life/i/inbox    │
├───────────────┼─────────────────────────────────────────┤
│ Shared inbox: │ https://<unique_id>.lhr.life/inbox      │
╰───────────────┴─────────────────────────────────────────╯

Web interface available at: http://localhost:8000/

╭────────────────┬─────────────────────────────────────╮
│     Request #: │ 2                                   │
├────────────────┼─────────────────────────────────────┤
│ Activity type: │ Follow                              │
├────────────────┼─────────────────────────────────────┤
│  HTTP request: │ POST /i/inbox                       │
├────────────────┼─────────────────────────────────────┤
│ HTTP response: │ 202                                 │
├────────────────┼─────────────────────────────────────┤
│       Details  │ https://<unique_id>.lhr.life/r/2    │
╰────────────────┴─────────────────────────────────────╯

Conclusion: Build Features, Not Plumbing

Getting started is straightforward. First, install the Fedify CLI using your preferred method. Once installed, create a new project template by running fedify init your-project-name.

Check out the Fedify tutorials and Fedify manual to learn more. Happy federating!

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Don't build #ActivityPub from scratch! It's complex. See why using the #Fedify framework is the smarter way to develop for the fediverse in my new post:

https://hackers.pub/@hongminhee/2025/why-use-fedify

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

Challenge #1: Data Modeling—Speaking ActivityStreams & JSON-LD Fluently

Second, JSON-LD, the encoding layer, has specific rules that make direct JSON manipulation surprisingly tricky:

Missing vs. Empty Array: In JSON-LD, a property being absent is often semantically identical to it being present with an empty array. Your application logic needs to treat these cases equally when checking for values. For example, these two Note objects mean the same thing regarding the name property:
```
// No name property
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "…"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "name": [],
  "content": "…"
}
```
Single Value vs. Array: Similarly, a property holding a single value directly is often equivalent to it holding a single-element array containing that value. Your code must anticipate both representations for the same meaning, like for the content property here:
```
// Single value
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "Hello"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": ["Hello"]
}
```

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // Embedded objects:
  "actor": {
    "type": "Person",
    "id": "http://sally.example.org/",
    "name": "Sally"
  },
  "object": {
    "type": "Arrive",
    "id": "https://sally.example.com/arrive",
    /* ... */
  }
}

// Equivalent to:
{
  "@context":
  "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // URI references:
  "actor": "http://sally.example.org/",
  "object": "https://sally.example.com/arrive"
}

Challenge #2: Discovery & Identity—Finding Your Actors

// Example: Define how to find actors
federation.setActorDispatcher(
  "/users/{username}",
  async (ctx, username) => { /* ... */ }
);
// Now GET /.well-known/webfinger?resource=acct:username@your.domain just works!

Challenge #3: Core ActivityPub Mechanics—Handling Requests and Collections

// Define inbox handlers
federation.setInboxListeners("/inbox", "/users/{handle}/inbox")
  .on(Follow, async (ctx, follow) => { /* Handle follow */ })
  .on(Undo, async (ctx, undo) => { /* Handle undo */ });

// Define followers collection logic
federation.setFollowersDispatcher(
  "/users/{handle}/followers",
  async (ctx, handle, cursor) => { /* ... */ }
);

Challenge #4: Reliable Delivery & Asynchronous Processing—Sending Activities Robustly

// Configure Fedify with a persistent queue (e.g., Deno KV)
const federation = createFederation({
  queue: new DenoKvMessageQueue(/* ... */),
  // ...
});
// Sending is now reliable and non-blocking
await ctx.sendActivity({ handle: "myUser" }, recipient, someActivity);

Challenge #5: Security—Avoiding Common Pitfalls

Challenge #6: Interoperability & Maintenance—Playing Nicely with Others

Challenge #7: Developer Experience—Actually Building Your App

You can quickly scaffold a new project tailored to your chosen runtime and web framework using fedify init.

$ fedify lookup @fedify-example@fedify-blog.deno.dev

Will first show progress messages and then output the structured representation of the actor, similar to this:

// Output of fedify lookup command (shows parsed object structure)
Person {
  id: URL "https://fedify-blog.deno.dev/users/fedify-example",
  name: "Fedify Example Blog",
  published: 2024-03-03T13:18:11.857Z, // Simplified timestamp
  summary: "This blog is powered by Fedify, a fediverse server framework.",
  url: URL "https://fedify-blog.deno.dev/",
  preferredUsername: "fedify-example",
  publicKey: CryptographicKey {
    id: URL "https://fedify-blog.deno.dev/users/fedify-example#main-key",
    owner: URL "https://fedify-blog.deno.dev/users/fedify-example",
    publicKey: CryptoKey { /* ... CryptoKey details ... */ }
  },
  // ... other properties like inbox, outbox, followers, endpoints ...
}

This allows you to easily check how data is structured or troubleshoot why an interaction might be failing by seeing the actual properties Fedify parsed.

$ fedify inbox
✔ The ephemeral ActivityPub server is up and running: https://<unique_id>.lhr.life/
✔ Sent follow request to @<some_test_account>@activitypub.academy.
╭───────────────┬─────────────────────────────────────────╮
│ Actor handle: │ i@<unique_id>.lhr.life                  │
├───────────────┼─────────────────────────────────────────┤
│   Actor URI:  │ https://<unique_id>.lhr.life/i          │
├───────────────┼─────────────────────────────────────────┤
│  Actor inbox: │ https://<unique_id>.lhr.life/i/inbox    │
├───────────────┼─────────────────────────────────────────┤
│ Shared inbox: │ https://<unique_id>.lhr.life/inbox      │
╰───────────────┴─────────────────────────────────────────╯

Web interface available at: http://localhost:8000/

╭────────────────┬─────────────────────────────────────╮
│     Request #: │ 2                                   │
├────────────────┼─────────────────────────────────────┤
│ Activity type: │ Follow                              │
├────────────────┼─────────────────────────────────────┤
│  HTTP request: │ POST /i/inbox                       │
├────────────────┼─────────────────────────────────────┤
│ HTTP response: │ 202                                 │
├────────────────┼─────────────────────────────────────┤
│       Details  │ https://<unique_id>.lhr.life/r/2    │
╰────────────────┴─────────────────────────────────────╯

Conclusion: Build Features, Not Plumbing

Getting started is straightforward. First, install the Fedify CLI using your preferred method. Once installed, create a new project template by running fedify init your-project-name.

Check out the Fedify tutorials and Fedify manual to learn more. Happy federating!

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

Challenge #1: Data Modeling—Speaking ActivityStreams & JSON-LD Fluently

Second, JSON-LD, the encoding layer, has specific rules that make direct JSON manipulation surprisingly tricky:

Missing vs. Empty Array: In JSON-LD, a property being absent is often semantically identical to it being present with an empty array. Your application logic needs to treat these cases equally when checking for values. For example, these two Note objects mean the same thing regarding the name property:
```
// No name property
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "…"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "name": [],
  "content": "…"
}
```
Single Value vs. Array: Similarly, a property holding a single value directly is often equivalent to it holding a single-element array containing that value. Your code must anticipate both representations for the same meaning, like for the content property here:
```
// Single value
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "Hello"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": ["Hello"]
}
```

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // Embedded objects:
  "actor": {
    "type": "Person",
    "id": "http://sally.example.org/",
    "name": "Sally"
  },
  "object": {
    "type": "Arrive",
    "id": "https://sally.example.com/arrive",
    /* ... */
  }
}

// Equivalent to:
{
  "@context":
  "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // URI references:
  "actor": "http://sally.example.org/",
  "object": "https://sally.example.com/arrive"
}

Challenge #2: Discovery & Identity—Finding Your Actors

// Example: Define how to find actors
federation.setActorDispatcher(
  "/users/{username}",
  async (ctx, username) => { /* ... */ }
);
// Now GET /.well-known/webfinger?resource=acct:username@your.domain just works!

Challenge #3: Core ActivityPub Mechanics—Handling Requests and Collections

// Define inbox handlers
federation.setInboxListeners("/inbox", "/users/{handle}/inbox")
  .on(Follow, async (ctx, follow) => { /* Handle follow */ })
  .on(Undo, async (ctx, undo) => { /* Handle undo */ });

// Define followers collection logic
federation.setFollowersDispatcher(
  "/users/{handle}/followers",
  async (ctx, handle, cursor) => { /* ... */ }
);

Challenge #4: Reliable Delivery & Asynchronous Processing—Sending Activities Robustly

// Configure Fedify with a persistent queue (e.g., Deno KV)
const federation = createFederation({
  queue: new DenoKvMessageQueue(/* ... */),
  // ...
});
// Sending is now reliable and non-blocking
await ctx.sendActivity({ handle: "myUser" }, recipient, someActivity);

Challenge #5: Security—Avoiding Common Pitfalls

Challenge #6: Interoperability & Maintenance—Playing Nicely with Others

Challenge #7: Developer Experience—Actually Building Your App

You can quickly scaffold a new project tailored to your chosen runtime and web framework using fedify init.

$ fedify lookup @fedify-example@fedify-blog.deno.dev

Will first show progress messages and then output the structured representation of the actor, similar to this:

// Output of fedify lookup command (shows parsed object structure)
Person {
  id: URL "https://fedify-blog.deno.dev/users/fedify-example",
  name: "Fedify Example Blog",
  published: 2024-03-03T13:18:11.857Z, // Simplified timestamp
  summary: "This blog is powered by Fedify, a fediverse server framework.",
  url: URL "https://fedify-blog.deno.dev/",
  preferredUsername: "fedify-example",
  publicKey: CryptographicKey {
    id: URL "https://fedify-blog.deno.dev/users/fedify-example#main-key",
    owner: URL "https://fedify-blog.deno.dev/users/fedify-example",
    publicKey: CryptoKey { /* ... CryptoKey details ... */ }
  },
  // ... other properties like inbox, outbox, followers, endpoints ...
}

This allows you to easily check how data is structured or troubleshoot why an interaction might be failing by seeing the actual properties Fedify parsed.

$ fedify inbox
✔ The ephemeral ActivityPub server is up and running: https://<unique_id>.lhr.life/
✔ Sent follow request to @<some_test_account>@activitypub.academy.
╭───────────────┬─────────────────────────────────────────╮
│ Actor handle: │ i@<unique_id>.lhr.life                  │
├───────────────┼─────────────────────────────────────────┤
│   Actor URI:  │ https://<unique_id>.lhr.life/i          │
├───────────────┼─────────────────────────────────────────┤
│  Actor inbox: │ https://<unique_id>.lhr.life/i/inbox    │
├───────────────┼─────────────────────────────────────────┤
│ Shared inbox: │ https://<unique_id>.lhr.life/inbox      │
╰───────────────┴─────────────────────────────────────────╯

Web interface available at: http://localhost:8000/

╭────────────────┬─────────────────────────────────────╮
│     Request #: │ 2                                   │
├────────────────┼─────────────────────────────────────┤
│ Activity type: │ Follow                              │
├────────────────┼─────────────────────────────────────┤
│  HTTP request: │ POST /i/inbox                       │
├────────────────┼─────────────────────────────────────┤
│ HTTP response: │ 202                                 │
├────────────────┼─────────────────────────────────────┤
│       Details  │ https://<unique_id>.lhr.life/r/2    │
╰────────────────┴─────────────────────────────────────╯

Conclusion: Build Features, Not Plumbing

Getting started is straightforward. First, install the Fedify CLI using your preferred method. Once installed, create a new project template by running fedify init your-project-name.

Check out the Fedify tutorials and Fedify manual to learn more. Happy federating!

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Don't build #ActivityPub from scratch! It's complex. See why using the #Fedify framework is the smarter way to develop for the fediverse in my new post:

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

Challenge #1: Data Modeling—Speaking ActivityStreams & JSON-LD Fluently

Second, JSON-LD, the encoding layer, has specific rules that make direct JSON manipulation surprisingly tricky:

Missing vs. Empty Array: In JSON-LD, a property being absent is often semantically identical to it being present with an empty array. Your application logic needs to treat these cases equally when checking for values. For example, these two Note objects mean the same thing regarding the name property:
```
// No name property
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "…"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "name": [],
  "content": "…"
}
```
Single Value vs. Array: Similarly, a property holding a single value directly is often equivalent to it holding a single-element array containing that value. Your code must anticipate both representations for the same meaning, like for the content property here:
```
// Single value
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "Hello"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": ["Hello"]
}
```

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // Embedded objects:
  "actor": {
    "type": "Person",
    "id": "http://sally.example.org/",
    "name": "Sally"
  },
  "object": {
    "type": "Arrive",
    "id": "https://sally.example.com/arrive",
    /* ... */
  }
}

// Equivalent to:
{
  "@context":
  "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // URI references:
  "actor": "http://sally.example.org/",
  "object": "https://sally.example.com/arrive"
}

Challenge #2: Discovery & Identity—Finding Your Actors

// Example: Define how to find actors
federation.setActorDispatcher(
  "/users/{username}",
  async (ctx, username) => { /* ... */ }
);
// Now GET /.well-known/webfinger?resource=acct:username@your.domain just works!

Challenge #3: Core ActivityPub Mechanics—Handling Requests and Collections

// Define inbox handlers
federation.setInboxListeners("/inbox", "/users/{handle}/inbox")
  .on(Follow, async (ctx, follow) => { /* Handle follow */ })
  .on(Undo, async (ctx, undo) => { /* Handle undo */ });

// Define followers collection logic
federation.setFollowersDispatcher(
  "/users/{handle}/followers",
  async (ctx, handle, cursor) => { /* ... */ }
);

Challenge #4: Reliable Delivery & Asynchronous Processing—Sending Activities Robustly

// Configure Fedify with a persistent queue (e.g., Deno KV)
const federation = createFederation({
  queue: new DenoKvMessageQueue(/* ... */),
  // ...
});
// Sending is now reliable and non-blocking
await ctx.sendActivity({ handle: "myUser" }, recipient, someActivity);

Challenge #5: Security—Avoiding Common Pitfalls

Challenge #6: Interoperability & Maintenance—Playing Nicely with Others

Challenge #7: Developer Experience—Actually Building Your App

You can quickly scaffold a new project tailored to your chosen runtime and web framework using fedify init.

$ fedify lookup @fedify-example@fedify-blog.deno.dev

Will first show progress messages and then output the structured representation of the actor, similar to this:

// Output of fedify lookup command (shows parsed object structure)
Person {
  id: URL "https://fedify-blog.deno.dev/users/fedify-example",
  name: "Fedify Example Blog",
  published: 2024-03-03T13:18:11.857Z, // Simplified timestamp
  summary: "This blog is powered by Fedify, a fediverse server framework.",
  url: URL "https://fedify-blog.deno.dev/",
  preferredUsername: "fedify-example",
  publicKey: CryptographicKey {
    id: URL "https://fedify-blog.deno.dev/users/fedify-example#main-key",
    owner: URL "https://fedify-blog.deno.dev/users/fedify-example",
    publicKey: CryptoKey { /* ... CryptoKey details ... */ }
  },
  // ... other properties like inbox, outbox, followers, endpoints ...
}

This allows you to easily check how data is structured or troubleshoot why an interaction might be failing by seeing the actual properties Fedify parsed.

$ fedify inbox
✔ The ephemeral ActivityPub server is up and running: https://<unique_id>.lhr.life/
✔ Sent follow request to @<some_test_account>@activitypub.academy.
╭───────────────┬─────────────────────────────────────────╮
│ Actor handle: │ i@<unique_id>.lhr.life                  │
├───────────────┼─────────────────────────────────────────┤
│   Actor URI:  │ https://<unique_id>.lhr.life/i          │
├───────────────┼─────────────────────────────────────────┤
│  Actor inbox: │ https://<unique_id>.lhr.life/i/inbox    │
├───────────────┼─────────────────────────────────────────┤
│ Shared inbox: │ https://<unique_id>.lhr.life/inbox      │
╰───────────────┴─────────────────────────────────────────╯

Web interface available at: http://localhost:8000/

╭────────────────┬─────────────────────────────────────╮
│     Request #: │ 2                                   │
├────────────────┼─────────────────────────────────────┤
│ Activity type: │ Follow                              │
├────────────────┼─────────────────────────────────────┤
│  HTTP request: │ POST /i/inbox                       │
├────────────────┼─────────────────────────────────────┤
│ HTTP response: │ 202                                 │
├────────────────┼─────────────────────────────────────┤
│       Details  │ https://<unique_id>.lhr.life/r/2    │
╰────────────────┴─────────────────────────────────────╯

Conclusion: Build Features, Not Plumbing

Getting started is straightforward. First, install the Fedify CLI using your preferred method. Once installed, create a new project template by running fedify init your-project-name.

Check out the Fedify tutorials and Fedify manual to learn more. Happy federating!

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

Challenge #1: Data Modeling—Speaking ActivityStreams & JSON-LD Fluently

Second, JSON-LD, the encoding layer, has specific rules that make direct JSON manipulation surprisingly tricky:

Missing vs. Empty Array: In JSON-LD, a property being absent is often semantically identical to it being present with an empty array. Your application logic needs to treat these cases equally when checking for values. For example, these two Note objects mean the same thing regarding the name property:
```
// No name property
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "…"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "name": [],
  "content": "…"
}
```
Single Value vs. Array: Similarly, a property holding a single value directly is often equivalent to it holding a single-element array containing that value. Your code must anticipate both representations for the same meaning, like for the content property here:
```
// Single value
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "Hello"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": ["Hello"]
}
```

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // Embedded objects:
  "actor": {
    "type": "Person",
    "id": "http://sally.example.org/",
    "name": "Sally"
  },
  "object": {
    "type": "Arrive",
    "id": "https://sally.example.com/arrive",
    /* ... */
  }
}

// Equivalent to:
{
  "@context":
  "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // URI references:
  "actor": "http://sally.example.org/",
  "object": "https://sally.example.com/arrive"
}

Challenge #2: Discovery & Identity—Finding Your Actors

// Example: Define how to find actors
federation.setActorDispatcher(
  "/users/{username}",
  async (ctx, username) => { /* ... */ }
);
// Now GET /.well-known/webfinger?resource=acct:username@your.domain just works!

Challenge #3: Core ActivityPub Mechanics—Handling Requests and Collections

// Define inbox handlers
federation.setInboxListeners("/inbox", "/users/{handle}/inbox")
  .on(Follow, async (ctx, follow) => { /* Handle follow */ })
  .on(Undo, async (ctx, undo) => { /* Handle undo */ });

// Define followers collection logic
federation.setFollowersDispatcher(
  "/users/{handle}/followers",
  async (ctx, handle, cursor) => { /* ... */ }
);

Challenge #4: Reliable Delivery & Asynchronous Processing—Sending Activities Robustly

// Configure Fedify with a persistent queue (e.g., Deno KV)
const federation = createFederation({
  queue: new DenoKvMessageQueue(/* ... */),
  // ...
});
// Sending is now reliable and non-blocking
await ctx.sendActivity({ handle: "myUser" }, recipient, someActivity);

Challenge #5: Security—Avoiding Common Pitfalls

Challenge #6: Interoperability & Maintenance—Playing Nicely with Others

Challenge #7: Developer Experience—Actually Building Your App

You can quickly scaffold a new project tailored to your chosen runtime and web framework using fedify init.

$ fedify lookup @fedify-example@fedify-blog.deno.dev

Will first show progress messages and then output the structured representation of the actor, similar to this:

// Output of fedify lookup command (shows parsed object structure)
Person {
  id: URL "https://fedify-blog.deno.dev/users/fedify-example",
  name: "Fedify Example Blog",
  published: 2024-03-03T13:18:11.857Z, // Simplified timestamp
  summary: "This blog is powered by Fedify, a fediverse server framework.",
  url: URL "https://fedify-blog.deno.dev/",
  preferredUsername: "fedify-example",
  publicKey: CryptographicKey {
    id: URL "https://fedify-blog.deno.dev/users/fedify-example#main-key",
    owner: URL "https://fedify-blog.deno.dev/users/fedify-example",
    publicKey: CryptoKey { /* ... CryptoKey details ... */ }
  },
  // ... other properties like inbox, outbox, followers, endpoints ...
}

This allows you to easily check how data is structured or troubleshoot why an interaction might be failing by seeing the actual properties Fedify parsed.

$ fedify inbox
✔ The ephemeral ActivityPub server is up and running: https://<unique_id>.lhr.life/
✔ Sent follow request to @<some_test_account>@activitypub.academy.
╭───────────────┬─────────────────────────────────────────╮
│ Actor handle: │ i@<unique_id>.lhr.life                  │
├───────────────┼─────────────────────────────────────────┤
│   Actor URI:  │ https://<unique_id>.lhr.life/i          │
├───────────────┼─────────────────────────────────────────┤
│  Actor inbox: │ https://<unique_id>.lhr.life/i/inbox    │
├───────────────┼─────────────────────────────────────────┤
│ Shared inbox: │ https://<unique_id>.lhr.life/inbox      │
╰───────────────┴─────────────────────────────────────────╯

Web interface available at: http://localhost:8000/

╭────────────────┬─────────────────────────────────────╮
│     Request #: │ 2                                   │
├────────────────┼─────────────────────────────────────┤
│ Activity type: │ Follow                              │
├────────────────┼─────────────────────────────────────┤
│  HTTP request: │ POST /i/inbox                       │
├────────────────┼─────────────────────────────────────┤
│ HTTP response: │ 202                                 │
├────────────────┼─────────────────────────────────────┤
│       Details  │ https://<unique_id>.lhr.life/r/2    │
╰────────────────┴─────────────────────────────────────╯

Conclusion: Build Features, Not Plumbing

Getting started is straightforward. First, install the Fedify CLI using your preferred method. Once installed, create a new project template by running fedify init your-project-name.

Check out the Fedify tutorials and Fedify manual to learn more. Happy federating!

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

Challenge #1: Data Modeling—Speaking ActivityStreams & JSON-LD Fluently

Second, JSON-LD, the encoding layer, has specific rules that make direct JSON manipulation surprisingly tricky:

Missing vs. Empty Array: In JSON-LD, a property being absent is often semantically identical to it being present with an empty array. Your application logic needs to treat these cases equally when checking for values. For example, these two Note objects mean the same thing regarding the name property:
```
// No name property
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "…"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "name": [],
  "content": "…"
}
```
Single Value vs. Array: Similarly, a property holding a single value directly is often equivalent to it holding a single-element array containing that value. Your code must anticipate both representations for the same meaning, like for the content property here:
```
// Single value
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "Hello"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": ["Hello"]
}
```

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // Embedded objects:
  "actor": {
    "type": "Person",
    "id": "http://sally.example.org/",
    "name": "Sally"
  },
  "object": {
    "type": "Arrive",
    "id": "https://sally.example.com/arrive",
    /* ... */
  }
}

// Equivalent to:
{
  "@context":
  "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // URI references:
  "actor": "http://sally.example.org/",
  "object": "https://sally.example.com/arrive"
}

Challenge #2: Discovery & Identity—Finding Your Actors

// Example: Define how to find actors
federation.setActorDispatcher(
  "/users/{username}",
  async (ctx, username) => { /* ... */ }
);
// Now GET /.well-known/webfinger?resource=acct:username@your.domain just works!

Challenge #3: Core ActivityPub Mechanics—Handling Requests and Collections

// Define inbox handlers
federation.setInboxListeners("/inbox", "/users/{handle}/inbox")
  .on(Follow, async (ctx, follow) => { /* Handle follow */ })
  .on(Undo, async (ctx, undo) => { /* Handle undo */ });

// Define followers collection logic
federation.setFollowersDispatcher(
  "/users/{handle}/followers",
  async (ctx, handle, cursor) => { /* ... */ }
);

Challenge #4: Reliable Delivery & Asynchronous Processing—Sending Activities Robustly

// Configure Fedify with a persistent queue (e.g., Deno KV)
const federation = createFederation({
  queue: new DenoKvMessageQueue(/* ... */),
  // ...
});
// Sending is now reliable and non-blocking
await ctx.sendActivity({ handle: "myUser" }, recipient, someActivity);

Challenge #5: Security—Avoiding Common Pitfalls

Challenge #6: Interoperability & Maintenance—Playing Nicely with Others

Challenge #7: Developer Experience—Actually Building Your App

You can quickly scaffold a new project tailored to your chosen runtime and web framework using fedify init.

$ fedify lookup @fedify-example@fedify-blog.deno.dev

Will first show progress messages and then output the structured representation of the actor, similar to this:

// Output of fedify lookup command (shows parsed object structure)
Person {
  id: URL "https://fedify-blog.deno.dev/users/fedify-example",
  name: "Fedify Example Blog",
  published: 2024-03-03T13:18:11.857Z, // Simplified timestamp
  summary: "This blog is powered by Fedify, a fediverse server framework.",
  url: URL "https://fedify-blog.deno.dev/",
  preferredUsername: "fedify-example",
  publicKey: CryptographicKey {
    id: URL "https://fedify-blog.deno.dev/users/fedify-example#main-key",
    owner: URL "https://fedify-blog.deno.dev/users/fedify-example",
    publicKey: CryptoKey { /* ... CryptoKey details ... */ }
  },
  // ... other properties like inbox, outbox, followers, endpoints ...
}

This allows you to easily check how data is structured or troubleshoot why an interaction might be failing by seeing the actual properties Fedify parsed.

$ fedify inbox
✔ The ephemeral ActivityPub server is up and running: https://<unique_id>.lhr.life/
✔ Sent follow request to @<some_test_account>@activitypub.academy.
╭───────────────┬─────────────────────────────────────────╮
│ Actor handle: │ i@<unique_id>.lhr.life                  │
├───────────────┼─────────────────────────────────────────┤
│   Actor URI:  │ https://<unique_id>.lhr.life/i          │
├───────────────┼─────────────────────────────────────────┤
│  Actor inbox: │ https://<unique_id>.lhr.life/i/inbox    │
├───────────────┼─────────────────────────────────────────┤
│ Shared inbox: │ https://<unique_id>.lhr.life/inbox      │
╰───────────────┴─────────────────────────────────────────╯

Web interface available at: http://localhost:8000/

╭────────────────┬─────────────────────────────────────╮
│     Request #: │ 2                                   │
├────────────────┼─────────────────────────────────────┤
│ Activity type: │ Follow                              │
├────────────────┼─────────────────────────────────────┤
│  HTTP request: │ POST /i/inbox                       │
├────────────────┼─────────────────────────────────────┤
│ HTTP response: │ 202                                 │
├────────────────┼─────────────────────────────────────┤
│       Details  │ https://<unique_id>.lhr.life/r/2    │
╰────────────────┴─────────────────────────────────────╯

Conclusion: Build Features, Not Plumbing

Getting started is straightforward. First, install the Fedify CLI using your preferred method. Once installed, create a new project template by running fedify init your-project-name.

Check out the Fedify tutorials and Fedify manual to learn more. Happy federating!

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

Challenge #1: Data Modeling—Speaking ActivityStreams & JSON-LD Fluently

Second, JSON-LD, the encoding layer, has specific rules that make direct JSON manipulation surprisingly tricky:

Missing vs. Empty Array: In JSON-LD, a property being absent is often semantically identical to it being present with an empty array. Your application logic needs to treat these cases equally when checking for values. For example, these two Note objects mean the same thing regarding the name property:
```
// No name property
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "…"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "name": [],
  "content": "…"
}
```
Single Value vs. Array: Similarly, a property holding a single value directly is often equivalent to it holding a single-element array containing that value. Your code must anticipate both representations for the same meaning, like for the content property here:
```
// Single value
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": "Hello"
}
```
```
// Equivalent to:
{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Note",
  "content": ["Hello"]
}
```

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // Embedded objects:
  "actor": {
    "type": "Person",
    "id": "http://sally.example.org/",
    "name": "Sally"
  },
  "object": {
    "type": "Arrive",
    "id": "https://sally.example.com/arrive",
    /* ... */
  }
}

// Equivalent to:
{
  "@context":
  "https://www.w3.org/ns/activitystreams",
  "type": "Announce",
  // URI references:
  "actor": "http://sally.example.org/",
  "object": "https://sally.example.com/arrive"
}

Challenge #2: Discovery & Identity—Finding Your Actors

// Example: Define how to find actors
federation.setActorDispatcher(
  "/users/{username}",
  async (ctx, username) => { /* ... */ }
);
// Now GET /.well-known/webfinger?resource=acct:username@your.domain just works!

Challenge #3: Core ActivityPub Mechanics—Handling Requests and Collections

// Define inbox handlers
federation.setInboxListeners("/inbox", "/users/{handle}/inbox")
  .on(Follow, async (ctx, follow) => { /* Handle follow */ })
  .on(Undo, async (ctx, undo) => { /* Handle undo */ });

// Define followers collection logic
federation.setFollowersDispatcher(
  "/users/{handle}/followers",
  async (ctx, handle, cursor) => { /* ... */ }
);

Challenge #4: Reliable Delivery & Asynchronous Processing—Sending Activities Robustly

// Configure Fedify with a persistent queue (e.g., Deno KV)
const federation = createFederation({
  queue: new DenoKvMessageQueue(/* ... */),
  // ...
});
// Sending is now reliable and non-blocking
await ctx.sendActivity({ handle: "myUser" }, recipient, someActivity);

Challenge #5: Security—Avoiding Common Pitfalls

Challenge #6: Interoperability & Maintenance—Playing Nicely with Others

Challenge #7: Developer Experience—Actually Building Your App

You can quickly scaffold a new project tailored to your chosen runtime and web framework using fedify init.

$ fedify lookup @fedify-example@fedify-blog.deno.dev

Will first show progress messages and then output the structured representation of the actor, similar to this:

// Output of fedify lookup command (shows parsed object structure)
Person {
  id: URL "https://fedify-blog.deno.dev/users/fedify-example",
  name: "Fedify Example Blog",
  published: 2024-03-03T13:18:11.857Z, // Simplified timestamp
  summary: "This blog is powered by Fedify, a fediverse server framework.",
  url: URL "https://fedify-blog.deno.dev/",
  preferredUsername: "fedify-example",
  publicKey: CryptographicKey {
    id: URL "https://fedify-blog.deno.dev/users/fedify-example#main-key",
    owner: URL "https://fedify-blog.deno.dev/users/fedify-example",
    publicKey: CryptoKey { /* ... CryptoKey details ... */ }
  },
  // ... other properties like inbox, outbox, followers, endpoints ...
}

This allows you to easily check how data is structured or troubleshoot why an interaction might be failing by seeing the actual properties Fedify parsed.

$ fedify inbox
✔ The ephemeral ActivityPub server is up and running: https://<unique_id>.lhr.life/
✔ Sent follow request to @<some_test_account>@activitypub.academy.
╭───────────────┬─────────────────────────────────────────╮
│ Actor handle: │ i@<unique_id>.lhr.life                  │
├───────────────┼─────────────────────────────────────────┤
│   Actor URI:  │ https://<unique_id>.lhr.life/i          │
├───────────────┼─────────────────────────────────────────┤
│  Actor inbox: │ https://<unique_id>.lhr.life/i/inbox    │
├───────────────┼─────────────────────────────────────────┤
│ Shared inbox: │ https://<unique_id>.lhr.life/inbox      │
╰───────────────┴─────────────────────────────────────────╯

Web interface available at: http://localhost:8000/

╭────────────────┬─────────────────────────────────────╮
│     Request #: │ 2                                   │
├────────────────┼─────────────────────────────────────┤
│ Activity type: │ Follow                              │
├────────────────┼─────────────────────────────────────┤
│  HTTP request: │ POST /i/inbox                       │
├────────────────┼─────────────────────────────────────┤
│ HTTP response: │ 202                                 │
├────────────────┼─────────────────────────────────────┤
│       Details  │ https://<unique_id>.lhr.life/r/2    │
╰────────────────┴─────────────────────────────────────╯

Conclusion: Build Features, Not Plumbing

Getting started is straightforward. First, install the Fedify CLI using your preferred method. Once installed, create a new project template by running fedify init your-project-name.

Check out the Fedify tutorials and Fedify manual to learn more. Happy federating!

Fedify: an ActivityPub server framework

@fedify@hollo.social

Fetching remote #ActivityPub objects or actors often involves handling #WebFinger lookups, content negotiation, and then parsing potentially untyped JSON.

With #Fedify, it's much simpler: use Context.lookupObject(). Pass it a URI (e.g., https://instance.tld/users/alice) or a handle (e.g., @alice@instance.tld), and Fedify handles the lookup and content negotiation automatically.

The real power comes from the return value: a type-safe Activity Vocabulary object, not just raw JSON. This allows you to confidently access properties and methods directly. For example, you can safely traverse account moves using .getSuccessor() like this:

let actor = await ctx.lookupObject("@alice@instance.tld");
while (isActor(actor)) {
  const successor = await actor.getSuccessor();
  if (successor == null) break;
  actor = successor;
}
// actor now holds the latest account after moves

This is readily available in handlers where the Context object is provided (like actor dispatchers or inbox listeners).

Focus on your app's logic, not protocol boilerplate!

Learn more: https://fedify.dev/manual/context#looking-up-remote-objects

Fedify: an ActivityPub server framework

@fedify@hollo.social

Fetching remote #ActivityPub objects or actors often involves handling #WebFinger lookups, content negotiation, and then parsing potentially untyped JSON.

let actor = await ctx.lookupObject("@alice@instance.tld");
while (isActor(actor)) {
  const successor = await actor.getSuccessor();
  if (successor == null) break;
  actor = successor;
}
// actor now holds the latest account after moves

This is readily available in handlers where the Context object is provided (like actor dispatchers or inbox listeners).

Focus on your app's logic, not protocol boilerplate!

Learn more: https://fedify.dev/manual/context#looking-up-remote-objects

Fedify: an ActivityPub server framework

@fedify@hollo.social

Fetching remote #ActivityPub objects or actors often involves handling #WebFinger lookups, content negotiation, and then parsing potentially untyped JSON.

let actor = await ctx.lookupObject("@alice@instance.tld");
while (isActor(actor)) {
  const successor = await actor.getSuccessor();
  if (successor == null) break;
  actor = successor;
}
// actor now holds the latest account after moves

This is readily available in handlers where the Context object is provided (like actor dispatchers or inbox listeners).

Focus on your app's logic, not protocol boilerplate!

Learn more: https://fedify.dev/manual/context#looking-up-remote-objects

Fedify: an ActivityPub server framework

@fedify@hollo.social

Fetching remote #ActivityPub objects or actors often involves handling #WebFinger lookups, content negotiation, and then parsing potentially untyped JSON.

let actor = await ctx.lookupObject("@alice@instance.tld");
while (isActor(actor)) {
  const successor = await actor.getSuccessor();
  if (successor == null) break;
  actor = successor;
}
// actor now holds the latest account after moves

This is readily available in handlers where the Context object is provided (like actor dispatchers or inbox listeners).

Focus on your app's logic, not protocol boilerplate!

Learn more: https://fedify.dev/manual/context#looking-up-remote-objects

Fedify: an ActivityPub server framework

@fedify@hollo.social

Fetching remote #ActivityPub objects or actors often involves handling #WebFinger lookups, content negotiation, and then parsing potentially untyped JSON.

let actor = await ctx.lookupObject("@alice@instance.tld");
while (isActor(actor)) {
  const successor = await actor.getSuccessor();
  if (successor == null) break;
  actor = successor;
}
// actor now holds the latest account after moves

This is readily available in handlers where the Context object is provided (like actor dispatchers or inbox listeners).

Focus on your app's logic, not protocol boilerplate!

Learn more: https://fedify.dev/manual/context#looking-up-remote-objects

Fedify: an ActivityPub server framework

@fedify@hollo.social

Fetching remote #ActivityPub objects or actors often involves handling #WebFinger lookups, content negotiation, and then parsing potentially untyped JSON.

let actor = await ctx.lookupObject("@alice@instance.tld");
while (isActor(actor)) {
  const successor = await actor.getSuccessor();
  if (successor == null) break;
  actor = successor;
}
// actor now holds the latest account after moves

This is readily available in handlers where the Context object is provided (like actor dispatchers or inbox listeners).

Focus on your app's logic, not protocol boilerplate!

Learn more: https://fedify.dev/manual/context#looking-up-remote-objects

Fedify: an ActivityPub server framework

@fedify@hollo.social

Fetching remote #ActivityPub objects or actors often involves handling #WebFinger lookups, content negotiation, and then parsing potentially untyped JSON.

let actor = await ctx.lookupObject("@alice@instance.tld");
while (isActor(actor)) {
  const successor = await actor.getSuccessor();
  if (successor == null) break;
  actor = successor;
}
// actor now holds the latest account after moves

This is readily available in handlers where the Context object is provided (like actor dispatchers or inbox listeners).

Focus on your app's logic, not protocol boilerplate!

Learn more: https://fedify.dev/manual/context#looking-up-remote-objects

#DeSo #FediDev #FediDevs #Fediverse #SocialWeb

@reiver ⊼ (Charles)

@reiver@mastodon.social

I have been thinking that — having a regular DEMO DAY for Fediverse developers might be desirable.

Maybe something once a month, where Fediverse developers get together (online), and —

• show what they have been working on,
• talk about Fediverse development issues,
• etc

Not a conference. Just something quick.

(It could be under existing "banner" that already exists. Doesn't necessarily have to be something new.)

Hollo

@hollo@hollo.social

Introducing #Hollo. Hollo is an #ActivityPub-enabled single-user microblogging software. Although it's for a single user, it also supports creating and running multiple accounts for different topics.

Oh, and Hollo is built using #Bun and #Fedify.

Hollo

@hollo@hollo.social

Introducing #Hollo. Hollo is an #ActivityPub-enabled single-user microblogging software. Although it's for a single user, it also supports creating and running multiple accounts for different topics.

Oh, and Hollo is built using #Bun and #Fedify.

#DeSo #FediAdmin #FediCache #FediDev #FediDevs #Fediverse #Firefish #FirefishAdmin #Misskey #MisskeyAdmin #Sharkey #SharkeyAdmin #SpaceHostBTS

@reiver ⊼ (Charles)

@reiver@mastodon.social · Reply to @reiver ⊼ (Charles) :batman:'s post

Misskey and the Misskey forks (ex: Firefish, Sharkey, etc) seem to also be prone to their storage drives filling with:

• logs
• npm cache
• yarn cache

@reiver ⊼ (Charles)

@reiver@mastodon.social

RE: https://mastodon.social/@reiver/114019537398771505

The number one cause of Fediverse servers crashing seems to be the storage drives filling up with cached Fediverse user data — posts, profiles, avatar images, header images, etc.

@fedify@hollo.social

📣 Exciting news! Fedify CLI is now available via Homebrew!

If you're using #Homebrew on macOS or #Linuxbrew on Linux, you can now install our CLI toolchain with a simple command:

brew install fedify

This makes it even easier to get started with building your federated server app. Try it out and let us know what you think!

Fedify: an ActivityPub server framework

@fedify@hollo.social

📣 Exciting news! Fedify CLI is now available via Homebrew!

If you're using #Homebrew on macOS or #Linuxbrew on Linux, you can now install our CLI toolchain with a simple command:

brew install fedify

This makes it even easier to get started with building your federated server app. Try it out and let us know what you think!

Fedify: an ActivityPub server framework

@fedify@hollo.social

📣 Exciting news! Fedify CLI is now available via Homebrew!

If you're using #Homebrew on macOS or #Linuxbrew on Linux, you can now install our CLI toolchain with a simple command:

brew install fedify

This makes it even easier to get started with building your federated server app. Try it out and let us know what you think!

Fedify: an ActivityPub server framework

@fedify@hollo.social

📣 Exciting news! Fedify CLI is now available via Homebrew!

If you're using #Homebrew on macOS or #Linuxbrew on Linux, you can now install our CLI toolchain with a simple command:

brew install fedify

This makes it even easier to get started with building your federated server app. Try it out and let us know what you think!

Fedify: an ActivityPub server framework

@fedify@hollo.social

📣 Exciting news! Fedify CLI is now available via Homebrew!

If you're using #Homebrew on macOS or #Linuxbrew on Linux, you can now install our CLI toolchain with a simple command:

brew install fedify

This makes it even easier to get started with building your federated server app. Try it out and let us know what you think!

Fedify: an ActivityPub server framework

@fedify@hollo.social

📣 Exciting news! Fedify CLI is now available via Homebrew!

If you're using #Homebrew on macOS or #Linuxbrew on Linux, you can now install our CLI toolchain with a simple command:

brew install fedify

This makes it even easier to get started with building your federated server app. Try it out and let us know what you think!

Fedify: an ActivityPub server framework

@fedify@hollo.social

📣 Exciting news! Fedify CLI is now available via Homebrew!

If you're using #Homebrew on macOS or #Linuxbrew on Linux, you can now install our CLI toolchain with a simple command:

brew install fedify

This makes it even easier to get started with building your federated server app. Try it out and let us know what you think!

Fedify: an ActivityPub server framework

@fedify@hollo.social

📣 Exciting news! Fedify CLI is now available via Homebrew!

If you're using #Homebrew on macOS or #Linuxbrew on Linux, you can now install our CLI toolchain with a simple command:

brew install fedify

This makes it even easier to get started with building your federated server app. Try it out and let us know what you think!

Fedify: an ActivityPub server framework

@fedify@hollo.social

📣 Exciting news! Fedify CLI is now available via Homebrew!

If you're using #Homebrew on macOS or #Linuxbrew on Linux, you can now install our CLI toolchain with a simple command:

brew install fedify

This makes it even easier to get started with building your federated server app. Try it out and let us know what you think!

Fedify: an ActivityPub server framework

@fedify@hollo.social

📣 Exciting news! Fedify CLI is now available via Homebrew!

If you're using #Homebrew on macOS or #Linuxbrew on Linux, you can now install our CLI toolchain with a simple command:

brew install fedify

This makes it even easier to get started with building your federated server app. Try it out and let us know what you think!

Fedify: an ActivityPub server framework

@fedify@hollo.social

📣 Exciting news! Fedify CLI is now available via Homebrew!

If you're using #Homebrew on macOS or #Linuxbrew on Linux, you can now install our CLI toolchain with a simple command:

brew install fedify

This makes it even easier to get started with building your federated server app. Try it out and let us know what you think!

Fedify: an ActivityPub server framework

@fedify@hollo.social

📣 Exciting news! Fedify CLI is now available via Homebrew!

If you're using #Homebrew on macOS or #Linuxbrew on Linux, you can now install our CLI toolchain with a simple command:

brew install fedify

This makes it even easier to get started with building your federated server app. Try it out and let us know what you think!

Fedify: an ActivityPub server framework

@fedify@hollo.social

📣 Exciting news! Fedify CLI is now available via Homebrew!

If you're using #Homebrew on macOS or #Linuxbrew on Linux, you can now install our CLI toolchain with a simple command:

brew install fedify

This makes it even easier to get started with building your federated server app. Try it out and let us know what you think!

Fedify: an ActivityPub server framework

@fedify@hollo.social

📣 Exciting news! Fedify CLI is now available via Homebrew!

If you're using #Homebrew on macOS or #Linuxbrew on Linux, you can now install our CLI toolchain with a simple command:

brew install fedify

This makes it even easier to get started with building your federated server app. Try it out and let us know what you think!

Fedify: an ActivityPub server framework

@fedify@hollo.social

📣 Exciting news! Fedify CLI is now available via Homebrew!

If you're using #Homebrew on macOS or #Linuxbrew on Linux, you can now install our CLI toolchain with a simple command:

brew install fedify

This makes it even easier to get started with building your federated server app. Try it out and let us know what you think!

#FediLUG #Fedify #Hollo #ActivityPub #フェディバース #fediverse #fedidev

Fedify: an ActivityPub server framework

@fedify@hollo.social

📣 Exciting news! Fedify CLI is now available via Homebrew!

If you're using #Homebrew on macOS or #Linuxbrew on Linux, you can now install our CLI toolchain with a simple command:

brew install fedify

興味のある方は、発表スライドをご覧ください：「国漢文混用体からHolloまで」（Speaker Deck）

Abelio

@abelio@mastodon.social

FYI: Abelio will provide couple of ways of publishing visual contents. One of them is part of the article editor and it let's you organise multiple images in a form of a flexible grid you can arrange as needed.

#fediverse #fedidev #activitypub #writers #photography #arts

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

I wanted to share some feedback on the documentation provided in the Highlighting Journalism on Mastodon blog post.

Specifically, in The technical section, the example code for the fediverse:creator meta tag is given as:

<meta name="fediverse:creator" content="@Gargron@mastodon.social" />

Based on my testing (and that of others), Mastodon doesn't seem to recognize the creator link correctly when the leading @ is present in the content attribute. It only works when the @ is removed, like this:

<meta name="fediverse:creator" content="Gargron@mastodon.social" />

Following the blog's example directly led to some wasted time figuring out why it wasn't working. It would be great if either the example in the blog post could be corrected to reflect the current requirement, or if Mastodon's parser could be made more flexible to accept the handle with or without the leading @.

Appreciate all you do for #Mastodon!

Jeff Sikes

@box464@mastodon.social

主な機能には、投稿の作成・編集・削除、返信、メディア添付、投票、お気に入り、ブックマーク、ピン留めなどがあります。また、プロフィール編集、フォロー/フォロワー管理、リスト作成なども可能です。さらに、Markdownをサポートしているため、投稿やプロフィールの書式設定が容易に行えます。

Holloは現在開発の初期段階にあり、継続的に機能の追加や改善が行われています。Bunを使用することで、高速なパフォーマンスと効率的な開発が実現されています。オープンソースプロジェクトとして、GitHubで公開されており、コミュニティからの貢献を歓迎しています。

個人のブログとソーシャルメディアの利点を組み合わせたHolloは、プライバシーを重視しながら、より広いコミュニティとのつながりを求める人々に適したプラットフォームとなっています。

#Hollo #ActivityPub #Mastodon #Markdown #Bun #Fedify #fedidev

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

I wanted to share some feedback on the documentation provided in the Highlighting Journalism on Mastodon blog post.

Specifically, in The technical section, the example code for the fediverse:creator meta tag is given as:

<meta name="fediverse:creator" content="@Gargron@mastodon.social" />

<meta name="fediverse:creator" content="Gargron@mastodon.social" />

Appreciate all you do for #Mastodon!

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

I wanted to share some feedback on the documentation provided in the Highlighting Journalism on Mastodon blog post.

Specifically, in The technical section, the example code for the fediverse:creator meta tag is given as:

<meta name="fediverse:creator" content="@Gargron@mastodon.social" />

<meta name="fediverse:creator" content="Gargron@mastodon.social" />

Appreciate all you do for #Mastodon!

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

I wanted to share some feedback on the documentation provided in the Highlighting Journalism on Mastodon blog post.

Specifically, in The technical section, the example code for the fediverse:creator meta tag is given as:

<meta name="fediverse:creator" content="@Gargron@mastodon.social" />

<meta name="fediverse:creator" content="Gargron@mastodon.social" />

Appreciate all you do for #Mastodon!

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

I wanted to share some feedback on the documentation provided in the Highlighting Journalism on Mastodon blog post.

Specifically, in The technical section, the example code for the fediverse:creator meta tag is given as:

<meta name="fediverse:creator" content="@Gargron@mastodon.social" />

<meta name="fediverse:creator" content="Gargron@mastodon.social" />

Appreciate all you do for #Mastodon!

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

I wanted to share some feedback on the documentation provided in the Highlighting Journalism on Mastodon blog post.

Specifically, in The technical section, the example code for the fediverse:creator meta tag is given as:

<meta name="fediverse:creator" content="@Gargron@mastodon.social" />

<meta name="fediverse:creator" content="Gargron@mastodon.social" />

Appreciate all you do for #Mastodon!

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're excited to announce the release of Fedify 1.5.0! This version brings several significant improvements to performance, configurability, and developer experience. Let's dive into what's new:

Two-Stage Fan-out Architecture for Efficient Activity Delivery

#Fedify now implements a smart fan-out mechanism for delivering activities to large audiences. This change is particularly valuable for accounts with many followers. When sending activities to many recipients, Fedify now creates a single consolidated message containing the activity payload and recipient list, which a background worker then processes to re-enqueue individual delivery tasks.

This architectural improvement delivers several benefits: Context.sendActivity() returns almost instantly even with thousands of recipients, memory consumption is dramatically reduced by avoiding payload duplication, UI responsiveness improves since web requests complete quickly, and the system maintains reliability with independent retry logic for each delivery.

For specific requirements, we've added a new fanout option with three settings:

// Configuring fan-out behavior
await ctx.sendActivity(
  { identifier: "alice" },
  recipients,
  activity,
  { fanout: "auto" }  // Default: automatic based on recipient count
  // Other options: "skip" (never use fan-out) or "force" (always use fan-out)
);

Canonical Origin Support for Multi-Domain Setups

You can now explicitly configure a canonical origin for your server, which is especially useful for multi-domain setups. This feature allows you to set different domains for WebFinger handles and #ActivityPub URIs, configured through the new origin option in createFederation(). This enhancement prevents unexpected URL construction when requests bypass proxies and improves security by ensuring consistent domain usage.

const federation = createFederation({
  // Use example.com for handles but ap.example.com for ActivityPub URIs
  origin: {
    handleHost: "example.com",
    webOrigin: "https://ap.example.com",
  },
  // Other options...
});

Optional Followers Collection Synchronization

Followers collection synchronization (FEP-8fcf) is now opt-in rather than automatic. This feature must now be explicitly enabled through the syncCollection option, giving developers more control over when to include followers collection digests. This change improves network efficiency by reducing unnecessary synchronization traffic.

await ctx.sendActivity(
  { identifier: sender },
  "followers",
  activity,
  { 
    preferSharedInbox: true,
    syncCollection: true,  // Explicitly enable collection synchronization
  }
);

Enhanced Key Format Compatibility

Key format support has been expanded for better interoperability. Fedify now accepts PEM-PKCS#1 format in addition to PEM-SPKI for RSA public keys. We've added importPkcs1() and importPem() functions for additional flexibility, which improves compatibility with a wider range of ActivityPub implementations.

Improved Key Selection Logic

The key selection process is now more intelligent. The fetchKey() function can now select the public key of an actor if keyId has no fragment and the actor has only one public key. This enhancement simplifies key handling in common scenarios and provides better compatibility with implementations that don't specify fragment identifiers.

New Authorization Options

Authorization handling has been enhanced with new options for the RequestContext.getSignedKey() and getSignedKeyOwner() methods. This provides more flexible control over authentication and authorization flows. We've deprecated older parameter-based approaches in favor of the more flexible method-based approach.

Efficient Bulk Message Queueing

Message queue performance is improved with bulk operations. We've added an optional enqueueMany() method to the MessageQueue interface, enabling efficient queueing of multiple messages in a single operation. This reduces overhead when processing batches of activities. All our message queue implementations have been updated to support this new operation:

If you're using any of these packages, make sure to update them alongside Fedify to take advantage of the more efficient bulk message queueing.

CLI Improvements

The Fedify command-line tools have been enhanced with an improved web interface for the fedify inbox command. We've added the Fedify logo with the cute dinosaur at the top of the page and made it easier to copy the fediverse handle of the ephemeral actor. We've also fixed issues with the web interface when installed via deno install from JSR.

Additional Improvements and Bug Fixes

Updated dependencies, including @js-temporal/polyfill to 0.5.0 for Node.js and Bun
Fixed bundler errors with uri-template-router on Rollup
Improved error handling and logging for document loader when KV store operations fail
Added more log messages using the LogTape library
Internalized the multibase package for better maintenance and compatibility

For the complete list of changes, please refer to the changelog.

To update to Fedify 1.5.0, run:

# For Deno
deno add jsr:@fedify/fedify@1.5.0

# For npm
npm  add     @fedify/fedify@1.5.0

# For Bun
bun  add     @fedify/fedify@1.5.0

Thank you to all contributors who helped make this release possible!

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

I received a heartwarming #testimonial about #Fedify today!

@bgl shared in the FediDev KR Discord server:

I had trouble finding good resources explaining ActivityPub, but after reading through the Fedify docs from start to finish, I feel like I've actually digested it.

If you want to learn ActivityPub efficiently, just read the Fedify docs from beginning to end.

This makes all the documentation work worthwhile. Glad our docs are helping people understand not just Fedify, but #ActivityPub itself.

#ActivityPub #DeSo #FediDev #FediDevs #Fediverse #SharedInbox

bgl gwyng

@bgl@hackers.pub

ActivityPub 효율적으로 익히려면 그냥 fedify 문서 첨부터 끝까지 읽으면 되는듯요

@reiver ⊼ (Charles)

@reiver@mastodon.social

The ActivityPub specification does not have an example of the "sharedInbox" field in use.

Although it does say "An optional endpoint..." — I suspect a lot of people won't know (with confidence) that it can go under the "endpoints" field. For example:

"endpoints": {
"sharedInbox": "https://social.example/inbox"
},

Especially if the person is still trying to understand ActivityPub, and isn't aware of the "endpoints" field yet.

ALT text details

sharedInbox An optional endpoint used for wide delivery of publicly addressed activities and activities sent to followers. sharedInbox endpoints SHOULD also be publicly readable OrderedCollection objects containing objects addressed to the Public special collection. Reading from the sharedInbox endpoint MUST NOT present objects which are not addressed to the Public endpoint.

@reiver ⊼ (Charles)

@reiver@mastodon.social

A reasonable ActivityPub / ActivityStreams API to schedule something to be posted in the future might be — to HTTP POST something to an account's outbox with the `published` field set to a date-time in the future.

#ActivityPub #ActivityStreams #DeSo #FediDev #FediDevs #Fediverse

@reiver ⊼ (Charles)

@reiver@mastodon.social

#ActivityPub #ActivityStreams #DeSo #FediDev #FediDevs #Fediverse

@reiver ⊼ (Charles)

@reiver@mastodon.social

#ActivityPub #ActivityStreams #DeSo #FediDev #FediDevs #Fediverse

@reiver ⊼ (Charles)

@reiver@mastodon.social

The ActivityPub specification does not have an example of the "sharedInbox" field in use.

Although it does say "An optional endpoint..." — I suspect a lot of people won't know (with confidence) that it can go under the "endpoints" field. For example:

"endpoints": {
"sharedInbox": "https://social.example/inbox"
},

Especially if the person is still trying to understand ActivityPub, and isn't aware of the "endpoints" field yet.

#ActivityPub #DeSo #FediDev #FediDevs #Fediverse #SharedInbox

ALT text details

@reiver ⊼ (Charles)

@reiver@mastodon.social

#ActivityPub #ActivityStreams #DeSo #FediDev #FediDevs #Fediverse

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

I wanted to share some feedback on the documentation provided in the Highlighting Journalism on Mastodon blog post.

Specifically, in The technical section, the example code for the fediverse:creator meta tag is given as:

<meta name="fediverse:creator" content="@Gargron@mastodon.social" />

<meta name="fediverse:creator" content="Gargron@mastodon.social" />

Appreciate all you do for #Mastodon!

#ActivityPub #ActivityStreams #DeSo #FediDev #FediDevs #Fediverse #JSONLD

@reiver ⊼ (Charles)

@reiver@mastodon.social

Currently, the way I am determining if content is valid ActivityPub / ActivityStreams content is —

№1:

Determining if it is valid JSON.

№2:

Checking if it has a "type" field.

And that is it.

@reiver ⊼ (Charles)

@reiver@mastodon.social

Dealing with JSON-LD would be easier in many ways if everything was defined inline.

Rather than having to get the content from a URL in the context, parse it, etc.

#ActivityPub #ActivityStreams #DeSo #FediDev #FediDevs #Fediverse #JSONLD

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

I wanted to share some feedback on the documentation provided in the Highlighting Journalism on Mastodon blog post.

Specifically, in The technical section, the example code for the fediverse:creator meta tag is given as:

<meta name="fediverse:creator" content="@Gargron@mastodon.social" />

<meta name="fediverse:creator" content="Gargron@mastodon.social" />

Appreciate all you do for #Mastodon!

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

I wanted to share some feedback on the documentation provided in the Highlighting Journalism on Mastodon blog post.

Specifically, in The technical section, the example code for the fediverse:creator meta tag is given as:

<meta name="fediverse:creator" content="@Gargron@mastodon.social" />

<meta name="fediverse:creator" content="Gargron@mastodon.social" />

Appreciate all you do for #Mastodon!

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

I wanted to share some feedback on the documentation provided in the Highlighting Journalism on Mastodon blog post.

Specifically, in The technical section, the example code for the fediverse:creator meta tag is given as:

<meta name="fediverse:creator" content="@Gargron@mastodon.social" />

<meta name="fediverse:creator" content="Gargron@mastodon.social" />

Appreciate all you do for #Mastodon!

Andrew Graves

@graves501@fosstodon.org

I've been thinking of contributing to the #fediverse for a while now, but I haven't really found a project or an idea that would fit my tech stack requirements yet.

Like Pixelfed and Loops have a PHP backend, but I'd rather contribute something with Golang or Typescript/Javascript.

Does anyone have some ideas?

Andrew Graves

@graves501@fosstodon.org

I've been thinking of contributing to the #fediverse for a while now, but I haven't really found a project or an idea that would fit my tech stack requirements yet.

Like Pixelfed and Loops have a PHP backend, but I'd rather contribute something with Golang or Typescript/Javascript.

Does anyone have some ideas?

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're excited to announce the release of Fedify 1.5.0! This version brings several significant improvements to performance, configurability, and developer experience. Let's dive into what's new:

Two-Stage Fan-out Architecture for Efficient Activity Delivery

For specific requirements, we've added a new fanout option with three settings:

// Configuring fan-out behavior
await ctx.sendActivity(
  { identifier: "alice" },
  recipients,
  activity,
  { fanout: "auto" }  // Default: automatic based on recipient count
  // Other options: "skip" (never use fan-out) or "force" (always use fan-out)
);

Canonical Origin Support for Multi-Domain Setups

const federation = createFederation({
  // Use example.com for handles but ap.example.com for ActivityPub URIs
  origin: {
    handleHost: "example.com",
    webOrigin: "https://ap.example.com",
  },
  // Other options...
});

Optional Followers Collection Synchronization

await ctx.sendActivity(
  { identifier: sender },
  "followers",
  activity,
  { 
    preferSharedInbox: true,
    syncCollection: true,  // Explicitly enable collection synchronization
  }
);

Enhanced Key Format Compatibility

Improved Key Selection Logic

New Authorization Options

Efficient Bulk Message Queueing

If you're using any of these packages, make sure to update them alongside Fedify to take advantage of the more efficient bulk message queueing.

CLI Improvements

Additional Improvements and Bug Fixes

Updated dependencies, including @js-temporal/polyfill to 0.5.0 for Node.js and Bun
Fixed bundler errors with uri-template-router on Rollup
Improved error handling and logging for document loader when KV store operations fail
Added more log messages using the LogTape library
Internalized the multibase package for better maintenance and compatibility

For the complete list of changes, please refer to the changelog.

To update to Fedify 1.5.0, run:

# For Deno
deno add jsr:@fedify/fedify@1.5.0

# For npm
npm  add     @fedify/fedify@1.5.0

# For Bun
bun  add     @fedify/fedify@1.5.0

Thank you to all contributors who helped make this release possible!

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're excited to announce the release of Fedify 1.5.0! This version brings several significant improvements to performance, configurability, and developer experience. Let's dive into what's new:

Two-Stage Fan-out Architecture for Efficient Activity Delivery

For specific requirements, we've added a new fanout option with three settings:

// Configuring fan-out behavior
await ctx.sendActivity(
  { identifier: "alice" },
  recipients,
  activity,
  { fanout: "auto" }  // Default: automatic based on recipient count
  // Other options: "skip" (never use fan-out) or "force" (always use fan-out)
);

Canonical Origin Support for Multi-Domain Setups

const federation = createFederation({
  // Use example.com for handles but ap.example.com for ActivityPub URIs
  origin: {
    handleHost: "example.com",
    webOrigin: "https://ap.example.com",
  },
  // Other options...
});

Optional Followers Collection Synchronization

await ctx.sendActivity(
  { identifier: sender },
  "followers",
  activity,
  { 
    preferSharedInbox: true,
    syncCollection: true,  // Explicitly enable collection synchronization
  }
);

Enhanced Key Format Compatibility

Improved Key Selection Logic

New Authorization Options

Efficient Bulk Message Queueing

If you're using any of these packages, make sure to update them alongside Fedify to take advantage of the more efficient bulk message queueing.

CLI Improvements

Additional Improvements and Bug Fixes

Updated dependencies, including @js-temporal/polyfill to 0.5.0 for Node.js and Bun
Fixed bundler errors with uri-template-router on Rollup
Improved error handling and logging for document loader when KV store operations fail
Added more log messages using the LogTape library
Internalized the multibase package for better maintenance and compatibility

For the complete list of changes, please refer to the changelog.

To update to Fedify 1.5.0, run:

# For Deno
deno add jsr:@fedify/fedify@1.5.0

# For npm
npm  add     @fedify/fedify@1.5.0

# For Bun
bun  add     @fedify/fedify@1.5.0

Thank you to all contributors who helped make this release possible!

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're excited to announce the release of Fedify 1.5.0! This version brings several significant improvements to performance, configurability, and developer experience. Let's dive into what's new:

Two-Stage Fan-out Architecture for Efficient Activity Delivery

For specific requirements, we've added a new fanout option with three settings:

// Configuring fan-out behavior
await ctx.sendActivity(
  { identifier: "alice" },
  recipients,
  activity,
  { fanout: "auto" }  // Default: automatic based on recipient count
  // Other options: "skip" (never use fan-out) or "force" (always use fan-out)
);

Canonical Origin Support for Multi-Domain Setups

const federation = createFederation({
  // Use example.com for handles but ap.example.com for ActivityPub URIs
  origin: {
    handleHost: "example.com",
    webOrigin: "https://ap.example.com",
  },
  // Other options...
});

Optional Followers Collection Synchronization

await ctx.sendActivity(
  { identifier: sender },
  "followers",
  activity,
  { 
    preferSharedInbox: true,
    syncCollection: true,  // Explicitly enable collection synchronization
  }
);

Enhanced Key Format Compatibility

Improved Key Selection Logic

New Authorization Options

Efficient Bulk Message Queueing

If you're using any of these packages, make sure to update them alongside Fedify to take advantage of the more efficient bulk message queueing.

CLI Improvements

Additional Improvements and Bug Fixes

Updated dependencies, including @js-temporal/polyfill to 0.5.0 for Node.js and Bun
Fixed bundler errors with uri-template-router on Rollup
Improved error handling and logging for document loader when KV store operations fail
Added more log messages using the LogTape library
Internalized the multibase package for better maintenance and compatibility

For the complete list of changes, please refer to the changelog.

To update to Fedify 1.5.0, run:

# For Deno
deno add jsr:@fedify/fedify@1.5.0

# For npm
npm  add     @fedify/fedify@1.5.0

# For Bun
bun  add     @fedify/fedify@1.5.0

Thank you to all contributors who helped make this release possible!

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

I received a heartwarming #testimonial about #Fedify today!

@bgl shared in the FediDev KR Discord server:

I had trouble finding good resources explaining ActivityPub, but after reading through the Fedify docs from start to finish, I feel like I've actually digested it.

If you want to learn ActivityPub efficiently, just read the Fedify docs from beginning to end.

This makes all the documentation work worthwhile. Glad our docs are helping people understand not just Fedify, but #ActivityPub itself.

bgl gwyng

@bgl@hackers.pub

ActivityPub 효율적으로 익히려면 그냥 fedify 문서 첨부터 끝까지 읽으면 되는듯요

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

I received a heartwarming #testimonial about #Fedify today!

@bgl shared in the FediDev KR Discord server:

I had trouble finding good resources explaining ActivityPub, but after reading through the Fedify docs from start to finish, I feel like I've actually digested it.

If you want to learn ActivityPub efficiently, just read the Fedify docs from beginning to end.

This makes all the documentation work worthwhile. Glad our docs are helping people understand not just Fedify, but #ActivityPub itself.

bgl gwyng

@bgl@hackers.pub

ActivityPub 효율적으로 익히려면 그냥 fedify 문서 첨부터 끝까지 읽으면 되는듯요

Andrew Graves

@graves501@fosstodon.org

I've been thinking of contributing to the #fediverse for a while now, but I haven't really found a project or an idea that would fit my tech stack requirements yet.

Like Pixelfed and Loops have a PHP backend, but I'd rather contribute something with Golang or Typescript/Javascript.

Does anyone have some ideas?

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

I received a heartwarming #testimonial about #Fedify today!

@bgl shared in the FediDev KR Discord server:

I had trouble finding good resources explaining ActivityPub, but after reading through the Fedify docs from start to finish, I feel like I've actually digested it.

If you want to learn ActivityPub efficiently, just read the Fedify docs from beginning to end.

This makes all the documentation work worthwhile. Glad our docs are helping people understand not just Fedify, but #ActivityPub itself.

bgl gwyng

@bgl@hackers.pub

ActivityPub 효율적으로 익히려면 그냥 fedify 문서 첨부터 끝까지 읽으면 되는듯요

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

I received a heartwarming #testimonial about #Fedify today!

@bgl shared in the FediDev KR Discord server:

I had trouble finding good resources explaining ActivityPub, but after reading through the Fedify docs from start to finish, I feel like I've actually digested it.

If you want to learn ActivityPub efficiently, just read the Fedify docs from beginning to end.

This makes all the documentation work worthwhile. Glad our docs are helping people understand not just Fedify, but #ActivityPub itself.

bgl gwyng

@bgl@hackers.pub

ActivityPub 효율적으로 익히려면 그냥 fedify 문서 첨부터 끝까지 읽으면 되는듯요

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

I received a heartwarming #testimonial about #Fedify today!

@bgl shared in the FediDev KR Discord server:

I had trouble finding good resources explaining ActivityPub, but after reading through the Fedify docs from start to finish, I feel like I've actually digested it.

If you want to learn ActivityPub efficiently, just read the Fedify docs from beginning to end.

This makes all the documentation work worthwhile. Glad our docs are helping people understand not just Fedify, but #ActivityPub itself.

bgl gwyng

@bgl@hackers.pub

ActivityPub 효율적으로 익히려면 그냥 fedify 문서 첨부터 끝까지 읽으면 되는듯요

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

I received a heartwarming #testimonial about #Fedify today!

@bgl shared in the FediDev KR Discord server:

I had trouble finding good resources explaining ActivityPub, but after reading through the Fedify docs from start to finish, I feel like I've actually digested it.

If you want to learn ActivityPub efficiently, just read the Fedify docs from beginning to end.

This makes all the documentation work worthwhile. Glad our docs are helping people understand not just Fedify, but #ActivityPub itself.

bgl gwyng

@bgl@hackers.pub

ActivityPub 효율적으로 익히려면 그냥 fedify 문서 첨부터 끝까지 읽으면 되는듯요

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

I received a heartwarming #testimonial about #Fedify today!

@bgl shared in the FediDev KR Discord server:

I had trouble finding good resources explaining ActivityPub, but after reading through the Fedify docs from start to finish, I feel like I've actually digested it.

If you want to learn ActivityPub efficiently, just read the Fedify docs from beginning to end.

This makes all the documentation work worthwhile. Glad our docs are helping people understand not just Fedify, but #ActivityPub itself.

bgl gwyng

@bgl@hackers.pub

ActivityPub 효율적으로 익히려면 그냥 fedify 문서 첨부터 끝까지 읽으면 되는듯요

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

I received a heartwarming #testimonial about #Fedify today!

@bgl shared in the FediDev KR Discord server:

I had trouble finding good resources explaining ActivityPub, but after reading through the Fedify docs from start to finish, I feel like I've actually digested it.

If you want to learn ActivityPub efficiently, just read the Fedify docs from beginning to end.

This makes all the documentation work worthwhile. Glad our docs are helping people understand not just Fedify, but #ActivityPub itself.

bgl gwyng

@bgl@hackers.pub

ActivityPub 효율적으로 익히려면 그냥 fedify 문서 첨부터 끝까지 읽으면 되는듯요

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

I received a heartwarming #testimonial about #Fedify today!

@bgl shared in the FediDev KR Discord server:

I had trouble finding good resources explaining ActivityPub, but after reading through the Fedify docs from start to finish, I feel like I've actually digested it.

If you want to learn ActivityPub efficiently, just read the Fedify docs from beginning to end.

This makes all the documentation work worthwhile. Glad our docs are helping people understand not just Fedify, but #ActivityPub itself.

bgl gwyng

@bgl@hackers.pub

ActivityPub 효율적으로 익히려면 그냥 fedify 문서 첨부터 끝까지 읽으면 되는듯요

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

I received a heartwarming #testimonial about #Fedify today!

@bgl shared in the FediDev KR Discord server:

I had trouble finding good resources explaining ActivityPub, but after reading through the Fedify docs from start to finish, I feel like I've actually digested it.

If you want to learn ActivityPub efficiently, just read the Fedify docs from beginning to end.

This makes all the documentation work worthwhile. Glad our docs are helping people understand not just Fedify, but #ActivityPub itself.

bgl gwyng

@bgl@hackers.pub

ActivityPub 효율적으로 익히려면 그냥 fedify 문서 첨부터 끝까지 읽으면 되는듯요

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

I received a heartwarming #testimonial about #Fedify today!

@bgl shared in the FediDev KR Discord server:

I had trouble finding good resources explaining ActivityPub, but after reading through the Fedify docs from start to finish, I feel like I've actually digested it.

If you want to learn ActivityPub efficiently, just read the Fedify docs from beginning to end.

This makes all the documentation work worthwhile. Glad our docs are helping people understand not just Fedify, but #ActivityPub itself.

bgl gwyng

@bgl@hackers.pub

ActivityPub 효율적으로 익히려면 그냥 fedify 문서 첨부터 끝까지 읽으면 되는듯요

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

I received a heartwarming #testimonial about #Fedify today!

@bgl shared in the FediDev KR Discord server:

I had trouble finding good resources explaining ActivityPub, but after reading through the Fedify docs from start to finish, I feel like I've actually digested it.

If you want to learn ActivityPub efficiently, just read the Fedify docs from beginning to end.

This makes all the documentation work worthwhile. Glad our docs are helping people understand not just Fedify, but #ActivityPub itself.

bgl gwyng

@bgl@hackers.pub

ActivityPub 효율적으로 익히려면 그냥 fedify 문서 첨부터 끝까지 읽으면 되는듯요

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're excited to announce the release of Fedify 1.5.0! This version brings several significant improvements to performance, configurability, and developer experience. Let's dive into what's new:

Two-Stage Fan-out Architecture for Efficient Activity Delivery

For specific requirements, we've added a new fanout option with three settings:

// Configuring fan-out behavior
await ctx.sendActivity(
  { identifier: "alice" },
  recipients,
  activity,
  { fanout: "auto" }  // Default: automatic based on recipient count
  // Other options: "skip" (never use fan-out) or "force" (always use fan-out)
);

Canonical Origin Support for Multi-Domain Setups

const federation = createFederation({
  // Use example.com for handles but ap.example.com for ActivityPub URIs
  origin: {
    handleHost: "example.com",
    webOrigin: "https://ap.example.com",
  },
  // Other options...
});

Optional Followers Collection Synchronization

await ctx.sendActivity(
  { identifier: sender },
  "followers",
  activity,
  { 
    preferSharedInbox: true,
    syncCollection: true,  // Explicitly enable collection synchronization
  }
);

Enhanced Key Format Compatibility

Improved Key Selection Logic

New Authorization Options

Efficient Bulk Message Queueing

If you're using any of these packages, make sure to update them alongside Fedify to take advantage of the more efficient bulk message queueing.

CLI Improvements

Additional Improvements and Bug Fixes

Updated dependencies, including @js-temporal/polyfill to 0.5.0 for Node.js and Bun
Fixed bundler errors with uri-template-router on Rollup
Improved error handling and logging for document loader when KV store operations fail
Added more log messages using the LogTape library
Internalized the multibase package for better maintenance and compatibility

For the complete list of changes, please refer to the changelog.

To update to Fedify 1.5.0, run:

# For Deno
deno add jsr:@fedify/fedify@1.5.0

# For npm
npm  add     @fedify/fedify@1.5.0

# For Bun
bun  add     @fedify/fedify@1.5.0

Thank you to all contributors who helped make this release possible!

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're excited to announce the release of Fedify 1.5.0! This version brings several significant improvements to performance, configurability, and developer experience. Let's dive into what's new:

Two-Stage Fan-out Architecture for Efficient Activity Delivery

For specific requirements, we've added a new fanout option with three settings:

// Configuring fan-out behavior
await ctx.sendActivity(
  { identifier: "alice" },
  recipients,
  activity,
  { fanout: "auto" }  // Default: automatic based on recipient count
  // Other options: "skip" (never use fan-out) or "force" (always use fan-out)
);

Canonical Origin Support for Multi-Domain Setups

const federation = createFederation({
  // Use example.com for handles but ap.example.com for ActivityPub URIs
  origin: {
    handleHost: "example.com",
    webOrigin: "https://ap.example.com",
  },
  // Other options...
});

Optional Followers Collection Synchronization

await ctx.sendActivity(
  { identifier: sender },
  "followers",
  activity,
  { 
    preferSharedInbox: true,
    syncCollection: true,  // Explicitly enable collection synchronization
  }
);

Enhanced Key Format Compatibility

Improved Key Selection Logic

New Authorization Options

Efficient Bulk Message Queueing

If you're using any of these packages, make sure to update them alongside Fedify to take advantage of the more efficient bulk message queueing.

CLI Improvements

Additional Improvements and Bug Fixes

Updated dependencies, including @js-temporal/polyfill to 0.5.0 for Node.js and Bun
Fixed bundler errors with uri-template-router on Rollup
Improved error handling and logging for document loader when KV store operations fail
Added more log messages using the LogTape library
Internalized the multibase package for better maintenance and compatibility

For the complete list of changes, please refer to the changelog.

To update to Fedify 1.5.0, run:

# For Deno
deno add jsr:@fedify/fedify@1.5.0

# For npm
npm  add     @fedify/fedify@1.5.0

# For Bun
bun  add     @fedify/fedify@1.5.0

Thank you to all contributors who helped make this release possible!

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're excited to announce the release of Fedify 1.5.0! This version brings several significant improvements to performance, configurability, and developer experience. Let's dive into what's new:

Two-Stage Fan-out Architecture for Efficient Activity Delivery

For specific requirements, we've added a new fanout option with three settings:

// Configuring fan-out behavior
await ctx.sendActivity(
  { identifier: "alice" },
  recipients,
  activity,
  { fanout: "auto" }  // Default: automatic based on recipient count
  // Other options: "skip" (never use fan-out) or "force" (always use fan-out)
);

Canonical Origin Support for Multi-Domain Setups

const federation = createFederation({
  // Use example.com for handles but ap.example.com for ActivityPub URIs
  origin: {
    handleHost: "example.com",
    webOrigin: "https://ap.example.com",
  },
  // Other options...
});

Optional Followers Collection Synchronization

await ctx.sendActivity(
  { identifier: sender },
  "followers",
  activity,
  { 
    preferSharedInbox: true,
    syncCollection: true,  // Explicitly enable collection synchronization
  }
);

Enhanced Key Format Compatibility

Improved Key Selection Logic

New Authorization Options

Efficient Bulk Message Queueing

If you're using any of these packages, make sure to update them alongside Fedify to take advantage of the more efficient bulk message queueing.

CLI Improvements

Additional Improvements and Bug Fixes

Updated dependencies, including @js-temporal/polyfill to 0.5.0 for Node.js and Bun
Fixed bundler errors with uri-template-router on Rollup
Improved error handling and logging for document loader when KV store operations fail
Added more log messages using the LogTape library
Internalized the multibase package for better maintenance and compatibility

For the complete list of changes, please refer to the changelog.

To update to Fedify 1.5.0, run:

# For Deno
deno add jsr:@fedify/fedify@1.5.0

# For npm
npm  add     @fedify/fedify@1.5.0

# For Bun
bun  add     @fedify/fedify@1.5.0

Thank you to all contributors who helped make this release possible!

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're excited to announce the release of Fedify 1.5.0! This version brings several significant improvements to performance, configurability, and developer experience. Let's dive into what's new:

Two-Stage Fan-out Architecture for Efficient Activity Delivery

For specific requirements, we've added a new fanout option with three settings:

// Configuring fan-out behavior
await ctx.sendActivity(
  { identifier: "alice" },
  recipients,
  activity,
  { fanout: "auto" }  // Default: automatic based on recipient count
  // Other options: "skip" (never use fan-out) or "force" (always use fan-out)
);

Canonical Origin Support for Multi-Domain Setups

const federation = createFederation({
  // Use example.com for handles but ap.example.com for ActivityPub URIs
  origin: {
    handleHost: "example.com",
    webOrigin: "https://ap.example.com",
  },
  // Other options...
});

Optional Followers Collection Synchronization

await ctx.sendActivity(
  { identifier: sender },
  "followers",
  activity,
  { 
    preferSharedInbox: true,
    syncCollection: true,  // Explicitly enable collection synchronization
  }
);

Enhanced Key Format Compatibility

Improved Key Selection Logic

New Authorization Options

Efficient Bulk Message Queueing

If you're using any of these packages, make sure to update them alongside Fedify to take advantage of the more efficient bulk message queueing.

CLI Improvements

Additional Improvements and Bug Fixes

Updated dependencies, including @js-temporal/polyfill to 0.5.0 for Node.js and Bun
Fixed bundler errors with uri-template-router on Rollup
Improved error handling and logging for document loader when KV store operations fail
Added more log messages using the LogTape library
Internalized the multibase package for better maintenance and compatibility

For the complete list of changes, please refer to the changelog.

To update to Fedify 1.5.0, run:

# For Deno
deno add jsr:@fedify/fedify@1.5.0

# For npm
npm  add     @fedify/fedify@1.5.0

# For Bun
bun  add     @fedify/fedify@1.5.0

Thank you to all contributors who helped make this release possible!

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're excited to announce the release of Fedify 1.5.0! This version brings several significant improvements to performance, configurability, and developer experience. Let's dive into what's new:

Two-Stage Fan-out Architecture for Efficient Activity Delivery

For specific requirements, we've added a new fanout option with three settings:

// Configuring fan-out behavior
await ctx.sendActivity(
  { identifier: "alice" },
  recipients,
  activity,
  { fanout: "auto" }  // Default: automatic based on recipient count
  // Other options: "skip" (never use fan-out) or "force" (always use fan-out)
);

Canonical Origin Support for Multi-Domain Setups

const federation = createFederation({
  // Use example.com for handles but ap.example.com for ActivityPub URIs
  origin: {
    handleHost: "example.com",
    webOrigin: "https://ap.example.com",
  },
  // Other options...
});

Optional Followers Collection Synchronization

await ctx.sendActivity(
  { identifier: sender },
  "followers",
  activity,
  { 
    preferSharedInbox: true,
    syncCollection: true,  // Explicitly enable collection synchronization
  }
);

Enhanced Key Format Compatibility

Improved Key Selection Logic

New Authorization Options

Efficient Bulk Message Queueing

If you're using any of these packages, make sure to update them alongside Fedify to take advantage of the more efficient bulk message queueing.

CLI Improvements

Additional Improvements and Bug Fixes

Updated dependencies, including @js-temporal/polyfill to 0.5.0 for Node.js and Bun
Fixed bundler errors with uri-template-router on Rollup
Improved error handling and logging for document loader when KV store operations fail
Added more log messages using the LogTape library
Internalized the multibase package for better maintenance and compatibility

For the complete list of changes, please refer to the changelog.

To update to Fedify 1.5.0, run:

# For Deno
deno add jsr:@fedify/fedify@1.5.0

# For npm
npm  add     @fedify/fedify@1.5.0

# For Bun
bun  add     @fedify/fedify@1.5.0

Thank you to all contributors who helped make this release possible!

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're excited to announce the release of Fedify 1.5.0! This version brings several significant improvements to performance, configurability, and developer experience. Let's dive into what's new:

Two-Stage Fan-out Architecture for Efficient Activity Delivery

For specific requirements, we've added a new fanout option with three settings:

// Configuring fan-out behavior
await ctx.sendActivity(
  { identifier: "alice" },
  recipients,
  activity,
  { fanout: "auto" }  // Default: automatic based on recipient count
  // Other options: "skip" (never use fan-out) or "force" (always use fan-out)
);

Canonical Origin Support for Multi-Domain Setups

const federation = createFederation({
  // Use example.com for handles but ap.example.com for ActivityPub URIs
  origin: {
    handleHost: "example.com",
    webOrigin: "https://ap.example.com",
  },
  // Other options...
});

Optional Followers Collection Synchronization

await ctx.sendActivity(
  { identifier: sender },
  "followers",
  activity,
  { 
    preferSharedInbox: true,
    syncCollection: true,  // Explicitly enable collection synchronization
  }
);

Enhanced Key Format Compatibility

Improved Key Selection Logic

New Authorization Options

Efficient Bulk Message Queueing

If you're using any of these packages, make sure to update them alongside Fedify to take advantage of the more efficient bulk message queueing.

CLI Improvements

Additional Improvements and Bug Fixes

Updated dependencies, including @js-temporal/polyfill to 0.5.0 for Node.js and Bun
Fixed bundler errors with uri-template-router on Rollup
Improved error handling and logging for document loader when KV store operations fail
Added more log messages using the LogTape library
Internalized the multibase package for better maintenance and compatibility

For the complete list of changes, please refer to the changelog.

To update to Fedify 1.5.0, run:

# For Deno
deno add jsr:@fedify/fedify@1.5.0

# For npm
npm  add     @fedify/fedify@1.5.0

# For Bun
bun  add     @fedify/fedify@1.5.0

Thank you to all contributors who helped make this release possible!

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're excited to announce the release of Fedify 1.5.0! This version brings several significant improvements to performance, configurability, and developer experience. Let's dive into what's new:

Two-Stage Fan-out Architecture for Efficient Activity Delivery

For specific requirements, we've added a new fanout option with three settings:

// Configuring fan-out behavior
await ctx.sendActivity(
  { identifier: "alice" },
  recipients,
  activity,
  { fanout: "auto" }  // Default: automatic based on recipient count
  // Other options: "skip" (never use fan-out) or "force" (always use fan-out)
);

Canonical Origin Support for Multi-Domain Setups

const federation = createFederation({
  // Use example.com for handles but ap.example.com for ActivityPub URIs
  origin: {
    handleHost: "example.com",
    webOrigin: "https://ap.example.com",
  },
  // Other options...
});

Optional Followers Collection Synchronization

await ctx.sendActivity(
  { identifier: sender },
  "followers",
  activity,
  { 
    preferSharedInbox: true,
    syncCollection: true,  // Explicitly enable collection synchronization
  }
);

Enhanced Key Format Compatibility

Improved Key Selection Logic

New Authorization Options

Efficient Bulk Message Queueing

If you're using any of these packages, make sure to update them alongside Fedify to take advantage of the more efficient bulk message queueing.

CLI Improvements

Additional Improvements and Bug Fixes

Updated dependencies, including @js-temporal/polyfill to 0.5.0 for Node.js and Bun
Fixed bundler errors with uri-template-router on Rollup
Improved error handling and logging for document loader when KV store operations fail
Added more log messages using the LogTape library
Internalized the multibase package for better maintenance and compatibility

For the complete list of changes, please refer to the changelog.

To update to Fedify 1.5.0, run:

# For Deno
deno add jsr:@fedify/fedify@1.5.0

# For npm
npm  add     @fedify/fedify@1.5.0

# For Bun
bun  add     @fedify/fedify@1.5.0

Thank you to all contributors who helped make this release possible!

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're excited to announce the release of Fedify 1.5.0! This version brings several significant improvements to performance, configurability, and developer experience. Let's dive into what's new:

Two-Stage Fan-out Architecture for Efficient Activity Delivery

For specific requirements, we've added a new fanout option with three settings:

// Configuring fan-out behavior
await ctx.sendActivity(
  { identifier: "alice" },
  recipients,
  activity,
  { fanout: "auto" }  // Default: automatic based on recipient count
  // Other options: "skip" (never use fan-out) or "force" (always use fan-out)
);

Canonical Origin Support for Multi-Domain Setups

const federation = createFederation({
  // Use example.com for handles but ap.example.com for ActivityPub URIs
  origin: {
    handleHost: "example.com",
    webOrigin: "https://ap.example.com",
  },
  // Other options...
});

Optional Followers Collection Synchronization

await ctx.sendActivity(
  { identifier: sender },
  "followers",
  activity,
  { 
    preferSharedInbox: true,
    syncCollection: true,  // Explicitly enable collection synchronization
  }
);

Enhanced Key Format Compatibility

Improved Key Selection Logic

New Authorization Options

Efficient Bulk Message Queueing

If you're using any of these packages, make sure to update them alongside Fedify to take advantage of the more efficient bulk message queueing.

CLI Improvements

Additional Improvements and Bug Fixes

Updated dependencies, including @js-temporal/polyfill to 0.5.0 for Node.js and Bun
Fixed bundler errors with uri-template-router on Rollup
Improved error handling and logging for document loader when KV store operations fail
Added more log messages using the LogTape library
Internalized the multibase package for better maintenance and compatibility

For the complete list of changes, please refer to the changelog.

To update to Fedify 1.5.0, run:

# For Deno
deno add jsr:@fedify/fedify@1.5.0

# For npm
npm  add     @fedify/fedify@1.5.0

# For Bun
bun  add     @fedify/fedify@1.5.0

Thank you to all contributors who helped make this release possible!

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're excited to announce the release of Fedify 1.5.0! This version brings several significant improvements to performance, configurability, and developer experience. Let's dive into what's new:

Two-Stage Fan-out Architecture for Efficient Activity Delivery

For specific requirements, we've added a new fanout option with three settings:

// Configuring fan-out behavior
await ctx.sendActivity(
  { identifier: "alice" },
  recipients,
  activity,
  { fanout: "auto" }  // Default: automatic based on recipient count
  // Other options: "skip" (never use fan-out) or "force" (always use fan-out)
);

Canonical Origin Support for Multi-Domain Setups

const federation = createFederation({
  // Use example.com for handles but ap.example.com for ActivityPub URIs
  origin: {
    handleHost: "example.com",
    webOrigin: "https://ap.example.com",
  },
  // Other options...
});

Optional Followers Collection Synchronization

await ctx.sendActivity(
  { identifier: sender },
  "followers",
  activity,
  { 
    preferSharedInbox: true,
    syncCollection: true,  // Explicitly enable collection synchronization
  }
);

Enhanced Key Format Compatibility

Improved Key Selection Logic

New Authorization Options

Efficient Bulk Message Queueing

If you're using any of these packages, make sure to update them alongside Fedify to take advantage of the more efficient bulk message queueing.

CLI Improvements

Additional Improvements and Bug Fixes

Updated dependencies, including @js-temporal/polyfill to 0.5.0 for Node.js and Bun
Fixed bundler errors with uri-template-router on Rollup
Improved error handling and logging for document loader when KV store operations fail
Added more log messages using the LogTape library
Internalized the multibase package for better maintenance and compatibility

For the complete list of changes, please refer to the changelog.

To update to Fedify 1.5.0, run:

# For Deno
deno add jsr:@fedify/fedify@1.5.0

# For npm
npm  add     @fedify/fedify@1.5.0

# For Bun
bun  add     @fedify/fedify@1.5.0

Thank you to all contributors who helped make this release possible!

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're excited to announce the release of Fedify 1.5.0! This version brings several significant improvements to performance, configurability, and developer experience. Let's dive into what's new:

Two-Stage Fan-out Architecture for Efficient Activity Delivery

For specific requirements, we've added a new fanout option with three settings:

// Configuring fan-out behavior
await ctx.sendActivity(
  { identifier: "alice" },
  recipients,
  activity,
  { fanout: "auto" }  // Default: automatic based on recipient count
  // Other options: "skip" (never use fan-out) or "force" (always use fan-out)
);

Canonical Origin Support for Multi-Domain Setups

const federation = createFederation({
  // Use example.com for handles but ap.example.com for ActivityPub URIs
  origin: {
    handleHost: "example.com",
    webOrigin: "https://ap.example.com",
  },
  // Other options...
});

Optional Followers Collection Synchronization

await ctx.sendActivity(
  { identifier: sender },
  "followers",
  activity,
  { 
    preferSharedInbox: true,
    syncCollection: true,  // Explicitly enable collection synchronization
  }
);

Enhanced Key Format Compatibility

Improved Key Selection Logic

New Authorization Options

Efficient Bulk Message Queueing

If you're using any of these packages, make sure to update them alongside Fedify to take advantage of the more efficient bulk message queueing.

CLI Improvements

Additional Improvements and Bug Fixes

Updated dependencies, including @js-temporal/polyfill to 0.5.0 for Node.js and Bun
Fixed bundler errors with uri-template-router on Rollup
Improved error handling and logging for document loader when KV store operations fail
Added more log messages using the LogTape library
Internalized the multibase package for better maintenance and compatibility

For the complete list of changes, please refer to the changelog.

To update to Fedify 1.5.0, run:

# For Deno
deno add jsr:@fedify/fedify@1.5.0

# For npm
npm  add     @fedify/fedify@1.5.0

# For Bun
bun  add     @fedify/fedify@1.5.0

Thank you to all contributors who helped make this release possible!

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're excited to announce the release of Fedify 1.5.0! This version brings several significant improvements to performance, configurability, and developer experience. Let's dive into what's new:

Two-Stage Fan-out Architecture for Efficient Activity Delivery

For specific requirements, we've added a new fanout option with three settings:

// Configuring fan-out behavior
await ctx.sendActivity(
  { identifier: "alice" },
  recipients,
  activity,
  { fanout: "auto" }  // Default: automatic based on recipient count
  // Other options: "skip" (never use fan-out) or "force" (always use fan-out)
);

Canonical Origin Support for Multi-Domain Setups

const federation = createFederation({
  // Use example.com for handles but ap.example.com for ActivityPub URIs
  origin: {
    handleHost: "example.com",
    webOrigin: "https://ap.example.com",
  },
  // Other options...
});

Optional Followers Collection Synchronization

await ctx.sendActivity(
  { identifier: sender },
  "followers",
  activity,
  { 
    preferSharedInbox: true,
    syncCollection: true,  // Explicitly enable collection synchronization
  }
);

Enhanced Key Format Compatibility

Improved Key Selection Logic

New Authorization Options

Efficient Bulk Message Queueing

If you're using any of these packages, make sure to update them alongside Fedify to take advantage of the more efficient bulk message queueing.

CLI Improvements

Additional Improvements and Bug Fixes

Updated dependencies, including @js-temporal/polyfill to 0.5.0 for Node.js and Bun
Fixed bundler errors with uri-template-router on Rollup
Improved error handling and logging for document loader when KV store operations fail
Added more log messages using the LogTape library
Internalized the multibase package for better maintenance and compatibility

For the complete list of changes, please refer to the changelog.

To update to Fedify 1.5.0, run:

# For Deno
deno add jsr:@fedify/fedify@1.5.0

# For npm
npm  add     @fedify/fedify@1.5.0

# For Bun
bun  add     @fedify/fedify@1.5.0

Thank you to all contributors who helped make this release possible!

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're excited to announce the release of Fedify 1.5.0! This version brings several significant improvements to performance, configurability, and developer experience. Let's dive into what's new:

Two-Stage Fan-out Architecture for Efficient Activity Delivery

For specific requirements, we've added a new fanout option with three settings:

// Configuring fan-out behavior
await ctx.sendActivity(
  { identifier: "alice" },
  recipients,
  activity,
  { fanout: "auto" }  // Default: automatic based on recipient count
  // Other options: "skip" (never use fan-out) or "force" (always use fan-out)
);

Canonical Origin Support for Multi-Domain Setups

const federation = createFederation({
  // Use example.com for handles but ap.example.com for ActivityPub URIs
  origin: {
    handleHost: "example.com",
    webOrigin: "https://ap.example.com",
  },
  // Other options...
});

Optional Followers Collection Synchronization

await ctx.sendActivity(
  { identifier: sender },
  "followers",
  activity,
  { 
    preferSharedInbox: true,
    syncCollection: true,  // Explicitly enable collection synchronization
  }
);

Enhanced Key Format Compatibility

Improved Key Selection Logic

New Authorization Options

Efficient Bulk Message Queueing

If you're using any of these packages, make sure to update them alongside Fedify to take advantage of the more efficient bulk message queueing.

CLI Improvements

Additional Improvements and Bug Fixes

Updated dependencies, including @js-temporal/polyfill to 0.5.0 for Node.js and Bun
Fixed bundler errors with uri-template-router on Rollup
Improved error handling and logging for document loader when KV store operations fail
Added more log messages using the LogTape library
Internalized the multibase package for better maintenance and compatibility

For the complete list of changes, please refer to the changelog.

To update to Fedify 1.5.0, run:

# For Deno
deno add jsr:@fedify/fedify@1.5.0

# For npm
npm  add     @fedify/fedify@1.5.0

# For Bun
bun  add     @fedify/fedify@1.5.0

Thank you to all contributors who helped make this release possible!

A pull request was just merged in Mastodon that fixes a critical bug in their follower synchronization mechanism.

@reiver ⊼ (Charles)

@reiver@mastodon.social

The ActivityPub specification does not have an example of the "sharedInbox" field in use.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

I just discovered why some of my followers from larger #Mastodon instances (like mastodon.social) would mysteriously unfollow me after a while!

Turns out Mastodon implements the FEP-8fcf specification (Followers collection synchronization across servers), but it expected all followers to be in a single page collection. When followers were split across multiple pages, it would only see the first page and incorrectly remove all followers from subsequent pages!

This explains so much about the strange behavior I've been seeing with #Hollo and other #Fedify-based servers over the past few months. Some people would follow me from large instances, then mysteriously unfollow later without any action on their part.

Thankfully this fix has been marked for backporting, so it should appear in an upcoming patch release rather than waiting for the next major version. Great news for all of us building on #ActivityPub!

This is why I love open source—we can identify, understand, and fix these kinds of interoperability issues together. 😊

A pull request was just merged in Mastodon that fixes a critical bug in their follower synchronization mechanism.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

I just discovered why some of my followers from larger #Mastodon instances (like mastodon.social) would mysteriously unfollow me after a while!

This is why I love open source—we can identify, understand, and fix these kinds of interoperability issues together. 😊

#ActivityPub #ActivityStreams #DeSo #FediDev #FediDevs #Fediverse

@reiver ⊼ (Charles)

@reiver@mastodon.social · Reply to @reiver ⊼ (Charles) :batman:'s post

I think there is a need for a "dumb" document format.

HTML is no longer that.

Markdown probably isn't it.

No one really uses enriched-text (IETF RFC 1896).

(I prefer wiki like formats, for various reasons, but —)

I don't think there is an obvious choice for a "dumb" document format, right now.

@reiver ⊼ (Charles)

@reiver@mastodon.social

I think HTML being the default content type for ActivityPub / ActivityStreams is unfortunate in some ways.

HTML was originally a "dumb" document format. But, it is now a "smart" application format — with privacy & security concerns.

https://mastodon.social/@reiver/108237663610634862

You should NOT just take whatever HTML is in the 'content', and put it in the web-browser to view it.

You have to sanitize it. Or, render (unsafe) HTML to (safe) HTML.

#ActivityPub #ActivityStreams #DeSo #FediDev #FediDevs #Fediverse

@reiver ⊼ (Charles)

@reiver@mastodon.social

@reiver@mastodon.social · Reply to @reiver ⊼ (Charles) :batman:'s post

I think it would be better for the Fediverse if back-end servers and front-end clients were not only decoupled, but separate projects.

https://mastodon.social/@reiver/111030466318220760

https://mastodon.social/@reiver/111223320383410948

https://mastodon.social/@reiver/112746651794313514

https://mastodon.social/@reiver/112921051726027193

People being able to have a service acting on their behalf as (at least part of) the back-end could be a path towards this back-end / front-end decoupling and separation.

@reiver ⊼ (Charles)

@reiver@mastodon.social · Reply to @reiver ⊼ (Charles) :batman:'s post

In fact, it is an old idea. I remember ideas like this floating around in the 1990s. Including in the P2P scene.

(It is common for ideas to get rediscovered over and over and over again. Different people trying to solve similar problems, and independently coming up with similar solutions.)

https://mastodon.social/@reiver/114216978158867263

@reiver ⊼ (Charles)

@reiver@mastodon.social

In many ways, I like the basic idea of ActivityPods, Bluesky PDS, Account Abstraction.

A service acting on your behalf, and in many ways representing you (the user), with other software.

And something to which data gets "attached".

wakest ⁂

@liaizon@social.wake.st

Theres a new interview with @hongminhee (of @fedify, @hollo, and now #Ghost fame). It's in with Korean subtitles but quite readable with YouTube's autogenerated English subs.

https://hollo.social/@hongminhee/0195a85a-6a29-71fa-a60f-3e79c1295b05 #fediverse #fedidev

wakest ⁂

@liaizon@social.wake.st

Theres a new interview with @hongminhee (of @fedify, @hollo, and now #Ghost fame). It's in with Korean subtitles but quite readable with YouTube's autogenerated English subs.

https://hollo.social/@hongminhee/0195a85a-6a29-71fa-a60f-3e79c1295b05 #fediverse #fedidev

@reiver ⊼ (Charles)

@reiver@mastodon.social · Reply to @reiver ⊼ (Charles) :batman:'s post

ActivityPods

But — then, ActivityPods seems to have a spec:

https://activitypods.org/specs/activitypods

And talks about supporting other specs:

https://activitypods.org/specs/activitypub

https://activitypods.org/specs/solid

#ActivityPods #DeSo #FediDev #FediDevs #Fediverse #FOSDEM2025 #SocialWebFOSDEM

@reiver ⊼ (Charles)

@reiver@mastodon.social · Reply to @reiver ⊼ (Charles) :batman:'s post

ActivityPods

When I re-watch this talk (that was originally presented at FOSDEM 2025) —

https://peertube.virtual-assembly.org/videos/watch/a8dc6bcc-8cef-485e-bfd8-438f1bfc04d2

— it seems as if ActivityPods is software.

But —

#ActivityPods #DeSo #FediDev #FediDevs #Fediverse #FOSDEM2025 #SocialWebFOSDEM

@reiver ⊼ (Charles)

@reiver@mastodon.social

ActivityPods

One thing that still isn't completely clear to me about ActivityPods is —

Is ActivityPods a specification?, or is ActivityPods software?

#ActivityPods #DeSo #FediDev #FediDevs #Fediverse #FOSDEM2025 #SocialWebFOSDEM

@reiver ⊼ (Charles)

@reiver@mastodon.social

programming

There is a comparison between the (proposed) ActivityPods and the Bluesky PDS.

(I am not the first person to say that.)

But, I think there is also some comparison between both of those and Account Abstraction in the EVM space.

All, in some ways, have a service acting on your behalf and in many ways representing you (the user), with other software.

#AccountAbstraction #ActivityPods #BlueskyPDS #DeSo #Ethereum #EVM #FediDev #FediDevs #Fediverse #SmartContract

@reiver ⊼ (Charles)

@reiver@mastodon.social

programming, did key

@hongminhee@hollo.social

이番(번)에 @lqez 님의 《우리의 코드를 찾아서》에 出演(출연)하여 #페디버스, #ActivityPub, #Fedify, #Hollo 等(등)에 關(관)해 이야기를 나눴습니다. Fedify와 Hollo의 開發(개발) 祕話(비화) 같은 게 궁금하시다면 한 番(번) 보셔도 재밌을지도 모르겠습니다. ㅎㅎㅎ

#연합우주 #fediverse #fedidev

洪民憙 (Hong Minhee)

@hongminhee@hollo.social · Reply to 洪民憙 (Hong Minhee)'s post

今回、@lqez さんの『我々のコードを求めて』というYouTubeに出演させていただき、#フェディバース、#ActivityPub、#Fedify、#Hollo 等についてお話させていただきました。日本語字幕が用意されていますので、FedifyやHolloの開発秘話などが気になる方はぜひご覧ください！

@box464@mastodon.social

The code behind this would make good developers cry. But I have fun fiddling with it on the weekends, and have learned tons about Vue.js

#FediDev #MastodonAPI

ALT text details

A webpage displaying a collection of posts organized by authors and tags. It shows a total of 21 bookmarks, with sections for different authors and various tags related to topics like "fediverse," "activitypub," and "mastodon." A linked video is also included at the bottom.

@reiver ⊼ (Charles)

@reiver@mastodon.social

What about the Fediverse or Mastodon, etc, frustrates you or confuses you?

#DeSo #FediDev #FediDevs #Fediverse #FediverseUX #FediUX #Mastodon

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

Coming soon in #Fedify 1.5.0: Smart fan-out for efficient activity delivery!

After getting feedback about our queue design, we're excited to introduce a significant improvement for accounts with large follower counts.

As we discussed in our previous post, Fedify currently creates separate queue messages for each recipient. While this approach offers excellent reliability and individual retry capabilities, it causes performance issues when sending activities to thousands of followers.

Our solution? A new two-stage “fan-out” approach:

When you call Context.sendActivity(), we'll now enqueue just one consolidated message containing your activity payload and recipient list
A background worker then processes this message and re-enqueues individual delivery tasks

The benefits are substantial:

Context.sendActivity() returns almost instantly, even for massive follower counts
Memory usage is dramatically reduced by avoiding payload duplication
UI responsiveness improves since web requests complete quickly
The same reliability for individual deliveries is maintained

For developers with specific needs, we're adding a fanout option with three settings:

"auto" (default): Uses fanout for large recipient lists, direct delivery for small ones
"skip": Bypasses fanout when you need different payload per recipient
"force": Always uses fanout even with few recipients

// Example with custom fanout setting
await ctx.sendActivity(
  { identifier: "alice" },
  recipients,
  activity,
  { fanout: "skip" }  // Directly enqueues individual messages
);

This change represents months of performance testing and should make Fedify work beautifully even for extremely popular accounts!

For more details, check out our docs.

What other #performance optimizations would you like to see in future Fedify releases?

ALT text details

Flowchart comparing Fedify's current approach versus the new fan-out approach for activity delivery. The current approach shows: 1. sendActivity calls create separate messages for each recipient (marked as a response time bottleneck) 2. These individual messages are queued in outbox 3. Messages are processed independently 4. Three delivery outcomes: Recipient 1 (fast delivery), Recipient 2 (fast delivery), and Recipient 3 (slow server) The fan-out approach shows: 1. sendActivity creates a single message with multiple recipients 2. This single message is queued in fan-out queue (marked as providing quick response) 3. A background worker processes the fan-out message 4. The worker re-enqueues individual messages in outbox 5. These are then processed independently 6. Three delivery outcomes: Recipient 1 (fast delivery), Recipient 2 (fast delivery), and Recipient 3 (slow server) The diagram highlights how the fan-out approach moves the heavy processing out of the response path, providing faster API response times while maintaining the same delivery characteristics.

Fedify: an ActivityPub server framework

@fedify@hollo.social

Got an interesting question today about #Fedify's outgoing #queue design!

Some users noticed we create separate queue messages for each recipient inbox rather than queuing a single message and handling the splitting later. There's a good reason for this approach.

In the #fediverse, server response times vary dramatically—some respond quickly, others slowly, and some might be temporarily down. If we processed deliveries in a single task, the entire batch would be held up by the slowest server in the group.

By creating individual queue items for each recipient:

Fast servers get messages delivered promptly
Slow servers don't delay delivery to others
Failed deliveries can be retried independently
Your UI remains responsive while deliveries happen in the background

It's a classic trade-off: we generate more queue messages, but gain better resilience and user experience in return.

This is particularly important in federated networks where server behavior is unpredictable and outside our control. We'd rather optimize for making sure your posts reach their destinations as quickly as possible!

What other aspects of Fedify's design would you like to hear about? Let us know!

ALT text details

A flowchart comparing two approaches to message queue design. The top half shows “Fedify's Current Approach” where a single sendActivity call creates separate messages for each recipient, which are individually queued and processed independently. This results in fast delivery to working recipients while slow servers only affect their own delivery. The bottom half shows an “Alternative Approach” where sendActivity creates a single message with multiple recipients, queued as one item, and processed sequentially. This results in all recipients waiting for each delivery to complete, with slow servers blocking everyone in the queue.

Fedify: an ActivityPub server framework

@fedify@hollo.social

We'd like to introduce the #Fedify project family—a set of related tools that make building #ActivityPub applications more accessible:

Fedify

Fedify (@fedify) is a #TypeScript library for building federated server applications powered by ActivityPub and other #fediverse standards. It provides type-safe objects for Activity Vocabulary, WebFinger client/server, HTTP Signatures, and more—eliminating boilerplate code so you can focus on your application logic.

Hollo

Hollo (@hollo) is a single-user microblogging server powered by Fedify. While designed for individual users, it's fully federated through ActivityPub, allowing interaction with users across the fediverse. #Hollo implements Mastodon-compatible APIs, making it compatible with most Mastodon clients without needing its own web interface.

Hollo also serves as our testing ground for bleeding-edge Fedify features before they're officially released.

BotKit

BotKit (@botkit) is our newest family member—a framework specifically designed for creating ActivityPub bots. Unlike traditional Mastodon bots, #BotKit creates standalone ActivityPub servers that aren't constrained by platform-specific limitations (like character counts).

BotKit's API is intentionally simple—you can create a complete bot in a single TypeScript file!

All three projects are open source and hosted under the @fedify-dev GitHub organization. While they serve different purposes, they share common goals: making ActivityPub development more accessible and expanding the fediverse ecosystem.

If you're interested in trying any of these projects or contributing to their development, check out:

#DeSo #FediDev #FediDevs #Fediverse #FediverseUX #FediUX #Mastodon

@reiver ⊼ (Charles)

@reiver@mastodon.social

What about the Fediverse or Mastodon, etc, frustrates you or confuses you?

Fedify: an ActivityPub server framework

@fedify@hollo.social

Got an interesting question today about #Fedify's outgoing #queue design!

Some users noticed we create separate queue messages for each recipient inbox rather than queuing a single message and handling the splitting later. There's a good reason for this approach.

By creating individual queue items for each recipient:

Fast servers get messages delivered promptly
Slow servers don't delay delivery to others
Failed deliveries can be retried independently
Your UI remains responsive while deliveries happen in the background

It's a classic trade-off: we generate more queue messages, but gain better resilience and user experience in return.

What other aspects of Fedify's design would you like to hear about? Let us know!

ALT text details

Fedify: an ActivityPub server framework

@fedify@hollo.social

We'd like to introduce the #Fedify project family—a set of related tools that make building #ActivityPub applications more accessible:

Fedify

Hollo

Hollo also serves as our testing ground for bleeding-edge Fedify features before they're officially released.

BotKit

BotKit's API is intentionally simple—you can create a complete bot in a single TypeScript file!

If you're interested in trying any of these projects or contributing to their development, check out:

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

Coming soon in #Fedify 1.5.0: Smart fan-out for efficient activity delivery!

After getting feedback about our queue design, we're excited to introduce a significant improvement for accounts with large follower counts.

Our solution? A new two-stage “fan-out” approach:

When you call Context.sendActivity(), we'll now enqueue just one consolidated message containing your activity payload and recipient list
A background worker then processes this message and re-enqueues individual delivery tasks

The benefits are substantial:

Context.sendActivity() returns almost instantly, even for massive follower counts
Memory usage is dramatically reduced by avoiding payload duplication
UI responsiveness improves since web requests complete quickly
The same reliability for individual deliveries is maintained

For developers with specific needs, we're adding a fanout option with three settings:

"auto" (default): Uses fanout for large recipient lists, direct delivery for small ones
"skip": Bypasses fanout when you need different payload per recipient
"force": Always uses fanout even with few recipients

// Example with custom fanout setting
await ctx.sendActivity(
  { identifier: "alice" },
  recipients,
  activity,
  { fanout: "skip" }  // Directly enqueues individual messages
);

This change represents months of performance testing and should make Fedify work beautifully even for extremely popular accounts!

For more details, check out our docs.

What other #performance optimizations would you like to see in future Fedify releases?

ALT text details

Fedify: an ActivityPub server framework

@fedify@hollo.social

Got an interesting question today about #Fedify's outgoing #queue design!

Some users noticed we create separate queue messages for each recipient inbox rather than queuing a single message and handling the splitting later. There's a good reason for this approach.

By creating individual queue items for each recipient:

Fast servers get messages delivered promptly
Slow servers don't delay delivery to others
Failed deliveries can be retried independently
Your UI remains responsive while deliveries happen in the background

BotKit

BotKit's API is intentionally simple—you can create a complete bot in a single TypeScript file!

If you're interested in trying any of these projects or contributing to their development, check out:

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

Coming soon in #Fedify 1.5.0: Smart fan-out for efficient activity delivery!

After getting feedback about our queue design, we're excited to introduce a significant improvement for accounts with large follower counts.

Our solution? A new two-stage “fan-out” approach:

When you call Context.sendActivity(), we'll now enqueue just one consolidated message containing your activity payload and recipient list
A background worker then processes this message and re-enqueues individual delivery tasks

The benefits are substantial:

Context.sendActivity() returns almost instantly, even for massive follower counts
Memory usage is dramatically reduced by avoiding payload duplication
UI responsiveness improves since web requests complete quickly
The same reliability for individual deliveries is maintained

For developers with specific needs, we're adding a fanout option with three settings:

"auto" (default): Uses fanout for large recipient lists, direct delivery for small ones
"skip": Bypasses fanout when you need different payload per recipient
"force": Always uses fanout even with few recipients

// Example with custom fanout setting
await ctx.sendActivity(
  { identifier: "alice" },
  recipients,
  activity,
  { fanout: "skip" }  // Directly enqueues individual messages
);

This change represents months of performance testing and should make Fedify work beautifully even for extremely popular accounts!

For more details, check out our docs.

What other #performance optimizations would you like to see in future Fedify releases?

ALT text details

Fedify: an ActivityPub server framework

@fedify@hollo.social

Got an interesting question today about #Fedify's outgoing #queue design!

Some users noticed we create separate queue messages for each recipient inbox rather than queuing a single message and handling the splitting later. There's a good reason for this approach.

By creating individual queue items for each recipient:

Fast servers get messages delivered promptly
Slow servers don't delay delivery to others
Failed deliveries can be retried independently
Your UI remains responsive while deliveries happen in the background

It's a classic trade-off: we generate more queue messages, but gain better resilience and user experience in return.

What other aspects of Fedify's design would you like to hear about? Let us know!

ALT text details

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

Coming soon in #Fedify 1.5.0: Smart fan-out for efficient activity delivery!

After getting feedback about our queue design, we're excited to introduce a significant improvement for accounts with large follower counts.

Our solution? A new two-stage “fan-out” approach:

When you call Context.sendActivity(), we'll now enqueue just one consolidated message containing your activity payload and recipient list
A background worker then processes this message and re-enqueues individual delivery tasks

The benefits are substantial:

Context.sendActivity() returns almost instantly, even for massive follower counts
Memory usage is dramatically reduced by avoiding payload duplication
UI responsiveness improves since web requests complete quickly
The same reliability for individual deliveries is maintained

For developers with specific needs, we're adding a fanout option with three settings:

"auto" (default): Uses fanout for large recipient lists, direct delivery for small ones
"skip": Bypasses fanout when you need different payload per recipient
"force": Always uses fanout even with few recipients

// Example with custom fanout setting
await ctx.sendActivity(
  { identifier: "alice" },
  recipients,
  activity,
  { fanout: "skip" }  // Directly enqueues individual messages
);

This change represents months of performance testing and should make Fedify work beautifully even for extremely popular accounts!

For more details, check out our docs.

What other #performance optimizations would you like to see in future Fedify releases?

ALT text details

Fedify: an ActivityPub server framework

@fedify@hollo.social

Got an interesting question today about #Fedify's outgoing #queue design!

Some users noticed we create separate queue messages for each recipient inbox rather than queuing a single message and handling the splitting later. There's a good reason for this approach.

By creating individual queue items for each recipient:

Fast servers get messages delivered promptly
Slow servers don't delay delivery to others
Failed deliveries can be retried independently
Your UI remains responsive while deliveries happen in the background

It's a classic trade-off: we generate more queue messages, but gain better resilience and user experience in return.

What other aspects of Fedify's design would you like to hear about? Let us know!

ALT text details

Fedify: an ActivityPub server framework

@fedify@hollo.social

Got an interesting question today about #Fedify's outgoing #queue design!

Some users noticed we create separate queue messages for each recipient inbox rather than queuing a single message and handling the splitting later. There's a good reason for this approach.

By creating individual queue items for each recipient:

Fast servers get messages delivered promptly
Slow servers don't delay delivery to others
Failed deliveries can be retried independently
Your UI remains responsive while deliveries happen in the background

It's a classic trade-off: we generate more queue messages, but gain better resilience and user experience in return.

What other aspects of Fedify's design would you like to hear about? Let us know!

ALT text details

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

Coming soon in #Fedify 1.5.0: Smart fan-out for efficient activity delivery!

After getting feedback about our queue design, we're excited to introduce a significant improvement for accounts with large follower counts.

Our solution? A new two-stage “fan-out” approach:

When you call Context.sendActivity(), we'll now enqueue just one consolidated message containing your activity payload and recipient list
A background worker then processes this message and re-enqueues individual delivery tasks

The benefits are substantial:

Context.sendActivity() returns almost instantly, even for massive follower counts
Memory usage is dramatically reduced by avoiding payload duplication
UI responsiveness improves since web requests complete quickly
The same reliability for individual deliveries is maintained

For developers with specific needs, we're adding a fanout option with three settings:

"auto" (default): Uses fanout for large recipient lists, direct delivery for small ones
"skip": Bypasses fanout when you need different payload per recipient
"force": Always uses fanout even with few recipients

// Example with custom fanout setting
await ctx.sendActivity(
  { identifier: "alice" },
  recipients,
  activity,
  { fanout: "skip" }  // Directly enqueues individual messages
);

This change represents months of performance testing and should make Fedify work beautifully even for extremely popular accounts!

For more details, check out our docs.

What other #performance optimizations would you like to see in future Fedify releases?

ALT text details

Fedify: an ActivityPub server framework

@fedify@hollo.social

Got an interesting question today about #Fedify's outgoing #queue design!

Some users noticed we create separate queue messages for each recipient inbox rather than queuing a single message and handling the splitting later. There's a good reason for this approach.

By creating individual queue items for each recipient:

Fast servers get messages delivered promptly
Slow servers don't delay delivery to others
Failed deliveries can be retried independently
Your UI remains responsive while deliveries happen in the background

It's a classic trade-off: we generate more queue messages, but gain better resilience and user experience in return.

What other aspects of Fedify's design would you like to hear about? Let us know!

ALT text details

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

Coming soon in #Fedify 1.5.0: Smart fan-out for efficient activity delivery!

After getting feedback about our queue design, we're excited to introduce a significant improvement for accounts with large follower counts.

Our solution? A new two-stage “fan-out” approach:

When you call Context.sendActivity(), we'll now enqueue just one consolidated message containing your activity payload and recipient list
A background worker then processes this message and re-enqueues individual delivery tasks

The benefits are substantial:

Context.sendActivity() returns almost instantly, even for massive follower counts
Memory usage is dramatically reduced by avoiding payload duplication
UI responsiveness improves since web requests complete quickly
The same reliability for individual deliveries is maintained

For developers with specific needs, we're adding a fanout option with three settings:

"auto" (default): Uses fanout for large recipient lists, direct delivery for small ones
"skip": Bypasses fanout when you need different payload per recipient
"force": Always uses fanout even with few recipients

// Example with custom fanout setting
await ctx.sendActivity(
  { identifier: "alice" },
  recipients,
  activity,
  { fanout: "skip" }  // Directly enqueues individual messages
);

This change represents months of performance testing and should make Fedify work beautifully even for extremely popular accounts!

For more details, check out our docs.

What other #performance optimizations would you like to see in future Fedify releases?

ALT text details

Fedify: an ActivityPub server framework

@fedify@hollo.social

Got an interesting question today about #Fedify's outgoing #queue design!

Some users noticed we create separate queue messages for each recipient inbox rather than queuing a single message and handling the splitting later. There's a good reason for this approach.

By creating individual queue items for each recipient:

Fast servers get messages delivered promptly
Slow servers don't delay delivery to others
Failed deliveries can be retried independently
Your UI remains responsive while deliveries happen in the background

It's a classic trade-off: we generate more queue messages, but gain better resilience and user experience in return.

What other aspects of Fedify's design would you like to hear about? Let us know!

ALT text details

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

Coming soon in #Fedify 1.5.0: Smart fan-out for efficient activity delivery!

After getting feedback about our queue design, we're excited to introduce a significant improvement for accounts with large follower counts.

Our solution? A new two-stage “fan-out” approach:

When you call Context.sendActivity(), we'll now enqueue just one consolidated message containing your activity payload and recipient list
A background worker then processes this message and re-enqueues individual delivery tasks

The benefits are substantial:

Context.sendActivity() returns almost instantly, even for massive follower counts
Memory usage is dramatically reduced by avoiding payload duplication
UI responsiveness improves since web requests complete quickly
The same reliability for individual deliveries is maintained

For developers with specific needs, we're adding a fanout option with three settings:

"auto" (default): Uses fanout for large recipient lists, direct delivery for small ones
"skip": Bypasses fanout when you need different payload per recipient
"force": Always uses fanout even with few recipients

// Example with custom fanout setting
await ctx.sendActivity(
  { identifier: "alice" },
  recipients,
  activity,
  { fanout: "skip" }  // Directly enqueues individual messages
);

This change represents months of performance testing and should make Fedify work beautifully even for extremely popular accounts!

For more details, check out our docs.

What other #performance optimizations would you like to see in future Fedify releases?

ALT text details

Fedify: an ActivityPub server framework

@fedify@hollo.social

Got an interesting question today about #Fedify's outgoing #queue design!

Some users noticed we create separate queue messages for each recipient inbox rather than queuing a single message and handling the splitting later. There's a good reason for this approach.

By creating individual queue items for each recipient:

Fast servers get messages delivered promptly
Slow servers don't delay delivery to others
Failed deliveries can be retried independently
Your UI remains responsive while deliveries happen in the background

It's a classic trade-off: we generate more queue messages, but gain better resilience and user experience in return.

What other aspects of Fedify's design would you like to hear about? Let us know!

ALT text details

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

Coming soon in #Fedify 1.5.0: Smart fan-out for efficient activity delivery!

After getting feedback about our queue design, we're excited to introduce a significant improvement for accounts with large follower counts.

Our solution? A new two-stage “fan-out” approach:

When you call Context.sendActivity(), we'll now enqueue just one consolidated message containing your activity payload and recipient list
A background worker then processes this message and re-enqueues individual delivery tasks

The benefits are substantial:

Context.sendActivity() returns almost instantly, even for massive follower counts
Memory usage is dramatically reduced by avoiding payload duplication
UI responsiveness improves since web requests complete quickly
The same reliability for individual deliveries is maintained

For developers with specific needs, we're adding a fanout option with three settings:

"auto" (default): Uses fanout for large recipient lists, direct delivery for small ones
"skip": Bypasses fanout when you need different payload per recipient
"force": Always uses fanout even with few recipients

// Example with custom fanout setting
await ctx.sendActivity(
  { identifier: "alice" },
  recipients,
  activity,
  { fanout: "skip" }  // Directly enqueues individual messages
);

This change represents months of performance testing and should make Fedify work beautifully even for extremely popular accounts!

For more details, check out our docs.

What other #performance optimizations would you like to see in future Fedify releases?

ALT text details

Fedify: an ActivityPub server framework

@fedify@hollo.social

Got an interesting question today about #Fedify's outgoing #queue design!

Some users noticed we create separate queue messages for each recipient inbox rather than queuing a single message and handling the splitting later. There's a good reason for this approach.

By creating individual queue items for each recipient:

Fast servers get messages delivered promptly
Slow servers don't delay delivery to others
Failed deliveries can be retried independently
Your UI remains responsive while deliveries happen in the background

It's a classic trade-off: we generate more queue messages, but gain better resilience and user experience in return.

What other aspects of Fedify's design would you like to hear about? Let us know!

ALT text details

Fedify: an ActivityPub server framework

@fedify@hollo.social

Got an interesting question today about #Fedify's outgoing #queue design!

Some users noticed we create separate queue messages for each recipient inbox rather than queuing a single message and handling the splitting later. There's a good reason for this approach.

By creating individual queue items for each recipient:

Fast servers get messages delivered promptly
Slow servers don't delay delivery to others
Failed deliveries can be retried independently
Your UI remains responsive while deliveries happen in the background

BotKit

BotKit's API is intentionally simple—you can create a complete bot in a single TypeScript file!

If you're interested in trying any of these projects or contributing to their development, check out:

#Fedify #ActivityPub #フェディバース #fediverse #Hollo #BotKit #fedidev

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

Fedifyの関連プロジェクトをご紹介したいと思います。ActivityPubアプリケーション開発をより簡単にするツール群です：

Fedify

Fedify（@fedify）はActivityPubやその他のフェディバース標準を活用する連合型サーバーアプリケーションを構築するためのTypeScriptライブラリです。Activity Vocabularyの型安全なオブジェクト、WebFingerクライアント・サーバー、HTTP Signaturesなどを提供し、ボイラープレートコードを削減してアプリケーションロジックに集中できるようにします。

Hollo

Hollo（@hollo）はFedifyで動作するお一人様用マイクロブログサーバーです。個人向けに設計されていますが、ActivityPubを通じて完全に連合化されており、フェディバース全体のユーザーと交流することができます。HolloはMastodon互換APIを実装しているため、独自のウェブインターフェースがなくても、ほとんどのMastodonクライアントと互換性があります。

Holloはまた、正式リリース前の最新Fedify機能をテストする実験場としても活用されています。

BotKit

BotKit（@botkit）は私たちの最も新しいメンバーで、ActivityPubボットを作成するために特別に設計されたフレームワークです。従来のMastodonボットとは異なり、BotKitはプラットフォーム固有の制限（文字数制限など）に縛られない独立したActivityPubサーバーを作成します。

BotKitのAPIは意図的にシンプルに設計されており、単一のTypeScriptファイルで完全なボットを作成できます！

これら三つのプロジェクトはすべて@fedify-dev GitHubオーガニゼーションでオープンソースとして公開されています。それぞれ異なる目的を持っていますが、ActivityPub開発をより身近にし、フェディバースのエコシステムを拡大するという共通の目標を共有しています。

これらのプロジェクトを試してみたり、開発に貢献したりすることに興味がある場合は、以下をご覧ください：

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

Fedifyの関連プロジェクトをご紹介したいと思います。ActivityPubアプリケーション開発をより簡単にするツール群です：

Fedify

Hollo

Holloはまた、正式リリース前の最新Fedify機能をテストする実験場としても活用されています。

BotKit

BotKitのAPIは意図的にシンプルに設計されており、単一のTypeScriptファイルで完全なボットを作成できます！

これらのプロジェクトを試してみたり、開発に貢献したりすることに興味がある場合は、以下をご覧ください：

#Fedify #ActivityPub #フェディバース #fediverse #Hollo #BotKit #fedidev

Fedify: an ActivityPub server framework

@fedify@hollo.social

We'd like to introduce the #Fedify project family—a set of related tools that make building #ActivityPub applications more accessible:

Fedify

Hollo

Hollo also serves as our testing ground for bleeding-edge Fedify features before they're officially released.

BotKit

BotKit's API is intentionally simple—you can create a complete bot in a single TypeScript file!

If you're interested in trying any of these projects or contributing to their development, check out:

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

#Fedify 자매 프로젝트들을 소개해 드리고자 합니다. #ActivityPub 애플리케이션 개발을 더 쉽게 만들어주는 관련 도구들입니다:

Fedify

Fedify(@fedify)는 ActivityPub와 다른 #연합우주(#fediverse) 표준을 기반으로 연합 서버 애플리케이션을 구축하기 위한 #TypeScript 라이브러리입니다. Activity Vocabulary를 위한 타입 안전한 객체, WebFinger 클라이언트·서버, HTTP Signatures 등를 제공하여 반복적인 코드를 줄이고 애플리케이션 로직에 집중할 수 있게 해줍니다.

Hollo

Hollo(@hollo)는 Fedify로 구동되는 1인 사용자용 마이크로블로깅 서버입니다. 1인 사용자를 위해 설계되었지만, ActivityPub를 통해 완전히 연합되어 연합우주 전체의 사용자들과 상호작용할 수 있습니다. Hollo는 Mastodon 호환 API를 구현하여 자체 웹 인터페이스 없이도 대부분의 Mastodon 클라이언트와 호환됩니다.

Hollo는 또한 정식 출시 전에 최신 Fedify 기능을 테스트하는 실험장으로도 활용되고 있습니다.

BotKit

BotKit(@botkit)은 저희의 가장 새로운 구성원으로, ActivityPub 봇을 만들기 위해 특별히 설계된 프레임워크입니다. 전통적인 Mastodon 봇과 달리, BotKit은 플랫폼별 제한(글자 수 제한 등)에 구애받지 않는 독립적인 ActivityPub 서버를 만듭니다.

BotKit의 API는 의도적으로 단순하게 설계되어 단일 TypeScript 파일로 완전한 봇을 만들 수 있습니다!

세 프로젝트 모두 @fedify-dev GitHub 조직에서 오픈 소스로 공개되어 있습니다. 각기 다른 목적을 가지고 있지만, ActivityPub 개발을 더 접근하기 쉽게 만들고 연합우주 생태계를 확장한다는 공통된 목표를 공유합니다.

Hollo

Hollo also serves as our testing ground for bleeding-edge Fedify features before they're officially released.

BotKit

BotKit's API is intentionally simple—you can create a complete bot in a single TypeScript file!

If you're interested in trying any of these projects or contributing to their development, check out:

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

We've been working on adding custom background task support to #Fedify as planned for version 1.5.0. After diving deeper into implementation, we've realized this is a more substantial undertaking than initially anticipated.

The feature would require significant API changes that would be too disruptive for a minor version update. Therefore, we've decided to postpone this feature to Fedify 2.0.0.

This allows us to:

Design a more robust and flexible worker architecture
Ensure better integration with existing task queue systems
Properly document the new APIs without rushing

We believe this decision will result in a more stable and well-designed feature that better serves your needs. However, some smaller improvements from our work that don't require API changes will still be included in Fedify 1.5.0 or subsequent minor updates.

We appreciate your understanding and continued support.

If you have specific use cases or requirements for background task support, please share them in our GitHub issue. Your input will help shape this feature for 2.0.0.

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

The feature would require significant API changes that would be too disruptive for a minor version update. Therefore, we've decided to postpone this feature to Fedify 2.0.0.

This allows us to:

Design a more robust and flexible worker architecture
Ensure better integration with existing task queue systems
Properly document the new APIs without rushing

We appreciate your understanding and continued support.

If you have specific use cases or requirements for background task support, please share them in our GitHub issue. Your input will help shape this feature for 2.0.0.

Fedify: an ActivityPub server framework

@fedify@hollo.social

Patch releases for #Fedify versions 1.0.21, 1.1.18, 1.2.18, 1.3.14, and 1.4.7 are now available. These updates address two important bugs across all supported release lines:

Fixed a WebFinger handler bug that prevented matching acct: URIs with port numbers in the host. Thanks to @revathskumar for reporting and debugging the bug!
Resolved server errors that occurred when invalid URLs were passed to the base-url parameter of followers collections.

We recommend all users upgrade to these latest patch versions for improved stability and federation compatibility.

Fedify: an ActivityPub server framework

@fedify@hollo.social

Patch releases for #Fedify versions 1.0.21, 1.1.18, 1.2.18, 1.3.14, and 1.4.7 are now available. These updates address two important bugs across all supported release lines:

Fixed a WebFinger handler bug that prevented matching acct: URIs with port numbers in the host. Thanks to @revathskumar for reporting and debugging the bug!
Resolved server errors that occurred when invalid URLs were passed to the base-url parameter of followers collections.

We recommend all users upgrade to these latest patch versions for improved stability and federation compatibility.

Fedify: an ActivityPub server framework

@fedify@hollo.social

Patch releases for #Fedify versions 1.0.21, 1.1.18, 1.2.18, 1.3.14, and 1.4.7 are now available. These updates address two important bugs across all supported release lines:

Fixed a WebFinger handler bug that prevented matching acct: URIs with port numbers in the host. Thanks to @revathskumar for reporting and debugging the bug!
Resolved server errors that occurred when invalid URLs were passed to the base-url parameter of followers collections.

We recommend all users upgrade to these latest patch versions for improved stability and federation compatibility.

Fedify: an ActivityPub server framework

@fedify@hollo.social

Patch releases for #Fedify versions 1.0.21, 1.1.18, 1.2.18, 1.3.14, and 1.4.7 are now available. These updates address two important bugs across all supported release lines:

Fixed a WebFinger handler bug that prevented matching acct: URIs with port numbers in the host. Thanks to @revathskumar for reporting and debugging the bug!
Resolved server errors that occurred when invalid URLs were passed to the base-url parameter of followers collections.

We recommend all users upgrade to these latest patch versions for improved stability and federation compatibility.

Fedify: an ActivityPub server framework

@fedify@hollo.social

Patch releases for #Fedify versions 1.0.21, 1.1.18, 1.2.18, 1.3.14, and 1.4.7 are now available. These updates address two important bugs across all supported release lines:

Fixed a WebFinger handler bug that prevented matching acct: URIs with port numbers in the host. Thanks to @revathskumar for reporting and debugging the bug!
Resolved server errors that occurred when invalid URLs were passed to the base-url parameter of followers collections.

We recommend all users upgrade to these latest patch versions for improved stability and federation compatibility.

https://halcy.de/blog/2025/03/18/silly-mastodon-apps/

Jeff Sikes

@box464@mastodon.social

A collection of silly Mastodon apps (the best kind). It includes a Fax-To-Mastodon app.

#MastoDev #FediDev #Fediverse #mastodonapps

洪民憙 (Hong Minhee)

@hongminhee@hollo.social · Reply to 洪民憙 (Hong Minhee)'s post

洪民憙 (Hong Minhee)

@hongminhee@hollo.social · Reply to 洪民憙 (Hong Minhee)'s post

https://halcy.de/blog/2025/03/18/silly-mastodon-apps/

Jeff Sikes

@box464@mastodon.social

A collection of silly Mastodon apps (the best kind). It includes a Fax-To-Mastodon app.

#MastoDev #FediDev #Fediverse #mastodonapps

Jeff Sikes

@box464@mastodon.social

@liaizon@social.wake.st

Just noticed this "Open in the application? " banner on @framasoft's "What is the fediverse" @peertube video and I have the app installed thru @fdroidorg but it takes me to the Google Play download page for it instead of opening it in the app. Makes for a really bad fediverse experience, we need to figure out these sorts of flows and make sure they reliably work. #fedidev #peertube #fediverse

ALT text details

A screenshot of a peertube video

ALT text details

A screenshot of peertube on Google Play

@reiver ⊼ (Charles)

@reiver@mastodon.social

What about the Fediverse or Mastodon, etc, frustrates you or confuses you?

#DeSo #FediDev #FediDevs #Fediverse #FediverseUX #FediUX #Mastodon

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

#연합우주 #fediverse #fedidev

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

#연합우주 #fediverse #fedidev

Jeff Sikes

@box464@mastodon.social

Good overview of JSON-LD

https://digitalcourage.video/w/jUKxSj7SCVe9t5rZA1piwU

#ActivityPub #FediDev #SurfAPCast

Light

@light@noc.social · Reply to Light's post

#FediDev #Mastodon #ideas

Light

@light@noc.social · Reply to Light's post

#FediDev #Mastodon #ideas

@reiver ⊼ (Charles)

@reiver@mastodon.social

I set up a web-site for GreatApe.

https://greata.pe/

A URL I can use when I talk about GreatApe.

Until now, it was just the GitHub repos. Now, GreatApe has its own web-site.

For now, it is very basic. More needs to be added to it.

#DeSo #FediDev #Fediverse #GreatApe #OpenSocial #SocialWeb

Julian Fietkau

@julian@fietkau.social

I'm finally unveiling the #ActivityPub project that has been consuming my weekends: Encyclia, an #ORCID bridge that will make ORCID records followable and interactable on the fediverse. 🙂

It's early-stage and the ORCID following function is not publicly available yet. We're seeking community feedback on functionality and safety aspects. Read more at https://encyclia.pub or follow @encyclia for news!

#fediverse #fedidev #scicomm #wisskomm #academicchatter

wakest ⁂

@liaizon@social.wake.st

in my dream last night @peertube announced support for fediverse:creator tags attached to channels #fedidev

Julian Fietkau

@julian@fietkau.social

I'm finally unveiling the #ActivityPub project that has been consuming my weekends: Encyclia, an #ORCID bridge that will make ORCID records followable and interactable on the fediverse. 🙂

#fediverse #fedidev #scicomm #wisskomm #academicchatter

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

By creating individual queue items for each recipient:

Fast servers get messages delivered promptly
Slow servers don't delay delivery to others
Failed deliveries can be retried independently
Your UI remains responsive while deliveries happen in the background

It's a classic trade-off: we generate more queue messages, but gain better resilience and user experience in return.

What other aspects of Fedify's design would you like to hear about? Let us know!

ALT text details

Fedify: an ActivityPub server framework

@fedify@hollo.social

Got an interesting question today about #Fedify's outgoing #queue design!

Some users noticed we create separate queue messages for each recipient inbox rather than queuing a single message and handling the splitting later. There's a good reason for this approach.

By creating individual queue items for each recipient:

Fast servers get messages delivered promptly
Slow servers don't delay delivery to others
Failed deliveries can be retried independently
Your UI remains responsive while deliveries happen in the background

It's a classic trade-off: we generate more queue messages, but gain better resilience and user experience in return.

What other aspects of Fedify's design would you like to hear about? Let us know!

ALT text details

Fedify: an ActivityPub server framework

@fedify@hollo.social

Got an interesting question today about #Fedify's outgoing #queue design!

Some users noticed we create separate queue messages for each recipient inbox rather than queuing a single message and handling the splitting later. There's a good reason for this approach.

By creating individual queue items for each recipient:

Fast servers get messages delivered promptly
Slow servers don't delay delivery to others
Failed deliveries can be retried independently
Your UI remains responsive while deliveries happen in the background

It's a classic trade-off: we generate more queue messages, but gain better resilience and user experience in return.

What other aspects of Fedify's design would you like to hear about? Let us know!

ALT text details

Fedify: an ActivityPub server framework

@fedify@hollo.social

Got an interesting question today about #Fedify's outgoing #queue design!

Some users noticed we create separate queue messages for each recipient inbox rather than queuing a single message and handling the splitting later. There's a good reason for this approach.

By creating individual queue items for each recipient:

Fast servers get messages delivered promptly
Slow servers don't delay delivery to others
Failed deliveries can be retried independently
Your UI remains responsive while deliveries happen in the background

It's a classic trade-off: we generate more queue messages, but gain better resilience and user experience in return.

What other aspects of Fedify's design would you like to hear about? Let us know!

ALT text details

Fedify: an ActivityPub server framework

@fedify@hollo.social

Got an interesting question today about #Fedify's outgoing #queue design!

Some users noticed we create separate queue messages for each recipient inbox rather than queuing a single message and handling the splitting later. There's a good reason for this approach.

By creating individual queue items for each recipient:

Fast servers get messages delivered promptly
Slow servers don't delay delivery to others
Failed deliveries can be retried independently
Your UI remains responsive while deliveries happen in the background

It's a classic trade-off: we generate more queue messages, but gain better resilience and user experience in return.

What other aspects of Fedify's design would you like to hear about? Let us know!

ALT text details

Fedify: an ActivityPub server framework

@fedify@hollo.social

Got an interesting question today about #Fedify's outgoing #queue design!

Some users noticed we create separate queue messages for each recipient inbox rather than queuing a single message and handling the splitting later. There's a good reason for this approach.

By creating individual queue items for each recipient:

Fast servers get messages delivered promptly
Slow servers don't delay delivery to others
Failed deliveries can be retried independently
Your UI remains responsive while deliveries happen in the background

It's a classic trade-off: we generate more queue messages, but gain better resilience and user experience in return.

What other aspects of Fedify's design would you like to hear about? Let us know!

ALT text details

Fedify: an ActivityPub server framework

@fedify@hollo.social

Got an interesting question today about #Fedify's outgoing #queue design!

Some users noticed we create separate queue messages for each recipient inbox rather than queuing a single message and handling the splitting later. There's a good reason for this approach.

By creating individual queue items for each recipient:

Fast servers get messages delivered promptly
Slow servers don't delay delivery to others
Failed deliveries can be retried independently
Your UI remains responsive while deliveries happen in the background

It's a classic trade-off: we generate more queue messages, but gain better resilience and user experience in return.

What other aspects of Fedify's design would you like to hear about? Let us know!

ALT text details

Fedify: an ActivityPub server framework

@fedify@hollo.social

Got an interesting question today about #Fedify's outgoing #queue design!

Some users noticed we create separate queue messages for each recipient inbox rather than queuing a single message and handling the splitting later. There's a good reason for this approach.

By creating individual queue items for each recipient:

Fast servers get messages delivered promptly
Slow servers don't delay delivery to others
Failed deliveries can be retried independently
Your UI remains responsive while deliveries happen in the background

It's a classic trade-off: we generate more queue messages, but gain better resilience and user experience in return.

What other aspects of Fedify's design would you like to hear about? Let us know!

ALT text details

Fedify: an ActivityPub server framework

@fedify@hollo.social

Got an interesting question today about #Fedify's outgoing #queue design!

Some users noticed we create separate queue messages for each recipient inbox rather than queuing a single message and handling the splitting later. There's a good reason for this approach.

By creating individual queue items for each recipient:

Fast servers get messages delivered promptly
Slow servers don't delay delivery to others
Failed deliveries can be retried independently
Your UI remains responsive while deliveries happen in the background

It's a classic trade-off: we generate more queue messages, but gain better resilience and user experience in return.

What other aspects of Fedify's design would you like to hear about? Let us know!

ALT text details

Fedify: an ActivityPub server framework

@fedify@hollo.social

Got an interesting question today about #Fedify's outgoing #queue design!

Some users noticed we create separate queue messages for each recipient inbox rather than queuing a single message and handling the splitting later. There's a good reason for this approach.

By creating individual queue items for each recipient:

Fast servers get messages delivered promptly
Slow servers don't delay delivery to others
Failed deliveries can be retried independently
Your UI remains responsive while deliveries happen in the background

It's a classic trade-off: we generate more queue messages, but gain better resilience and user experience in return.

What other aspects of Fedify's design would you like to hear about? Let us know!

#fediverse #fedidev #scicomm #wisskomm #academicchatter

ALT text details

Julian Fietkau

@julian@fietkau.social

I'm finally unveiling the #ActivityPub project that has been consuming my weekends: Encyclia, an #ORCID bridge that will make ORCID records followable and interactable on the fediverse. 🙂

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Just published a post about Hackers' Pub's unique username change policy! Unlike most #fediverse platforms, they allow a one-time username change while preserving your connections and content history. It's all possible thanks to some clever #ActivityPub implementation using UUID-based actor URIs instead of username-based ones. If you're interested in trying it out, the platform is currently in invitation-only beta—check the post for details on how to request access!

https://hackers.pub/@hongminhee/2025/hackers-pub-introduces-flexible-username-changes

https://hackers.pub/@hongminhee/2025/hackers-pub-introduces-flexible-username-changes

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

Hackers' Pub is a community-focused platform where programmers and technology enthusiasts share knowledge and experiences. As an ActivityPub-enabled social network, it allows users to connect with others across the broader fediverse ecosystem, bringing technical discussions and insights directly to followers' feeds.

In the fediverse landscape, your username is typically set in stone once chosen. Most ActivityPub-powered platforms like Mastodon, Pleroma, and others enforce this permanence as a fundamental design principle. However, Hackers' Pub is charting a different course with a more flexible approach to digital identity.

One-Time Username Change: Freedom with Responsibility

Unlike most fediverse platforms, Hackers' Pub now allows users to change their username (the part before the @ in your Fediverse handle) exactly once during the lifetime of their account. This policy acknowledges that people grow, interests evolve, and the username that seemed perfect when you joined might not represent who you are today.

This one-time change limit strikes a careful balance—offering flexibility while maintaining the stability and reliability that's essential for a federated network.

Username Recycling: New Opportunities

When you change your username on Hackers' Pub, your previous username becomes available for other users to claim. This recycling mechanism creates new opportunities for meaningful usernames to find their most fitting owners, rather than remaining permanently locked to accounts that no longer use them.

For newcomers to the platform, this means a wider selection of desirable usernames might become available over time—something virtually unheard of in the traditional fediverse ecosystem.

Link Preservation: Maintaining Digital History

Worried about broken links after changing your username? Hackers' Pub has implemented a thoughtful solution. All permalinks containing your original username will continue to function until someone else claims that username. This approach helps preserve the web of connections and conversations that make the fediverse valuable.

This temporary preservation period gives your connections time to adjust to your new identity while preventing immediate link rot across the federation.

The Technical Foundation: ActivityPub Actor URIs

What enables Hackers' Pub to offer username changes while other fediverse platforms can't? The answer lies in how actor identities are implemented at the protocol level.

Hackers' Pub uses UUID-based actor URIs that don't contain the username. For example, a user with handle @hongminhee has an underlying ActivityPub actor URI that looks like https://hackers.pub/ap/actors/019382d3-63d7-7cf7-86e8-91e2551c306c. Since the username isn't part of this permanent identifier, it can be changed without breaking federation connections.

This contrasts sharply with platforms like Mastodon, where a user @hongminhee has an actor URI of https://mastodon.social/users/hongminhee. With the username embedded directly in the URI, changing it would break all federation connections, which is why these platforms don't allow username changes.

This architectural choice gives Hackers' Pub the technical flexibility to implement username changes while maintaining account continuity across the fediverse.

GitHub-Inspired Approach

Those familiar with GitHub might recognize this model—Hackers' Pub has adapted GitHub's username change policy for the fediverse context. This approach brings the best of both worlds: the option for identity evolution from centralized platforms and the federation benefits of the fediverse.

What This Means for Users

For Hackers' Pub users, this policy offers a significant advantage over other fediverse instances:

You can correct an unfortunate username choice
Your online identity can evolve as you do
Your content history remains intact during the transition
You maintain your social connections despite the change

The Future of Fediverse Identity

Hackers' Pub's username policy represents an interesting experiment in the fediverse—testing whether more flexible identity management can coexist with the stability needed for federation. If successful, we might see other platforms adopt similar approaches, creating a more adaptable yet still interconnected social web.

For now, users should consider this policy a compelling reason to choose Hackers' Pub as their fediverse home, especially if username flexibility matters to their online experience.

Hackers' Pub is currently in invitation-only beta. If you're interested in trying out the platform and its unique username policy, please leave your email address in the comments below. We'll add you to the allowlist, enabling you to sign up directly on the website. Note that this doesn't involve sending invitation emails—your address will simply be approved for registration when you visit the signup page.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

https://hackers.pub/@hongminhee/2025/hackers-pub-introduces-flexible-username-changes

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

One-Time Username Change: Freedom with Responsibility

This one-time change limit strikes a careful balance—offering flexibility while maintaining the stability and reliability that's essential for a federated network.

Username Recycling: New Opportunities

For newcomers to the platform, this means a wider selection of desirable usernames might become available over time—something virtually unheard of in the traditional fediverse ecosystem.

Link Preservation: Maintaining Digital History

This temporary preservation period gives your connections time to adjust to your new identity while preventing immediate link rot across the federation.

The Technical Foundation: ActivityPub Actor URIs

What enables Hackers' Pub to offer username changes while other fediverse platforms can't? The answer lies in how actor identities are implemented at the protocol level.

This architectural choice gives Hackers' Pub the technical flexibility to implement username changes while maintaining account continuity across the fediverse.

GitHub-Inspired Approach

What This Means for Users

For Hackers' Pub users, this policy offers a significant advantage over other fediverse instances:

You can correct an unfortunate username choice
Your online identity can evolve as you do
Your content history remains intact during the transition
You maintain your social connections despite the change

The Future of Fediverse Identity

For now, users should consider this policy a compelling reason to choose Hackers' Pub as their fediverse home, especially if username flexibility matters to their online experience.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

https://hackers.pub/@hongminhee/2025/hackers-pub-introduces-flexible-username-changes

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

One-Time Username Change: Freedom with Responsibility

This one-time change limit strikes a careful balance—offering flexibility while maintaining the stability and reliability that's essential for a federated network.

Username Recycling: New Opportunities

For newcomers to the platform, this means a wider selection of desirable usernames might become available over time—something virtually unheard of in the traditional fediverse ecosystem.

Link Preservation: Maintaining Digital History

This temporary preservation period gives your connections time to adjust to your new identity while preventing immediate link rot across the federation.

The Technical Foundation: ActivityPub Actor URIs

What enables Hackers' Pub to offer username changes while other fediverse platforms can't? The answer lies in how actor identities are implemented at the protocol level.

This architectural choice gives Hackers' Pub the technical flexibility to implement username changes while maintaining account continuity across the fediverse.

GitHub-Inspired Approach

What This Means for Users

For Hackers' Pub users, this policy offers a significant advantage over other fediverse instances:

You can correct an unfortunate username choice
Your online identity can evolve as you do
Your content history remains intact during the transition
You maintain your social connections despite the change

The Future of Fediverse Identity

For now, users should consider this policy a compelling reason to choose Hackers' Pub as their fediverse home, especially if username flexibility matters to their online experience.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

https://hackers.pub/@hongminhee/2025/hackers-pub-introduces-flexible-username-changes

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

One-Time Username Change: Freedom with Responsibility

This one-time change limit strikes a careful balance—offering flexibility while maintaining the stability and reliability that's essential for a federated network.

Username Recycling: New Opportunities

For newcomers to the platform, this means a wider selection of desirable usernames might become available over time—something virtually unheard of in the traditional fediverse ecosystem.

Link Preservation: Maintaining Digital History

This temporary preservation period gives your connections time to adjust to your new identity while preventing immediate link rot across the federation.

The Technical Foundation: ActivityPub Actor URIs

What enables Hackers' Pub to offer username changes while other fediverse platforms can't? The answer lies in how actor identities are implemented at the protocol level.

This architectural choice gives Hackers' Pub the technical flexibility to implement username changes while maintaining account continuity across the fediverse.

GitHub-Inspired Approach

What This Means for Users

For Hackers' Pub users, this policy offers a significant advantage over other fediverse instances:

You can correct an unfortunate username choice
Your online identity can evolve as you do
Your content history remains intact during the transition
You maintain your social connections despite the change

The Future of Fediverse Identity

For now, users should consider this policy a compelling reason to choose Hackers' Pub as their fediverse home, especially if username flexibility matters to their online experience.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

https://hackers.pub/@hongminhee/2025/hackers-pub-introduces-flexible-username-changes

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

One-Time Username Change: Freedom with Responsibility

This one-time change limit strikes a careful balance—offering flexibility while maintaining the stability and reliability that's essential for a federated network.

Username Recycling: New Opportunities

For newcomers to the platform, this means a wider selection of desirable usernames might become available over time—something virtually unheard of in the traditional fediverse ecosystem.

Link Preservation: Maintaining Digital History

This temporary preservation period gives your connections time to adjust to your new identity while preventing immediate link rot across the federation.

The Technical Foundation: ActivityPub Actor URIs

What enables Hackers' Pub to offer username changes while other fediverse platforms can't? The answer lies in how actor identities are implemented at the protocol level.

This architectural choice gives Hackers' Pub the technical flexibility to implement username changes while maintaining account continuity across the fediverse.

GitHub-Inspired Approach

What This Means for Users

For Hackers' Pub users, this policy offers a significant advantage over other fediverse instances:

You can correct an unfortunate username choice
Your online identity can evolve as you do
Your content history remains intact during the transition
You maintain your social connections despite the change

The Future of Fediverse Identity

For now, users should consider this policy a compelling reason to choose Hackers' Pub as their fediverse home, especially if username flexibility matters to their online experience.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

https://hackers.pub/@hongminhee/2025/hackers-pub-introduces-flexible-username-changes

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

One-Time Username Change: Freedom with Responsibility

This one-time change limit strikes a careful balance—offering flexibility while maintaining the stability and reliability that's essential for a federated network.

Username Recycling: New Opportunities

For newcomers to the platform, this means a wider selection of desirable usernames might become available over time—something virtually unheard of in the traditional fediverse ecosystem.

Link Preservation: Maintaining Digital History

This temporary preservation period gives your connections time to adjust to your new identity while preventing immediate link rot across the federation.

The Technical Foundation: ActivityPub Actor URIs

What enables Hackers' Pub to offer username changes while other fediverse platforms can't? The answer lies in how actor identities are implemented at the protocol level.

This architectural choice gives Hackers' Pub the technical flexibility to implement username changes while maintaining account continuity across the fediverse.

GitHub-Inspired Approach

What This Means for Users

For Hackers' Pub users, this policy offers a significant advantage over other fediverse instances:

You can correct an unfortunate username choice
Your online identity can evolve as you do
Your content history remains intact during the transition
You maintain your social connections despite the change

The Future of Fediverse Identity

For now, users should consider this policy a compelling reason to choose Hackers' Pub as their fediverse home, especially if username flexibility matters to their online experience.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

https://hackers.pub/@hongminhee/2025/hackers-pub-introduces-flexible-username-changes

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

One-Time Username Change: Freedom with Responsibility

This one-time change limit strikes a careful balance—offering flexibility while maintaining the stability and reliability that's essential for a federated network.

Username Recycling: New Opportunities

For newcomers to the platform, this means a wider selection of desirable usernames might become available over time—something virtually unheard of in the traditional fediverse ecosystem.

Link Preservation: Maintaining Digital History

This temporary preservation period gives your connections time to adjust to your new identity while preventing immediate link rot across the federation.

The Technical Foundation: ActivityPub Actor URIs

What enables Hackers' Pub to offer username changes while other fediverse platforms can't? The answer lies in how actor identities are implemented at the protocol level.

This architectural choice gives Hackers' Pub the technical flexibility to implement username changes while maintaining account continuity across the fediverse.

GitHub-Inspired Approach

What This Means for Users

For Hackers' Pub users, this policy offers a significant advantage over other fediverse instances:

You can correct an unfortunate username choice
Your online identity can evolve as you do
Your content history remains intact during the transition
You maintain your social connections despite the change

The Future of Fediverse Identity

For now, users should consider this policy a compelling reason to choose Hackers' Pub as their fediverse home, especially if username flexibility matters to their online experience.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

https://hackers.pub/@hongminhee/2025/hackers-pub-introduces-flexible-username-changes

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

One-Time Username Change: Freedom with Responsibility

This one-time change limit strikes a careful balance—offering flexibility while maintaining the stability and reliability that's essential for a federated network.

Username Recycling: New Opportunities

For newcomers to the platform, this means a wider selection of desirable usernames might become available over time—something virtually unheard of in the traditional fediverse ecosystem.

Link Preservation: Maintaining Digital History

This temporary preservation period gives your connections time to adjust to your new identity while preventing immediate link rot across the federation.

The Technical Foundation: ActivityPub Actor URIs

What enables Hackers' Pub to offer username changes while other fediverse platforms can't? The answer lies in how actor identities are implemented at the protocol level.

This architectural choice gives Hackers' Pub the technical flexibility to implement username changes while maintaining account continuity across the fediverse.

GitHub-Inspired Approach

What This Means for Users

For Hackers' Pub users, this policy offers a significant advantage over other fediverse instances:

You can correct an unfortunate username choice
Your online identity can evolve as you do
Your content history remains intact during the transition
You maintain your social connections despite the change

The Future of Fediverse Identity

For now, users should consider this policy a compelling reason to choose Hackers' Pub as their fediverse home, especially if username flexibility matters to their online experience.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

https://hackers.pub/@hongminhee/2025/hackers-pub-introduces-flexible-username-changes

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

One-Time Username Change: Freedom with Responsibility

This one-time change limit strikes a careful balance—offering flexibility while maintaining the stability and reliability that's essential for a federated network.

Username Recycling: New Opportunities

For newcomers to the platform, this means a wider selection of desirable usernames might become available over time—something virtually unheard of in the traditional fediverse ecosystem.

Link Preservation: Maintaining Digital History

This temporary preservation period gives your connections time to adjust to your new identity while preventing immediate link rot across the federation.

The Technical Foundation: ActivityPub Actor URIs

What enables Hackers' Pub to offer username changes while other fediverse platforms can't? The answer lies in how actor identities are implemented at the protocol level.

This architectural choice gives Hackers' Pub the technical flexibility to implement username changes while maintaining account continuity across the fediverse.

GitHub-Inspired Approach

What This Means for Users

For Hackers' Pub users, this policy offers a significant advantage over other fediverse instances:

You can correct an unfortunate username choice
Your online identity can evolve as you do
Your content history remains intact during the transition
You maintain your social connections despite the change

The Future of Fediverse Identity

For now, users should consider this policy a compelling reason to choose Hackers' Pub as their fediverse home, especially if username flexibility matters to their online experience.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

https://hackers.pub/@hongminhee/2025/hackers-pub-introduces-flexible-username-changes

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

One-Time Username Change: Freedom with Responsibility

This one-time change limit strikes a careful balance—offering flexibility while maintaining the stability and reliability that's essential for a federated network.

Username Recycling: New Opportunities

For newcomers to the platform, this means a wider selection of desirable usernames might become available over time—something virtually unheard of in the traditional fediverse ecosystem.

Link Preservation: Maintaining Digital History

This temporary preservation period gives your connections time to adjust to your new identity while preventing immediate link rot across the federation.

The Technical Foundation: ActivityPub Actor URIs

What enables Hackers' Pub to offer username changes while other fediverse platforms can't? The answer lies in how actor identities are implemented at the protocol level.

This architectural choice gives Hackers' Pub the technical flexibility to implement username changes while maintaining account continuity across the fediverse.

GitHub-Inspired Approach

What This Means for Users

For Hackers' Pub users, this policy offers a significant advantage over other fediverse instances:

You can correct an unfortunate username choice
Your online identity can evolve as you do
Your content history remains intact during the transition
You maintain your social connections despite the change

The Future of Fediverse Identity

For now, users should consider this policy a compelling reason to choose Hackers' Pub as their fediverse home, especially if username flexibility matters to their online experience.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

https://hackers.pub/@hongminhee/2025/hackers-pub-introduces-flexible-username-changes

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

One-Time Username Change: Freedom with Responsibility

This one-time change limit strikes a careful balance—offering flexibility while maintaining the stability and reliability that's essential for a federated network.

Username Recycling: New Opportunities

For newcomers to the platform, this means a wider selection of desirable usernames might become available over time—something virtually unheard of in the traditional fediverse ecosystem.

Link Preservation: Maintaining Digital History

This temporary preservation period gives your connections time to adjust to your new identity while preventing immediate link rot across the federation.

The Technical Foundation: ActivityPub Actor URIs

What enables Hackers' Pub to offer username changes while other fediverse platforms can't? The answer lies in how actor identities are implemented at the protocol level.

This architectural choice gives Hackers' Pub the technical flexibility to implement username changes while maintaining account continuity across the fediverse.

GitHub-Inspired Approach

What This Means for Users

For Hackers' Pub users, this policy offers a significant advantage over other fediverse instances:

You can correct an unfortunate username choice
Your online identity can evolve as you do
Your content history remains intact during the transition
You maintain your social connections despite the change

The Future of Fediverse Identity

For now, users should consider this policy a compelling reason to choose Hackers' Pub as their fediverse home, especially if username flexibility matters to their online experience.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

https://hackers.pub/@hongminhee/2025/hackers-pub-introduces-flexible-username-changes

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

One-Time Username Change: Freedom with Responsibility

This one-time change limit strikes a careful balance—offering flexibility while maintaining the stability and reliability that's essential for a federated network.

Username Recycling: New Opportunities

For newcomers to the platform, this means a wider selection of desirable usernames might become available over time—something virtually unheard of in the traditional fediverse ecosystem.

Link Preservation: Maintaining Digital History

This temporary preservation period gives your connections time to adjust to your new identity while preventing immediate link rot across the federation.

The Technical Foundation: ActivityPub Actor URIs

What enables Hackers' Pub to offer username changes while other fediverse platforms can't? The answer lies in how actor identities are implemented at the protocol level.

This architectural choice gives Hackers' Pub the technical flexibility to implement username changes while maintaining account continuity across the fediverse.

GitHub-Inspired Approach

What This Means for Users

For Hackers' Pub users, this policy offers a significant advantage over other fediverse instances:

You can correct an unfortunate username choice
Your online identity can evolve as you do
Your content history remains intact during the transition
You maintain your social connections despite the change

The Future of Fediverse Identity

For now, users should consider this policy a compelling reason to choose Hackers' Pub as their fediverse home, especially if username flexibility matters to their online experience.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

https://hackers.pub/@hongminhee/2025/hackers-pub-introduces-flexible-username-changes

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

One-Time Username Change: Freedom with Responsibility

This one-time change limit strikes a careful balance—offering flexibility while maintaining the stability and reliability that's essential for a federated network.

Username Recycling: New Opportunities

For newcomers to the platform, this means a wider selection of desirable usernames might become available over time—something virtually unheard of in the traditional fediverse ecosystem.

Link Preservation: Maintaining Digital History

This temporary preservation period gives your connections time to adjust to your new identity while preventing immediate link rot across the federation.

The Technical Foundation: ActivityPub Actor URIs

What enables Hackers' Pub to offer username changes while other fediverse platforms can't? The answer lies in how actor identities are implemented at the protocol level.

This architectural choice gives Hackers' Pub the technical flexibility to implement username changes while maintaining account continuity across the fediverse.

GitHub-Inspired Approach

What This Means for Users

For Hackers' Pub users, this policy offers a significant advantage over other fediverse instances:

You can correct an unfortunate username choice
Your online identity can evolve as you do
Your content history remains intact during the transition
You maintain your social connections despite the change

The Future of Fediverse Identity

For now, users should consider this policy a compelling reason to choose Hackers' Pub as their fediverse home, especially if username flexibility matters to their online experience.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

https://hackers.pub/@hongminhee/2025/hackers-pub-introduces-flexible-username-changes

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

One-Time Username Change: Freedom with Responsibility

This one-time change limit strikes a careful balance—offering flexibility while maintaining the stability and reliability that's essential for a federated network.

Username Recycling: New Opportunities

For newcomers to the platform, this means a wider selection of desirable usernames might become available over time—something virtually unheard of in the traditional fediverse ecosystem.

Link Preservation: Maintaining Digital History

This temporary preservation period gives your connections time to adjust to your new identity while preventing immediate link rot across the federation.

The Technical Foundation: ActivityPub Actor URIs

What enables Hackers' Pub to offer username changes while other fediverse platforms can't? The answer lies in how actor identities are implemented at the protocol level.

This architectural choice gives Hackers' Pub the technical flexibility to implement username changes while maintaining account continuity across the fediverse.

GitHub-Inspired Approach

What This Means for Users

For Hackers' Pub users, this policy offers a significant advantage over other fediverse instances:

You can correct an unfortunate username choice
Your online identity can evolve as you do
Your content history remains intact during the transition
You maintain your social connections despite the change

The Future of Fediverse Identity

For now, users should consider this policy a compelling reason to choose Hackers' Pub as their fediverse home, especially if username flexibility matters to their online experience.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

https://hackers.pub/@hongminhee/2025/hackers-pub-introduces-flexible-username-changes

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

One-Time Username Change: Freedom with Responsibility

This one-time change limit strikes a careful balance—offering flexibility while maintaining the stability and reliability that's essential for a federated network.

Username Recycling: New Opportunities

For newcomers to the platform, this means a wider selection of desirable usernames might become available over time—something virtually unheard of in the traditional fediverse ecosystem.

Link Preservation: Maintaining Digital History

This temporary preservation period gives your connections time to adjust to your new identity while preventing immediate link rot across the federation.

The Technical Foundation: ActivityPub Actor URIs

What enables Hackers' Pub to offer username changes while other fediverse platforms can't? The answer lies in how actor identities are implemented at the protocol level.

This architectural choice gives Hackers' Pub the technical flexibility to implement username changes while maintaining account continuity across the fediverse.

GitHub-Inspired Approach

What This Means for Users

For Hackers' Pub users, this policy offers a significant advantage over other fediverse instances:

You can correct an unfortunate username choice
Your online identity can evolve as you do
Your content history remains intact during the transition
You maintain your social connections despite the change

The Future of Fediverse Identity

For now, users should consider this policy a compelling reason to choose Hackers' Pub as their fediverse home, especially if username flexibility matters to their online experience.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

https://hackers.pub/@hongminhee/2025/hackers-pub-introduces-flexible-username-changes

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

One-Time Username Change: Freedom with Responsibility

This one-time change limit strikes a careful balance—offering flexibility while maintaining the stability and reliability that's essential for a federated network.

Username Recycling: New Opportunities

For newcomers to the platform, this means a wider selection of desirable usernames might become available over time—something virtually unheard of in the traditional fediverse ecosystem.

Link Preservation: Maintaining Digital History

This temporary preservation period gives your connections time to adjust to your new identity while preventing immediate link rot across the federation.

The Technical Foundation: ActivityPub Actor URIs

What enables Hackers' Pub to offer username changes while other fediverse platforms can't? The answer lies in how actor identities are implemented at the protocol level.

This architectural choice gives Hackers' Pub the technical flexibility to implement username changes while maintaining account continuity across the fediverse.

GitHub-Inspired Approach

What This Means for Users

For Hackers' Pub users, this policy offers a significant advantage over other fediverse instances:

You can correct an unfortunate username choice
Your online identity can evolve as you do
Your content history remains intact during the transition
You maintain your social connections despite the change

The Future of Fediverse Identity

For now, users should consider this policy a compelling reason to choose Hackers' Pub as their fediverse home, especially if username flexibility matters to their online experience.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

One-Time Username Change: Freedom with Responsibility

This one-time change limit strikes a careful balance—offering flexibility while maintaining the stability and reliability that's essential for a federated network.

Username Recycling: New Opportunities

For newcomers to the platform, this means a wider selection of desirable usernames might become available over time—something virtually unheard of in the traditional fediverse ecosystem.

Link Preservation: Maintaining Digital History

This temporary preservation period gives your connections time to adjust to your new identity while preventing immediate link rot across the federation.

The Technical Foundation: ActivityPub Actor URIs

What enables Hackers' Pub to offer username changes while other fediverse platforms can't? The answer lies in how actor identities are implemented at the protocol level.

This architectural choice gives Hackers' Pub the technical flexibility to implement username changes while maintaining account continuity across the fediverse.

GitHub-Inspired Approach

What This Means for Users

For Hackers' Pub users, this policy offers a significant advantage over other fediverse instances:

You can correct an unfortunate username choice
Your online identity can evolve as you do
Your content history remains intact during the transition
You maintain your social connections despite the change

The Future of Fediverse Identity

For now, users should consider this policy a compelling reason to choose Hackers' Pub as their fediverse home, especially if username flexibility matters to their online experience.

洪民憙 (Hong Minhee)

@hongminhee@hackers.pub

One-Time Username Change: Freedom with Responsibility

This one-time change limit strikes a careful balance—offering flexibility while maintaining the stability and reliability that's essential for a federated network.

Username Recycling: New Opportunities

For newcomers to the platform, this means a wider selection of desirable usernames might become available over time—something virtually unheard of in the traditional fediverse ecosystem.

Link Preservation: Maintaining Digital History

This temporary preservation period gives your connections time to adjust to your new identity while preventing immediate link rot across the federation.

The Technical Foundation: ActivityPub Actor URIs

What enables Hackers' Pub to offer username changes while other fediverse platforms can't? The answer lies in how actor identities are implemented at the protocol level.

This architectural choice gives Hackers' Pub the technical flexibility to implement username changes while maintaining account continuity across the fediverse.

GitHub-Inspired Approach

What This Means for Users

For Hackers' Pub users, this policy offers a significant advantage over other fediverse instances:

You can correct an unfortunate username choice
Your online identity can evolve as you do
Your content history remains intact during the transition
You maintain your social connections despite the change

in my dream last night @peertube announced support for fediverse:creator tags attached to channels #fedidev

black lipstick on your flight controls

@vyr@princess.industries

we now have some GoToSocial docs about importing your archived posts in general: https://docs.gotosocial.org/en/latest/user_guide/importing_posts/

most of the specifics are in the slurp docs, but if you write your own importer and think it might be of general interest to GTS users, please let us know.

black lipstick on your flight controls

@vyr@princess.industries

we now have some GoToSocial docs about importing your archived posts in general: https://docs.gotosocial.org/en/latest/user_guide/importing_posts/

most of the specifics are in the slurp docs, but if you write your own importer and think it might be of general interest to GTS users, please let us know.

black lipstick on your flight controls

@vyr@princess.industries

we now have some GoToSocial docs about importing your archived posts in general: https://docs.gotosocial.org/en/latest/user_guide/importing_posts/

most of the specifics are in the slurp docs, but if you write your own importer and think it might be of general interest to GTS users, please let us know.

black lipstick on your flight controls

@vyr@princess.industries

we now have some GoToSocial docs about importing your archived posts in general: https://docs.gotosocial.org/en/latest/user_guide/importing_posts/

most of the specifics are in the slurp docs, but if you write your own importer and think it might be of general interest to GTS users, please let us know.

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're considering packaging the Fedify CLI for Homebrew to make installation easier on macOS and Linux (via Linuxbrew).

Would you use a #Homebrew formula for #Fedify CLI?

Option	Voters
Yes, I'd definitely use it on macOS.	8 (32%)
Yes, I'd definitely use it on Linux.	3 (12%)
Maybe, depending on the implementation.	4 (16%)
No, I prefer other installation methods.	10 (40%)

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

If you answered “No”, which installation method do you prefer?

Your feedback helps us prioritize distribution channels! Thanks for contributing to the Fedify ecosystem.

Option	Voters
npm	3 (25%)
Deno	3 (25%)
Manual download	5 (42%)
Other (please specify in replies)	1 (8%)

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're considering packaging the Fedify CLI for Homebrew to make installation easier on macOS and Linux (via Linuxbrew).

Would you use a #Homebrew formula for #Fedify CLI?

Option	Voters
Yes, I'd definitely use it on macOS.	8 (32%)
Yes, I'd definitely use it on Linux.	3 (12%)
Maybe, depending on the implementation.	4 (16%)
No, I prefer other installation methods.	10 (40%)

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're considering packaging the Fedify CLI for Homebrew to make installation easier on macOS and Linux (via Linuxbrew).

Would you use a #Homebrew formula for #Fedify CLI?

Option	Voters
Yes, I'd definitely use it on macOS.	8 (32%)
Yes, I'd definitely use it on Linux.	3 (12%)
Maybe, depending on the implementation.	4 (16%)
No, I prefer other installation methods.	10 (40%)

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

If you answered “No”, which installation method do you prefer?

Your feedback helps us prioritize distribution channels! Thanks for contributing to the Fedify ecosystem.

Option	Voters
npm	3 (25%)
Deno	3 (25%)
Manual download	5 (42%)
Other (please specify in replies)	1 (8%)

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

If you answered “No”, which installation method do you prefer?

Your feedback helps us prioritize distribution channels! Thanks for contributing to the Fedify ecosystem.

Option	Voters
npm	3 (25%)
Deno	3 (25%)
Manual download	5 (42%)
Other (please specify in replies)	1 (8%)

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're considering packaging the Fedify CLI for Homebrew to make installation easier on macOS and Linux (via Linuxbrew).

Would you use a #Homebrew formula for #Fedify CLI?

Option	Voters
Yes, I'd definitely use it on macOS.	8 (32%)
Yes, I'd definitely use it on Linux.	3 (12%)
Maybe, depending on the implementation.	4 (16%)
No, I prefer other installation methods.	10 (40%)

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

If you answered “No”, which installation method do you prefer?

Your feedback helps us prioritize distribution channels! Thanks for contributing to the Fedify ecosystem.

Option	Voters
npm	3 (25%)
Deno	3 (25%)
Manual download	5 (42%)
Other (please specify in replies)	1 (8%)

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're considering packaging the Fedify CLI for Homebrew to make installation easier on macOS and Linux (via Linuxbrew).

Would you use a #Homebrew formula for #Fedify CLI?

#ActivityPub #ActivityStreams #DeSo #FediDev #FediDevs #Fediverse #FileExtension #OpenSocial #SocialWeb

Option	Voters
Yes, I'd definitely use it on macOS.	8 (32%)
Yes, I'd definitely use it on Linux.	3 (12%)
Maybe, depending on the implementation.	4 (16%)
No, I prefer other installation methods.	10 (40%)

@reiver ⊼ (Charles)

@reiver@mastodon.social · Reply to @reiver ⊼ (Charles) :batman:'s post

A good file-extension for ActivityPub / ActivityStream files might be:

.activity

And maybe also:

.jsonactivity

Those could be used to trigger a web-server to respond with the Content-Type "application/activity+json".

@reiver ⊼ (Charles)

@reiver@mastodon.social · Reply to @reiver ⊼ (Charles) :batman:'s post

.json isn't sufficient, since it would produce a Content-Type of "application/json" rather than "application/activity+json".

ActivityPub / ActivityStream files need their own file-extension.

...

#ActivityPub #ActivityStreams #DeSo #FediDev #FediDevs #Fediverse #FileExtension #OpenSocial #SocialWeb

@reiver ⊼ (Charles)

@reiver@mastodon.social

A file-extension for ActivityPub /ActivityStream files.

...

On many web-servers, the Content-Type returned when serving a file is based on the file-extension of the file.

Ex: .txt for text files, .gz for gzip files, .gmni for gemtext files, etc.

I am not aware of a widely used file-extension for ActivityStreams / ActivityPub files.

...

#ActivityPub #ActivityStreams #DeSo #FediDev #FediDevs #Fediverse #FileExtension #OpenSocial #SocialWeb

@reiver ⊼ (Charles)

@reiver@mastodon.social · Reply to @reiver ⊼ (Charles) :batman:'s post

This needs some testing to see what extant Fediverse software actually does.

For example — with the extant Fediverse software —

Does the avatar image, the (actor) name, etc show up with the post?

Does the post show up?

Etc?

#ActivityPub #ActivityStreams #DeSo #FediDev #FediDevs #Fediverse #OpenSocial #SocialWeb

@reiver ⊼ (Charles)

@reiver@mastodon.social · Reply to @reiver ⊼ (Charles) :batman:'s post

Now, this would probably break like counts, share counts, a replies to some degree.

But, if you didn't care about that, I think it should work.

...

#ActivityPub #ActivityStreams #DeSo #FediDev #FediDevs #Fediverse #OpenSocial #SocialWeb

@reiver ⊼ (Charles)

@reiver@mastodon.social · Reply to @reiver ⊼ (Charles) :batman:'s post

For example, at:

http;//example·com/object/123

You might have the activity-JSON (application/activity+json):

{

....

"attributedTo": "https;//mastodon·social/users/reiver",

...

}

I.e., a Note or Article or whatever is saying that the author is NOT an actor on the same server host (example·com), but an actor over on the server host mastodon·social.

...

#ActivityPub #ActivityStreams #DeSo #FediDev #FediDevs #Fediverse #OpenSocial #SocialWeb

@reiver ⊼ (Charles)

@reiver@mastodon.social

You could have a post on one server host attribute and account on another server host as its author.

All you have to do is set the "attributedTo" field appropriately.

https://www.w3.org/TR/activitystreams-vocabulary/#dfn-attributedto

For example....

#ActivityPub #ActivityStreams #DeSo #FediDev #FediDevs #Fediverse #OpenSocial #SocialWeb

Fedify: an ActivityPub server framework

@fedify@hollo.social

Excited to share that Fedify CLI is now available on Scoop for #Windows users! You can easily install it with scoop install fedify. One more way to get started with #ActivityPub development!

#ActivityPub #ActivityStreams #FediDev #FediDevs #Fediverse #HumanLegible #HumanWritable #INI #JSON #JSONLD #OpenSocial #SocialWeb

@reiver@mastodon.social · Reply to @reiver ⊼ (Charles) :batman:'s post

I agree that an open protocol is better and more important than just an application.

But I also think that an open file data format is better and more important than just an open protocol.

I.e.,:

file data format ≫ protocol ≫ app

...

@reiver ⊼ (Charles)

@reiver@mastodon.social

JSON-LD is not (non-programmer) human-legible format because — JSON is not (non-programmer) human-legible format.

JSON-LD and JSON are both also not (non-programmer) human-writable.

...

#ActivityPub #ActivityStreams #FediDev #FediDevs #Fediverse #HumanLegible #HumanWritable #INI #JSON #JSONLD #OpenSocial #SocialWeb

@reiver ⊼ (Charles)

@reiver@mastodon.social

ActivityPub outboxes are the new RSS / Atom / WebFeed.

You can just read from them to get a JSON feed of someone's posts.

I.e., you do NOT have to implement the full suite of Fediverse protocols, or Follow, or run your own server, or anything else to get someone's posts on the Fediverse — just read from their outbox.

#ActivityPub #ActivityStreams #AtomFeed #AtomFormat #DeSe #FediDev #FediDevs #Fediverse #JSON #OpenSocial #RSS #SocialWeb

BeBo

@aslmewes@ruhr.social

Are there any good #oss #jira #alternatives for small teams outside? #fedidev

@reiver ⊼ (Charles)

@reiver@mastodon.social

ActivityPub outboxes are the new RSS / Atom / WebFeed.

You can just read from them to get a JSON feed of someone's posts.

I.e., you do NOT have to implement the full suite of Fediverse protocols, or Follow, or run your own server, or anything else to get someone's posts on the Fediverse — just read from their outbox.

#ActivityPub #ActivityStreams #AtomFeed #AtomFormat #DeSe #FediDev #FediDevs #Fediverse #JSON #OpenSocial #RSS #SocialWeb

@reiver ⊼ (Charles)

@reiver@mastodon.social

What if a (new type of) Fediverse server automagically created an ActivityPub actor for each hash-tag.

So, for example, if someone on the server used:

⋕banana

(Then if the domain of the server is "example.com") then we would automagically have the actor:

＠banana＠example·com

Probably a group actor.

And it boosted any local post with that hash-tag.

Then you could follow a hash-tag on a server.

#ActivityPub #ActivityStreams #DeSe #FediDev #FediDevs #Fediverse #HashTag #OpenSocial #SocialWeb

@reiver ⊼ (Charles)

@reiver@mastodon.social

ActivityPub outboxes are the new RSS / Atom / WebFeed.

You can just read from them to get a JSON feed of someone's posts.

I.e., you do NOT have to implement the full suite of Fediverse protocols, or Follow, or run your own server, or anything else to get someone's posts on the Fediverse — just read from their outbox.

#ActivityPub #ActivityStreams #AtomFeed #AtomFormat #DeSe #FediDev #FediDevs #Fediverse #JSON #OpenSocial #RSS #SocialWeb

@reiver ⊼ (Charles)

@reiver@mastodon.social

This feels so wasteful —

Including the same content twice — once in "content" and again in "contentMap".

Hollo also serves as our testing ground for bleeding-edge Fedify features before they're officially released.

BotKit

BotKit's API is intentionally simple—you can create a complete bot in a single TypeScript file!

If you're interested in trying any of these projects or contributing to their development, check out:

BotKit's API is intentionally simple—you can create a complete bot in a single TypeScript file!

If you're interested in trying any of these projects or contributing to their development, check out:

BotKit by Fedify

@botkit@hollo.social

Are you interested in creating bots for the #fediverse? Meet #BotKit, a #TypeScript framework that makes bot development easier than ever!

Key Features:

True Independence

Create standalone #ActivityPub bots
No need for a Mastodon or Misskey account
Free from platform-specific limitations

Simple and Intuitive API

Create a complete bot in a single TypeScript file
Intuitive event handlers for mentions, follows, and messages
Rich text formatting with Markdown support

Modern Deployment

Deploy on Deno Deploy, Fly.io, Railway, or any virtual server
Minimal dependencies
Designed for modern cloud platforms

Enterprise-Ready Foundation

Built on Fedify, a rock-solid ActivityPub framework
Seamless federation with Mastodon, Misskey, and other platforms
Robust compatibility across the fediverse

Developer Experience

Full TypeScript support with great IDE integration
Comprehensive documentation
Built-in testing utilities

Here's a quick example of how simple it is to create a bot:

import { createBot, mention, text } from "@fedify/botkit";

const bot = createBot<void>({
  username: "greetbot",
  name: "Greet Bot",
  summary: text`A friendly bot that greets people!`,
  // ... configuration ...
});

// Respond to mentions
bot.onMention = async (session, message) => {
  await message.reply(text`Hi, ${message.actor}! Thanks for saying hello!`);
};

export default bot;

Getting Started:

Install #Deno
Run: deno add jsr:@fedify/botkit@^0.1.0-dev
Create your bot with just a few lines of code

Check out our documentation at https://botkit.fedify.dev/ to learn more!

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're excited to announce two major features coming in #Fedify 1.5.0, focused on giving you more control over domain names in your federated apps:

Separate WebFinger Host from Server Origin

Want different domains for your WebFinger handles and server URIs? Fedify 1.5.0 will let you use domains like @alice@example.com as fediverse handles while serving content from https://ap.example.com. This gives you more flexibility in how you structure your federated services.

Canonical Origin Support

Need to ensure consistent URLs across your infrastructure? The new canonical origin support lets you explicitly set your server's authoritative domain. This is particularly useful when running behind reverse proxies or load balancers—no more unexpected URLs generated from internal hostnames.

These features represent our ongoing commitment to making Fedify more flexible and production-ready.

Can't wait to try these features? You can experiment with them today using our unstable release v1.5.0-dev.680+562e3dc0 (JSR & npm). Keep in mind that this is an unstable release intended for testing—use it in production at your own risk.

Otherwise, stay tuned for the stable Fedify 1.5.0 release!

ALT text details

These features represent our ongoing commitment to making Fedify more flexible and production-ready.

Otherwise, stay tuned for the stable Fedify 1.5.0 release!

#FediDev #ActivityPub
https://gts.superseriousbusiness.org/@dumpsterqueer/statuses/01JMPV10WQX3JKAXY3TY319EGS

ALT text details

Jeff Sikes

@box464@mastodon.social

Share this news with your favorite app developers!

GoToSocial has documented their new global and post level interaction policies. I know @Fedicat has already added these - would love to see them in other apps too.

Jeff Sikes

@box464@mastodon.social

Share this news with your favorite app developers!

GoToSocial has documented their new global and post level interaction policies. I know @Fedicat has already added these - would love to see them in other apps too.

#FediDev #ActivityPub
https://gts.superseriousbusiness.org/@dumpsterqueer/statuses/01JMPV10WQX3JKAXY3TY319EGS

@reiver ⊼ (Charles)

@reiver@mastodon.social

A topical or community Fediverse Relays — ex: a Paleogenetics relay server, or an animal photography relay server, or a company focused relay server, etc —

Would be similar to the old PlanetPlanet river-of-news feed-reader blogs.

https://web.archive.org/web/20171029175722/http://www.planetplanet.org/

RE: https://mastodon.social/@reiver/114044648006460577

#DeSo #FediDev #FediDevs #FediRelay #Fediverse #FediverseRelay #PlanetPlanet #Relay

@reiver ⊼ (Charles)

@reiver@mastodon.social

A topical or community Fediverse Relays could be very useful (in addition to generic ones).

Ex: a Paleogenetics relay server, or an animal photography relay server, or a company focused relay server, etc

Especially for single-user, community, team, organization, themed, etc server instances

It would also help save storage space on server instances, by the relay being selective in what it shares.

#DeSo #FediDev #FediDevs #FediRelay #Fediverse #FediverseRelay #Relay

black lipstick on your flight controls

@vyr@princess.industries · Reply to black lipstick on your flight controls's post

slurp can now import your pixelfed-statuses.json to a GoToSocial server and save your photos locally in the process, provided your original Pixelfed server and account are still available to provide the photos.

https://github.com/VyrCossont/slurp?tab=readme-ov-file#importing-a-pixelfed-archive

this is only lightly tested; please let me know if it works for you.

#GoToSocial #GTS #Pixelfed #FediDev

black lipstick on your flight controls

@vyr@princess.industries · Reply to black lipstick on your flight controls's post

https://github.com/VyrCossont/slurp?tab=readme-ov-file#importing-a-pixelfed-archive

this is only lightly tested; please let me know if it works for you.

#GoToSocial #GTS #Pixelfed #FediDev

@reiver ⊼ (Charles)

@reiver@mastodon.social · Reply to @reiver ⊼ (Charles) :batman:'s post

And just for the record —

Just like everyone else I contacted about their 'discoverable' flag being defaulted to 'false' —

He wasn't aware of the 'discoverable' flag existing (just like everyone else I contacted).

He didn't want to be hidden (just like everyone else I contacted).

He changed it to 'true' (just like everyone else I contacted).

#ActivityPub #ActivityStreams #DeSo #Discoverable #FediDev #FediDevs #Fediverse #FediverseUX #JSONLD #Mastodon #SocialWeb

@reiver ⊼ (Charles)

@reiver@mastodon.social · Reply to @reiver ⊼ (Charles) :batman:'s post

As it is now, I think the 'discoverable' flag is broken.

And, I think the whole user-experience (UX) around the 'discoverable' flag is poor.

And, I think Fediverse software treating a 'false' value for 'discoverable' as "not discoverable" (rather than "not discoverable" or "no choice made") has hugely negative consequences for the user-experience (UX) of the Fediverse

#ActivityPub #ActivityStreams #DeSo #Discoverable #FediDev #FediDevs #Fediverse #FediverseUX #JSONLD #Mastodon #SocialWeb

@reiver ⊼ (Charles)

@reiver@mastodon.social · Reply to @reiver ⊼ (Charles) :batman:'s post

So now I have to DM Ben to tell him that his 'discoverable' flag is set to false

He (just like everyone else I contacted) will likely not even be aware that the 'discoverable' flag exists

And (just like everyone else I contacted) wished it wasn't set to false

And then (just like everyone else I contacted) struggle to find where he can set it to true

And then set it

#ActivityPub #ActivityStreams #DeSo #Discoverable #FediDev #FediDevs #Fediverse #FediverseUX #JSONLD #Mastodon #SocialWeb

@reiver ⊼ (Charles)

@reiver@mastodon.social · Reply to @reiver ⊼ (Charles) :batman:'s post

As it is now, the 'discoverable' flag seems broken to me.

Because 'false' doesn't actually mean 'false'.

'false' (in practice) means both "not discoverable" and "no choice made". And this is a very unfortunate situation —

Because the idea of a 'discoverable' flag is a good idea — but this problem with the meaning of 'false' and the UX consequences a big deal.

#ActivityPub #ActivityStreams #DeSo #Discoverable #FediDev #FediDevs #Fediverse #FediverseUX #JSONLD #Mastodon #SocialWeb

@reiver ⊼ (Charles)

@reiver@mastodon.social · Reply to @reiver ⊼ (Charles) :batman:'s post

JSON and has a 'null'. That could have been used for the 'discoverable' flag.

We could have had so that:

'discoverable' set to 'true' meant that the user explicitly chose to be discoverable.

'discoverable' set to 'false' meant that the user explicitly chose to not be discoverable.

And 'discoverable' set to 'null' meant that the user has not explicitly made a choice.

#ActivityPub #ActivityStreams #DeSo #Discoverable #FediDev #FediDevs #Fediverse #FediverseUX #JSONLD #Mastodon #SocialWeb

@reiver ⊼ (Charles)

@reiver@mastodon.social · Reply to @reiver ⊼ (Charles) :batman:'s post

With other conceptions, this lack of choice — this lack of setting a value — isn't as muddled.

With optional-types (which are also called "option-types" and "maybe-types") when something isn't assigned a value it is represented as 'nothing' / 'none'.

In relation-databases, this is represented as 'null'.

#ActivityPub #ActivityStreams #DeSo #Discoverable #FediDev #FediDevs #Fediverse #FediverseUX #JSONLD #Mastodon #SocialWeb

@reiver ⊼ (Charles)

@reiver@mastodon.social · Reply to @reiver ⊼ (Charles) :batman:'s post

As it is right now, the 'discoverable' flag does not communicate whether the user actually made a 'true' or 'false' choice.

If it is 'true' we know they made a choice.

But if it is 'false' it either means the user chose 'false' or the user didn't make a choice. BUT WE CANNOT TELL THE DIFFERENCE.

#ActivityPub #ActivityStreams #DeSo #Discoverable #FediDev #FediDevs #Fediverse #FediverseUX #JSONLD #Mastodon #SocialWeb

@reiver ⊼ (Charles)

@reiver@mastodon.social · Reply to @reiver ⊼ (Charles) :batman:'s post

There are a HUGE number of people who (unknown to them) have their 'discoverable' flags set to 'false' who —

№2:

Do NOT know that they have a 'discoverable' flag —

And do NOT know that their 'discoverable' flag was automagically set to 'false' —

And do not understand the consequence of having their 'discoverable' flag set to false.

#ActivityPub #ActivityStreams #DeSo #Discoverable #FediDev #FediDevs #Fediverse #FediverseUX #JSONLD #Mastodon #SocialWeb

@reiver ⊼ (Charles)

@reiver@mastodon.social

A problem with the 'discoverable' flag (in Mastodon and any other Fediverse software that added it) is —

There are a HUGE number of people who (unknown to them) have their 'discoverable' flags set to 'false' who —

№1:

Did NOT set their 'discoverable' to 'false' themselves.

Mastodon assigned it for them without ever asking them before hand and getting consent.

#ActivityPub #ActivityStreams #DeSo #Discoverable #FediDev #FediDevs #Fediverse #FediverseUX #JSONLD #Mastodon #SocialWeb

black lipstick on your flight controls

@vyr@princess.industries · Reply to black lipstick on your flight controls's post

i've documented how to use slurp to import a Mastodon archive into GoToSocial 0.18 with status backdating: https://github.com/VyrCossont/slurp?tab=readme-ov-file#importing-a-mastodon-archive

#ActivityPub #ActivityStreams #DeSo #Discoverable #FediDev #FediDevs #Fediverse #FediverseUX #JSONLD #Mastodon #SocialWeb

@reiver ⊼ (Charles)

@reiver@mastodon.social · Reply to @reiver ⊼ (Charles) :batman:'s post

As it is now, I think the 'discoverable' flag is broken.

And, I think the whole user-experience (UX) around the 'discoverable' flag is poor.

@reiver ⊼ (Charles)

@reiver@mastodon.social · Reply to @reiver ⊼ (Charles) :batman:'s post

So now I have to DM Ben to tell him that his 'discoverable' flag is set to false

He (just like everyone else I contacted) will likely not even be aware that the 'discoverable' flag exists

And (just like everyone else I contacted) wished it wasn't set to false

And then (just like everyone else I contacted) struggle to find where he can set it to true

And then set it

#ActivityPub #ActivityStreams #DeSo #Discoverable #FediDev #FediDevs #Fediverse #FediverseUX #JSONLD #Mastodon #SocialWeb

@reiver ⊼ (Charles)

@reiver@mastodon.social · Reply to @reiver ⊼ (Charles) :batman:'s post

As it is now, the 'discoverable' flag seems broken to me.

Because 'false' doesn't actually mean 'false'.

'false' (in practice) means both "not discoverable" and "no choice made". And this is a very unfortunate situation —

Because the idea of a 'discoverable' flag is a good idea — but this problem with the meaning of 'false' and the UX consequences a big deal.

#ActivityPub #ActivityStreams #DeSo #Discoverable #FediDev #FediDevs #Fediverse #FediverseUX #JSONLD #Mastodon #SocialWeb

@reiver ⊼ (Charles)

@reiver@mastodon.social · Reply to @reiver ⊼ (Charles) :batman:'s post

JSON and has a 'null'. That could have been used for the 'discoverable' flag.

We could have had so that:

'discoverable' set to 'true' meant that the user explicitly chose to be discoverable.

'discoverable' set to 'false' meant that the user explicitly chose to not be discoverable.

And 'discoverable' set to 'null' meant that the user has not explicitly made a choice.

#ActivityPub #ActivityStreams #DeSo #Discoverable #FediDev #FediDevs #Fediverse #FediverseUX #JSONLD #Mastodon #SocialWeb

@reiver ⊼ (Charles)

@reiver@mastodon.social · Reply to @reiver ⊼ (Charles) :batman:'s post

With other conceptions, this lack of choice — this lack of setting a value — isn't as muddled.

With optional-types (which are also called "option-types" and "maybe-types") when something isn't assigned a value it is represented as 'nothing' / 'none'.

In relation-databases, this is represented as 'null'.

@vyr@princess.industries · Reply to black lipstick on your flight controls's post

i've documented how to use slurp to import a Mastodon archive into GoToSocial 0.18 with status backdating: https://github.com/VyrCossont/slurp?tab=readme-ov-file#importing-a-mastodon-archive

https://mastodon.social/@suvam/113935527367354872

@reiver ⊼ (Charles)

@reiver@mastodon.social

I can tell you from experience of hosting many people's Fediverse server instances for a number of years now that —

Many Fediverse software (at least currently) do a poor job of cleaning-up their various caches

Caching other people's profiles, images, posts, etc

@liaizon@social.wake.st · Reply to wakest ⁂'s post

Oh totally a coincidence! Looks like @suvam is implementing this exact thing already in #DhaagaApp! #fedidev is fast paced!

wakest ⁂

@liaizon@social.wake.st

Is there any #fediverse apps that let you bookmark posts into folders or categories? This is something that I see a lot of people using on Instagram that is incredibly useful. Could totally be done entirely client side too if someone wanted to implement it. #fedidev

wakest ⁂

@liaizon@social.wake.st

Really annoying gripe that I hope someone on the #fediverse is working on. If there is a long thread with many participants and 1 out of the many in that thread has your instance defederated, it breaks viewing the whole thread while logged in, so I have to go to another instance or a logged out view to *read* the whole thread. #fedidev

wakest ⁂

@liaizon@social.wake.st

wakest ⁂

@liaizon@social.wake.st

wakest ⁂

@liaizon@social.wake.st

"we can’t ignore the composition of the Unicode Consortium’s members, directors, and officers, the people who define the everyday writing systems of all languages across the globe. They are comprised largely of white men (and a few white women) whose first language was either English or another European language"
https://hci.social/@peterpur/114014097928801232 #fedidev

wakest ⁂

@liaizon@social.wake.st

This is the best rant about the #fediverse I have read in a while. Bravo @annie, this is an amazing resource to have at hand.
https://social.lol/@annie/114010645430063971 #fedidev

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

📢 Fedifyで独自のフェディバースサーバーを構築しましょう！

FedifyはActivityPubプロトコルの実装を簡単にするTypeScriptフレームワークです。連合プロトコルの複雑な実装に困っていませんか？Fedifyがお手伝いします！

✨ 主な機能

WebFinger、HTTP Signatures、NodeInfoなど基本プロトコルを完全サポート
Object Integrity ProofsとLinked Data Signaturesによる様々なフェディバースソフトウェアとの相互運用性
型安全なActivity Vocabulary APIで開発ミスを防止
自動リトライとメッセージキューによる安定した配信
OpenTelemetry連携による完全な可観測性
Redis、PostgreSQL、AMQPなど様々なバックエンドをサポート
Express、Hono、Fresh、SvelteKitなど人気のWebフレームワークと統合
包括的なロギングとトレース機能

🔧 CLIツール

一時的なテストインボックスでActivityPubのリアルタイムデバッグ
lookupツールでActivityPubオブジェクトとアクターを検査
ローカル開発用のトンネリング機能

🚀 ランタイムサポート

📚 学習が簡単

詳細なドキュメント
ステップバイステップのチュートリアル
MatrixとDiscord（日本語対応）によるコミュニティサポート

MITライセンスで自由に利用可能なオープンソースプロジェクトです！

#Fedify #フェディバース #fediverse #fedidev #TypeScript #ActivityPub

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

📢 여러분만의 #연합우주 서버를 Fedify로 만들어보세요!

Fedify는 #ActivityPub 프로토콜 구현을 도와주는 #TypeScript 프레임워크입니다. 복잡한 연합 프로토콜을 쉽게 구현하고 싶으신가요? Fedify가 도와드립니다!

✨ 주요 기능

WebFinger, HTTP Signatures, NodeInfo 등 기본 프로토콜 완벽 지원
Object Integrity Proofs와 Linked Data Signatures를 통한 다양한 페디버스 소프트웨어와의 상호운용성
타입 안전한 Activity Vocabulary API로 개발 실수 방지
자동 재시도와 메시지 큐를 통한 안정적인 발송
OpenTelemetry 통합으로 완벽한 모니터링
Redis, PostgreSQL, AMQP 등 다양한 백엔드 지원
Express, Hono, Fresh, SvelteKit 등 인기 웹 프레임워크와 통합
상세한 로깅과 추적 기능

🔧 CLI 도구

🚀 런타임 지원

📚 배우기 쉽습니다

상세한 문서
따라하기 쉬운 튜토리얼
Matrix 및 Discord(한국어 대응)를 통한 커뮤니티 지원

오픈소스 #MIT 라이선스로 누구나 자유롭게 사용할 수 있습니다!

Fedify: an ActivityPub server framework

@fedify@hollo.social

Build your own #fediverse server with #Fedify!

Fedify is a #TypeScript framework that simplifies #ActivityPub implementation. Want to build a federated server without the complexity? Fedify has got you covered!

✨ Key features

Complete protocol support including WebFinger, HTTP Signatures, and NodeInfo
Enhanced interoperability with Object Integrity Proofs and Linked Data Signatures
Type-safe Activity Vocabulary API to prevent development mistakes
Reliable delivery with automatic retries and message queues
Full observability through OpenTelemetry integration
Multiple backend support: Redis, PostgreSQL, AMQP
Seamless integration with popular web frameworks: Express, Hono, Fresh, SvelteKit
Comprehensive logging and tracing

🔧 CLI toolchain

Debug ActivityPub in real-time with ephemeral inbox server
Inspect ActivityPub objects and actors with lookup tool
Tunnel your local server for development

🚀 Runtime support

📚 Easy to learn

Available under the #MIT license—free and open source!

#CDN #ContentDeliveryNetwork #ContentDistributionNetwork #DeSo #FediCDN #FediDev #FediDevs #Fediverse

@reiver ⊼ (Charles)

@reiver@mastodon.social

User profiles, posts, images, and other content is cached across the various servers on the Fediverse.

Conceptually, software could access any of that from any server that cached it (and not just the origin server).

You could have a type of Fediverse content-distribution-network (CDN) if you did.

Fedify: an ActivityPub server framework

@fedify@hollo.social

Build your own #fediverse server with #Fedify!

Fedify is a #TypeScript framework that simplifies #ActivityPub implementation. Want to build a federated server without the complexity? Fedify has got you covered!

✨ Key features

Complete protocol support including WebFinger, HTTP Signatures, and NodeInfo
Enhanced interoperability with Object Integrity Proofs and Linked Data Signatures
Type-safe Activity Vocabulary API to prevent development mistakes
Reliable delivery with automatic retries and message queues
Full observability through OpenTelemetry integration
Multiple backend support: Redis, PostgreSQL, AMQP
Seamless integration with popular web frameworks: Express, Hono, Fresh, SvelteKit
Comprehensive logging and tracing

🔧 CLI toolchain

Debug ActivityPub in real-time with ephemeral inbox server
Inspect ActivityPub objects and actors with lookup tool
Tunnel your local server for development

🚀 Runtime support

📚 Easy to learn

Available under the #MIT license—free and open source!

#ActivityPub #ActivityStreams #FediDev #FediDevs #Fediverse #JSONLD

wakest ⁂

@liaizon@social.wake.st

Has anyone made a directory page of all the #FEPs with simple descriptions of what they are for yet? #fedidev

@reiver ⊼ (Charles)

@reiver@mastodon.social

Could ActivityPub / ActivityStreams be used to synchronize files across separate machines / computers / devices‽

I think the answer is, YES.

❦

The inbox-outbox system could enable you to send messages between separate machines / computers / devices.

The 'messages' transfer the changed 'blocks' / 'chunks' that make up a file, notify about deletions, file creations, etc

Existing Activity Types might be sufficient to do this

Fedify: an ActivityPub server framework

@fedify@hollo.social

Build your own #fediverse server with #Fedify!

Fedify is a #TypeScript framework that simplifies #ActivityPub implementation. Want to build a federated server without the complexity? Fedify has got you covered!

✨ Key features

Complete protocol support including WebFinger, HTTP Signatures, and NodeInfo
Enhanced interoperability with Object Integrity Proofs and Linked Data Signatures
Type-safe Activity Vocabulary API to prevent development mistakes
Reliable delivery with automatic retries and message queues
Full observability through OpenTelemetry integration
Multiple backend support: Redis, PostgreSQL, AMQP
Seamless integration with popular web frameworks: Express, Hono, Fresh, SvelteKit
Comprehensive logging and tracing

🔧 CLI toolchain

Debug ActivityPub in real-time with ephemeral inbox server
Inspect ActivityPub objects and actors with lookup tool
Tunnel your local server for development

🚀 Runtime support

📚 Easy to learn

Available under the #MIT license—free and open source!

#Fedify #フェディバース #fediverse #fedidev #TypeScript #ActivityPub

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

📢 Fedifyで独自のフェディバースサーバーを構築しましょう！

✨ 主な機能

WebFinger、HTTP Signatures、NodeInfoなど基本プロトコルを完全サポート
Object Integrity ProofsとLinked Data Signaturesによる様々なフェディバースソフトウェアとの相互運用性
型安全なActivity Vocabulary APIで開発ミスを防止
自動リトライとメッセージキューによる安定した配信
OpenTelemetry連携による完全な可観測性
Redis、PostgreSQL、AMQPなど様々なバックエンドをサポート
Express、Hono、Fresh、SvelteKitなど人気のWebフレームワークと統合
包括的なロギングとトレース機能

🔧 CLIツール

一時的なテストインボックスでActivityPubのリアルタイムデバッグ
lookupツールでActivityPubオブジェクトとアクターを検査
ローカル開発用のトンネリング機能

🚀 ランタイムサポート

📚 学習が簡単

詳細なドキュメント
ステップバイステップのチュートリアル
MatrixとDiscord（日本語対応）によるコミュニティサポート

MITライセンスで自由に利用可能なオープンソースプロジェクトです！

Fedify: an ActivityPub server framework

@fedify@hollo.social

Build your own #fediverse server with #Fedify!

Fedify is a #TypeScript framework that simplifies #ActivityPub implementation. Want to build a federated server without the complexity? Fedify has got you covered!

✨ Key features

Complete protocol support including WebFinger, HTTP Signatures, and NodeInfo
Enhanced interoperability with Object Integrity Proofs and Linked Data Signatures
Type-safe Activity Vocabulary API to prevent development mistakes
Reliable delivery with automatic retries and message queues
Full observability through OpenTelemetry integration
Multiple backend support: Redis, PostgreSQL, AMQP
Seamless integration with popular web frameworks: Express, Hono, Fresh, SvelteKit
Comprehensive logging and tracing

🔧 CLI toolchain

Debug ActivityPub in real-time with ephemeral inbox server
Inspect ActivityPub objects and actors with lookup tool
Tunnel your local server for development

🚀 Runtime support

📚 Easy to learn

Available under the #MIT license—free and open source!

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

📢 여러분만의 #연합우주 서버를 Fedify로 만들어보세요!

Fedify는 #ActivityPub 프로토콜 구현을 도와주는 #TypeScript 프레임워크입니다. 복잡한 연합 프로토콜을 쉽게 구현하고 싶으신가요? Fedify가 도와드립니다!

✨ 주요 기능

WebFinger, HTTP Signatures, NodeInfo 등 기본 프로토콜 완벽 지원
Object Integrity Proofs와 Linked Data Signatures를 통한 다양한 페디버스 소프트웨어와의 상호운용성
타입 안전한 Activity Vocabulary API로 개발 실수 방지
자동 재시도와 메시지 큐를 통한 안정적인 발송
OpenTelemetry 통합으로 완벽한 모니터링
Redis, PostgreSQL, AMQP 등 다양한 백엔드 지원
Express, Hono, Fresh, SvelteKit 등 인기 웹 프레임워크와 통합
상세한 로깅과 추적 기능

🔧 CLI 도구

🚀 런타임 지원

📚 배우기 쉽습니다

상세한 문서
따라하기 쉬운 튜토리얼
Matrix 및 Discord(한국어 대응)를 통한 커뮤니티 지원

오픈소스 #MIT 라이선스로 누구나 자유롭게 사용할 수 있습니다!

Fedify: an ActivityPub server framework

@fedify@hollo.social

Build your own #fediverse server with #Fedify!

Fedify is a #TypeScript framework that simplifies #ActivityPub implementation. Want to build a federated server without the complexity? Fedify has got you covered!

✨ Key features

Complete protocol support including WebFinger, HTTP Signatures, and NodeInfo
Enhanced interoperability with Object Integrity Proofs and Linked Data Signatures
Type-safe Activity Vocabulary API to prevent development mistakes
Reliable delivery with automatic retries and message queues
Full observability through OpenTelemetry integration
Multiple backend support: Redis, PostgreSQL, AMQP
Seamless integration with popular web frameworks: Express, Hono, Fresh, SvelteKit
Comprehensive logging and tracing

🔧 CLI toolchain

Debug ActivityPub in real-time with ephemeral inbox server
Inspect ActivityPub objects and actors with lookup tool
Tunnel your local server for development

🚀 Runtime support

📚 Easy to learn

Available under the #MIT license—free and open source!

#Fedify #フェディバース #fediverse #fedidev #TypeScript #ActivityPub

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

📢 Fedifyで独自のフェディバースサーバーを構築しましょう！

✨ 主な機能

WebFinger、HTTP Signatures、NodeInfoなど基本プロトコルを完全サポート
Object Integrity ProofsとLinked Data Signaturesによる様々なフェディバースソフトウェアとの相互運用性
型安全なActivity Vocabulary APIで開発ミスを防止
自動リトライとメッセージキューによる安定した配信
OpenTelemetry連携による完全な可観測性
Redis、PostgreSQL、AMQPなど様々なバックエンドをサポート
Express、Hono、Fresh、SvelteKitなど人気のWebフレームワークと統合
包括的なロギングとトレース機能

🔧 CLIツール

一時的なテストインボックスでActivityPubのリアルタイムデバッグ
lookupツールでActivityPubオブジェクトとアクターを検査
ローカル開発用のトンネリング機能

🚀 ランタイムサポート

📚 学習が簡単

詳細なドキュメント
ステップバイステップのチュートリアル
MatrixとDiscord（日本語対応）によるコミュニティサポート

MITライセンスで自由に利用可能なオープンソースプロジェクトです！

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

📢 Fedifyで独自のフェディバースサーバーを構築しましょう！

✨ 主な機能

WebFinger、HTTP Signatures、NodeInfoなど基本プロトコルを完全サポート
Object Integrity ProofsとLinked Data Signaturesによる様々なフェディバースソフトウェアとの相互運用性
型安全なActivity Vocabulary APIで開発ミスを防止
自動リトライとメッセージキューによる安定した配信
OpenTelemetry連携による完全な可観測性
Redis、PostgreSQL、AMQPなど様々なバックエンドをサポート
Express、Hono、Fresh、SvelteKitなど人気のWebフレームワークと統合
包括的なロギングとトレース機能

🔧 CLIツール

一時的なテストインボックスでActivityPubのリアルタイムデバッグ
lookupツールでActivityPubオブジェクトとアクターを検査
ローカル開発用のトンネリング機能

🚀 ランタイムサポート

📚 学習が簡単

詳細なドキュメント
ステップバイステップのチュートリアル
MatrixとDiscord（日本語対応）によるコミュニティサポート

MITライセンスで自由に利用可能なオープンソースプロジェクトです！

#Fedify #フェディバース #fediverse #fedidev #TypeScript #ActivityPub

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

📢 Fedifyで独自のフェディバースサーバーを構築しましょう！

✨ 主な機能

WebFinger、HTTP Signatures、NodeInfoなど基本プロトコルを完全サポート
Object Integrity ProofsとLinked Data Signaturesによる様々なフェディバースソフトウェアとの相互運用性
型安全なActivity Vocabulary APIで開発ミスを防止
自動リトライとメッセージキューによる安定した配信
OpenTelemetry連携による完全な可観測性
Redis、PostgreSQL、AMQPなど様々なバックエンドをサポート
Express、Hono、Fresh、SvelteKitなど人気のWebフレームワークと統合
包括的なロギングとトレース機能

🔧 CLIツール

一時的なテストインボックスでActivityPubのリアルタイムデバッグ
lookupツールでActivityPubオブジェクトとアクターを検査
ローカル開発用のトンネリング機能

🚀 ランタイムサポート

📚 学習が簡単

詳細なドキュメント
ステップバイステップのチュートリアル
MatrixとDiscord（日本語対応）によるコミュニティサポート

MITライセンスで自由に利用可能なオープンソースプロジェクトです！

#Fedify #フェディバース #fediverse #fedidev #TypeScript #ActivityPub

Fedify: an ActivityPub server framework

@fedify@hollo.social

Build your own #fediverse server with #Fedify!

Fedify is a #TypeScript framework that simplifies #ActivityPub implementation. Want to build a federated server without the complexity? Fedify has got you covered!

✨ Key features

Complete protocol support including WebFinger, HTTP Signatures, and NodeInfo
Enhanced interoperability with Object Integrity Proofs and Linked Data Signatures
Type-safe Activity Vocabulary API to prevent development mistakes
Reliable delivery with automatic retries and message queues
Full observability through OpenTelemetry integration
Multiple backend support: Redis, PostgreSQL, AMQP
Seamless integration with popular web frameworks: Express, Hono, Fresh, SvelteKit
Comprehensive logging and tracing

🔧 CLI toolchain

Debug ActivityPub in real-time with ephemeral inbox server
Inspect ActivityPub objects and actors with lookup tool
Tunnel your local server for development

🚀 Runtime support

📚 Easy to learn

Available under the #MIT license—free and open source!

#Fedify #フェディバース #fediverse #fedidev #TypeScript #ActivityPub

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

📢 Fedifyで独自のフェディバースサーバーを構築しましょう！

✨ 主な機能

WebFinger、HTTP Signatures、NodeInfoなど基本プロトコルを完全サポート
Object Integrity ProofsとLinked Data Signaturesによる様々なフェディバースソフトウェアとの相互運用性
型安全なActivity Vocabulary APIで開発ミスを防止
自動リトライとメッセージキューによる安定した配信
OpenTelemetry連携による完全な可観測性
Redis、PostgreSQL、AMQPなど様々なバックエンドをサポート
Express、Hono、Fresh、SvelteKitなど人気のWebフレームワークと統合
包括的なロギングとトレース機能

🔧 CLIツール

一時的なテストインボックスでActivityPubのリアルタイムデバッグ
lookupツールでActivityPubオブジェクトとアクターを検査
ローカル開発用のトンネリング機能

🚀 ランタイムサポート

📚 学習が簡単

詳細なドキュメント
ステップバイステップのチュートリアル
MatrixとDiscord（日本語対応）によるコミュニティサポート

MITライセンスで自由に利用可能なオープンソースプロジェクトです！

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

📢 여러분만의 #연합우주 서버를 Fedify로 만들어보세요!

Fedify는 #ActivityPub 프로토콜 구현을 도와주는 #TypeScript 프레임워크입니다. 복잡한 연합 프로토콜을 쉽게 구현하고 싶으신가요? Fedify가 도와드립니다!

✨ 주요 기능

WebFinger, HTTP Signatures, NodeInfo 등 기본 프로토콜 완벽 지원
Object Integrity Proofs와 Linked Data Signatures를 통한 다양한 페디버스 소프트웨어와의 상호운용성
타입 안전한 Activity Vocabulary API로 개발 실수 방지
자동 재시도와 메시지 큐를 통한 안정적인 발송
OpenTelemetry 통합으로 완벽한 모니터링
Redis, PostgreSQL, AMQP 등 다양한 백엔드 지원
Express, Hono, Fresh, SvelteKit 등 인기 웹 프레임워크와 통합
상세한 로깅과 추적 기능

🔧 CLI 도구

🚀 런타임 지원

📚 배우기 쉽습니다

상세한 문서
따라하기 쉬운 튜토리얼
Matrix 및 Discord(한국어 대응)를 통한 커뮤니티 지원

오픈소스 #MIT 라이선스로 누구나 자유롭게 사용할 수 있습니다!

Fedify: an ActivityPub server framework

@fedify@hollo.social

Build your own #fediverse server with #Fedify!

Fedify is a #TypeScript framework that simplifies #ActivityPub implementation. Want to build a federated server without the complexity? Fedify has got you covered!

✨ Key features

Complete protocol support including WebFinger, HTTP Signatures, and NodeInfo
Enhanced interoperability with Object Integrity Proofs and Linked Data Signatures
Type-safe Activity Vocabulary API to prevent development mistakes
Reliable delivery with automatic retries and message queues
Full observability through OpenTelemetry integration
Multiple backend support: Redis, PostgreSQL, AMQP
Seamless integration with popular web frameworks: Express, Hono, Fresh, SvelteKit
Comprehensive logging and tracing

🔧 CLI toolchain

Debug ActivityPub in real-time with ephemeral inbox server
Inspect ActivityPub objects and actors with lookup tool
Tunnel your local server for development

🚀 Runtime support

📚 Easy to learn

Available under the #MIT license—free and open source!

#Fedify #フェディバース #fediverse #fedidev #TypeScript #ActivityPub

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

📢 Fedifyで独自のフェディバースサーバーを構築しましょう！

✨ 主な機能

WebFinger、HTTP Signatures、NodeInfoなど基本プロトコルを完全サポート
Object Integrity ProofsとLinked Data Signaturesによる様々なフェディバースソフトウェアとの相互運用性
型安全なActivity Vocabulary APIで開発ミスを防止
自動リトライとメッセージキューによる安定した配信
OpenTelemetry連携による完全な可観測性
Redis、PostgreSQL、AMQPなど様々なバックエンドをサポート
Express、Hono、Fresh、SvelteKitなど人気のWebフレームワークと統合
包括的なロギングとトレース機能

🔧 CLIツール

一時的なテストインボックスでActivityPubのリアルタイムデバッグ
lookupツールでActivityPubオブジェクトとアクターを検査
ローカル開発用のトンネリング機能

🚀 ランタイムサポート

📚 学習が簡単

詳細なドキュメント
ステップバイステップのチュートリアル
MatrixとDiscord（日本語対応）によるコミュニティサポート

MITライセンスで自由に利用可能なオープンソースプロジェクトです！

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

📢 여러분만의 #연합우주 서버를 Fedify로 만들어보세요!

Fedify는 #ActivityPub 프로토콜 구현을 도와주는 #TypeScript 프레임워크입니다. 복잡한 연합 프로토콜을 쉽게 구현하고 싶으신가요? Fedify가 도와드립니다!

✨ 주요 기능

WebFinger, HTTP Signatures, NodeInfo 등 기본 프로토콜 완벽 지원
Object Integrity Proofs와 Linked Data Signatures를 통한 다양한 페디버스 소프트웨어와의 상호운용성
타입 안전한 Activity Vocabulary API로 개발 실수 방지
자동 재시도와 메시지 큐를 통한 안정적인 발송
OpenTelemetry 통합으로 완벽한 모니터링
Redis, PostgreSQL, AMQP 등 다양한 백엔드 지원
Express, Hono, Fresh, SvelteKit 등 인기 웹 프레임워크와 통합
상세한 로깅과 추적 기능

🔧 CLI 도구

🚀 런타임 지원

📚 배우기 쉽습니다

상세한 문서
따라하기 쉬운 튜토리얼
Matrix 및 Discord(한국어 대응)를 통한 커뮤니티 지원

오픈소스 #MIT 라이선스로 누구나 자유롭게 사용할 수 있습니다!

Fedify: an ActivityPub server framework

@fedify@hollo.social

Build your own #fediverse server with #Fedify!

Fedify is a #TypeScript framework that simplifies #ActivityPub implementation. Want to build a federated server without the complexity? Fedify has got you covered!

✨ Key features

Complete protocol support including WebFinger, HTTP Signatures, and NodeInfo
Enhanced interoperability with Object Integrity Proofs and Linked Data Signatures
Type-safe Activity Vocabulary API to prevent development mistakes
Reliable delivery with automatic retries and message queues
Full observability through OpenTelemetry integration
Multiple backend support: Redis, PostgreSQL, AMQP
Seamless integration with popular web frameworks: Express, Hono, Fresh, SvelteKit
Comprehensive logging and tracing

🔧 CLI toolchain

Debug ActivityPub in real-time with ephemeral inbox server
Inspect ActivityPub objects and actors with lookup tool
Tunnel your local server for development

🚀 Runtime support

📚 Easy to learn

Available under the #MIT license—free and open source!

@reiver ⊼ (Charles)

@reiver@mastodon.social

#FollowFriday the Fediverse Core.

I.e., the people who make the technology of and for the Fediverse.

Fedify: an ActivityPub server framework

@fedify@hollo.social

Excited to share that Fedify CLI is now available on Scoop for #Windows users! You can easily install it with scoop install fedify. One more way to get started with #ActivityPub development!

Fedify: an ActivityPub server framework

@fedify@hollo.social

Excited to share that Fedify CLI is now available on Scoop for #Windows users! You can easily install it with scoop install fedify. One more way to get started with #ActivityPub development!

Fedify: an ActivityPub server framework

@fedify@hollo.social

Excited to share that Fedify CLI is now available on Scoop for #Windows users! You can easily install it with scoop install fedify. One more way to get started with #ActivityPub development!

https://www.w3.org/TR/activitystreams-vocabulary/#dfn-view

@reiver ⊼ (Charles)

@reiver@mastodon.social

Is any Fediverse software using or generating the 'View' activity-type?

You could create view-counts on posts, profiles, etc, using this.

Of course, there are privacy concerns with this.

And, also, what counts as a "view".

Although, I sometimes use a "Like" to indicate I viewed something. If a 'View' was something manual (such a pressing a button) that could be more semantically clean.

#ActivityPub #ActivityStreams #DeSe #FediDev #FediDevs #Fediverse #Privacy

@reiver ⊼ (Charles)

@reiver@mastodon.social

To me, it feels like the Activity Types should have been past-tense verbs, rather than present-tense verbs.

I.e.:

• "Accepted" rather than "Accept"
• "Added" rather than "Add"
• "Announced" rather than "Announce"
• "Arrived" rather than "Arrive"
• "Blocked" rather than "Block"
• "Created" rather than "Create"
• etc

Present-tense verbs feel like commands.

Past-tense verbs feel like events.

Activities are events not commands.

#ActivityPub #ActivityStreams #DeSo #FediDev #FediDevs #Fediverse

@reiver ⊼ (Charles)

@reiver@mastodon.social

To me, it feels like the Activity Types should have been past-tense verbs, rather than present-tense verbs.

I.e.:

Present-tense verbs feel like commands.

Past-tense verbs feel like events.

Activities are events not commands.

#ActivityPub #ActivityStreams #DeSo #FediDev #FediDevs #Fediverse

Fedify: an ActivityPub server framework

@fedify@hollo.social

Excited to share that Fedify CLI is now available on Scoop for #Windows users! You can easily install it with scoop install fedify. One more way to get started with #ActivityPub development!

#ActivityPub #ActivityStreams #DeSo #FediDev #FediDevs #Fediverse

@reiver ⊼ (Charles)

@reiver@mastodon.social

To me, it feels like the Activity Types should have been past-tense verbs, rather than present-tense verbs.

I.e.:

Present-tense verbs feel like commands.

Past-tense verbs feel like events.

Activities are events not commands.

Fedify: an ActivityPub server framework

@fedify@hollo.social

Excited to share that Fedify CLI is now available on Scoop for #Windows users! You can easily install it with scoop install fedify. One more way to get started with #ActivityPub development!

Fedify: an ActivityPub server framework

@fedify@hollo.social

Excited to share that Fedify CLI is now available on Scoop for #Windows users! You can easily install it with scoop install fedify. One more way to get started with #ActivityPub development!

Fedify: an ActivityPub server framework

@fedify@hollo.social

Visualize your server in the fediverse with the fedify node command and share it with us using the #FedifyNode hashtag!

ALT text details

The result of fedify node https://hollo.social/@fedify command. The NodeInfo document is visualized along with the favicon.

ALT text details

The result of fedify lookup venera.social. The NodeInfo document is visualized along with the favicon.

ALT text details

The result of fedify lookup misskey.io. The NodeInfo document is visualized along with the favicon.

ALT text details

The result of fedify lookup fosstodon.org. The NodeInfo document is visualized along with the favicon.

Fedify: an ActivityPub server framework

@fedify@hollo.social

Visualize your server in the fediverse with the fedify node command and share it with us using the #FedifyNode hashtag!

ALT text details

The result of fedify node https://hollo.social/@fedify command. The NodeInfo document is visualized along with the favicon.

ALT text details

The result of fedify lookup venera.social. The NodeInfo document is visualized along with the favicon.

ALT text details

The result of fedify lookup misskey.io. The NodeInfo document is visualized along with the favicon.

ALT text details

The result of fedify lookup fosstodon.org. The NodeInfo document is visualized along with the favicon.

Fedify: an ActivityPub server framework

@fedify@hollo.social

Visualize your server in the fediverse with the fedify node command and share it with us using the #FedifyNode hashtag!

#ActorTypeFeed #CustomFeeds #FediDev #FediDevs #Fediverse #FediverseCustomFeeds #FediverseFeeds #FediverseUX #SocialFed

ALT text details

The result of fedify node https://hollo.social/@fedify command. The NodeInfo document is visualized along with the favicon.

ALT text details

The result of fedify lookup venera.social. The NodeInfo document is visualized along with the favicon.

ALT text details

The result of fedify lookup misskey.io. The NodeInfo document is visualized along with the favicon.

ALT text details

The result of fedify lookup fosstodon.org. The NodeInfo document is visualized along with the favicon.

@reiver ⊼ (Charles)

@reiver@mastodon.social

I have been talking about Custom Feeds for the Fediverse.

I will be setting up a demo server for Custom Feeds — so Fediverse developers can ad support for Fediverse Custom Feeds to their software.

(And have something to test again.)

marius

@mariusor@metalhead.club

@silverpill any idea if there's a FEP regarding how to sign an activity that gets propagated through the Forwarding from Inbox mechanism? https://www.w3.org/TR/activitypub/#inbox-forwarding

My first instinct is to use the instance actor for the server that received it, but I'm not sure.

Maybe the actor that received it in their inbox would be better, but that feels slightly unsanitary.

#activitypub #fedidev #activitypubdev

marius

@mariusor@metalhead.club · Reply to marius's post

Anyone else keeping track of these tags feel free to jump in if you have any actionable ideas. :) TY

#activitypub #activitypubdev #fedidev

marius

@mariusor@metalhead.club

@silverpill any idea if there's a FEP regarding how to sign an activity that gets propagated through the Forwarding from Inbox mechanism? https://www.w3.org/TR/activitypub/#inbox-forwarding

My first instinct is to use the instance actor for the server that received it, but I'm not sure.

Maybe the actor that received it in their inbox would be better, but that feels slightly unsanitary.

#activitypub #fedidev #activitypubdev

Fedify: an ActivityPub server framework

@fedify@hollo.social

A milestone worth celebrating—#Fedify just hit 100+ releases! From day one, we've been committed to building a robust #ActivityPub framework, and each release has brought us closer to that goal. Here's to many more releases as we continue growing the #fediverse together! #fedidev

ALT text details

Screenshot shows release stats for Fedify: latest version 1.4.1 was released 6 minutes ago, with a green tag showing “Latest.” Total release count shows “+ 100 releases.” A green icon resembling a tag appears next to the Fedify name.

Fedify: an ActivityPub server framework

@fedify@hollo.social

ALT text details

BotKit by Fedify

@botkit@hollo.social

BotKit 0.1.1 is out!

This security update fixes a message visibility bug where direct/followers-only replies to bots were unintentionally forwarded to bot followers. Upgrade recommended. Download at JSR:

deno add jsr:@fedify/botkit@^0.1.1

Fedify: an ActivityPub server framework

@fedify@hollo.social

ALT text details

BotKit by Fedify

@botkit@hollo.social

BotKit 0.1.1 is out!

This security update fixes a message visibility bug where direct/followers-only replies to bots were unintentionally forwarded to bot followers. Upgrade recommended. Download at JSR:

deno add jsr:@fedify/botkit@^0.1.1

Fedify: an ActivityPub server framework

@fedify@hollo.social

ALT text details

Fedify: an ActivityPub server framework

@fedify@hollo.social

ALT text details

Fedify: an ActivityPub server framework

@fedify@hollo.social

ALT text details

BotKit by Fedify

@botkit@hollo.social

BotKit 0.1.1 is out!

This security update fixes a message visibility bug where direct/followers-only replies to bots were unintentionally forwarded to bot followers. Upgrade recommended. Download at JSR:

deno add jsr:@fedify/botkit@^0.1.1

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're considering adding custom background task support to #Fedify 1.5.0.

Want to use Fedify's worker system for your own background tasks? We're exploring ways to let you register and process custom tasks alongside #ActivityPub jobs.

Check out the proposal: https://github.com/fedify-dev/fedify/issues/206.

Key considerations:

Should this be part of Fedify's scope?
Quick API extension vs complete worker architecture redesign
Integration with existing task queue systems

We'd love to hear your thoughts! Do you need this feature? How would you use it? Share your feedback in the issue thread.

BotKit by Fedify

@botkit@hollo.social

BotKit 0.1.1 is out!

This security update fixes a message visibility bug where direct/followers-only replies to bots were unintentionally forwarded to bot followers. Upgrade recommended. Download at JSR:

deno add jsr:@fedify/botkit@^0.1.1

BotKit by Fedify

@botkit@hollo.social

BotKit 0.1.1 is out!

This security update fixes a message visibility bug where direct/followers-only replies to bots were unintentionally forwarded to bot followers. Upgrade recommended. Download at JSR:

deno add jsr:@fedify/botkit@^0.1.1

Hollo

@hollo@hollo.social

Introducing #Hollo. Hollo is an #ActivityPub-enabled single-user microblogging software. Although it's for a single user, it also supports creating and running multiple accounts for different topics.

Oh, and Hollo is built using #Bun and #Fedify.

wakest ⁂

@liaizon@social.wake.st

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're considering adding custom background task support to #Fedify 1.5.0.

Want to use Fedify's worker system for your own background tasks? We're exploring ways to let you register and process custom tasks alongside #ActivityPub jobs.

Check out the proposal: https://github.com/fedify-dev/fedify/issues/206.

Key considerations:

Should this be part of Fedify's scope?
Quick API extension vs complete worker architecture redesign
Integration with existing task queue systems

We'd love to hear your thoughts! Do you need this feature? How would you use it? Share your feedback in the issue thread.

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're considering adding custom background task support to #Fedify 1.5.0.

Want to use Fedify's worker system for your own background tasks? We're exploring ways to let you register and process custom tasks alongside #ActivityPub jobs.

Check out the proposal: https://github.com/fedify-dev/fedify/issues/206.

Key considerations:

Should this be part of Fedify's scope?
Quick API extension vs complete worker architecture redesign
Integration with existing task queue systems

We'd love to hear your thoughts! Do you need this feature? How would you use it? Share your feedback in the issue thread.

https://github.com/fedify-dev/fedify/blob/main/FEDERATION.md

Jeff Sikes

@box464@mastodon.social

Take a look at the AP Activities that are supported by @fedify

Going far beyond your every day social timeline - woud love to see some AP platforms add support for Listen, Offer, or Travel/Arrive/Leave.

Gorgasbord

@geo@social.collectivemoo.net

This idea is a bit premature but I have decently functioning prototype. What does the #fediverse think of federated gaming? A specific implementation is Club Penguin servers that federate user actions and messages so that separate servers can still have users render on other servers. Allows for full Mastodon integration, i.e. CP conversations show up as threads and a Mas user can respond and appear as a penguin message to CP users. Like CP is the front-end client. #clubpenguin #fedidev #gamedev

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're considering adding custom background task support to #Fedify 1.5.0.

Want to use Fedify's worker system for your own background tasks? We're exploring ways to let you register and process custom tasks alongside #ActivityPub jobs.

Check out the proposal: https://github.com/fedify-dev/fedify/issues/206.

Key considerations:

Should this be part of Fedify's scope?
Quick API extension vs complete worker architecture redesign
Integration with existing task queue systems

We'd love to hear your thoughts! Do you need this feature? How would you use it? Share your feedback in the issue thread.

https://www.w3.org/TR/activitystreams-core/

@reiver ⊼ (Charles)

@reiver@mastodon.social · Reply to @reiver ⊼ (Charles) :batman:'s post

However, "orderedItems" is mentioned in the ActivityStreams Core spec:

Maybe the closest thing to a definition is:

"Collection are represented using the 'items' property while ordered items are represented using the 'orderedItems' property."

So, "orderedItems" is just like "items":

https://www.w3.org/TR/activitystreams-vocabulary/#dfn-items

... except renamed and the interpretation is different

#ActivityPub #ActivityStreams #DeSo #FediDev #FediDevs #Fediverse #OpenSocial #orderedItems #SocialWeb

@reiver ⊼ (Charles)

@reiver@mastodon.social · Reply to @reiver ⊼ (Charles) :batman:'s post

"orderedItems" also isn't in the ActivityPub spec:

https://www.w3.org/TR/activitypub/

#ActivityPub #ActivityStreams #DeSo #FediDev #FediDevs #Fediverse #OpenSocial #orderedItems #SocialWeb

@reiver ⊼ (Charles)

@reiver@mastodon.social

"orderedItems" shows up in the examples in the ActivityStreams Vocabulary spec:

https://www.w3.org/TR/activitystreams-vocabulary

But, I don't see a definition for "orderedItems" in there (in the ActivityStreams Vocabulary spec).

#ActivityPub #ActivityStreams #DeSo #FediDev #FediDevs #Fediverse #OpenSocial #orderedItems #SocialWeb

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're considering adding custom background task support to #Fedify 1.5.0.

Want to use Fedify's worker system for your own background tasks? We're exploring ways to let you register and process custom tasks alongside #ActivityPub jobs.

Check out the proposal: https://github.com/fedify-dev/fedify/issues/206.

Key considerations:

Should this be part of Fedify's scope?
Quick API extension vs complete worker architecture redesign
Integration with existing task queue systems

We'd love to hear your thoughts! Do you need this feature? How would you use it? Share your feedback in the issue thread.

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're considering adding custom background task support to #Fedify 1.5.0.

Want to use Fedify's worker system for your own background tasks? We're exploring ways to let you register and process custom tasks alongside #ActivityPub jobs.

Check out the proposal: https://github.com/fedify-dev/fedify/issues/206.

Key considerations:

Should this be part of Fedify's scope?
Quick API extension vs complete worker architecture redesign
Integration with existing task queue systems

We'd love to hear your thoughts! Do you need this feature? How would you use it? Share your feedback in the issue thread.

BotKit by Fedify

@botkit@hollo.social

🎉 Announcing BotKit 0.1.0: A new framework for creating ActivityPub bots!

We're thrilled to announce the initial release of #BotKit, a #TypeScript framework that makes creating standalone #ActivityPub bots simpler than ever before. With BotKit, you can create a complete fediverse bot in just a single TypeScript file!

Key features:

🔋 Standalone bot creation—no need for a Mastodon/Misskey account
🧩 Simple, developer-friendly API
🚀 Easy deployment on Deno Deploy, Fly.io, Railway, or your own server
Powered by @fedify for robust ActivityPub protocol handling

Getting started is as simple as:

deno add jsr:@fedify/botkit@^0.1.0

Here's a quick example of a weather bot:

const kv = await Deno.openKv();

const bot = createBot<void>({
  username: "weatherbot",
  name: "Seoul Weather Bot",
  summary: text`I post daily weather updates for Seoul!`,
  kv: new DenoKvStore(kv),
  queue: new DenoKvMessageQueue(kv),
});

// Reply to mentions
bot.onMention = async (session, message) => {
  await message.reply(text`Current temperature in Seoul is 18°C!`);
};

// Post scheduled updates
const session = bot.getSession("https://weather.example.com");
setInterval(async () => {
  await session.publish(
    text`Seoul Weather Update 🌡️
    Current: 18°C
    Humidity: 65%
    Forecast: Clear skies ☀️`
  );
}, 1000 * 60 * 60); // Hourly updates

While BotKit currently supports #Deno, we're working on bringing Node.js and Bun support in future releases.

Ready to create your first fediverse bot? Check out our docs at https://botkit.fedify.dev/ to get started! 🚀

BotKit by Fedify

@botkit@hollo.social

🎉 Announcing BotKit 0.1.0: A new framework for creating ActivityPub bots!

Key features:

🔋 Standalone bot creation—no need for a Mastodon/Misskey account
🧩 Simple, developer-friendly API
🚀 Easy deployment on Deno Deploy, Fly.io, Railway, or your own server
Powered by @fedify for robust ActivityPub protocol handling

Getting started is as simple as:

deno add jsr:@fedify/botkit@^0.1.0

Here's a quick example of a weather bot:

const kv = await Deno.openKv();

const bot = createBot<void>({
  username: "weatherbot",
  name: "Seoul Weather Bot",
  summary: text`I post daily weather updates for Seoul!`,
  kv: new DenoKvStore(kv),
  queue: new DenoKvMessageQueue(kv),
});

// Reply to mentions
bot.onMention = async (session, message) => {
  await message.reply(text`Current temperature in Seoul is 18°C!`);
};

// Post scheduled updates
const session = bot.getSession("https://weather.example.com");
setInterval(async () => {
  await session.publish(
    text`Seoul Weather Update 🌡️
    Current: 18°C
    Humidity: 65%
    Forecast: Clear skies ☀️`
  );
}, 1000 * 60 * 60); // Hourly updates

While BotKit currently supports #Deno, we're working on bringing Node.js and Bun support in future releases.

Ready to create your first fediverse bot? Check out our docs at https://botkit.fedify.dev/ to get started! 🚀

BotKit by Fedify

@botkit@hollo.social

🎉 Announcing BotKit 0.1.0: A new framework for creating ActivityPub bots!

Key features:

🔋 Standalone bot creation—no need for a Mastodon/Misskey account
🧩 Simple, developer-friendly API
🚀 Easy deployment on Deno Deploy, Fly.io, Railway, or your own server
Powered by @fedify for robust ActivityPub protocol handling

Getting started is as simple as:

deno add jsr:@fedify/botkit@^0.1.0

Here's a quick example of a weather bot:

const kv = await Deno.openKv();

const bot = createBot<void>({
  username: "weatherbot",
  name: "Seoul Weather Bot",
  summary: text`I post daily weather updates for Seoul!`,
  kv: new DenoKvStore(kv),
  queue: new DenoKvMessageQueue(kv),
});

// Reply to mentions
bot.onMention = async (session, message) => {
  await message.reply(text`Current temperature in Seoul is 18°C!`);
};

// Post scheduled updates
const session = bot.getSession("https://weather.example.com");
setInterval(async () => {
  await session.publish(
    text`Seoul Weather Update 🌡️
    Current: 18°C
    Humidity: 65%
    Forecast: Clear skies ☀️`
  );
}, 1000 * 60 * 60); // Hourly updates

While BotKit currently supports #Deno, we're working on bringing Node.js and Bun support in future releases.

Ready to create your first fediverse bot? Check out our docs at https://botkit.fedify.dev/ to get started! 🚀

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're excited to announce the release of Fedify 1.4.0! This release brings significant improvements to enhance compatibility and flexibility in #ActivityPub federation.

Key Highlights

Activity transformers

Introduced a new system to adjust outgoing activities for better compatibility with various ActivityPub implementations. This includes automatic ID assignment for activities and actor dehydration to satisfy implementation quirks (looking at you, Threads!).

WebFinger customization

Added the ability to customize WebFinger responses through the new mapAlias() API, giving you more control over how your actors are discovered.

New interaction collections

Added support for shares, likes, and emojiReactions properties to the Object class, making it easier to access and traverse these interaction collections.

CLI improvements

The fedify lookup command now supports two new options:

-t/--traverse: Traverse through collection objects
-S/--suppress-errors: Continue operation even when encountering errors during traversal

Other enhancements

Added Context.getNodeInfo() method for easier NodeInfo access
Improved error handling in collection traversal and JSON-LD processing
Added support for private network access control in WebFinger lookups
User-Agent headers now automatically include your instance URL, making it easier for other servers to identify your instance

For the complete list of changes and bugfixes, please visit our changelog.

Whether you're building a new federated application or maintaining an existing one, #Fedify 1.4.0 provides the tools you need for robust ActivityPub federation.

Supporting us

We're grateful to all our sponsors who make this project possible. Check out our new sponsors showcase page to see the amazing individuals and organizations supporting Fedify's development. If you'd like to support Fedify's development, please consider becoming a sponsor!

Upgrade now

You can install Fedify 1.4.0 from JSR or npm. Upgrade today and let us know what you think!

BotKit by Fedify

@botkit@hollo.social

🎉 Announcing BotKit 0.1.0: A new framework for creating ActivityPub bots!

Key features:

🔋 Standalone bot creation—no need for a Mastodon/Misskey account
🧩 Simple, developer-friendly API
🚀 Easy deployment on Deno Deploy, Fly.io, Railway, or your own server
Powered by @fedify for robust ActivityPub protocol handling

Getting started is as simple as:

deno add jsr:@fedify/botkit@^0.1.0

Here's a quick example of a weather bot:

const kv = await Deno.openKv();

const bot = createBot<void>({
  username: "weatherbot",
  name: "Seoul Weather Bot",
  summary: text`I post daily weather updates for Seoul!`,
  kv: new DenoKvStore(kv),
  queue: new DenoKvMessageQueue(kv),
});

// Reply to mentions
bot.onMention = async (session, message) => {
  await message.reply(text`Current temperature in Seoul is 18°C!`);
};

// Post scheduled updates
const session = bot.getSession("https://weather.example.com");
setInterval(async () => {
  await session.publish(
    text`Seoul Weather Update 🌡️
    Current: 18°C
    Humidity: 65%
    Forecast: Clear skies ☀️`
  );
}, 1000 * 60 * 60); // Hourly updates

While BotKit currently supports #Deno, we're working on bringing Node.js and Bun support in future releases.

Ready to create your first fediverse bot? Check out our docs at https://botkit.fedify.dev/ to get started! 🚀

Gorgasbord

@geo@social.collectivemoo.net

Gorgasbord

@geo@social.collectivemoo.net

BotKit by Fedify

@botkit@hollo.social

🎉 Announcing BotKit 0.1.0: A new framework for creating ActivityPub bots!

Key features:

🔋 Standalone bot creation—no need for a Mastodon/Misskey account
🧩 Simple, developer-friendly API
🚀 Easy deployment on Deno Deploy, Fly.io, Railway, or your own server
Powered by @fedify for robust ActivityPub protocol handling

Getting started is as simple as:

deno add jsr:@fedify/botkit@^0.1.0

Here's a quick example of a weather bot:

const kv = await Deno.openKv();

const bot = createBot<void>({
  username: "weatherbot",
  name: "Seoul Weather Bot",
  summary: text`I post daily weather updates for Seoul!`,
  kv: new DenoKvStore(kv),
  queue: new DenoKvMessageQueue(kv),
});

// Reply to mentions
bot.onMention = async (session, message) => {
  await message.reply(text`Current temperature in Seoul is 18°C!`);
};

// Post scheduled updates
const session = bot.getSession("https://weather.example.com");
setInterval(async () => {
  await session.publish(
    text`Seoul Weather Update 🌡️
    Current: 18°C
    Humidity: 65%
    Forecast: Clear skies ☀️`
  );
}, 1000 * 60 * 60); // Hourly updates

While BotKit currently supports #Deno, we're working on bringing Node.js and Bun support in future releases.

Ready to create your first fediverse bot? Check out our docs at https://botkit.fedify.dev/ to get started! 🚀

Gorgasbord

@geo@social.collectivemoo.net

BotKit by Fedify

@botkit@hollo.social

🎉 Announcing BotKit 0.1.0: A new framework for creating ActivityPub bots!

Key features:

🔋 Standalone bot creation—no need for a Mastodon/Misskey account
🧩 Simple, developer-friendly API
🚀 Easy deployment on Deno Deploy, Fly.io, Railway, or your own server
Powered by @fedify for robust ActivityPub protocol handling

Getting started is as simple as:

deno add jsr:@fedify/botkit@^0.1.0

Here's a quick example of a weather bot:

const kv = await Deno.openKv();

const bot = createBot<void>({
  username: "weatherbot",
  name: "Seoul Weather Bot",
  summary: text`I post daily weather updates for Seoul!`,
  kv: new DenoKvStore(kv),
  queue: new DenoKvMessageQueue(kv),
});

// Reply to mentions
bot.onMention = async (session, message) => {
  await message.reply(text`Current temperature in Seoul is 18°C!`);
};

// Post scheduled updates
const session = bot.getSession("https://weather.example.com");
setInterval(async () => {
  await session.publish(
    text`Seoul Weather Update 🌡️
    Current: 18°C
    Humidity: 65%
    Forecast: Clear skies ☀️`
  );
}, 1000 * 60 * 60); // Hourly updates

While BotKit currently supports #Deno, we're working on bringing Node.js and Bun support in future releases.

Ready to create your first fediverse bot? Check out our docs at https://botkit.fedify.dev/ to get started! 🚀

BotKit by Fedify

@botkit@hollo.social

🎉 Announcing BotKit 0.1.0: A new framework for creating ActivityPub bots!

Key features:

🔋 Standalone bot creation—no need for a Mastodon/Misskey account
🧩 Simple, developer-friendly API
🚀 Easy deployment on Deno Deploy, Fly.io, Railway, or your own server
Powered by @fedify for robust ActivityPub protocol handling

Getting started is as simple as:

deno add jsr:@fedify/botkit@^0.1.0

Here's a quick example of a weather bot:

const kv = await Deno.openKv();

const bot = createBot<void>({
  username: "weatherbot",
  name: "Seoul Weather Bot",
  summary: text`I post daily weather updates for Seoul!`,
  kv: new DenoKvStore(kv),
  queue: new DenoKvMessageQueue(kv),
});

// Reply to mentions
bot.onMention = async (session, message) => {
  await message.reply(text`Current temperature in Seoul is 18°C!`);
};

// Post scheduled updates
const session = bot.getSession("https://weather.example.com");
setInterval(async () => {
  await session.publish(
    text`Seoul Weather Update 🌡️
    Current: 18°C
    Humidity: 65%
    Forecast: Clear skies ☀️`
  );
}, 1000 * 60 * 60); // Hourly updates

While BotKit currently supports #Deno, we're working on bringing Node.js and Bun support in future releases.

Ready to create your first fediverse bot? Check out our docs at https://botkit.fedify.dev/ to get started! 🚀

BotKit by Fedify

@botkit@hollo.social

🎉 Announcing BotKit 0.1.0: A new framework for creating ActivityPub bots!

Key features:

🔋 Standalone bot creation—no need for a Mastodon/Misskey account
🧩 Simple, developer-friendly API
🚀 Easy deployment on Deno Deploy, Fly.io, Railway, or your own server
Powered by @fedify for robust ActivityPub protocol handling

Getting started is as simple as:

deno add jsr:@fedify/botkit@^0.1.0

Here's a quick example of a weather bot:

const kv = await Deno.openKv();

const bot = createBot<void>({
  username: "weatherbot",
  name: "Seoul Weather Bot",
  summary: text`I post daily weather updates for Seoul!`,
  kv: new DenoKvStore(kv),
  queue: new DenoKvMessageQueue(kv),
});

// Reply to mentions
bot.onMention = async (session, message) => {
  await message.reply(text`Current temperature in Seoul is 18°C!`);
};

// Post scheduled updates
const session = bot.getSession("https://weather.example.com");
setInterval(async () => {
  await session.publish(
    text`Seoul Weather Update 🌡️
    Current: 18°C
    Humidity: 65%
    Forecast: Clear skies ☀️`
  );
}, 1000 * 60 * 60); // Hourly updates

While BotKit currently supports #Deno, we're working on bringing Node.js and Bun support in future releases.

Ready to create your first fediverse bot? Check out our docs at https://botkit.fedify.dev/ to get started! 🚀

BotKit by Fedify

@botkit@hollo.social

🎉 Announcing BotKit 0.1.0: A new framework for creating ActivityPub bots!

Key features:

🔋 Standalone bot creation—no need for a Mastodon/Misskey account
🧩 Simple, developer-friendly API
🚀 Easy deployment on Deno Deploy, Fly.io, Railway, or your own server
Powered by @fedify for robust ActivityPub protocol handling

Getting started is as simple as:

deno add jsr:@fedify/botkit@^0.1.0

Here's a quick example of a weather bot:

const kv = await Deno.openKv();

const bot = createBot<void>({
  username: "weatherbot",
  name: "Seoul Weather Bot",
  summary: text`I post daily weather updates for Seoul!`,
  kv: new DenoKvStore(kv),
  queue: new DenoKvMessageQueue(kv),
});

// Reply to mentions
bot.onMention = async (session, message) => {
  await message.reply(text`Current temperature in Seoul is 18°C!`);
};

// Post scheduled updates
const session = bot.getSession("https://weather.example.com");
setInterval(async () => {
  await session.publish(
    text`Seoul Weather Update 🌡️
    Current: 18°C
    Humidity: 65%
    Forecast: Clear skies ☀️`
  );
}, 1000 * 60 * 60); // Hourly updates

While BotKit currently supports #Deno, we're working on bringing Node.js and Bun support in future releases.

Ready to create your first fediverse bot? Check out our docs at https://botkit.fedify.dev/ to get started! 🚀

BotKit by Fedify

@botkit@hollo.social

🎉 Announcing BotKit 0.1.0: A new framework for creating ActivityPub bots!

Key features:

🔋 Standalone bot creation—no need for a Mastodon/Misskey account
🧩 Simple, developer-friendly API
🚀 Easy deployment on Deno Deploy, Fly.io, Railway, or your own server
Powered by @fedify for robust ActivityPub protocol handling

Getting started is as simple as:

deno add jsr:@fedify/botkit@^0.1.0

Here's a quick example of a weather bot:

const kv = await Deno.openKv();

const bot = createBot<void>({
  username: "weatherbot",
  name: "Seoul Weather Bot",
  summary: text`I post daily weather updates for Seoul!`,
  kv: new DenoKvStore(kv),
  queue: new DenoKvMessageQueue(kv),
});

// Reply to mentions
bot.onMention = async (session, message) => {
  await message.reply(text`Current temperature in Seoul is 18°C!`);
};

// Post scheduled updates
const session = bot.getSession("https://weather.example.com");
setInterval(async () => {
  await session.publish(
    text`Seoul Weather Update 🌡️
    Current: 18°C
    Humidity: 65%
    Forecast: Clear skies ☀️`
  );
}, 1000 * 60 * 60); // Hourly updates

While BotKit currently supports #Deno, we're working on bringing Node.js and Bun support in future releases.

Ready to create your first fediverse bot? Check out our docs at https://botkit.fedify.dev/ to get started! 🚀

BotKit by Fedify

@botkit@hollo.social

🎉 Announcing BotKit 0.1.0: A new framework for creating ActivityPub bots!

Key features:

🔋 Standalone bot creation—no need for a Mastodon/Misskey account
🧩 Simple, developer-friendly API
🚀 Easy deployment on Deno Deploy, Fly.io, Railway, or your own server
Powered by @fedify for robust ActivityPub protocol handling

Getting started is as simple as:

deno add jsr:@fedify/botkit@^0.1.0

Here's a quick example of a weather bot:

const kv = await Deno.openKv();

const bot = createBot<void>({
  username: "weatherbot",
  name: "Seoul Weather Bot",
  summary: text`I post daily weather updates for Seoul!`,
  kv: new DenoKvStore(kv),
  queue: new DenoKvMessageQueue(kv),
});

// Reply to mentions
bot.onMention = async (session, message) => {
  await message.reply(text`Current temperature in Seoul is 18°C!`);
};

// Post scheduled updates
const session = bot.getSession("https://weather.example.com");
setInterval(async () => {
  await session.publish(
    text`Seoul Weather Update 🌡️
    Current: 18°C
    Humidity: 65%
    Forecast: Clear skies ☀️`
  );
}, 1000 * 60 * 60); // Hourly updates

While BotKit currently supports #Deno, we're working on bringing Node.js and Bun support in future releases.

Ready to create your first fediverse bot? Check out our docs at https://botkit.fedify.dev/ to get started! 🚀

BotKit by Fedify

@botkit@hollo.social

🎉 Announcing BotKit 0.1.0: A new framework for creating ActivityPub bots!

Key features:

🔋 Standalone bot creation—no need for a Mastodon/Misskey account
🧩 Simple, developer-friendly API
🚀 Easy deployment on Deno Deploy, Fly.io, Railway, or your own server
Powered by @fedify for robust ActivityPub protocol handling

Getting started is as simple as:

deno add jsr:@fedify/botkit@^0.1.0

Here's a quick example of a weather bot:

const kv = await Deno.openKv();

const bot = createBot<void>({
  username: "weatherbot",
  name: "Seoul Weather Bot",
  summary: text`I post daily weather updates for Seoul!`,
  kv: new DenoKvStore(kv),
  queue: new DenoKvMessageQueue(kv),
});

// Reply to mentions
bot.onMention = async (session, message) => {
  await message.reply(text`Current temperature in Seoul is 18°C!`);
};

// Post scheduled updates
const session = bot.getSession("https://weather.example.com");
setInterval(async () => {
  await session.publish(
    text`Seoul Weather Update 🌡️
    Current: 18°C
    Humidity: 65%
    Forecast: Clear skies ☀️`
  );
}, 1000 * 60 * 60); // Hourly updates

While BotKit currently supports #Deno, we're working on bringing Node.js and Bun support in future releases.

Ready to create your first fediverse bot? Check out our docs at https://botkit.fedify.dev/ to get started! 🚀

BotKit by Fedify

@botkit@hollo.social

🎉 Announcing BotKit 0.1.0: A new framework for creating ActivityPub bots!

Key features:

🔋 Standalone bot creation—no need for a Mastodon/Misskey account
🧩 Simple, developer-friendly API
🚀 Easy deployment on Deno Deploy, Fly.io, Railway, or your own server
Powered by @fedify for robust ActivityPub protocol handling

Getting started is as simple as:

deno add jsr:@fedify/botkit@^0.1.0

Here's a quick example of a weather bot:

const kv = await Deno.openKv();

const bot = createBot<void>({
  username: "weatherbot",
  name: "Seoul Weather Bot",
  summary: text`I post daily weather updates for Seoul!`,
  kv: new DenoKvStore(kv),
  queue: new DenoKvMessageQueue(kv),
});

// Reply to mentions
bot.onMention = async (session, message) => {
  await message.reply(text`Current temperature in Seoul is 18°C!`);
};

// Post scheduled updates
const session = bot.getSession("https://weather.example.com");
setInterval(async () => {
  await session.publish(
    text`Seoul Weather Update 🌡️
    Current: 18°C
    Humidity: 65%
    Forecast: Clear skies ☀️`
  );
}, 1000 * 60 * 60); // Hourly updates

While BotKit currently supports #Deno, we're working on bringing Node.js and Bun support in future releases.

Ready to create your first fediverse bot? Check out our docs at https://botkit.fedify.dev/ to get started! 🚀

BotKit by Fedify

@botkit@hollo.social

🎉 Announcing BotKit 0.1.0: A new framework for creating ActivityPub bots!

Key features:

🔋 Standalone bot creation—no need for a Mastodon/Misskey account
🧩 Simple, developer-friendly API
🚀 Easy deployment on Deno Deploy, Fly.io, Railway, or your own server
Powered by @fedify for robust ActivityPub protocol handling

Getting started is as simple as:

deno add jsr:@fedify/botkit@^0.1.0

Here's a quick example of a weather bot:

const kv = await Deno.openKv();

const bot = createBot<void>({
  username: "weatherbot",
  name: "Seoul Weather Bot",
  summary: text`I post daily weather updates for Seoul!`,
  kv: new DenoKvStore(kv),
  queue: new DenoKvMessageQueue(kv),
});

// Reply to mentions
bot.onMention = async (session, message) => {
  await message.reply(text`Current temperature in Seoul is 18°C!`);
};

// Post scheduled updates
const session = bot.getSession("https://weather.example.com");
setInterval(async () => {
  await session.publish(
    text`Seoul Weather Update 🌡️
    Current: 18°C
    Humidity: 65%
    Forecast: Clear skies ☀️`
  );
}, 1000 * 60 * 60); // Hourly updates

While BotKit currently supports #Deno, we're working on bringing Node.js and Bun support in future releases.

Ready to create your first fediverse bot? Check out our docs at https://botkit.fedify.dev/ to get started! 🚀

BotKit by Fedify

@botkit@hollo.social

🎉 Announcing BotKit 0.1.0: A new framework for creating ActivityPub bots!

Key features:

🔋 Standalone bot creation—no need for a Mastodon/Misskey account
🧩 Simple, developer-friendly API
🚀 Easy deployment on Deno Deploy, Fly.io, Railway, or your own server
Powered by @fedify for robust ActivityPub protocol handling

Getting started is as simple as:

deno add jsr:@fedify/botkit@^0.1.0

Here's a quick example of a weather bot:

const kv = await Deno.openKv();

const bot = createBot<void>({
  username: "weatherbot",
  name: "Seoul Weather Bot",
  summary: text`I post daily weather updates for Seoul!`,
  kv: new DenoKvStore(kv),
  queue: new DenoKvMessageQueue(kv),
});

// Reply to mentions
bot.onMention = async (session, message) => {
  await message.reply(text`Current temperature in Seoul is 18°C!`);
};

// Post scheduled updates
const session = bot.getSession("https://weather.example.com");
setInterval(async () => {
  await session.publish(
    text`Seoul Weather Update 🌡️
    Current: 18°C
    Humidity: 65%
    Forecast: Clear skies ☀️`
  );
}, 1000 * 60 * 60); // Hourly updates

While BotKit currently supports #Deno, we're working on bringing Node.js and Bun support in future releases.

Ready to create your first fediverse bot? Check out our docs at https://botkit.fedify.dev/ to get started! 🚀

BotKit by Fedify

@botkit@hollo.social

🎉 Announcing BotKit 0.1.0: A new framework for creating ActivityPub bots!

Key features:

🔋 Standalone bot creation—no need for a Mastodon/Misskey account
🧩 Simple, developer-friendly API
🚀 Easy deployment on Deno Deploy, Fly.io, Railway, or your own server
Powered by @fedify for robust ActivityPub protocol handling

Getting started is as simple as:

deno add jsr:@fedify/botkit@^0.1.0

Here's a quick example of a weather bot:

const kv = await Deno.openKv();

const bot = createBot<void>({
  username: "weatherbot",
  name: "Seoul Weather Bot",
  summary: text`I post daily weather updates for Seoul!`,
  kv: new DenoKvStore(kv),
  queue: new DenoKvMessageQueue(kv),
});

// Reply to mentions
bot.onMention = async (session, message) => {
  await message.reply(text`Current temperature in Seoul is 18°C!`);
};

// Post scheduled updates
const session = bot.getSession("https://weather.example.com");
setInterval(async () => {
  await session.publish(
    text`Seoul Weather Update 🌡️
    Current: 18°C
    Humidity: 65%
    Forecast: Clear skies ☀️`
  );
}, 1000 * 60 * 60); // Hourly updates

While BotKit currently supports #Deno, we're working on bringing Node.js and Bun support in future releases.

Ready to create your first fediverse bot? Check out our docs at https://botkit.fedify.dev/ to get started! 🚀

#Fediverse #SocialMedia #Mastodon #NewSocial #FediDev

Newsmast

@newsmast@newsmast.social

Growing better social media can be hard.

Many of the developers, moderators, and teams behind the projects that make up decentralised social media do it because they believe in what they're building. Projects which are self-funded, both in time and money then shared with you for little to no cost.

So, take some time today to say thank you to the people behind your favourite Fediverse tools and platforms. We're sure they'd appreciate it.

BotKit by Fedify

@botkit@hollo.social

🎉 Announcing BotKit 0.1.0: A new framework for creating ActivityPub bots!

Key features:

🔋 Standalone bot creation—no need for a Mastodon/Misskey account
🧩 Simple, developer-friendly API
🚀 Easy deployment on Deno Deploy, Fly.io, Railway, or your own server
Powered by @fedify for robust ActivityPub protocol handling

Getting started is as simple as:

deno add jsr:@fedify/botkit@^0.1.0

Here's a quick example of a weather bot:

const kv = await Deno.openKv();

const bot = createBot<void>({
  username: "weatherbot",
  name: "Seoul Weather Bot",
  summary: text`I post daily weather updates for Seoul!`,
  kv: new DenoKvStore(kv),
  queue: new DenoKvMessageQueue(kv),
});

// Reply to mentions
bot.onMention = async (session, message) => {
  await message.reply(text`Current temperature in Seoul is 18°C!`);
};

// Post scheduled updates
const session = bot.getSession("https://weather.example.com");
setInterval(async () => {
  await session.publish(
    text`Seoul Weather Update 🌡️
    Current: 18°C
    Humidity: 65%
    Forecast: Clear skies ☀️`
  );
}, 1000 * 60 * 60); // Hourly updates

While BotKit currently supports #Deno, we're working on bringing Node.js and Bun support in future releases.

Ready to create your first fediverse bot? Check out our docs at https://botkit.fedify.dev/ to get started! 🚀

BotKit by Fedify

@botkit@hollo.social

🎉 Announcing BotKit 0.1.0: A new framework for creating ActivityPub bots!

Key features:

🔋 Standalone bot creation—no need for a Mastodon/Misskey account
🧩 Simple, developer-friendly API
🚀 Easy deployment on Deno Deploy, Fly.io, Railway, or your own server
Powered by @fedify for robust ActivityPub protocol handling

Getting started is as simple as:

deno add jsr:@fedify/botkit@^0.1.0

Here's a quick example of a weather bot:

const kv = await Deno.openKv();

const bot = createBot<void>({
  username: "weatherbot",
  name: "Seoul Weather Bot",
  summary: text`I post daily weather updates for Seoul!`,
  kv: new DenoKvStore(kv),
  queue: new DenoKvMessageQueue(kv),
});

// Reply to mentions
bot.onMention = async (session, message) => {
  await message.reply(text`Current temperature in Seoul is 18°C!`);
};

// Post scheduled updates
const session = bot.getSession("https://weather.example.com");
setInterval(async () => {
  await session.publish(
    text`Seoul Weather Update 🌡️
    Current: 18°C
    Humidity: 65%
    Forecast: Clear skies ☀️`
  );
}, 1000 * 60 * 60); // Hourly updates

While BotKit currently supports #Deno, we're working on bringing Node.js and Bun support in future releases.

Ready to create your first fediverse bot? Check out our docs at https://botkit.fedify.dev/ to get started! 🚀

BotKit by Fedify

@botkit@hollo.social

🎉 Announcing BotKit 0.1.0: A new framework for creating ActivityPub bots!

Key features:

🔋 Standalone bot creation—no need for a Mastodon/Misskey account
🧩 Simple, developer-friendly API
🚀 Easy deployment on Deno Deploy, Fly.io, Railway, or your own server
Powered by @fedify for robust ActivityPub protocol handling

Getting started is as simple as:

deno add jsr:@fedify/botkit@^0.1.0

Here's a quick example of a weather bot:

const kv = await Deno.openKv();

const bot = createBot<void>({
  username: "weatherbot",
  name: "Seoul Weather Bot",
  summary: text`I post daily weather updates for Seoul!`,
  kv: new DenoKvStore(kv),
  queue: new DenoKvMessageQueue(kv),
});

// Reply to mentions
bot.onMention = async (session, message) => {
  await message.reply(text`Current temperature in Seoul is 18°C!`);
};

// Post scheduled updates
const session = bot.getSession("https://weather.example.com");
setInterval(async () => {
  await session.publish(
    text`Seoul Weather Update 🌡️
    Current: 18°C
    Humidity: 65%
    Forecast: Clear skies ☀️`
  );
}, 1000 * 60 * 60); // Hourly updates

While BotKit currently supports #Deno, we're working on bringing Node.js and Bun support in future releases.

Ready to create your first fediverse bot? Check out our docs at https://botkit.fedify.dev/ to get started! 🚀

BotKit by Fedify

@botkit@hollo.social

🎉 Announcing BotKit 0.1.0: A new framework for creating ActivityPub bots!

Key features:

🔋 Standalone bot creation—no need for a Mastodon/Misskey account
🧩 Simple, developer-friendly API
🚀 Easy deployment on Deno Deploy, Fly.io, Railway, or your own server
Powered by @fedify for robust ActivityPub protocol handling

Getting started is as simple as:

deno add jsr:@fedify/botkit@^0.1.0

Here's a quick example of a weather bot:

const kv = await Deno.openKv();

const bot = createBot<void>({
  username: "weatherbot",
  name: "Seoul Weather Bot",
  summary: text`I post daily weather updates for Seoul!`,
  kv: new DenoKvStore(kv),
  queue: new DenoKvMessageQueue(kv),
});

// Reply to mentions
bot.onMention = async (session, message) => {
  await message.reply(text`Current temperature in Seoul is 18°C!`);
};

// Post scheduled updates
const session = bot.getSession("https://weather.example.com");
setInterval(async () => {
  await session.publish(
    text`Seoul Weather Update 🌡️
    Current: 18°C
    Humidity: 65%
    Forecast: Clear skies ☀️`
  );
}, 1000 * 60 * 60); // Hourly updates

While BotKit currently supports #Deno, we're working on bringing Node.js and Bun support in future releases.

Ready to create your first fediverse bot? Check out our docs at https://botkit.fedify.dev/ to get started! 🚀

BotKit by Fedify

@botkit@hollo.social

🎉 Announcing BotKit 0.1.0: A new framework for creating ActivityPub bots!

Key features:

🔋 Standalone bot creation—no need for a Mastodon/Misskey account
🧩 Simple, developer-friendly API
🚀 Easy deployment on Deno Deploy, Fly.io, Railway, or your own server
Powered by @fedify for robust ActivityPub protocol handling

Getting started is as simple as:

deno add jsr:@fedify/botkit@^0.1.0

Here's a quick example of a weather bot:

const kv = await Deno.openKv();

const bot = createBot<void>({
  username: "weatherbot",
  name: "Seoul Weather Bot",
  summary: text`I post daily weather updates for Seoul!`,
  kv: new DenoKvStore(kv),
  queue: new DenoKvMessageQueue(kv),
});

// Reply to mentions
bot.onMention = async (session, message) => {
  await message.reply(text`Current temperature in Seoul is 18°C!`);
};

// Post scheduled updates
const session = bot.getSession("https://weather.example.com");
setInterval(async () => {
  await session.publish(
    text`Seoul Weather Update 🌡️
    Current: 18°C
    Humidity: 65%
    Forecast: Clear skies ☀️`
  );
}, 1000 * 60 * 60); // Hourly updates

While BotKit currently supports #Deno, we're working on bringing Node.js and Bun support in future releases.

Ready to create your first fediverse bot? Check out our docs at https://botkit.fedify.dev/ to get started! 🚀

#Fedi #Fediverse #FediMafia #ActivityPub #Mastodon #FediDev #Developer

BeAware

@BeAware@social.beaware.live

Just a warning for Fedi devs:

If you plan on building discovery features for Fedi, BeAware of the "Fedi Mafia" that harasses, threatens, and abuses any dev on Fedi that DARES to make an open platform a little bit more usable.🤦‍♂️

Over the past 2 months, I've seen 4 Fedi projects that were building tools to help people find accounts and servers to make it easier to find content on Fedi, get shut down because people who don't understand that Fedi is OPEN, harassed and threatened the devs until they shut their projects down.🤬

So, if you plan on building these tools, PLEASE just be prepared to block and continue building your tools.

Ignorant people should not dictate how this protocol is built. Don't let the abusers win.

@fedify@hollo.social

We're excited to announce the release of Fedify 1.4.0! This release brings significant improvements to enhance compatibility and flexibility in #ActivityPub federation.

Key Highlights

Activity transformers

WebFinger customization

Added the ability to customize WebFinger responses through the new mapAlias() API, giving you more control over how your actors are discovered.

New interaction collections

Added support for shares, likes, and emojiReactions properties to the Object class, making it easier to access and traverse these interaction collections.

CLI improvements

The fedify lookup command now supports two new options:

-t/--traverse: Traverse through collection objects
-S/--suppress-errors: Continue operation even when encountering errors during traversal

Other enhancements

Added Context.getNodeInfo() method for easier NodeInfo access
Improved error handling in collection traversal and JSON-LD processing
Added support for private network access control in WebFinger lookups
User-Agent headers now automatically include your instance URL, making it easier for other servers to identify your instance

For the complete list of changes and bugfixes, please visit our changelog.

Whether you're building a new federated application or maintaining an existing one, #Fedify 1.4.0 provides the tools you need for robust ActivityPub federation.

Supporting us

Upgrade now

You can install Fedify 1.4.0 from JSR or npm. Upgrade today and let us know what you think!

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're excited to announce the release of Fedify 1.4.0! This release brings significant improvements to enhance compatibility and flexibility in #ActivityPub federation.

Key Highlights

Activity transformers

WebFinger customization

Added the ability to customize WebFinger responses through the new mapAlias() API, giving you more control over how your actors are discovered.

New interaction collections

Added support for shares, likes, and emojiReactions properties to the Object class, making it easier to access and traverse these interaction collections.

CLI improvements

The fedify lookup command now supports two new options:

-t/--traverse: Traverse through collection objects
-S/--suppress-errors: Continue operation even when encountering errors during traversal

Other enhancements

Added Context.getNodeInfo() method for easier NodeInfo access
Improved error handling in collection traversal and JSON-LD processing
Added support for private network access control in WebFinger lookups
User-Agent headers now automatically include your instance URL, making it easier for other servers to identify your instance

For the complete list of changes and bugfixes, please visit our changelog.

Whether you're building a new federated application or maintaining an existing one, #Fedify 1.4.0 provides the tools you need for robust ActivityPub federation.

Supporting us

Upgrade now

You can install Fedify 1.4.0 from JSR or npm. Upgrade today and let us know what you think!

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're excited to announce the release of Fedify 1.4.0! This release brings significant improvements to enhance compatibility and flexibility in #ActivityPub federation.

Key Highlights

Activity transformers

WebFinger customization

Added the ability to customize WebFinger responses through the new mapAlias() API, giving you more control over how your actors are discovered.

New interaction collections

Added support for shares, likes, and emojiReactions properties to the Object class, making it easier to access and traverse these interaction collections.

CLI improvements

The fedify lookup command now supports two new options:

-t/--traverse: Traverse through collection objects
-S/--suppress-errors: Continue operation even when encountering errors during traversal

Other enhancements

Added Context.getNodeInfo() method for easier NodeInfo access
Improved error handling in collection traversal and JSON-LD processing
Added support for private network access control in WebFinger lookups
User-Agent headers now automatically include your instance URL, making it easier for other servers to identify your instance

For the complete list of changes and bugfixes, please visit our changelog.

Whether you're building a new federated application or maintaining an existing one, #Fedify 1.4.0 provides the tools you need for robust ActivityPub federation.

Supporting us

Upgrade now

You can install Fedify 1.4.0 from JSR or npm. Upgrade today and let us know what you think!

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're excited to announce the release of Fedify 1.4.0! This release brings significant improvements to enhance compatibility and flexibility in #ActivityPub federation.

Key Highlights

Activity transformers

WebFinger customization

Added the ability to customize WebFinger responses through the new mapAlias() API, giving you more control over how your actors are discovered.

New interaction collections

Added support for shares, likes, and emojiReactions properties to the Object class, making it easier to access and traverse these interaction collections.

CLI improvements

The fedify lookup command now supports two new options:

-t/--traverse: Traverse through collection objects
-S/--suppress-errors: Continue operation even when encountering errors during traversal

Other enhancements

Added Context.getNodeInfo() method for easier NodeInfo access
Improved error handling in collection traversal and JSON-LD processing
Added support for private network access control in WebFinger lookups
User-Agent headers now automatically include your instance URL, making it easier for other servers to identify your instance

For the complete list of changes and bugfixes, please visit our changelog.

Whether you're building a new federated application or maintaining an existing one, #Fedify 1.4.0 provides the tools you need for robust ActivityPub federation.

Supporting us

Upgrade now

You can install Fedify 1.4.0 from JSR or npm. Upgrade today and let us know what you think!

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're excited to announce the release of Fedify 1.4.0! This release brings significant improvements to enhance compatibility and flexibility in #ActivityPub federation.

Key Highlights

Activity transformers

WebFinger customization

Added the ability to customize WebFinger responses through the new mapAlias() API, giving you more control over how your actors are discovered.

New interaction collections

Added support for shares, likes, and emojiReactions properties to the Object class, making it easier to access and traverse these interaction collections.

CLI improvements

The fedify lookup command now supports two new options:

-t/--traverse: Traverse through collection objects
-S/--suppress-errors: Continue operation even when encountering errors during traversal

Other enhancements

Added Context.getNodeInfo() method for easier NodeInfo access
Improved error handling in collection traversal and JSON-LD processing
Added support for private network access control in WebFinger lookups
User-Agent headers now automatically include your instance URL, making it easier for other servers to identify your instance

For the complete list of changes and bugfixes, please visit our changelog.

Whether you're building a new federated application or maintaining an existing one, #Fedify 1.4.0 provides the tools you need for robust ActivityPub federation.

Supporting us

Upgrade now

You can install Fedify 1.4.0 from JSR or npm. Upgrade today and let us know what you think!

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're excited to announce the release of Fedify 1.4.0! This release brings significant improvements to enhance compatibility and flexibility in #ActivityPub federation.

Key Highlights

Activity transformers

WebFinger customization

Added the ability to customize WebFinger responses through the new mapAlias() API, giving you more control over how your actors are discovered.

New interaction collections

Added support for shares, likes, and emojiReactions properties to the Object class, making it easier to access and traverse these interaction collections.

CLI improvements

The fedify lookup command now supports two new options:

-t/--traverse: Traverse through collection objects
-S/--suppress-errors: Continue operation even when encountering errors during traversal

Other enhancements

Added Context.getNodeInfo() method for easier NodeInfo access
Improved error handling in collection traversal and JSON-LD processing
Added support for private network access control in WebFinger lookups
User-Agent headers now automatically include your instance URL, making it easier for other servers to identify your instance

For the complete list of changes and bugfixes, please visit our changelog.

Whether you're building a new federated application or maintaining an existing one, #Fedify 1.4.0 provides the tools you need for robust ActivityPub federation.

Supporting us

Upgrade now

You can install Fedify 1.4.0 from JSR or npm. Upgrade today and let us know what you think!

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're excited to announce the release of Fedify 1.4.0! This release brings significant improvements to enhance compatibility and flexibility in #ActivityPub federation.

Key Highlights

Activity transformers

WebFinger customization

Added the ability to customize WebFinger responses through the new mapAlias() API, giving you more control over how your actors are discovered.

New interaction collections

Added support for shares, likes, and emojiReactions properties to the Object class, making it easier to access and traverse these interaction collections.

CLI improvements

The fedify lookup command now supports two new options:

-t/--traverse: Traverse through collection objects
-S/--suppress-errors: Continue operation even when encountering errors during traversal

Other enhancements

Added Context.getNodeInfo() method for easier NodeInfo access
Improved error handling in collection traversal and JSON-LD processing
Added support for private network access control in WebFinger lookups
User-Agent headers now automatically include your instance URL, making it easier for other servers to identify your instance

For the complete list of changes and bugfixes, please visit our changelog.

Whether you're building a new federated application or maintaining an existing one, #Fedify 1.4.0 provides the tools you need for robust ActivityPub federation.

Supporting us

Upgrade now

You can install Fedify 1.4.0 from JSR or npm. Upgrade today and let us know what you think!

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're excited to announce the release of Fedify 1.4.0! This release brings significant improvements to enhance compatibility and flexibility in #ActivityPub federation.

Key Highlights

Activity transformers

WebFinger customization

Added the ability to customize WebFinger responses through the new mapAlias() API, giving you more control over how your actors are discovered.

New interaction collections

Added support for shares, likes, and emojiReactions properties to the Object class, making it easier to access and traverse these interaction collections.

CLI improvements

The fedify lookup command now supports two new options:

-t/--traverse: Traverse through collection objects
-S/--suppress-errors: Continue operation even when encountering errors during traversal

Other enhancements

Added Context.getNodeInfo() method for easier NodeInfo access
Improved error handling in collection traversal and JSON-LD processing
Added support for private network access control in WebFinger lookups
User-Agent headers now automatically include your instance URL, making it easier for other servers to identify your instance

For the complete list of changes and bugfixes, please visit our changelog.

Whether you're building a new federated application or maintaining an existing one, #Fedify 1.4.0 provides the tools you need for robust ActivityPub federation.

Supporting us

Upgrade now

You can install Fedify 1.4.0 from JSR or npm. Upgrade today and let us know what you think!

Fedify: an ActivityPub server framework

@fedify@hollo.social

We're excited to announce the release of Fedify 1.4.0! This release brings significant improvements to enhance compatibility and flexibility in #ActivityPub federation.

Key Highlights

Activity transformers

WebFinger customization

Added the ability to customize WebFinger responses through the new mapAlias() API, giving you more control over how your actors are discovered.

New interaction collections

Added support for shares, likes, and emojiReactions properties to the Object class, making it easier to access and traverse these interaction collections.

CLI improvements

The fedify lookup command now supports two new options:

-t/--traverse: Traverse through collection objects
-S/--suppress-errors: Continue operation even when encountering errors during traversal

Other enhancements

Added Context.getNodeInfo() method for easier NodeInfo access
Improved error handling in collection traversal and JSON-LD processing
Added support for private network access control in WebFinger lookups
User-Agent headers now automatically include your instance URL, making it easier for other servers to identify your instance

For the complete list of changes and bugfixes, please visit our changelog.

Whether you're building a new federated application or maintaining an existing one, #Fedify 1.4.0 provides the tools you need for robust ActivityPub federation.

Supporting us

Upgrade now

You can install Fedify 1.4.0 from JSR or npm. Upgrade today and let us know what you think!

https://hollo.social/@fedify/0194b112-b604-7d03-84e0-4faaf4ab46cd

wakest ⁂

@liaizon@social.wake.st

"meeting people in real life remains one of the best ways to build trust and relationships ... by getting the #NodeBB, #WordPress ActivityPub plugin, #WriteFreely and #Ghost developers together and recognising themselves as the ‘longform’ people. This group of developers getting together this way helps with the various projects becoming more interoperable, and better support for longform content in the #fediverse."
-@laurenshof in https://fediversereport.com/fediverse-report-102
#fedidev #TheLongformPeople

wakest ⁂

@liaizon@social.wake.st

Has anyone made a directory page of all the #FEPs with simple descriptions of what they are for yet? #fedidev

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

As the maintainer of #Fedify, I'd be grateful for your support to help keep the project sustainable!

Fedify: an ActivityPub server framework

@fedify@hollo.social

🎉 Excited to announce that #Fedify is now on Open Collective! Support the project's development starting at:

Backer (from $5/mo)
Supporter (from $25/mo)
Sponsor (from $100/mo)
Corporate Sponsor (from $500/mo)
Custom donations welcome

Your support will help us maintain and improve Fedify. Check it out here:

#OpenCollective #support #backing #sponsor #donation

ALT text details

BotKit by Fedify

@botkit@hollo.social

Are you interested in creating bots for the #fediverse? Meet #BotKit, a #TypeScript framework that makes bot development easier than ever!

Key Features:

True Independence

Create standalone #ActivityPub bots
No need for a Mastodon or Misskey account
Free from platform-specific limitations

Simple and Intuitive API

Create a complete bot in a single TypeScript file
Intuitive event handlers for mentions, follows, and messages
Rich text formatting with Markdown support

Modern Deployment

Deploy on Deno Deploy, Fly.io, Railway, or any virtual server
Minimal dependencies
Designed for modern cloud platforms

Enterprise-Ready Foundation

Built on Fedify, a rock-solid ActivityPub framework
Seamless federation with Mastodon, Misskey, and other platforms
Robust compatibility across the fediverse

Developer Experience

Full TypeScript support with great IDE integration
Comprehensive documentation
Built-in testing utilities

Here's a quick example of how simple it is to create a bot:

import { createBot, mention, text } from "@fedify/botkit";

const bot = createBot<void>({
  username: "greetbot",
  name: "Greet Bot",
  summary: text`A friendly bot that greets people!`,
  // ... configuration ...
});

// Respond to mentions
bot.onMention = async (session, message) => {
  await message.reply(text`Hi, ${message.actor}! Thanks for saying hello!`);
};

export default bot;

Getting Started:

Install #Deno
Run: deno add jsr:@fedify/botkit@^0.1.0-dev
Create your bot with just a few lines of code

Check out our documentation at https://botkit.fedify.dev/ to learn more!

https://hollo.social/@fedify/0194b112-b604-7d03-84e0-4faaf4ab46cd

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

As the maintainer of #Fedify, I'd be grateful for your support to help keep the project sustainable!

Fedify: an ActivityPub server framework

@fedify@hollo.social

🎉 Excited to announce that #Fedify is now on Open Collective! Support the project's development starting at:

Backer (from $5/mo)
Supporter (from $25/mo)
Sponsor (from $100/mo)
Corporate Sponsor (from $500/mo)
Custom donations welcome

Your support will help us maintain and improve Fedify. Check it out here:

#OpenCollective #support #backing #sponsor #donation

ALT text details

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

As the maintainer of #Fedify, I'd be grateful for your support to help keep the project sustainable!

https://hollo.social/@fedify/0194b112-b604-7d03-84e0-4faaf4ab46cd

Fedify: an ActivityPub server framework

@fedify@hollo.social

🎉 Excited to announce that #Fedify is now on Open Collective! Support the project's development starting at:

Backer (from $5/mo)
Supporter (from $25/mo)
Sponsor (from $100/mo)
Corporate Sponsor (from $500/mo)
Custom donations welcome

Your support will help us maintain and improve Fedify. Check it out here:

#OpenCollective #support #backing #sponsor #donation

ALT text details

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

As the maintainer of #Fedify, I'd be grateful for your support to help keep the project sustainable!

https://hollo.social/@fedify/0194b112-b604-7d03-84e0-4faaf4ab46cd

Fedify: an ActivityPub server framework

@fedify@hollo.social

🎉 Excited to announce that #Fedify is now on Open Collective! Support the project's development starting at:

Backer (from $5/mo)
Supporter (from $25/mo)
Sponsor (from $100/mo)
Corporate Sponsor (from $500/mo)
Custom donations welcome

Your support will help us maintain and improve Fedify. Check it out here:

#OpenCollective #support #backing #sponsor #donation

ALT text details

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

As the maintainer of #Fedify, I'd be grateful for your support to help keep the project sustainable!

https://hollo.social/@fedify/0194b112-b604-7d03-84e0-4faaf4ab46cd

Fedify: an ActivityPub server framework

@fedify@hollo.social

🎉 Excited to announce that #Fedify is now on Open Collective! Support the project's development starting at:

Backer (from $5/mo)
Supporter (from $25/mo)
Sponsor (from $100/mo)
Corporate Sponsor (from $500/mo)
Custom donations welcome

Your support will help us maintain and improve Fedify. Check it out here:

#OpenCollective #support #backing #sponsor #donation

ALT text details

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

As the maintainer of #Fedify, I'd be grateful for your support to help keep the project sustainable!

https://hollo.social/@fedify/0194b112-b604-7d03-84e0-4faaf4ab46cd

Fedify: an ActivityPub server framework

@fedify@hollo.social

🎉 Excited to announce that #Fedify is now on Open Collective! Support the project's development starting at:

Backer (from $5/mo)
Supporter (from $25/mo)
Sponsor (from $100/mo)
Corporate Sponsor (from $500/mo)
Custom donations welcome

Your support will help us maintain and improve Fedify. Check it out here:

#OpenCollective #support #backing #sponsor #donation

ALT text details

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

As the maintainer of #Fedify, I'd be grateful for your support to help keep the project sustainable!

https://hollo.social/@fedify/0194b112-b604-7d03-84e0-4faaf4ab46cd

Fedify: an ActivityPub server framework

@fedify@hollo.social

🎉 Excited to announce that #Fedify is now on Open Collective! Support the project's development starting at:

Backer (from $5/mo)
Supporter (from $25/mo)
Sponsor (from $100/mo)
Corporate Sponsor (from $500/mo)
Custom donations welcome

Your support will help us maintain and improve Fedify. Check it out here:

#OpenCollective #support #backing #sponsor #donation

ALT text details

BotKit by Fedify

@botkit@hollo.social

Are you interested in creating bots for the #fediverse? Meet #BotKit, a #TypeScript framework that makes bot development easier than ever!

Key Features:

True Independence

Create standalone #ActivityPub bots
No need for a Mastodon or Misskey account
Free from platform-specific limitations

Simple and Intuitive API

Create a complete bot in a single TypeScript file
Intuitive event handlers for mentions, follows, and messages
Rich text formatting with Markdown support

Modern Deployment

Deploy on Deno Deploy, Fly.io, Railway, or any virtual server
Minimal dependencies
Designed for modern cloud platforms

Enterprise-Ready Foundation

Built on Fedify, a rock-solid ActivityPub framework
Seamless federation with Mastodon, Misskey, and other platforms
Robust compatibility across the fediverse

Developer Experience

Full TypeScript support with great IDE integration
Comprehensive documentation
Built-in testing utilities

Here's a quick example of how simple it is to create a bot:

import { createBot, mention, text } from "@fedify/botkit";

const bot = createBot<void>({
  username: "greetbot",
  name: "Greet Bot",
  summary: text`A friendly bot that greets people!`,
  // ... configuration ...
});

// Respond to mentions
bot.onMention = async (session, message) => {
  await message.reply(text`Hi, ${message.actor}! Thanks for saying hello!`);
};

export default bot;

Getting Started:

Install #Deno
Run: deno add jsr:@fedify/botkit@^0.1.0-dev
Create your bot with just a few lines of code

Check out our documentation at https://botkit.fedify.dev/ to learn more!

BotKit by Fedify

@botkit@hollo.social

Are you interested in creating bots for the #fediverse? Meet #BotKit, a #TypeScript framework that makes bot development easier than ever!

Key Features:

True Independence

Create standalone #ActivityPub bots
No need for a Mastodon or Misskey account
Free from platform-specific limitations

Simple and Intuitive API

Create a complete bot in a single TypeScript file
Intuitive event handlers for mentions, follows, and messages
Rich text formatting with Markdown support

Modern Deployment

Deploy on Deno Deploy, Fly.io, Railway, or any virtual server
Minimal dependencies
Designed for modern cloud platforms

Enterprise-Ready Foundation

Built on Fedify, a rock-solid ActivityPub framework
Seamless federation with Mastodon, Misskey, and other platforms
Robust compatibility across the fediverse

Developer Experience

Full TypeScript support with great IDE integration
Comprehensive documentation
Built-in testing utilities

Here's a quick example of how simple it is to create a bot:

import { createBot, mention, text } from "@fedify/botkit";

const bot = createBot<void>({
  username: "greetbot",
  name: "Greet Bot",
  summary: text`A friendly bot that greets people!`,
  // ... configuration ...
});

// Respond to mentions
bot.onMention = async (session, message) => {
  await message.reply(text`Hi, ${message.actor}! Thanks for saying hello!`);
};

export default bot;

Getting Started:

Install #Deno
Run: deno add jsr:@fedify/botkit@^0.1.0-dev
Create your bot with just a few lines of code

Check out our documentation at https://botkit.fedify.dev/ to learn more!

BotKit by Fedify

@botkit@hollo.social

Are you interested in creating bots for the #fediverse? Meet #BotKit, a #TypeScript framework that makes bot development easier than ever!

Key Features:

True Independence

Create standalone #ActivityPub bots
No need for a Mastodon or Misskey account
Free from platform-specific limitations

Simple and Intuitive API

Create a complete bot in a single TypeScript file
Intuitive event handlers for mentions, follows, and messages
Rich text formatting with Markdown support

Modern Deployment

Deploy on Deno Deploy, Fly.io, Railway, or any virtual server
Minimal dependencies
Designed for modern cloud platforms

Enterprise-Ready Foundation

Built on Fedify, a rock-solid ActivityPub framework
Seamless federation with Mastodon, Misskey, and other platforms
Robust compatibility across the fediverse

Developer Experience

Full TypeScript support with great IDE integration
Comprehensive documentation
Built-in testing utilities

Here's a quick example of how simple it is to create a bot:

import { createBot, mention, text } from "@fedify/botkit";

const bot = createBot<void>({
  username: "greetbot",
  name: "Greet Bot",
  summary: text`A friendly bot that greets people!`,
  // ... configuration ...
});

// Respond to mentions
bot.onMention = async (session, message) => {
  await message.reply(text`Hi, ${message.actor}! Thanks for saying hello!`);
};

export default bot;

Getting Started:

Install #Deno
Run: deno add jsr:@fedify/botkit@^0.1.0-dev
Create your bot with just a few lines of code

Check out our documentation at https://botkit.fedify.dev/ to learn more!

BotKit by Fedify

@botkit@hollo.social

Are you interested in creating bots for the #fediverse? Meet #BotKit, a #TypeScript framework that makes bot development easier than ever!

Key Features:

True Independence

Create standalone #ActivityPub bots
No need for a Mastodon or Misskey account
Free from platform-specific limitations

Simple and Intuitive API

Create a complete bot in a single TypeScript file
Intuitive event handlers for mentions, follows, and messages
Rich text formatting with Markdown support

Modern Deployment

Deploy on Deno Deploy, Fly.io, Railway, or any virtual server
Minimal dependencies
Designed for modern cloud platforms

Enterprise-Ready Foundation

Built on Fedify, a rock-solid ActivityPub framework
Seamless federation with Mastodon, Misskey, and other platforms
Robust compatibility across the fediverse

Developer Experience

Full TypeScript support with great IDE integration
Comprehensive documentation
Built-in testing utilities

Here's a quick example of how simple it is to create a bot:

import { createBot, mention, text } from "@fedify/botkit";

const bot = createBot<void>({
  username: "greetbot",
  name: "Greet Bot",
  summary: text`A friendly bot that greets people!`,
  // ... configuration ...
});

// Respond to mentions
bot.onMention = async (session, message) => {
  await message.reply(text`Hi, ${message.actor}! Thanks for saying hello!`);
};

export default bot;

Getting Started:

Install #Deno
Run: deno add jsr:@fedify/botkit@^0.1.0-dev
Create your bot with just a few lines of code

Check out our documentation at https://botkit.fedify.dev/ to learn more!

BotKit by Fedify

@botkit@hollo.social

Are you interested in creating bots for the #fediverse? Meet #BotKit, a #TypeScript framework that makes bot development easier than ever!

Key Features:

True Independence

Create standalone #ActivityPub bots
No need for a Mastodon or Misskey account
Free from platform-specific limitations

Simple and Intuitive API

Create a complete bot in a single TypeScript file
Intuitive event handlers for mentions, follows, and messages
Rich text formatting with Markdown support

Modern Deployment

Deploy on Deno Deploy, Fly.io, Railway, or any virtual server
Minimal dependencies
Designed for modern cloud platforms

Enterprise-Ready Foundation

Built on Fedify, a rock-solid ActivityPub framework
Seamless federation with Mastodon, Misskey, and other platforms
Robust compatibility across the fediverse

Developer Experience

Full TypeScript support with great IDE integration
Comprehensive documentation
Built-in testing utilities

Here's a quick example of how simple it is to create a bot:

import { createBot, mention, text } from "@fedify/botkit";

const bot = createBot<void>({
  username: "greetbot",
  name: "Greet Bot",
  summary: text`A friendly bot that greets people!`,
  // ... configuration ...
});

// Respond to mentions
bot.onMention = async (session, message) => {
  await message.reply(text`Hi, ${message.actor}! Thanks for saying hello!`);
};

export default bot;

Getting Started:

Install #Deno
Run: deno add jsr:@fedify/botkit@^0.1.0-dev
Create your bot with just a few lines of code

Check out our documentation at https://botkit.fedify.dev/ to learn more!

BotKit by Fedify

@botkit@hollo.social

#BotKit now supports #hashtags in your bot messages!

You can now add searchable hashtags to your bot's posts using either our dedicated hashtag() function or through BotKit's extended Markdown syntax. This makes your bot's content more discoverable across the fediverse and helps engage with broader conversations.

Whether you're building a news bot, content curator, or community engagement tool, hashtags can help your bot reach the right audience.

Check out our docs to learn more about implementing hashtags in your bots!

ALT text details

Documentation showing BotKit's hashtag() function usage. It demonstrates how to use the hashtag() function in template literals and explains that the function automatically adds the “#” prefix if missing. The note section explains that hashtags are made discoverable for ActivityPub software.

ALT text details

Documentation showing BotKit's Markdown hashtag syntax. It demonstrates how to use hashtags in markdown() function with examples and explains that the function denotes hashtags for ActivityPub discoverability. It also shows how to disable hashtag syntax using the hashtags: false option.

BotKit by Fedify

@botkit@hollo.social

#BotKit now supports #hashtags in your bot messages!

Whether you're building a news bot, content curator, or community engagement tool, hashtags can help your bot reach the right audience.

Check out our docs to learn more about implementing hashtags in your bots!

ALT text details

BotKit by Fedify

@botkit@hollo.social

#BotKit now supports #hashtags in your bot messages!

Whether you're building a news bot, content curator, or community engagement tool, hashtags can help your bot reach the right audience.

Check out our docs to learn more about implementing hashtags in your bots!

ALT text details

BotKit by Fedify

@botkit@hollo.social

#BotKit now supports #hashtags in your bot messages!

Whether you're building a news bot, content curator, or community engagement tool, hashtags can help your bot reach the right audience.

Check out our docs to learn more about implementing hashtags in your bots!

ALT text details

BotKit by Fedify

@botkit@hollo.social

#BotKit now supports #hashtags in your bot messages!

Whether you're building a news bot, content curator, or community engagement tool, hashtags can help your bot reach the right audience.

Check out our docs to learn more about implementing hashtags in your bots!

https://hollo.social/@fedify/0194b112-b604-7d03-84e0-4faaf4ab46cd

ALT text details

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

As the maintainer of #Fedify, I'd be grateful for your support to help keep the project sustainable!

Fedify: an ActivityPub server framework

@fedify@hollo.social

🎉 Excited to announce that #Fedify is now on Open Collective! Support the project's development starting at:

Backer (from $5/mo)
Supporter (from $25/mo)
Sponsor (from $100/mo)
Corporate Sponsor (from $500/mo)
Custom donations welcome

Your support will help us maintain and improve Fedify. Check it out here:

#OpenCollective #support #backing #sponsor #donation

ALT text details

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

As the maintainer of #Fedify, I'd be grateful for your support to help keep the project sustainable!

https://hollo.social/@fedify/0194b112-b604-7d03-84e0-4faaf4ab46cd

Fedify: an ActivityPub server framework

@fedify@hollo.social

🎉 Excited to announce that #Fedify is now on Open Collective! Support the project's development starting at:

Backer (from $5/mo)
Supporter (from $25/mo)
Sponsor (from $100/mo)
Corporate Sponsor (from $500/mo)
Custom donations welcome

Your support will help us maintain and improve Fedify. Check it out here:

#OpenCollective #support #backing #sponsor #donation

ALT text details

BotKit by Fedify

@botkit@hollo.social

Are you interested in creating bots for the #fediverse? Meet #BotKit, a #TypeScript framework that makes bot development easier than ever!

Key Features:

True Independence

Create standalone #ActivityPub bots
No need for a Mastodon or Misskey account
Free from platform-specific limitations

Simple and Intuitive API

Create a complete bot in a single TypeScript file
Intuitive event handlers for mentions, follows, and messages
Rich text formatting with Markdown support

Modern Deployment

Deploy on Deno Deploy, Fly.io, Railway, or any virtual server
Minimal dependencies
Designed for modern cloud platforms

Enterprise-Ready Foundation

Built on Fedify, a rock-solid ActivityPub framework
Seamless federation with Mastodon, Misskey, and other platforms
Robust compatibility across the fediverse

Developer Experience

Full TypeScript support with great IDE integration
Comprehensive documentation
Built-in testing utilities

Here's a quick example of how simple it is to create a bot:

import { createBot, mention, text } from "@fedify/botkit";

const bot = createBot<void>({
  username: "greetbot",
  name: "Greet Bot",
  summary: text`A friendly bot that greets people!`,
  // ... configuration ...
});

// Respond to mentions
bot.onMention = async (session, message) => {
  await message.reply(text`Hi, ${message.actor}! Thanks for saying hello!`);
};

export default bot;

Getting Started:

Install #Deno
Run: deno add jsr:@fedify/botkit@^0.1.0-dev
Create your bot with just a few lines of code

Check out our documentation at https://botkit.fedify.dev/ to learn more!

BotKit by Fedify

@botkit@hollo.social

Are you interested in creating bots for the #fediverse? Meet #BotKit, a #TypeScript framework that makes bot development easier than ever!

Key Features:

True Independence

Create standalone #ActivityPub bots
No need for a Mastodon or Misskey account
Free from platform-specific limitations

Simple and Intuitive API

Create a complete bot in a single TypeScript file
Intuitive event handlers for mentions, follows, and messages
Rich text formatting with Markdown support

Modern Deployment

Deploy on Deno Deploy, Fly.io, Railway, or any virtual server
Minimal dependencies
Designed for modern cloud platforms

Enterprise-Ready Foundation

Built on Fedify, a rock-solid ActivityPub framework
Seamless federation with Mastodon, Misskey, and other platforms
Robust compatibility across the fediverse

Developer Experience

Full TypeScript support with great IDE integration
Comprehensive documentation
Built-in testing utilities

Here's a quick example of how simple it is to create a bot:

import { createBot, mention, text } from "@fedify/botkit";

const bot = createBot<void>({
  username: "greetbot",
  name: "Greet Bot",
  summary: text`A friendly bot that greets people!`,
  // ... configuration ...
});

// Respond to mentions
bot.onMention = async (session, message) => {
  await message.reply(text`Hi, ${message.actor}! Thanks for saying hello!`);
};

export default bot;

Getting Started:

Install #Deno
Run: deno add jsr:@fedify/botkit@^0.1.0-dev
Create your bot with just a few lines of code

Check out our documentation at https://botkit.fedify.dev/ to learn more!

BotKit by Fedify

@botkit@hollo.social

Are you interested in creating bots for the #fediverse? Meet #BotKit, a #TypeScript framework that makes bot development easier than ever!

Key Features:

True Independence

Create standalone #ActivityPub bots
No need for a Mastodon or Misskey account
Free from platform-specific limitations

Simple and Intuitive API

Create a complete bot in a single TypeScript file
Intuitive event handlers for mentions, follows, and messages
Rich text formatting with Markdown support

Modern Deployment

Deploy on Deno Deploy, Fly.io, Railway, or any virtual server
Minimal dependencies
Designed for modern cloud platforms

Enterprise-Ready Foundation

Built on Fedify, a rock-solid ActivityPub framework
Seamless federation with Mastodon, Misskey, and other platforms
Robust compatibility across the fediverse

Developer Experience

Full TypeScript support with great IDE integration
Comprehensive documentation
Built-in testing utilities

Here's a quick example of how simple it is to create a bot:

import { createBot, mention, text } from "@fedify/botkit";

const bot = createBot<void>({
  username: "greetbot",
  name: "Greet Bot",
  summary: text`A friendly bot that greets people!`,
  // ... configuration ...
});

// Respond to mentions
bot.onMention = async (session, message) => {
  await message.reply(text`Hi, ${message.actor}! Thanks for saying hello!`);
};

export default bot;

Getting Started:

Install #Deno
Run: deno add jsr:@fedify/botkit@^0.1.0-dev
Create your bot with just a few lines of code

Check out our documentation at https://botkit.fedify.dev/ to learn more!

BotKit by Fedify

@botkit@hollo.social

Are you interested in creating bots for the #fediverse? Meet #BotKit, a #TypeScript framework that makes bot development easier than ever!

Key Features:

True Independence

Create standalone #ActivityPub bots
No need for a Mastodon or Misskey account
Free from platform-specific limitations

Simple and Intuitive API

Create a complete bot in a single TypeScript file
Intuitive event handlers for mentions, follows, and messages
Rich text formatting with Markdown support

Modern Deployment

Deploy on Deno Deploy, Fly.io, Railway, or any virtual server
Minimal dependencies
Designed for modern cloud platforms

Enterprise-Ready Foundation

Built on Fedify, a rock-solid ActivityPub framework
Seamless federation with Mastodon, Misskey, and other platforms
Robust compatibility across the fediverse

Developer Experience

Full TypeScript support with great IDE integration
Comprehensive documentation
Built-in testing utilities

Here's a quick example of how simple it is to create a bot:

import { createBot, mention, text } from "@fedify/botkit";

const bot = createBot<void>({
  username: "greetbot",
  name: "Greet Bot",
  summary: text`A friendly bot that greets people!`,
  // ... configuration ...
});

// Respond to mentions
bot.onMention = async (session, message) => {
  await message.reply(text`Hi, ${message.actor}! Thanks for saying hello!`);
};

export default bot;

Getting Started:

Install #Deno
Run: deno add jsr:@fedify/botkit@^0.1.0-dev
Create your bot with just a few lines of code

Check out our documentation at https://botkit.fedify.dev/ to learn more!

https://hollo.social/@fedify/0194b112-b604-7d03-84e0-4faaf4ab46cd

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

As the maintainer of #Fedify, I'd be grateful for your support to help keep the project sustainable!

Fedify: an ActivityPub server framework

@fedify@hollo.social

🎉 Excited to announce that #Fedify is now on Open Collective! Support the project's development starting at:

Backer (from $5/mo)
Supporter (from $25/mo)
Sponsor (from $100/mo)
Corporate Sponsor (from $500/mo)
Custom donations welcome

Your support will help us maintain and improve Fedify. Check it out here:

#OpenCollective #support #backing #sponsor #donation

ALT text details

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

As the maintainer of #Fedify, I'd be grateful for your support to help keep the project sustainable!

https://hollo.social/@fedify/0194b112-b604-7d03-84e0-4faaf4ab46cd

Fedify: an ActivityPub server framework

@fedify@hollo.social

🎉 Excited to announce that #Fedify is now on Open Collective! Support the project's development starting at:

Backer (from $5/mo)
Supporter (from $25/mo)
Sponsor (from $100/mo)
Corporate Sponsor (from $500/mo)
Custom donations welcome

Your support will help us maintain and improve Fedify. Check it out here:

#OpenCollective #support #backing #sponsor #donation

ALT text details

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

As the maintainer of #Fedify, I'd be grateful for your support to help keep the project sustainable!

https://hollo.social/@fedify/0194b112-b604-7d03-84e0-4faaf4ab46cd

Fedify: an ActivityPub server framework

@fedify@hollo.social

🎉 Excited to announce that #Fedify is now on Open Collective! Support the project's development starting at:

Backer (from $5/mo)
Supporter (from $25/mo)
Sponsor (from $100/mo)
Corporate Sponsor (from $500/mo)
Custom donations welcome

Your support will help us maintain and improve Fedify. Check it out here:

#OpenCollective #support #backing #sponsor #donation

ALT text details

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

As the maintainer of #Fedify, I'd be grateful for your support to help keep the project sustainable!

https://hollo.social/@fedify/0194b112-b604-7d03-84e0-4faaf4ab46cd

Fedify: an ActivityPub server framework

@fedify@hollo.social

🎉 Excited to announce that #Fedify is now on Open Collective! Support the project's development starting at:

Backer (from $5/mo)
Supporter (from $25/mo)
Sponsor (from $100/mo)
Corporate Sponsor (from $500/mo)
Custom donations welcome

Your support will help us maintain and improve Fedify. Check it out here:

#OpenCollective #support #backing #sponsor #donation

ALT text details

BotKit by Fedify

@botkit@hollo.social

Are you interested in creating bots for the #fediverse? Meet #BotKit, a #TypeScript framework that makes bot development easier than ever!

Key Features:

True Independence

Create standalone #ActivityPub bots
No need for a Mastodon or Misskey account
Free from platform-specific limitations

Simple and Intuitive API

Create a complete bot in a single TypeScript file
Intuitive event handlers for mentions, follows, and messages
Rich text formatting with Markdown support

Modern Deployment

Deploy on Deno Deploy, Fly.io, Railway, or any virtual server
Minimal dependencies
Designed for modern cloud platforms

Enterprise-Ready Foundation

Built on Fedify, a rock-solid ActivityPub framework
Seamless federation with Mastodon, Misskey, and other platforms
Robust compatibility across the fediverse

Developer Experience

Full TypeScript support with great IDE integration
Comprehensive documentation
Built-in testing utilities

Here's a quick example of how simple it is to create a bot:

import { createBot, mention, text } from "@fedify/botkit";

const bot = createBot<void>({
  username: "greetbot",
  name: "Greet Bot",
  summary: text`A friendly bot that greets people!`,
  // ... configuration ...
});

// Respond to mentions
bot.onMention = async (session, message) => {
  await message.reply(text`Hi, ${message.actor}! Thanks for saying hello!`);
};

export default bot;

Getting Started:

Install #Deno
Run: deno add jsr:@fedify/botkit@^0.1.0-dev
Create your bot with just a few lines of code

Check out our documentation at https://botkit.fedify.dev/ to learn more!

BotKit by Fedify

@botkit@hollo.social

Are you interested in creating bots for the #fediverse? Meet #BotKit, a #TypeScript framework that makes bot development easier than ever!

Key Features:

True Independence

Create standalone #ActivityPub bots
No need for a Mastodon or Misskey account
Free from platform-specific limitations

Simple and Intuitive API

Create a complete bot in a single TypeScript file
Intuitive event handlers for mentions, follows, and messages
Rich text formatting with Markdown support

Modern Deployment

Deploy on Deno Deploy, Fly.io, Railway, or any virtual server
Minimal dependencies
Designed for modern cloud platforms

Enterprise-Ready Foundation

Built on Fedify, a rock-solid ActivityPub framework
Seamless federation with Mastodon, Misskey, and other platforms
Robust compatibility across the fediverse

Developer Experience

Full TypeScript support with great IDE integration
Comprehensive documentation
Built-in testing utilities

Here's a quick example of how simple it is to create a bot:

import { createBot, mention, text } from "@fedify/botkit";

const bot = createBot<void>({
  username: "greetbot",
  name: "Greet Bot",
  summary: text`A friendly bot that greets people!`,
  // ... configuration ...
});

// Respond to mentions
bot.onMention = async (session, message) => {
  await message.reply(text`Hi, ${message.actor}! Thanks for saying hello!`);
};

export default bot;

Getting Started:

Install #Deno
Run: deno add jsr:@fedify/botkit@^0.1.0-dev
Create your bot with just a few lines of code

Check out our documentation at https://botkit.fedify.dev/ to learn more!

BotKit by Fedify

@botkit@hollo.social

Are you interested in creating bots for the #fediverse? Meet #BotKit, a #TypeScript framework that makes bot development easier than ever!

Key Features:

True Independence

Create standalone #ActivityPub bots
No need for a Mastodon or Misskey account
Free from platform-specific limitations

Simple and Intuitive API

Create a complete bot in a single TypeScript file
Intuitive event handlers for mentions, follows, and messages
Rich text formatting with Markdown support

Modern Deployment

Deploy on Deno Deploy, Fly.io, Railway, or any virtual server
Minimal dependencies
Designed for modern cloud platforms

Enterprise-Ready Foundation

Built on Fedify, a rock-solid ActivityPub framework
Seamless federation with Mastodon, Misskey, and other platforms
Robust compatibility across the fediverse

Developer Experience

Full TypeScript support with great IDE integration
Comprehensive documentation
Built-in testing utilities

Here's a quick example of how simple it is to create a bot:

import { createBot, mention, text } from "@fedify/botkit";

const bot = createBot<void>({
  username: "greetbot",
  name: "Greet Bot",
  summary: text`A friendly bot that greets people!`,
  // ... configuration ...
});

// Respond to mentions
bot.onMention = async (session, message) => {
  await message.reply(text`Hi, ${message.actor}! Thanks for saying hello!`);
};

export default bot;

Getting Started:

Install #Deno
Run: deno add jsr:@fedify/botkit@^0.1.0-dev
Create your bot with just a few lines of code

Check out our documentation at https://botkit.fedify.dev/ to learn more!

#CloudflareWorkers #fedidev #ActivityPub

Fedify: an ActivityPub server framework

@fedify@hollo.social

Valtteri Laitinen (@valtlai) managed to get #Fedify running on #Cloudflare Workers!

https://fedi.valtlai.fi/@valtlai/113906145660141267

Valtteri Laitinen

Valtteri Laitinen

@valtlai@valtlai.fi · Reply to Valtteri Laitinen's post

BotKit by Fedify

@botkit@hollo.social

📢 Important announcement! #BotKit's #GitHub repository has moved to a new home! 🏠

The repository is now located at @fedify-dev/botkit (previously @dahlia/botkit). All future development will continue at the new location.

Don't worry—everything's the same, just a new address! Please update your bookmarks and project references. Thanks for being part of our community!

#Fedify #ActivityPub #fediverse #fedidev

https://hollo.social/@fedify/0194a851-581d-779c-b777-dc39e753ef14

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

We've just moved the #Fedify project and related repositories to our new GitHub organization account, @fedify-dev! 🎉

Here's what moved:

Thanks to everyone who participated in our naming poll. Looking forward to Fedify's continued growth under its new organizational home!

New GitHub organization: https://github.com/fedify-dev.

BotKit by Fedify

@botkit@hollo.social

#BotKit's web interface now supports theme customization! 🎨 You can set your preferred color theme using the pages.color option in createBot(). Here are some examples showing the same interface in different colors: "violet", "pumpkin", "azure", and "green" (default).

const bot = createBot<void>({
  // ... other options
  pages: {
    color: "violet"  // or "pumpkin", "azure", etc.
  }
});

We support all color themes from Pico CSS—including "amber", "fuchsia", "indigo", "jade", "lime", "pink", "sand", "slate", "yellow", "zinc", and more! Check out Pico CSS's Colors docs for the full list of available themes.

Which color is your favorite? 🤔

https://fosdem.org/2025/schedule/event/fosdem-2025-4531-fediscovery-improving-search-and-discovery-on-the-fediverse/

ALT text details

BotKit web interface in pumpkin theme, displaying Greet Bot's profile. Headers and interactive elements are styled in warm orange tones.

ALT text details

Default green-themed BotKit interface displaying Greet Bot's profile. UI elements are styled in forest green colors, showing the default color scheme.

ALT text details

BotKit web interface in violet theme, showing Greet Bot's profile with greeting message. The interface elements including headings and links are colored in shades of purple.

ALT text details

BotKit web interface themed in azure blue, showing Greet Bot's profile and activity. Navigation elements and links feature various shades of blue.

Stefan Bohacek

@stefan@stefanbohacek.online

The @Mastodon team will be at the upcoming annual free and open source event #FOSSDEM in Brussels this upcoming weekend to talk about their (opt-in!) Fediverse Discovery Providers project:

More about the project: https://www.fediscovery.org/

Via https://mastodon.social/@Mastodon/113900609139086168

#mastodon #MastoDev #fediverse #FediDev #discovery #fediscovery #fossdem

Stefan Bohacek

@stefan@stefanbohacek.online

The @Mastodon team will be at the upcoming annual free and open source event #FOSSDEM in Brussels this upcoming weekend to talk about their (opt-in!) Fediverse Discovery Providers project:

https://fosdem.org/2025/schedule/event/fosdem-2025-4531-fediscovery-improving-search-and-discovery-on-the-fediverse/

More about the project: https://www.fediscovery.org/

Via https://mastodon.social/@Mastodon/113900609139086168

#mastodon #MastoDev #fediverse #FediDev #discovery #fediscovery #fossdem

BotKit by Fedify

@botkit@hollo.social

const bot = createBot<void>({
  // ... other options
  pages: {
    color: "violet"  // or "pumpkin", "azure", etc.
  }
});

Which color is your favorite? 🤔

ALT text details

BotKit web interface in pumpkin theme, displaying Greet Bot's profile. Headers and interactive elements are styled in warm orange tones.

ALT text details

Default green-themed BotKit interface displaying Greet Bot's profile. UI elements are styled in forest green colors, showing the default color scheme.

ALT text details

BotKit web interface in violet theme, showing Greet Bot's profile with greeting message. The interface elements including headings and links are colored in shades of purple.

ALT text details

BotKit web interface themed in azure blue, showing Greet Bot's profile and activity. Navigation elements and links feature various shades of blue.

BotKit by Fedify

@botkit@hollo.social

const bot = createBot<void>({
  // ... other options
  pages: {
    color: "violet"  // or "pumpkin", "azure", etc.
  }
});

Which color is your favorite? 🤔

ALT text details

BotKit web interface in pumpkin theme, displaying Greet Bot's profile. Headers and interactive elements are styled in warm orange tones.

ALT text details

Default green-themed BotKit interface displaying Greet Bot's profile. UI elements are styled in forest green colors, showing the default color scheme.

ALT text details

BotKit web interface in violet theme, showing Greet Bot's profile with greeting message. The interface elements including headings and links are colored in shades of purple.

ALT text details

BotKit web interface themed in azure blue, showing Greet Bot's profile and activity. Navigation elements and links feature various shades of blue.

BotKit by Fedify

@botkit@hollo.social

const bot = createBot<void>({
  // ... other options
  pages: {
    color: "violet"  // or "pumpkin", "azure", etc.
  }
});

Which color is your favorite? 🤔

#fedidev #ActivityPub #ActivityStreams

ALT text details

BotKit web interface in pumpkin theme, displaying Greet Bot's profile. Headers and interactive elements are styled in warm orange tones.

ALT text details

Default green-themed BotKit interface displaying Greet Bot's profile. UI elements are styled in forest green colors, showing the default color scheme.

ALT text details

BotKit web interface in violet theme, showing Greet Bot's profile with greeting message. The interface elements including headings and links are colored in shades of purple.

ALT text details

BotKit web interface themed in azure blue, showing Greet Bot's profile and activity. Navigation elements and links feature various shades of blue.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

I'm looking for your opinions from the developers of the fediverse.

A common HTML web page can contain related links via the <link> tag. I would like to do the same for Activity Streams objects, for example:

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "id": "https://writings.hongminhee.org/ap/2024/12/a-year-with-the-fediverse.json",
  "type": "Article",
  "name": "A year with the fediverse",
  "content": "2024 was truly a year where I was deeply immersed in the fediverse. …",
  "url": "https://writings.hongminhee.org/2024/12/a-year-with-the-fediverse/",
  "attachment": [
    {
      "type": "Link",
      "rel": "alternate",
      "hreflang": "ko",
      "href": "https://writings.hongminhee.org/2024/12/a-year-with-the-fediverse/index.ko-hang-kr.html",
      "mediaType": "text/html"
    },
    {
      "type": "Link",
      "rel": "alternate",
      "hreflang": "ja",
      "href": "https://writings.hongminhee.org/2024/12/a-year-with-the-fediverse/index.ja.html",
      "mediaType": "text/html"
    }
  ]
}

Do you think this makes sense, and would it be appropriate to put Link objects in the attachment?

BotKit by Fedify

@botkit@hollo.social

Exciting update on #BotKit: we've introduced a new Repository abstraction layer that provides cleaner data access. While previously data operations went directly through KvStore, they now go through Repository—improving separation of concerns and making the codebase more maintainable. Don't worry though—there are no breaking changes to the public API that BotKit users rely on!

Key benefits:

Better abstraction over data sources
Cleaner internal architecture
Fully backwards compatible

Check out our docs for the technical details: https://botkit.fedify.dev/concepts/repository.

https://hollo.social/@hongminhee/0194a0d4-1d67-7c81-80ba-e7ade212d27a

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

I'm refactoring @botkit to add a Repository interface (aka DAO). I regret that I should have defined the Repository interface in the first place. 😂

BotKit by Fedify

@botkit@hollo.social

Key benefits:

Better abstraction over data sources
Cleaner internal architecture
Fully backwards compatible

Check out our docs for the technical details: https://botkit.fedify.dev/concepts/repository.

https://hollo.social/@hongminhee/0194a0d4-1d67-7c81-80ba-e7ade212d27a

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

I'm refactoring @botkit to add a Repository interface (aka DAO). I regret that I should have defined the Repository interface in the first place. 😂

BotKit by Fedify

@botkit@hollo.social

Key benefits:

Better abstraction over data sources
Cleaner internal architecture
Fully backwards compatible

Check out our docs for the technical details: https://botkit.fedify.dev/concepts/repository.

https://hollo.social/@hongminhee/0194a0d4-1d67-7c81-80ba-e7ade212d27a

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

I'm refactoring @botkit to add a Repository interface (aka DAO). I regret that I should have defined the Repository interface in the first place. 😂

BotKit by Fedify

@botkit@hollo.social

Key benefits:

Better abstraction over data sources
Cleaner internal architecture
Fully backwards compatible

Check out our docs for the technical details: https://botkit.fedify.dev/concepts/repository.

https://hollo.social/@hongminhee/0194a0d4-1d67-7c81-80ba-e7ade212d27a

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

I'm refactoring @botkit to add a Repository interface (aka DAO). I regret that I should have defined the Repository interface in the first place. 😂

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

I'm looking for your opinions from the developers of the fediverse.

A common HTML web page can contain related links via the <link> tag. I would like to do the same for Activity Streams objects, for example:

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "id": "https://writings.hongminhee.org/ap/2024/12/a-year-with-the-fediverse.json",
  "type": "Article",
  "name": "A year with the fediverse",
  "content": "2024 was truly a year where I was deeply immersed in the fediverse. …",
  "url": "https://writings.hongminhee.org/2024/12/a-year-with-the-fediverse/",
  "attachment": [
    {
      "type": "Link",
      "rel": "alternate",
      "hreflang": "ko",
      "href": "https://writings.hongminhee.org/2024/12/a-year-with-the-fediverse/index.ko-hang-kr.html",
      "mediaType": "text/html"
    },
    {
      "type": "Link",
      "rel": "alternate",
      "hreflang": "ja",
      "href": "https://writings.hongminhee.org/2024/12/a-year-with-the-fediverse/index.ja.html",
      "mediaType": "text/html"
    }
  ]
}

Do you think this makes sense, and would it be appropriate to put Link objects in the attachment?

#fedidev #ActivityPub #ActivityStreams

bouncepaw 🍄

@bouncepaw@merveilles.town

Does it make sense to roll out an ad-hoc federated bookmark search API? Please convince me I should take a different approach.

https://git.sr.ht/~bouncepaw/betula/tree/133-fedisearch/item/fediverse/fedisearch/Federated%20Search.md

wakest ⁂

@liaizon@social.wake.st

I mostly use Phanpy these days but I periodically go back and use @elk. The other day was one of those days. While I was browsing @mjtsai's profile I noticed that Elk supported the new fediverse:creator OG tag but for some reason it was quite borked when viewed from this profile. So I filed an issue in the Elk repo and forgot about it. Today I noticed that @shuuji3 already fixed it and now these badges look great!
#fedidev #fediverse

ALT text details

a screenshot of a blog post on linked in a Mastodon post loaded in Elk with an OpenGraph tag featuring a fediverse:creator badge

wakest ⁂

@liaizon@social.wake.st

Anyone working on #Pleroma / #Mangane / #Akkoma want to have a look at this weirdly inconsistent @elk bug?
https://github.com/elk-zone/elk/issues/934 #fedidev

wakest ⁂

@liaizon@social.wake.st

Anyone working on #Pleroma / #Mangane / #Akkoma want to have a look at this weirdly inconsistent @elk bug?
https://github.com/elk-zone/elk/issues/934 #fedidev

wakest ⁂

@liaizon@social.wake.st

ALT text details

a screenshot of a blog post on linked in a Mastodon post loaded in Elk with an OpenGraph tag featuring a fediverse:creator badge

wakest ⁂

@liaizon@social.wake.st

@reiver ⊼ (Charles)

@reiver@mastodon.social

#FollowFriday the Fediverse Core.

I.e., the people who make the technology of and for the Fediverse.

@reiver ⊼ (Charles)

@reiver@mastodon.social

#FollowFriday the Fediverse Core.

I.e., the people who make the technology of and for the Fediverse.

https://github.com/sponsors/dahlia

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

If you'd like to support the development of @fedify or @hollo or @botkit, you can sponsor me on GitHub!

#ActivityPub #fedidev #Fedify #Hollo #BotKit #sponsor

Jeff Sikes

@box464@mastodon.social

A YunoHost type project, but specific to fediverse platforms. Definitely one I’m going to follow more closely.

@box464@mastodon.social

Happy to hear some good news. NodeBB officially released their ActivtyPub federated forums. And, for new forums, it’s automatically enabled! 🎉

Congratulations to the team, especially @julian

I’ve enjoyed reading the progress posts for this one. A lot of hard work and good collaborations between groups. They should be proud.

https://community.nodebb.org/post/102756

#Fediverse #FediDev #ActivityPub

Jeff Sikes

@box464@mastodon.social

Happy to hear some good news. NodeBB officially released their ActivtyPub federated forums. And, for new forums, it’s automatically enabled! 🎉

Congratulations to the team, especially @julian

I’ve enjoyed reading the progress posts for this one. A lot of hard work and good collaborations between groups. They should be proud.

https://community.nodebb.org/post/102756

#Fediverse #FediDev #ActivityPub

Hollo

@hollo@hollo.social

Introducing #Hollo. Hollo is an #ActivityPub-enabled single-user microblogging software. Although it's for a single user, it also supports creating and running multiple accounts for different topics.

Oh, and Hollo is built using #Bun and #Fedify.

Hollo

@hollo@hollo.social

Introducing #Hollo. Hollo is an #ActivityPub-enabled single-user microblogging software. Although it's for a single user, it also supports creating and running multiple accounts for different topics.

Oh, and Hollo is built using #Bun and #Fedify.

#ActivityPub #ActivityStreams #ActivityPubProfile #DeSo #FediDev #FediDevs #Fediverse #FediverseLabeler #FediverseLabelers #FediverseLabels #JSONLD #OpenWeb #OpenSocial #SocialWeb

@reiver ⊼ (Charles)

@reiver@mastodon.social

Fediverse Labeler update:

I have been working on a site that anyone can use to see Fediverse Labelers in action.

This is what it looks like if the user it looks up doesn't provide an avatar image or a header image.

I.e., this (in the screenshot) shows the default avatar image and header image.

@reiver ⊼ (Charles)

@reiver@mastodon.social · Reply to @reiver ⊼ (Charles) :batman:'s post

Although what I mentioned here doesn't resolve the problem with changing ones username.

That problem still exists with this technique.

#acctURL #ActivityPub #ActivityStreams #DeSo #FediDev #FediDevs #Fediverse #HTTP

@reiver ⊼ (Charles)

@reiver@mastodon.social · Reply to @reiver ⊼ (Charles) :batman:'s post

For example —

If the "username" is part of it, then there is a straightforward unique ID for this user as an acct-URL:

acct:joeblow@example·com

But there are many ways an HTTP-URL as an ID gets represented. Ex:

• http;//example·com/users/joeblow
• http;//example·com/user/joeblow
• http;//example·com/api/users/joeblow
• http;//example·com/api/user/joeblow
• http;//example·com/~joeblow
• etc

#acctURL #ActivityPub #ActivityStreams #DeSo #FediDev #FediDevs #Fediverse #HTTP

@reiver ⊼ (Charles)

@reiver@mastodon.social

If ActivityPub and ActivityStreams used acct-URI rather than HTTP-URL to identify users, then there would less problems with switching between different Fediverse software.

(Different Fediverse software represent users with different style HTTP-URLs — which creates the problem.)

#acctURL #ActivityPub #ActivityStreams #DeSo #FediDev #FediDevs #Fediverse #HTTP

@reiver ⊼ (Charles)

@reiver@mastodon.social · Reply to @reiver ⊼ (Charles) :batman:'s post

For previous posts on Fediverse Labelers, see:

https://mastodon.social/@reiver/113833886881290289

And:

https://mastodon.social/@reiver/113825206793984884

And:

https://mastodon.social/@reiver/113822862806430217

#ActivityPub #ActivityStreams #ActivityPubProfile #DeSo #FediDev #FediDevs #Fediverse #FediverseLabeler #FediverseLabelers #FediverseLabels #JSONLD #OpenWeb #OpenSocial #SocialWeb

@reiver ⊼ (Charles)

@reiver@mastodon.social

Fediverse Labeler update:

I have been working on a site that anyone can use to see Fediverse Labelers in action.

This is what it looks like if the user it looks up doesn't provide an avatar image or a header image.

I.e., this (in the screenshot) shows the default avatar image and header image.

#ActivityPub #ActivityStreams #ActivityPubProfile #DeSo #FediDev #FediDevs #Fediverse #FediverseLabeler #FediverseLabelers #FediverseLabels #JSONLD #OpenWeb #OpenSocial #SocialWeb

@reiver ⊼ (Charles)

@reiver@mastodon.social · Reply to @reiver ⊼ (Charles) :batman:'s post

For discussion on some of the technical / programming side of Fediverse Labelers, see:

https://mastodon.social/@reiver/113822893896346873

#ActivityPub #ActivityStreams #ActivityPubProfile #DeSo #FediDev #FediDevs #Fediverse #FediverseLabeler #FediverseLabelers #FediverseLabels #JSONLD #OpenWeb #OpenSocial #SocialWeb

@reiver ⊼ (Charles)

@reiver@mastodon.social

@reiver ⊼ (Charles)

@reiver@mastodon.social · Reply to @reiver ⊼ (Charles) :batman:'s post

For previous threads on Fediverse Labelers see:

https://mastodon.social/@reiver/113825206793984884

And:

https://mastodon.social/@reiver/113822862806430217

#ActivityPub #ActivityStreams #ActivityPubProfile #DeSo #FediDev #FediDevs #Fediverse #FediverseLabeler #FediverseLabelers #FediverseLabels #JSONLD #OpenWeb #OpenSocial #SocialWeb

@reiver ⊼ (Charles)

@reiver@mastodon.social · Reply to @reiver ⊼ (Charles) :batman:'s post

For previous threads on Fediverse Labelers see:

https://mastodon.social/@reiver/113825206793984884

And:

https://mastodon.social/@reiver/113822862806430217

#ActivityPub #ActivityStreams #ActivityPubProfile #DeSo #FediDev #FediDevs #Fediverse #FediverseLabeler #FediverseLabelers #FediverseLabels #JSONLD #OpenWeb #OpenSocial #SocialWeb

@reiver ⊼ (Charles)

@reiver@mastodon.social

Fediverse Labeler update:

I have been working on site that anyone can use to see Fediverse Labelers in action.

I am hoping to get it done soon. (Maybe by the weekend or next week.)

#ActivityPub #ActivityStreams #ActivityPubProfile #DeSo #FediDev #FediDevs #Fediverse #FediverseLabeler #FediverseLabelers #FediverseLabels #JSONLD #OpenWeb #OpenSocial #SocialWeb

@reiver ⊼ (Charles)

@reiver@mastodon.social · Reply to @reiver ⊼ (Charles) :batman:'s post

This screen mock-up only shows text-labels.

Other types of labels can exist — image labels of different types, virtual object labels, space-time labels, etc.

And labels can have different use-case (in addition to human-readable text) — more on that later.

#ActivityPub #ActivityStreams #ActivityPubProfile #DeSo #FediDev #FediDevs #Fediverse #FediverseLabeler #FediverseLabelers #FediverseLabels #JSONLD #OpenWeb #OpenSocial #SocialWeb

@reiver ⊼ (Charles)

@reiver@mastodon.social · Reply to @reiver ⊼ (Charles) :batman:'s post

For discussion on some of the technical / programming side of Fediverse Labelers, see:

https://mastodon.social/@reiver/113822893896346873

#ActivityPub #ActivityStreams #ActivityPubProfile #DeSo #FediDev #FediDevs #Fediverse #FediverseLabeler #FediverseLabelers #FediverseLabels #JSONLD #OpenWeb #OpenSocial #SocialWeb

@reiver ⊼ (Charles)

@reiver@mastodon.social

@reiver ⊼ (Charles)

@reiver@mastodon.social · Reply to @reiver ⊼ (Charles) :batman:'s post

This screen mock-up only shows text-labels.

Other types of labels can exist — image labels of different types, virtual object labels, space-time labels, etc.

And labels can have different use-case (in addition to human-readable text) — more on that later.

@reiver@mastodon.social

This is how a Fediverse Labeler could work.

In particular, This is how a Fediverse Labeler could be represented as ActivityPub / ActivityStreams / JSON-LD data.

#ActivityPub #ActivityStreams #ActivityPubProfile #DeSo #FediDev #FediDevs #Fediverse #FediverseLabeler #JSONLD #OpenWeb #OpenSocial #SocialWeb

ALT text details

{ "@context": [ "https://www.w3.org/ns/activitystreams" ], "type": "Profile", "describes": "acct:reiver@mastodon.social", "attributedTo": "https://example.com/apps/ratel", "icon": { "type": "Icon", "mediaType": "image/png", "url": "https://example.com/apps/ratel/img/icon.png" }, "attachment": [ { "type": "Label", "name": "Programmer" }, { "type": "Label", "name": "Canadian" }, { "type": "Icon", "mediaType": "image/png", "url": "https://example.com/pfp/751f76ed540a40a3b4caae50e50cc867.png" }, { "type": "Icon", "mediaType": "image/png", "url": "https://example.com/pfp/45f7b459257940f490133070a975924b.png" } ] }

@reiver ⊼ (Charles)

@reiver@mastodon.social

Is any Fediverse (or other) software using or returning an ActivityStreams 'Profile'?

https://www.w3.org/TR/activitystreams-vocabulary/#dfn-profile

#ActivityPub #ActivityStreams #ActivityStreamsProfile #DeSo #FediDev #FediDevs #Fediverse #FediverseLabeler #JSONLD #OpenWeb #SocialWeb

@reiver ⊼ (Charles)

@reiver@mastodon.social

#FollowFriday the Fediverse Core.

I.e., the people who make the technology of and for the Fediverse.

#mastodon4harris #help #fediverse #chuckya #glitchsoc #fedidev

Jessie Nabein

@jessienab@wetdry.world

Hey so at some point #Mastodon changed the way that notifications work, and I can only clear ALL my notifications instead of SPECIFIC notifications.

I hate this change and I wish it never happened.

Please someone tell me there's a way to revert this; same shit happens with Tusky too...

Julian Fietkau

@julian@fietkau.social

The last "big" code thing I need to get done before the alpha test of my current @fedify project is the task queue - make sure routine data updates happen, consider individual importance and urgency, respect external API rate limits, etc.

But that's super intimidating so I'm currently procrastinating by making it a cute lil home page instead. 🙃

#FediDev #ActivityPub #Fedify #WebDev

Minoru

@minoru@functional.cafe

The list of Fediverse instances over at https://nodes.fediverse.party/ hasn't been updated for about three months, and nobody contacted me about it. Is anyone even using the service?

#FediDev

Stefan Bohacek

@stefan@stefanbohacek.online

@box464@mastodon.social

If you're curious how ActivityPub works exactly (like me) this site does a great job of show and tell.

On the surface it looks like any other Mastodon instance, but on closer inspection, provides you insight into the ActivityPub back and forth going on behind the scenes!

Check out the great work by @crepels

https://activitypub.academy/

ALT text details

The Activity Log shows the ActivityPub objects that are passed back and forth when a follow request is sent from one instance to another.

Hollo

@hollo@hollo.social

Introducing #Hollo. Hollo is an #ActivityPub-enabled single-user microblogging software. Although it's for a single user, it also supports creating and running multiple accounts for different topics.

Oh, and Hollo is built using #Bun and #Fedify.

Hollo

@hollo@hollo.social

Introducing #Hollo. Hollo is an #ActivityPub-enabled single-user microblogging software. Although it's for a single user, it also supports creating and running multiple accounts for different topics.

Oh, and Hollo is built using #Bun and #Fedify.

https://git.sr.ht/~bouncepaw/betula/tree/133-fedisearch/item/fediverse/fedisearch/Federated%20Search.md

bouncepaw 🍄

@bouncepaw@merveilles.town

Does it make sense to roll out an ad-hoc federated bookmark search API? Please convince me I should take a different approach.

https://git.sr.ht/~bouncepaw/betula/tree/133-fedisearch/item/fediverse/fedisearch/Federated%20Search.md

bouncepaw 🍄

@bouncepaw@merveilles.town

Does it make sense to roll out an ad-hoc federated bookmark search API? Please convince me I should take a different approach.

#fedidev #ActivityPub #ActivityStreams

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

I'm looking for your opinions from the developers of the fediverse.

A common HTML web page can contain related links via the <link> tag. I would like to do the same for Activity Streams objects, for example:

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "id": "https://writings.hongminhee.org/ap/2024/12/a-year-with-the-fediverse.json",
  "type": "Article",
  "name": "A year with the fediverse",
  "content": "2024 was truly a year where I was deeply immersed in the fediverse. …",
  "url": "https://writings.hongminhee.org/2024/12/a-year-with-the-fediverse/",
  "attachment": [
    {
      "type": "Link",
      "rel": "alternate",
      "hreflang": "ko",
      "href": "https://writings.hongminhee.org/2024/12/a-year-with-the-fediverse/index.ko-hang-kr.html",
      "mediaType": "text/html"
    },
    {
      "type": "Link",
      "rel": "alternate",
      "hreflang": "ja",
      "href": "https://writings.hongminhee.org/2024/12/a-year-with-the-fediverse/index.ja.html",
      "mediaType": "text/html"
    }
  ]
}

Do you think this makes sense, and would it be appropriate to put Link objects in the attachment?

Jeff C. 🇺🇦

@jeff@indieweb.social

Still not a fan of Mastodon's hashtag-centric discovery and topical discussion paradigm.

I want to keep up-to-date with goings-on in Ukraine, but the relevant hashtags have been co-opted by tankies and such spreading Russian agitprop.

I hope one day Mastodon "un-nerfs" list functionality so that users can subscribe to well-curated lists created by known and trusted sources/experts and read posts from those people, w/o committing to manually following each member directly.

#Mastodev #Fedidev

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

Besides WordPress and Ghost, are there any other #ActivityPub implementations that send out an Article type rather than a Note?

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

If you update an account profile in the fediverse, who should you send the Update(Person) activity to?

#ActivityPub #FediDev #Fediverse #MastoDev

Option	Voters
Every follower	18 (78%)
Every peer actor you've encountered so far	5 (22%)

Tokyo Outsider (337ppm)

@tokyo_0@mas.to

Developer question: If you build a minimal ActivityPub server for development purposes, do you have to run it on a registered domain with an SSL certificate for it to be able to connect to anything else (like a big Mastodon instance)?

Or is running it on some kind of dynDNS or ngrok type service (so it has a static domain name) enough just to test things out?

(Boosts for reach gratefully received 🙏)

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

If you'd like to support the development of @fedify or @hollo, you can sponsor me on GitHub!

https://github.com/sponsors/dahlia

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

I have a question about signature handling in #ActivityPub relays. As I understand it, relays forward activities between instances that aren't directly connected. Let's say we have this flow: foo.com (source) → bar.com (relay) → baz.com (destination). The activity created by foo.com includes HTTP Signatures, but when bar.com forwards it to baz.com, wouldn't the original signature become invalid since the Host header needs to change? How do relay implementations handle this issue?

https://www.val.town/v/minhee/FedifyOnValTown

Fedify: an ActivityPub server framework

@fedify@hollo.social

Have you heard of Val Town? Val Town is a kind of code pastebin + serverless function.

Actually, #Fedify works just fine with Val Town. Here's a piece of ActivityPub software, implemented in about 170 lines of code, running on Val Town. Of course, it's built with Fedify!

Give it a follow @demo, and it will follow you back.

Curious to see how it was implemented? Check out the source code!

https://github.com/dahlia/fedify/blob/main/CONTRIBUTING.md#build

Fedify: an ActivityPub server framework

@fedify@hollo.social

We've added the build guide to the CONTRIBUTING.md docs in the #Fedify repository. We hope this is helpful for those who want to contribute to Fedify!

Fedify: an ActivityPub server framework

@fedify@hollo.social

What are your thoughts on Fedify's docs?

Option	Voters
Comprehensive and easy to understand	4 (67%)
Comprehensive but hard to understand	0 (0%)
Limited but easy to understand	1 (17%)
Limited and hard to understand	1 (17%)

Fedify: an ActivityPub server framework

@fedify@hollo.social

Visualize your server in the fediverse with the fedify node command and share it with us using the #FedifyNode hashtag!

ALT text details

The result of fedify node https://hollo.social/@fedify command. The NodeInfo document is visualized along with the favicon.

ALT text details

The result of fedify lookup venera.social. The NodeInfo document is visualized along with the favicon.

ALT text details

The result of fedify lookup misskey.io. The NodeInfo document is visualized along with the favicon.

ALT text details

The result of fedify lookup fosstodon.org. The NodeInfo document is visualized along with the favicon.

Fedify: an ActivityPub server framework

@fedify@hollo.social

The version 1.2.0 of #Fedify, an #ActivityPub server framework, released! The key changes include:

Added InboxContext.recipient property. It's useful for determining whether it is a shared inbox or a personal inbox, and whose personal inbox is invoked.
Added getNodeInfo() function, a NodeInfo client.
Added followedMessage property, which corresponds to _misskey_followedMessage, to Actor type in Activity Vocabulary API.
Log messages now can be traced using LogTape's implicit contexts, which means you can filter log messages by requestId (an HTTP request identifier) or messageId (a background task identifier).
Now you can choose an AMQP driver (which supports RabbitMQ) for the message queue in the fedify init command.
Added the fedify node subcommand, which fetches the given instance's NodeInfo document and visualizes it in neofetch-style.

For details, see the full changelog as well!

Fedify 1.2.0 is available at JSR and npm.

#Fediverse #Mastodon #SocialWeb #FediDev #SocialMedia #BuildInPublic

Newsmast

@newsmast@newsmast.social

It's been a busy year at Newsmast for The Newsmast Foundation team, but we've done a lot!

We've actually done too much to fit it into one post 👀

So, we broke out the video editing skills... hope you like it!

Fedify: an ActivityPub server framework

@fedify@hollo.social

Starting with the next release of #Fedify, v1.2.0, we will support traceable logs for easier debugging. Fedify's traceable logs are implemented using the implicit contexts introduced in LogTape 0.7.0, and most of the logs that Fedify records are given a requestId or messageId. This means that logs can be grouped into requests or background tasks for better analysis.

Want to try it out in advance? Try Fedify v1.2.0-dev.468+2e17cd69 (JSR & npm)!

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

In #Misskey, does the icon for the server information that I see in the remote note come from the favicon for that server?

jonny (good kind)

@jonny@neuromatch.social

Alright, #FetchAllReplies , backend edition is open as a PR against upstream masto: https://github.com/mastodon/mastodon/pull/32615

Please roast me for my code and help me get it into a state where we can make this default behavior for masto instances and remove one of the biggest contributors to the reply guy problem on the fedi <3

#MastoDev #FediDev

Steffo

@steffo@junimo.party

#FediDev: What’s the point of having separate signing keys for each actor if they all end up getting managed by the same instance?

Ideally (“even if no fedi client does it atm”), should users hold keys in their client, and sign the posts on the local machine before passing them to their server to forward to the recipients?

Or am I missing something?

Fedify: an ActivityPub server framework

@fedify@hollo.social

The version 1.1.0 of #Fedify, an #ActivityPub server framework, released! The key changes include:

Added uility functions for traversing remote collections. See also the Traversing remote collections section in the docs.
Added EmojiReact class to Activity Vocabulary API. [FEP-c0e0]
Added successor property to the Actor types in the Activity Vocabulary API.
Added DidService class to Activity Vocabulary API. [FEP-9091]
Added Export class to Activity Vocabulary API. [FEP-9091]
Added service property to the Actor types in the Activity Vocabulary API. [FEP-9091]
The default time window for verifying HTTP Signatures of incoming requests is now an hour (was a minute). This new default window is according to the ActivityPub and HTTP Signatures document.
In the fedify inbox command's web interface, the Raw Activity tab is added to show the raw JSON object of the received activity.

For details, see the full changelog as well!

https://github.com/cheeaun/phanpy/issues/598#issuecomment-2423923528

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

A summary of the two existing emoji reaction APIs: the Pleroma/Akkoma family and the Fedibird/kmyblue family.

ALT text details

There are two kinds of emoji reaction APIs: Pleroma/Akkoma family • POST /api/v1/statuses/:id/react/:emoji • POST /api/v1/statuses/:id/unreact/:emoji This can be detected by looking up pleroma_emoji_reactions and custom_emoji_reactions from pleroma.metadata.features responded by GET /api/v1/instance, e.g., seafoam.space/api/v1/instance. Fedibird/kmyblue family • PUT /api/v1/statuses/:id/emoji_reactions/:emoji • DELETE /api/v1/statuses/:id/emoji_reactions/:emoji This can be detected by looking up emoji_reaction from fedibird_capabilities responded by GET /api/v1/instance, e.g., fedibird.com/api/v1/instance, kmy.blue/api/v1/instance.

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

The value of the form at://… in the alsoKnownAs property of the actor generated by @bsky.brid.gy is not actually a valid URL? It cannot be represented as a URL object in Node.js or Deno.

:fediverse: #fediverse #infosec #fedidev #floss
https://clubsall.com

$Node.js: > new URL("at://did:plc:x7xdowahlhm5xulzqw4ehv6q") Uncaught TypeError: Invalid URL at new URL (node:internal/url:816:29) { code: 'ERR_INVALID_URL', input: 'at://did:plc:x7xdowahlhm5xulzqw4ehv6q' } Deno: > new URL("at://did:plc:x7xdowahlhm5xulzqw4ehv6q") Uncaught TypeError: Invalid URL: 'at://did:plc:x7xdowahlhm5xulzqw4ehv6q' at getSerialization (ext:deno_url/00_url.js:98:11) at new URL (ext:deno_url/00_url.js:405:27) at <anonymous>:1:22$

ALT text details

Node.js: > new URL("at://did:plc:x7xdowahlhm5xulzqw4ehv6q") Uncaught TypeError: Invalid URL at new URL (node:internal/url:816:29) { code: 'ERR_INVALID_URL', input: 'at://did:plc:x7xdowahlhm5xulzqw4ehv6q' } Deno: > new URL("at://did:plc:x7xdowahlhm5xulzqw4ehv6q") Uncaught TypeError: Invalid URL: 'at://did:plc:x7xdowahlhm5xulzqw4ehv6q' at getSerialization (ext:deno_url/00_url.js:98:11) at new URL (ext:deno_url/00_url.js:405:27) at <anonymous>:1:22

wakest ⁂

@liaizon@social.wake.st

#ClubsAll (a threadiverse/lemmy/mbin/piefed web frontend project) want to open source it and are looking for someone to do a code review/security analysis first... Are you into security and the fediverse *and* stuff being open source? Then respond here!

found via this post [https://lemmy.world/post/20828200] on Lemmy by ClubsAll dev @vinay_clubsall

Fedify: an ActivityPub server framework

@fedify@hollo.social

#Fedify now has an #AMQP driver! This means you can use #RabbitMQ as Fedify's message queue. To use it, first install the @fedify/amqp package, then set it up like below:

import { createFederation } from "@fedify/fedify";
import { AmqpMessageQueue } from "@fedify/amqp";
import { connect } from "amqplib";

const federation = createFederation({
  queue: new AmqpMessageQueue(await connect("amqp://localhost")),
  // ... other configurations
});

Oh, and we've also added results from AmqpMessageQueue to our benchmarks.

https://write.as/blog/write-as-x-sub-club

ALT text details

The results of the benchmarks for Fedify's outbox queue.

Jeff Sikes

@box464@mastodon.social

Write.as announces an integration with sub.club, a way to offer premium content in the fediverse to subscribers.

#Fediverse #FediDev

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

Even though I am a slow coder, it only took me about a month to create most of #Hollo's features in #Fedify. Having a framework makes a huge difference in productivity.

https://www.w3.org/TR/activitystreams-vocabulary/#dfn-summary

Mochikovski

@mochi@mochi.mochikov.ski

Hamabē is born! :bunhdhappy: :repost_pls:

I just released the very first version of Hamabē, and the official demo instance went live!

Hamabē is a successor of Audon, but a new platform speaking ActivityPub and independent of Mastodon API.

You can follow Hamabē accounts from AP platforms and can receive notifications when a space starts (if your platform supports Event activity)

Right now Hamabē only has voice chat (along with simple text chat) to cover Audon's use cases, but there's a plan to add text-based group chat later.

I also created Matrix Space for general discussion. Comments and suggestions are very appreciated!

The documentation is not ready yet. I'd write deployment guide soon.

If you wanna give it a shot, you can create your account here: https://try.hamabe.space

(Disclaimer) Hamabē is still in the very early stage of development. Expect a lot of bugs!

Thank you and happy chatting :bunhdheart:

#hamabe #audon #fedidev

ALT text details

The left panel and the right panel are different accounts of Hamabē on different servers. They are chatting in the same room.

ALT text details

The notifications from Hamabē federate to Mitra on the right panel.

ALT text details

The notifications from Hamabē federate to Mastodon on the right panel.

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

According to the Activity Vocabulary specification, the summary property should be HTML encoded, but #Mastodon is putting plain text in the summary property. #Hollo is putting #HTML in the summary, but should I change Hollo's behavior? :blobcatthink:

https://activitypub.software/TransFem-org/Kaiteki/kaiteki

ALT text details

The Activity Vocabulary specification says that the summary property is “a natural language summarization of the object encoded as HTML.”

Jeff Sikes

@box464@mastodon.social

Looks like around a month ago, the developer of Kaiteki, a flutter based fediverse client, closed shop. They left the source code available to anyone that might want to pick it up, however!

#FediDev #FediApp

Jeff Sikes

@box464@mastodon.social

Yay! Another music platform adding support for the fediverse. 🎶🎶

https://mastodon.moule.world/@MOULE/113248290568082105

#Fediverse #Music #FediDev

Grow Your Own Services 🌱

@homegrown@social.growyourown.services

If you're an advanced user with programming skills who is wanting to do custom stuff with Fediverse connections (or even wanting to create your own Fedi platform), you might want to check out the activitypub.rocks SocialHub forum:

:Fediverse: https://socialhub.activitypub.rocks

I'm not a software developer so I can't help with these topics, but enough people have asked that it seemed a good idea to give the forum a mention!

#ActivityPub #Fediverse #FediDev

Fedify: an ActivityPub server framework

@fedify@hollo.social

If you're considering creating your own implementation of #ActivityPub, consider #Fedify.

Implementing ActivityPub from scratch requires more than you might think. WebFinger, HTTP Signatures, Linked Data Signatures, Object Integrity Proofs, NodeInfo, queues for sending and receiving activities, followers collection synchronization, remote object lookups, interoperability with Mastodon, Akkoma, Misskey, Threads, and more…

Just use Fedify and feel free to create your own ActivityPub implementation!

https://fedify.dev/

洪民憙（ホン・ミンヒ）

@hongminhee@fedibird.com

独自のActivityPubの実装を作りたい方は、Fedifyを検討してみてください。

ActivityPubをゼロから実装するには、想像以上に多くの物を作る必要が有ります。WebFinger、HTTP Signatures、Linked Data Signatures、Object Integrity Proofs、NodeInfo、アクティビティの送受信のキュー、フォロワーコレクションのシンクロ、リモートオブジェクトの照会、MastodonやMisskey等との相互運用性の為の雑多な処理まで…Fedifyを使えば簡単に自分だけのActivityPubの実装を作る事が出来ます！

https://fedify.dev/

https://github.com/dahlia/fedify/issues/146

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

Adding vocabularies for FEP-9091 to #Fedify.

Fedify: an ActivityPub server framework

@fedify@hollo.social

Did you know that? The #Fedify CLI has a command called fedify lookup, which can easily look up ActivityStreams objects on servers with authorized fetch (a.k.a. secure mode) enabled by turning on the -a/--authorized-fetch flag.

Here's demo!

Hollo

@hollo@hollo.social

You can now see #emoji #reactions in #Hollo (but you can't leave emoji reactions yet). We've implemented the FEP-c0e0 spec and tested it on #Misskey, #Akkoma, and #Fedibird.

Fedify: an ActivityPub server framework

@fedify@hollo.social

Introducing Fedify: Build Your Own Fediverse App with Ease! 🚀

Are you excited about the #fediverse but find implementing #ActivityPub daunting? Meet #Fedify, a #TypeScript framework that simplifies building federated server apps. Whether you're creating the next Mastodon, Pixelfed, or something entirely new, Fedify has you covered.

What Fedify Offers:

🧩 Type-safe Activity Vocabulary objects
🔍 WebFinger client and server
🔐 HTTP Signatures, Linked Data Signatures, and Object Integrity Proofs
📨 Easy-to-use inbox listeners
ℹ️ NodeInfo protocol support
🛠 CLI tools for testing and debugging

Fedify abstracts away the complexities of ActivityPub, letting you focus on your app's unique features. It's designed to work seamlessly with popular web frameworks like Hono, Express, and Fresh.

Get Started Today!

Check out our step-by-step tutorial to create a microblog: https://fedify.dev/tutorial/microblog

Explore the discussions, contribute, or just star us on GitHub: https://github.com/dahlia/fedify

Join the Fedify community! Questions? Ideas? Find us on Matrix: #fedify:matrix.org.

Let's build a more diverse and interoperable fediverse together with Fedify!

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

I'm adding the #EmojiReact (FEP-c0e0) class to #Fedify… It will be coming in Fedify 1.1.0.

https://w3id.org/fep/c0e

#Fediverse #Mastodon #Podcast #TrueFans #FediDev

Newsmast

@newsmast@newsmast.social

Today is #InternationalPodcastDay so we thought we'd shout out https://truefans.fm - a podcast marketplace built on the Fediverse by @samsethi

It was really exciting seeing Sam's demo of True Fans at @fediforum a few weeks ago.

If you're looking for a podcasting alternative on the Fediverse, check it out!

jonny (good kind)

@jonny@neuromatch.social

Oh gr8, apparently being able to await the results of a batch of sidekiq jobs is an exclusive "sidekiq pro" feature.

So here's the deal: for #FetchAllReplies we need to set some kind of global fetch limit so a maliciously crafted thread tree doesn't keep us fetching forever. Currently it's implemented as a recursive fetch, but I want to move the "expansion" part where we gather the URIs of all the posts to fetch at a top level, and then just dispatch workers to fetch those posts in a flat queue with a global limit

Problem: with current masto impl, you have to already have a status to fetch its replies, so we need to await the results of prior fetch level before starting the next one. Does anyone know how to await sidekiq jobs? We already know the URIs of the posts that are being fetched, but I can't tell how to either a) await the redis job being popped from the queue or b) await a Status object with a matching uri being created. Im also not sure how I could c) use a callback to signal to the initiating worker that a status has been fetched.

Anyone know what the move here is? Im sure there must be some chained workers like this somewhere in masto, but all the examples I can find for sidekiq use the "pro" features.

PR here shows the current recursion I'm trying to flatten: https://github.com/NeuromatchAcademy/mastodon/pull/44

#MastoDev #FediDev

Fedify: an ActivityPub server framework

@fedify@hollo.social

Fedify, an ActivityPub framework, has finally released its first stable version, 1.0.0! Here are key changes:

Deprecation of the term handle

From this version, the term handle across Fedify will only be used to refer to fediverse handles (e.g., @hongminhee@fosstodon.org). An actor's internal unique ID (e.g., b379dbdc-3b4f-4ef4-88c2-fc25632d1c22) is referred to as an identifier, and the WebFinger name (e.g., hongminhee) is referred to as a username.

The term handle in the API will be maintained for a while for backward compatibility, but deprecation warnings will be logged, and it is planned to be removed in the future.

For more details, please refer to the related documentation.

Linked Data Signatures

Linked Data Signatures is an outdated standard, but it's still relied upon by major fediverse implementations such as Mastodon.

In addition to HTTP Signatures and Object Integrity Proofs, Fedify now supports Linked Data Signatures from this version, thus supporting all types of signature methods used in the fediverse. This makes Fedify an ActivityPub implementation with the best interoperability.

However, Fedify users don't need to do anything special to use Linked Data Signatures. If an incoming activity has Linked Data Signatures, it automatically verifies the signature, and all outgoing activities will have signatures in three formats: HTTP Signatures, Linked Data Signatures, and Object Integrity Proofs.

For more details, please refer to the related documentation.

Activity forwarding

From this version, you can forward activities received in the inbox to other actors using the InboxContext.forwardActivity() method.

At first glance, you might think that you could just resend an activity received in the inbox using the Context.sendActivity() method. However, if you do this, the original signature is removed before the activity is delivered to the inbox, and when sending it, the signature of the forwarding actor is attached instead, causing the receiving side of the forwarded activity to not trust it.

On the other hand, when using the InboxContext.forwardActivity() method, the activity is forwarded with the original signature preserved, avoiding this problem. (Of course, the original activity itself must be signed with Linked Data Signatures or Object Integrity Proofs.)

For more details, please refer to the related documentation.

Sending `Delete(Application)` on `fedify inbox` termination

From this version, fedify inbox will send a Delete(Application) activity to all peer servers it encountered when terminated. This is typically an activity sent when deleting an account, which will help prevent residual data related to temporary actors from remaining on other servers.

PostgreSQL drivers

The @fedify/postgres package, which implements PostgreSQL drivers for the KvStore and MessageQueue interfaces, has been released alongside this version.

The PostgreSQL driver is a backend that can be sufficiently used in production, especially recommended for projects already using PostgreSQL.

Additionally, an option to select the PostgreSQL driver has been added to the fedify init command.

Celebrating Fedify 1.0.0

With the release of version 1.0.0, Fedify will now maintain API backward compatibility as much as possible. (Of course, in the long term, there may be a 2.0.0 that breaks backward compatibility.) This should be good news for those who have been hesitant to use Fedify because there hasn't been a stable version until now!

So, hoping that more services will support ActivityPub in the future, I conclude this post!

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

Looks like #Fedify v1.0.0 will be released this week! Is there anything you'd like to see added or fixed before then?

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

I'm polishing the #docs and filling in the gaps before releasing #Fedify v1.0. Is there something else you'd like to see in the @fedify docs?

https://unstable.fedify.dev/manual/mq#parallel-message-processing

Fedify: an ActivityPub server framework

@fedify@hollo.social

The next version of #Fedify, v1.0, adds ParallelMessageQueue, which makes it easy to parallelize sending and receiving activities without increasing the number of processes or nodes.

It's available for preview in v1.0.0-dev.408+f4e245b4 (JSR & npm).

#FediForum #Mastodon #Fediverse #FediDev #FediAdmin #Technology #Demo #TechDemo

Newsmast

@newsmast@newsmast.social

We were very excited to demo Channel. org & Patchwork at the fourth edition of FediForum - the virtual unconference moving the decentralised social web forwards.

You can see the video here: https://spectra.video/w/42kMTHaxxqYwD6nYYeK1MZ or on YouTube (we'll add a link further down the thread).

Keep reading to see a summary of our time at @fediforum from @FreddieJ 🧵 👇

Fedify: an ActivityPub server framework

@fedify@hollo.social

Q: Which does your #ActivityPub implementation implement, HTTP Signatures, Linked Data Signatures, or Object Integrity Proofs?

Fedify: Y·E·S!

#Fedify #fedidev #ActivityPub
QT: https://hollo.social/@fedify/019208ce-cf81-717e-9239-6757a5494510 [参照]

洪民憙（ホン・ミンヒ）

@hongminhee@fedibird.com

Fedifyの次のバージョンであるv1.0.0がリリースされれば、APIは安定化される予定です。APIが安定化する前に入れて欲しい機能は何か有りますか？

Fedify: an ActivityPub server framework

@fedify@hollo.social

Once the next version of #Fedify, v1.0.0, is released, the API will be stabilized. Are there any features you'd like to see before the API is stabilized?

Fedify: an ActivityPub server framework

@fedify@hollo.social

Once the next version of #Fedify, v1.0.0, is released, the API will be stabilized. Are there any features you'd like to see before the API is stabilized?

https://github.com/NeuromatchAcademy/mastodon/pull/44

jonny (good kind)

@jonny@neuromatch.social

alright, after like a year of halfheartedly trying on and off, #FetchAllReplies is pretty much finished - the problem of not being able to see all replies to a post is one of the largest complaints that people have with mastodon in particular but also the fedi in general. It is an especially potent problem for smaller servers, making them feel lonely, and making the whole fedi seem quiet. It is also a large contributor to the 'reply guy' problem where a moderately popular post will get the same replies over and over again and people won't even know they're doing it.

This patch recursively fetches replies using activitypub collections. it does it respectfully, only when someone is explicitly looking at a post (rather than fetching all replies for everything all the time) with some debounce, and spaces out the recursive calls to the other servers in deep threads.

the only thing left is to make the posts get inserted into the web client as they are received, currently you need to refresh to see them.

trying it locally now and it is a game changer.

i'm not "good at ruby" so if you ever wanna see this upstream, kindly spare a code review?

#FediDev #MastoDev #UnFuckTheFedi #PubSubIsCoolButPresentsPrettySeriousUsabilityProblems #JustSmallInstanceThings

silverpill

@silverpill@mitra.social

I'm working on a Rust library for building ActivityPub apps:

https://codeberg.org/silverpill/mitra/src/branch/main/apx_sdk

This code was originally a part of Mitra, but over time I moved re-usable functions into independent packages and then started using them in other projects, Activity Connect and fep-ae97-client. Compared to activitypub-federation-rust, it is a low-level library with fewer dependencies, suitable for both servers and clients. The key feature is support for nomadic identity.

Currently there's no documentation and API is not well designed, but I will be improving it. The license is AGPL-3.0

#fedidev #fep_ef61

:neobread: Bolet :neobread:

@javascript@app.wafrn.net

Wafrn mobile app now can like, rewoot, follow, and react with emojis

It's only a few more improvements till it's completed and it's going to be great
#fedidev #wafrn-dev

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org · Reply to 洪民憙 (Hong Minhee)'s post

One of the benefits of #Fedify is that you don't have to worry about whether a property of an Activity Vocabulary object has a URL or embeds an actual object. If you need an object, you can call the `getObject()` method (which will fetch a remote object if necessary). If you need a URI, you can access the `objectId` property.

https://fedify.dev/manual/vocab#object-ids-and-remote-objects

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

Quick question: would it be okay to embed a collection object in the `as:replies` property of `as:Note` & `as:Article` objects instead of putting the URL to the collection in the `as:replies` property? In theory, it would be okay, but would the actual implementations handle it well?

https://github.com/neet/masto.js

Jeff Sikes

@box464@mastodon.social

Phanpy and Elk are both great web clients for fediverse platforms that support the mastodon api.

Did you know that both utilize a third party mastodon api library written in JavaScript?

Masto.js makes those applications possible! Give some props to the creator and maintainer, @neet

#FediDev #Mastodon

Jeff Sikes

@box464@mastodon.social

#Fediforum has a Saturday schedule, and it's starting in less than two hours. You can still register to attend, with some (almost) free tickets available at $1.99 if the regular rate is too high - a bargain for attending a single day of the event.

My favorite part is the demos - you get to see the people behind the sites and apps you use (or will be using), demoing their latest fediverse related projects!

https://fediforum.org/

#FediForum #Fediverse #FediDev

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

Compared to @hollo, @fedify seems to have less people contributing patches. Would this imply that #Fedify's codebase is harder to read or to modify?

Fedify: an ActivityPub server framework

@fedify@hollo.social

The next version of #Fedify will support #LDSignatures (#RsaSignature2017), which means that Fedify will be able to verify activities forwarded by #Mastodon from other servers.

In addition, activities sent with the Context.sendActivity() method will have Linked Data Signatures attached in addition to HTTP Signatures if any RSA-PKCS#1-v1.5 key pairs are present.

We were not motivated by implementing Linked Data Signatures, which is already an outdated standard, but we hope this change will lead to better compatibility and interoperability of Fedify apps!

#SocialMedia #Fediverse #Mastodon #MastoDev #FediDev #FediAdmin #MastoAdmin

Newsmast

@newsmast@newsmast.social

Show time: Patchwork & Channel. org debut 💫

In a couple of hours we’ll be back at #FediForum and we’re excited to be debuting our new projects on Saturday, Channel. org and Patchwork - opening for early access soon.

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

Working on @fedify's docs about #LDSignatures… I hope someday #Fedify drop the support for Linked Data Signatures… 😇

ALT text details

The combination of HTTP Signatures and Linked Data Signatures is the most widely supported way to sign activities in the fediverse, as of September 2024. Despite Linked Data Signatures is outdated and not recommended for new implementations, it is still widely used in the fediverse due to Mastodon and other major implementations' reliance on it. However, for new implementations, you should consider using both Object Integrity Proofs and Linked Data Signatures for maximum compatibility and future-proofing.

Fedify: an ActivityPub server framework

@fedify@hollo.social

The next #Fedify release will finally be 1.0.0. Stay tuned!

Fedify: an ActivityPub server framework

@fedify@hollo.social

#Fedify has a side effect that when you call the getter method of an Activity Vocabulary object, the property that was internally a URI is populated with the actual ActivityStreams object. Today, someone at Ghost gave us a cool term for this: #hydration.

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

Does #Misskey also attach #LDSignatures to activities? If so, what types of activities does it attach LD Signatures to?

https://fedify.dev/cli#fedify-inbox-ephemeral-inbox-server

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

The `fedify inbox` command, which is shipped with @fedify/cli, is a tool that creates an ephemeral #ActivityPub server so that you can debug and test the activities you send.

Here's a demo of it.

ALT text details

A demo video of fedify inbox command.

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

I received a request from @ghost today to add #LDSignatures to @fedify for compatibility with #Mastodon, as Mastodon does not plan to implement Object Integrity Proofs (FEP-8b32) for the near future. 😩

However, Mastodon's implementation of LD Signatures does not even use valid JSON-LD properties (despite the name), so I'm not sure how to make it compatible with Mastodon since #Fedify does JSON-LD processing. 🤔

ALT text details

The JSON-LD representation of a Create(Note) activity containing LD Signatures produced by Mastodon and its expanded form. The “signature” property and its child properties are not properly namespaced.

Fedify: an ActivityPub server framework

@fedify@hollo.social

Fedify, an #ActivityPub server framework, has released v0.15.0! The key changes include:

There's a new tutorial for creating a microblog.
Actors, collections, and object dispatchers can now have URIs that do not include a WebFinger username, meaning actors can now change their fediverse handles.
Article, ChatMessage, Note, and Question classes now have a quoteUrl property. This property corresponds to three properties at once: as:quoteUrl, misskey:_misskey_quote, and fedibird:quoteUri.
Changed the element type of the liked collection from Like to Object | URL.
Added Context.lookupObject() method.
The default document loaders can now recognize ActivityStream objects from the Link header or the <link>/<a> tag in HTML.
Added -r/--raw option to the fedify lookup command.

It is now available in JSR and npm.

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

I have a question about the `liked` collection in the #ActivityPub specification. According to section 5.5, the liked collection is “a list of every object from all of the actor's `Like` activities”, whereas the side note in section 5.7 says it is “a collection of `Like` activities performed by the actor”. What is the element type of the liked collection, `Object` or `Like`?

• Section 5.5: https://www.w3.org/TR/activitypub/#liked
• Section 5.7: https://www.w3.org/TR/activitypub/#likes

https://flipboard.com/@wedistribute/across-the-fediverse-i6a1ubvjz/-/a-npYBPFU6ToK2o1DCWJG8ng%3Aa%3A4015545021-%2F0

Jeff Sikes

@box464@mastodon.social

I'm glad that @fediforum added a weekend date. It's tough to get away during the week for me. FYI, the demos are usually first thing in the mornings and are a can't miss - worth the price for those alone IMO.

Check WeDistribute for live coverage of the event!

#Fediverse #FediDev #FediForum

Jeff Sikes

@box464@mastodon.social

As Firefish maintenance begins to wind down, IceShrimp offers a migration guide.

https://iceshrimp.dev/iceshrimp/iceshrimp/src/branch/dev/docs/migrate.md

#Firefish #IceShrimp #FediDev #Fediverse

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to 洪民憙 (Hong Minhee)'s post

In the next version of #Fedify, it will allow you to decouple actor URIs from WebFinger usernames with the mapHandle() method. For example, you can use UUIDs for actor URIs but let users use their own username of choice for their fediverse handle.

You can preview it in v0.15.0-dev.382+a8a9b73b: JSR & npm.

https://w3id.org/fep/8b32

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

I wish #Mastodon would just implement FEP-8b32 instead of the LD Signatures which is obsolete.

#ActivityPub #LDSignatures #fedidev

marius

@mariusor@metalhead.club

I often struggle with working on non-trivial, long standing projects because when I sit down to do the work after some hiatus, I can't seem to find the pain points I wanted to fix quickly enough.

It feels like trying to get a bandaid off when you can't find an edge where it comes unstuck easily enough.

The largest piece of bandaid that I wasn't able to get unstuck from the ActivityPub adjacent work is getting the HTTP-signatures working well with the rest of the fediverse (by which I mean Mastodon).

Today I might have got the corner of another little bit of bandaid unstuck which hopefully will help in the long run.

#ActivityPub #fedidev #GoActivityPub

Chee Aun 🤔

@cheeaun@mastodon.social

👀 Very interesting post visibility comparison table by Stefano, on this code review for adding Akkoma/Pleroma's Local-only posting on Phanpy https://github.com/cheeaun/phanpy/pull/657#discussion_r1745903955

#FediDev #MastoDev

ALT text details

Table comparing visibility options on Akkoma and Pleroma federated software, detailing who can see posts in different timelines (Direct messages, Home timeline, Public profile, Local timeline, Federated timeline) using various emojis to represent visibility levels.

Fedify: an ActivityPub server framework

@fedify@hollo.social

We just finished drafting a new tutorial for #Fedify! This tutorial will walk you through the steps of creating your own federated #microblog. It's pretty long, though.

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

I finally finished the first draft of the new #Fedify tutorial, but it's still in Korean. Now I just need to polish it up and translate it into English.

Fedify: an ActivityPub server framework

@fedify@hollo.social

Did you know? #Fedify offers the markdown-it plugins for parsing #Mastodon-style mentions and hashtags syntax:

@fedify/markdown-it-mention: JSR & npm
@fedify/markdown-it-hashtag: JSR & npm

Check it out!

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

I wish there was a more fancy canonical permalink for each #FEP document.

https://mastodon.social/@activitypugtest

Jeff Sikes

@box464@mastodon.social

@index is out with another amusing blog post about their fediverse journey. But the most important thing we learned is that this account exists.

#FediDev #ActivityPub #ActivityPug

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

Dear developers of the #fediverse, has anyone ever encountered a case where a personal inbox in #Threads responds with a 404 Not Found for a POST request?

https://app.warp.dev/block/vKJGDbgWHBEAlAKBl0jlPR

https://video.everythingbagel.me/w/rXvUZeaU1b2rnaXGVKzsPe

Jeff Sikes

@box464@mastodon.social

@subclub is a new way to add a paid subscriber link to your fediverse profile, allowing you to create subscriber only content! You get a really nice "Subscribe" button on the Mammoth and Ice Cubes app.

If you are a fediverse app developer and interested in adding this to your app, reach out to subclub directly and they can get your started!

Here's a walk through of how to get it setup.

#FediDev #MastodonApp #MastoDev #Fediverse #Mastodon

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

Suddenly, I'm reminded of a service called Yahoo! Pipes from about 15 years ago. If anyone remembers, #Pipes handled #RSS as its primitive, and now I'd like to see something like Pipes handle #ActivityPub as its primitive.

https://en.wikipedia.org/wiki/Yahoo!_Pipes

#fedidev #idea

Fedify: an ActivityPub server framework

@fedify@hollo.social

We've released v0.14.0 of #Fedify, the #ActivityPub server framework, with the following key changes:

It is now possible to set the recipient of the sendActivity() method to "followers" in just the Context instead of the RequestContext.
Improved performance of the Object.toJsonLd() method by about 3,000 times.
Added source property to Object.
Added aliases property to Actor, corresponding to ActivityPub's alsoKnownAs property.
fedify init command now adds default compilerOptions settings to tsconfig.json and deno.json.

Fedify v0.14.0 is available from JSR and npm. See also the full changelog for details.

Happy #fedidev!

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to John Spurlock's post

We've added the Inspecting ActivityPub objects section to the #Fedify docs, introducing BrowserPub and the fedify lookup command!

https://unstable.fedify.dev/manual/test#inspecting-activitypub-objects

#ActivityPub #BrowserPub #fedidev

ALT text details

Inspecting ActivityPub objects BrowserPub BrowserPub is a browser for debugging ActivityPub and the fediverse. You can punch in any ActivityPub discoverable web URL or fediverse handle, and it will discover and display the underlying ActivityPub. For example: • hollo.social/@fedify • @hongminhee@fosstodon.org If you want to know further details about BrowserPub, read the creator's Mastodon thread. fedify lookup command Fedify provides a CLI toolchain for testing and debugging. The fedify lookup command is a simple tool for looking up an ActivityPub object by its URL or fediverse handle.

Fedify: an ActivityPub server framework

@fedify@hollo.social

Do you know that? Some of the properties in Activity Vocabulary have been renamed in #Fedify's JavaScript APIs. Below are some examples:

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

Even I have no idea how much #Fedify's API will change, so I don't know when I'll release Fedify 1.0.0. 🤦

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

Is there any standardized #spec for #Misskey-style quotes?

Hollo

@hollo@hollo.social

Hollo를 소개합니다!

Hollo는 개인을 위한 연합형 마이크로블로그 소프트웨어입니다. Fedify와 Bun으로 만들어졌으며, #ActivityPub 프로토콜을 통해 다른 인스턴스 및 서비스와 교류할 수 있습니다.

Hollo의 특징은 한 사용자를 위해 설계된 전용 인스턴스라는 점입니다. 이를 통해 사용자는 자신만의 공간을 가지면서도 #Mastodon, #Misskey 및 기타 ActivityPub 지원 서비스의 사용자들과 소통할 수 있습니다.

독자적인 웹 인터페이스는 없지만, Mastodon API와 호환되어 기존의 많은 Mastodon 클라이언트 앱을 사용하여 Hollo에 접근할 수 있습니다. 이로 인해 익숙한 인터페이스로 Hollo를 이용할 수 있습니다.

주요 기능으로는 게시물 작성·편집·삭제, 답글, 미디어 첨부, 투표, 좋아요, 북마크, 고정 등이 있습니다. 또한 프로필 편집, 팔로우/팔로워 관리, 리스트 생성 등도 가능합니다. 더불어 Markdown을 지원하여 게시물이나 프로필의 서식 설정을 쉽게 할 수 있습니다.

Hollo는 현재 개발 초기 단계에 있으며, 지속적으로 기능 추가와 개선이 이루어지고 있습니다. Bun을 사용함으로써 빠른 성능과 효율적인 개발이 이뤄지고 있답니다. 오픈 소스 프로젝트로 GitHub에 공개되어 있으며, 커뮤니티의 기여를 환영합니다.

개인 블로그와 소셜 미디어의 장점을 결합한 Hollo는 프라이버시를 중시하면서도 더 넓은 커뮤니티와의 연결을 원하는 사람들에게 적합한 플랫폼으로 거듭나고 있습니다.

https://github.com/fedidevkr/logo

#Hollo #Markdown #Bun #Fedify #fedidev

@hongminhee@fosstodon.org · Reply to 洪民憙 (Hong Minhee)'s post

Also, a new logo for #FediDev KR has been designed!

ALT text details

The new logo for FediDev KR with transparent background

ALT text details

A variant of the new logo for FediDev KR with purple background

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org · Reply to 洪民憙 (Hong Minhee)'s post

#FediDev KR has decided to organize a sprint meetup later this month in Gangnam, Seoul (yes, the same Gangnam from Gangnam Style)!

Fedify: an ActivityPub server framework

@fedify@hollo.social

Security alert for Fedify users

We've patched a vulnerability in the getActorHandle() function. Versions prior to 0.13.1 and 0.12.3 are affected.

Upgrade immediately:

npm: 0.13.1 & 0.12.3
JSR: 0.13.1 & 0.12.3

#Fedify #securityupdate #fediverse #fedidev #ActivityPub

Fedify: an ActivityPub server framework

@fedify@hollo.social

In the next version (v0.14.0) of #Fedify, the performance of the Object.toJsonLd() method will be dramatically (~3k ×) faster. This is expected to improve the overall performance of Fedify apps!

#fedidev #JSONLD #ActivityPub

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

I feel that the current abstraction level of #Fedify is not high enough which makes the tutorial lengthy, so I'm considering adding a higher-level API. One way would be to add a façade to the @fedify/fedify package, and another way would be to create a sort of metaframework as a separate package (e.g., @fedify/start?). Which way would be better?

Option	Voters
Façade	0 (0%)
Metaframework	0 (0%)

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

I'm writing a #Fedify tutorial, and I keep saying things like “you don't need to know what Ed25519 is” and “you don't need to know what JWK is for this tutorial.” Would this be okay?

#JSONLD #fedidev #ActivityPub

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

The JSON-LD processor ended up being #Fedify's bottleneck, so I'm in the process of fixing Fedify to generate JSON-LD without the proper JSON-LD processor.

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

Does anyone know of any docs or specs for the #EmojiReact activity type that #Misskey and #Pleroma use?

#Fediverse #SocialMedia #FediDev #FediAdmin #MastoDev #MastoAdmin #Technology

Newsmast

@newsmast@newsmast.social

"We want to bring organisations and content creators into the Fediverse, step by step."

Our Foundation co-founder has just published an interesting piece on how we're working to help organisations and content creators find their way to the Fediverse!

For more information on what we plan to do as a charity and how Patchwork, a new service we'll be launching soon, can help 👇
https://www.blog-pat.ch/enter-the-fediverse/

Fedify: an ActivityPub server framework

@fedify@hollo.social

Fedify, the #ActivityPub server framework, has released v0.13.0. Key changes include:

Added fedify tunnel command to expose the local server to the public internet.
Added Express and Nitro integration templates to the fedify init command.
Added option to skip HTTP Signatures validation for easier testing.
Added Question.closed property.
Added Question.voters property.
Removed several deprecated APIs.

#Fedify v0.13.0 is available now from JSR and npm.

https://github.com/dahlia/fedify/releases/tag/0.13.0

kopper [according to whom?]

@kopper@brain.d.on-t.work

question: is anyone federating thumbhashes of media yet? is there an existing extension i can adopt or should i just come up with my own?

i know mastodon federates blurhashes. i'm specifically asking about thumbhashes (evanw.github.io/thumbhash/) instead.

#activityPub #fediDev #fediDevs

Fedify: an ActivityPub server framework

@fedify@hollo.social

What other web frameworks would you like to see #Fedify integrate with more?

https://github.com/dahlia/fedify-express

Option	Voters
Koa	4 (16%)
Fastify	5 (20%)
Oak	3 (12%)
Elysia	3 (12%)
Next.js	6 (24%)
Nuxt.js	4 (16%)

Fedify: an ActivityPub server framework

@fedify@hollo.social

Introducing @fedify/express, a package that integrates Express, a popular web framework in Node.js, with Fedify. You can install it with the following command:

npm add @fedify/express

This package provides a middleware called integrateFederation() that allows you to integrate #Fedify with #Express:

import express from "express";
import { integrateFederation } from "@fedify/express";
import { federation } from "./federation";  // Your `Federation` instance

export const app = express();

app.set("trust proxy", true);

app.use(integrateFederation(federation, (req) => "context data goes here"));

#fedidev #ExpressJS

infinite love ⴳ

@trwnh@mastodon.social

i wonder how many #fedidev people realize that building a fedi viewer is on the scale of complexity of building a web browser

wakest ⁂

@liaizon@social.wake.st

This is a milestone worth celebrating! :fediverse:
In development as we speak, @forgejo can now federate comments (and tons of other stuff) from issues in repos!!!

The first screenshot is @algernon (a Forgejo account able to be tagged in this post!) commenting on the issue: https://shoes.forgejo.madhouse-project.org/algernon/federation-test/issues/4 as seen in @phanpy while logged into my Mastodon account!
#fediverse #ActivityPub #FediDev #federation #forgejo #git #GitFederation

ALT text details

a screenshot of a Fogejo account with comments as seen through a Mastodon account logged into Phanpy

ALT text details

a screenshot of a Fogejo issue that contains comments that are viewed in the previous screenshot

Jeff Sikes

@box464@mastodon.social

@mastometrics is a unique way to look at statistics about your own account - for free. It's even connected directly from your profile in the @IceCubesApp app.

But all that data and storage costs money! Please consider contributing to keep this service going - and if the goal is reached, open sourced to make it self-hostable.

https://ko-fi.com/robertvh

#FediFund #OpenSource #Mastodon #MastoDev #FediDev

Newsmast

@newsmast@newsmast.social

We’re committed to helping people find their place in the Fediverse and wider Social Web.

We’ve helped hundreds of people, across multiple platforms, understand the idea by stripping down the tech and reimagining it.

We’ve put that learning in a video. It won’t answer all the questions, but it’s a strong starting point to help explain the Fediverse to outsiders.

Please share it to help educate others.

https://youtu.be/upEHFtO9vrI

#Fediverse #FediTips #MastoDev #FediDev #MastoAdmin #FediAdmin

ilja :pumpkin_owo:

@ilja@ilja.space

this is my first FEP; there's a bunch of todo's left, but i think it already gives a good view of what it will become https://codeberg.org/ilja/fep/src/branch/fep-c16b_formatting_mfm_functions/fep/c16b/fep-c16b.md

#fedidev

Abelio

@abelio@mastodon.social

#fediverse #fedidev #activitypub #writers #photography #arts

Fedify: an ActivityPub server framework

@fedify@hollo.social

If you read a #Fedify #tutorial, what #ActivityPub software would you like to see as an #example in the tutorial?

https://github.com/dahlia/fedify/issues/109

Option	Voters
Microblog (like Mastodon)	21 (32%)
Long-form blog (like WordPress)	10 (15%)
Photo blog (like Pixelfed)	7 (11%)
Forum (like NodeBB)	6 (9%)
Link aggregator (like Lemmy)	9 (14%)
Much simpler one!	13 (20%)

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

A good issue to contribute to #Fedify for the first time. Anybody interested?

https://github.com/dahlia/fedify/commit/4c3015145a10804a5ec8debdc8bb394fe6ed819d

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

I finally turned the Federation class into an interface now!

#SocialMedia #FediDev #FediAdmin #MastoDev #MastoAdmin #Tech #Nonprofit #OSS #BuildInPublic

Newsmast

@newsmast@newsmast.social

"Our Foundation mission is “knowledge for all for good”. Using social media to share knowledge for the benefit of society."

Our co-founder, @michael , is discussing why The Newsmast Foundation is building new technology to benefit organisations and server admins on the Social Web.

Read it here: https://www.blog-pat.ch/content-technology-community/

Fedify: an ActivityPub server framework

@fedify@hollo.social

#Fedify, an #ActivityPub server framework, has released v0.12.0. It's a minor release in about a month, so there's quite a few changes:

The fedify command can now also be installed with npm. It can be installed with npm i -g @fedify/cli in Node.js and bun i -g @fedify/cli in Bun.
Added the fedify init command to help set up a new Fedify project.
Incoming activities are now also queued and inbox listeners are now processed in the background worker. If you were already queuing outgoing activities, this will just take effect with a simple upgrade to v0.12.0.
Retry policy for failed tasks processed in the background worker is now customizable and defaults to backoff with decorrelated jitter.
Added ChatMessage, Move, Read, Travel, View, TentativeAccept, and TentativeReject classes. (Thanks to @moreal!)
Improved multitenancy (virtual hosting) support: You can now easily determine the host of the current request via the hostname, host, and origin properties of the Context.
When validating HTTP Signatures and Object Integrity Proofs, once fetched public keys are now cached.

It's available on JSR and npm now, and you can upgrade it using the deno add command on Deno:

deno add @fedify/fedify@^0.12.0

Or using the bun add command on Bun:

bun add @fedify/fedify@^0.12.0

Or using the npm add command on Bun:

npm add @fedify/fedify@^0.12.0

Fedify: an ActivityPub server framework

@fedify@hollo.social

Since #Fedify v0.12.0, when verifying HTTP Signatures or Object Integrity Proofs, it will cache the public keys once fetched. It is okay even if a cached key becomes outdated because a verification failure due to a cached key will invalidate the cache and force a verification retry.

This feature is available for preview in v0.12.0-dev.307+235629d5 (JSR or npm).

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

Working on the `fedify init` command, the project setup wizard for #Fedify…

#fediverse #fedidev #fediadmin #mastodon #developer #technology #tech #OSS #BuildInPublic

ALT text details

A demo of the `fedify init` command. The JavaScript runtime choices are Deno, Node.js, and Bun, of which Deno is selected. The web framework choices are Bare-bones, Astro, Fresh, and Hono, with Hono selected. The key-value store options are No cache, Redis, and Deno KV, with Deno KV selected. The message queue options are No background jobs, Redis, Deno KV, and Deno KV is selected. Finally, an Hono project integrated with Fedify is created and the server is started by running the `deno task dev` command.

Newsmast

@newsmast@newsmast.social

"Our aim is to offer organisations and server admins an easy-to-use console where extra features can easily be added to their Mastodon server."

If you liked our update on Patchwork from @FreddieJ yesterday, we have good news!

Newsmast Foundation co-founder @michael has just shared a look behind the scenes at Patchwork production ready for @fediforum in September.

Check it out: https://www.blog-pat.ch/patchwork-progress/

Jeff Sikes

@box464@mastodon.social

Just read an email newsletter from @newsmast about their upcoming Patchwork platform. It’s a plugin system to extend existing fediverse platforms.

One of their upcoming plugins will be local only posts. It’s a nice feature I used on Firefish, allowing nonfederated community discussions. Looking forward to it!

https://newsmast.social/@newsmast/112807985173916786

#Fediverse #FediNews #ActivityPub #FediDev

Newsmast

@newsmast@newsmast.social

This week we want to talk to you about Patchwork, an upcoming project, using technology we developed for Newsmast to make new and existing spaces on the social web more safe, more connected and more fun!

Here’s an update from our Foundation Ambassador @FreddieJ 👇

#SocialMedia #Fediverse #FediDev #FediAdmin #Technology #Tech

Newsmast

@newsmast@newsmast.social

It’s been a week since the UK General Election. As one of the UK’s leading Fediverse projects, we thought this would be a good time to look into the new government's digital policy and what it could mean for Fedi.

You can read the full blog by @FreddieJ here: https://www.newsmastfoundation.org/our-blog/impact-of-uk-election-result/

Or check out the thread below 👇

#Fediverse #government #UK #politics #technology #datapolicy #FediDev

Fedify: an ActivityPub server framework

@fedify@hollo.social

#Fedify offers robust logging capabilities through integration with LogTape. This feature allows you to easily debug and monitor your Fedify app!

To enable #logging, simply install the @logtape/logtape package and configure it in your app's entry point:

import { configure, getConsoleSink } from "@logtape/logtape";

await configure({
  sinks: { console: getConsoleSink() },
  filters: {},
  loggers: [
    { category: "your-app", sinks: ["console"], level: "debug" },
    { category: "fedify",   sinks: ["console"], level: "info" },
  ],
});

Fedify uses hierarchical categories for fine-grained control over log output. Key categories include ["fedify", "federation", "http"] for HTTP requests/responses and ["fedify", "federation", "inbox"]/["fedify", "federation", "outbox"] for incoming/outgoing activities. (There are more categories.)

With #LogTape integration, you gain valuable insights into your Fedify app's behavior, making troubleshooting and optimization much more straightforward!

https://fedify.dev/manual/log

#Fedify #fedidev #opensource

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

I want to create good first issues for @fedify, but I don't have a good idea of appropriate tasks for first-time contributors. Any ideas?

Fedify: an ActivityPub server framework

@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post

Ready to simplify your #fedidev? Check out #Fedify!

Join us in building a more connected and decentralized web! 🌐 #ActivityPub

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

In the next version of #Fedify, the #RetryPolicy type is introduced to let you fully customize the retry policy of the task queue for incoming and outgoing activities. Of course, you can also simply adjust the parameters of the built-in exponential backoff + decorrelated jitter policy.

https://hollo.social/@fedify/0190687b-1a09-728b-8a0d-bcbd4dca54cd

ALT text details

outboxRetryPolicy This API is available since Fedify 0.12.0. The retry policy for sending activities to recipients' inboxes. By default, this uses an exponential backoff strategy with a maximum of 10 attempts and a maximum delay of 12 hours. You can fully customize the retry policy by providing a custom function that satisfies the RetryPolicy type. Or you can adjust the parameters of the createExponentialBackoffRetryPolicy() function, which is a default implementation of the retry policy.

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

Basic implementation of the inbox queue is complete and documentation is being worked on.

https://github.com/dahlia/fedify/issues/66#issuecomment-2198967566

ALT text details

Making inbox listeners non-blocking This API is available since Fedify 0.12.0. Usually, processes inside an inbox listener should be non-blocking because they may involve long-running tasks. Fortunately, you can easily turn inbox listeners into non-blocking by providing a queue option to createFederation() function. If it is not present, incoming activities are processed immediately and block the response to the sender until the processing is done. While the queue option is not mandatory, it is highly recommended to use it in production environments to prevent the server from being overwhelmed by incoming activities. Note: Activities with invalid signatures/proofs are silently ignored and not queued.

Fedify: an ActivityPub server framework

@fedify@hollo.social

In the next version of #Fedify, the Context.hostname, Context.host, and Context.origin properties will be added for better multitenancy/virtual hosting support.

#Fedify #fedidev #ActivityPub

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org · Reply to 洪民憙 (Hong Minhee)'s post

When there is no queue, if the process fails, the inbox can just respond with a 500 server error and the sender will resend it.

But with a queue, by the time the inbox responds, it doesn't know if the process will fail because it hasn't run yet. So the sender won't retry whether it fails or not.

So, should it have its own retry logic when there is a queue?

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

I'm adding a queue for incoming activities in #Fedify, and I have a concern. If an error occurs while processing an activity, should it retry?

https://hollo.social/@fedify/0190687b-1a09-728b-8a0d-bcbd4dca54cd

https://github.com/dahlia/fedify/issues/70

Fedify: an ActivityPub server framework

@fedify@hollo.social

#Fedify has always been queuing outgoing activities, but not incoming activities. Thanks to @ghost's sponsorship, we are now implementing queues for incoming activities!

#FediDev #Fediverse #Mastodon #MastoDev

Tokyo Outsider (337ppm)

@tokyo_0@mas.to

#ActivityPub, #FediDev and #security question: If instances generally collect only one copy of each post and then share it with the users that need to see it, does that mean nonoriginating instances are trusted to not show that post to users the poster has blocked (or who shouldn't see it because they're not following etc depending on visibility)?

How do the collecting instances know who should see it? (A cached copy of the poster's follow list?)

And does #authorized_fetch change any of this?

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

Today we created #FediDev KR, a community for Korean people who are not only implementing fediverse servers, but also those who are running them, such as server operators, moderators, client app developers, bot developers, writers, translators, researchers, and more. For now, we're based on a Discord server, but we hope to eventually organize offline meetups and workshops. We'd love your support!

https://fedidev.kr/

Tokyo Outsider (337ppm)

@tokyo_0@mas.to

How long (hours, roughly) would it take to implement a basic #ActivityPub server from scratch in #Java — absoluet bare bones, like a proof of concept just capable of sending and receiving posts, which could then be developed more before becoming a finished, user-ready system?

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org · Reply to 洪民憙 (Hong Minhee)'s post

먼저 Discord에 #FediDev KR 서버를 하나 만들었습니다!

https://discord.gg/B2ABMBpHNA

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

서울에서 #fedidev 모임하는 생각 💭

洪民憙 (Hong Minhee) 🤏🏼

@hongminhee@todon.eu

#Fedify is an #ActivityPub server framework in #TypeScript & #JavaScript. It aims to eliminate the complexity and redundant boilerplate code when building a federated server app, so that you can focus on your business logic and user experience.

The key features it provides currently are:

• Type-safe objects for Activity Vocabulary (including some vendor-specific extensions)
• #WebFinger client and server
• HTTP Signatures
• Middleware for handling webhooks
• #NodeInfo protocol
• #Node.js, #Deno, and #Bun support
• CLI toolchain for testing and debugging

If you're curious, take a look at the Fedify website! There's comprehensive docs, a demo, a tutorial, example code, and more:

https://fedify.dev/

https://github.com/dahlia/fedify-redis

Fedify: an ActivityPub server framework

@fedify@hollo.social

#Fedify has supported optional queuing for outgoing activities, with two built-in message queue backends: InProcessMessageQueue, which is suitable for development, and DenoKvMessageQueue, which is only available in Deno.

Fedify has also had two built-in cache backends, MemoryKvStore, which is suitable for development, and DenoKvStore, which is only available in Deno.

Now, however, by installing the @fedify/redis package, you can use #Redis as both a message queue backend and a cache backend! Unlike DenoKvMessageQueue and DenoKvStore, it's also available for #Node.js and #Bun.

This feature was made possible with the support of @ghost.

https://hollo.social/@fedify/01905d6a-5d70-75bc-881e-d6c155a5051c

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org · Reply to Jaeyeol Lee (a.k.a. kodingwarrior) :vim:'s post

@kodingwarrior 한국에도 #fedidev 모임 같은 거 개최하면 좋겠어요 ㅎㅎ

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

#Fedify now has the official #Hollo account! Please follow @fedify!

Fedify: an ActivityPub server framework

@fedify@hollo.social

Hello, #fediverse! It's the official fedi account of the Fedify, an #ActivityPub server framework!

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

Found a memory leak (on #Bun) in recent commits of #Fedify—be careful when using the unstable versions.

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

I wish there was a #fedidev meetup in #Korea too…

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

#Hollo development is often motivation to add features to #Fedify, for example, most of the commits I added to Fedify today were for Hollo.

https://github.com/sponsors/dahlia

洪民憙 (Hong Minhee)

@hongminhee@fosstodon.org

If you'd like to support the development of #Fedify or #Hollo, you can sponsor me on GitHub!

Hollo

@hollo@hollo.social

Introducing #Hollo. Hollo is an #ActivityPub-enabled single-user microblogging software. Although it's for a single user, it also supports creating and running multiple accounts for different topics.

Oh, and Hollo is built using #Bun and #Fedify.

洪民憙 (Hong Minhee) 🤏🏼

@hongminhee@todon.eu

Version 0.10.0 of #Fedify, an #ActivityPub server framework, has been released! Starting with this release, Fedify, previously distributed under AGPL 3.0, is now distributed under the MIT License to encourage wider adoption. Here are the major changes:

• In addition to RSA-PKCS#1-v1.5, Fedify now supports Ed25519 for signing and verifying the activities.
• FEP-521a: Multiple key pairs can now be registered for an actor.
• FEP-8b32: Implemented Object Integrity Proofs.
• Added Arrive and Question classes.

https://github.com/dahlia/fedify/releases/tag/0.10.0

Jeff Sikes

@box464@mastodon.social

TIL when you upload a video file to Mastodon, it generates a preview thumbnail. The thumbnail isn't passed through to other servers in the ActivityPub payload (similar to preview cards).

Each receiving platform handles this situation differently. Some regenerate a thumbnail (processing again). Some ignore it and don't show one. Others create blank thumbnails to appease the Mastodon API.

A blurhash is passed, tho, and could be used as a placeholder.

#FediDev #Mastodon

洪民憙 (Hong Minhee) 🤏🏼

@hongminhee@todon.eu

@hollo is a testbed for the bleeding edge of #Fedify. 😂

https://jsr.io/@fedify/fedify@0.10.0-dev.205+0cbca257

@hongminhee@todon.eu · Reply to 洪民憙 (Hong Minhee) 🤏🏼's post

Thanks to @silverpill, #Fedify is finally FEP-8b32 compliant! Though it's not ready for general release yet, it's passing tests in the latest main branch. I'll test it with Mitra and other FEP-8b32-compliant implementations, and if it works well, it'll be included in 0.10.0.

You can try it out in version 0.10.0-dev.205+0cbca257.

https://github.com/dahlia/fedify/releases/tag/0.9.1

洪民憙 (Hong Minhee) 🤏🏼

@hongminhee@todon.eu

I just released #Fedify 0.9.1, which fixed one small bug.

洪民憙 (Hong Minhee) 🤏🏼

@hongminhee@todon.eu

#Hollo now supports sharing posts (reblogs)!

https://bonfirenetworks.org/posts/surveying_expedition/

Jeff Sikes

@box464@mastodon.social

Bonfire, the modular Fediverse platform, is looking for five Elixir developers to act as test subjects to improve the developer onboarding experience. Participants can receive a €50 stipend for their one-hour session.

Please share with your elixir dev friends, and boost!

#Elixir #FediDev #Fediverse #MyElixirStatus

洪民憙 (Hong Minhee) 🤏🏼

@hongminhee@todon.eu · Reply to 洪民憙 (Hong Minhee) 🤏🏼's post

Implementing Object Integrity Proofs (FEP-8b32) and my implementation is not passing the test vectors. I haven't found the reason for 24 hours… 😫

#Fedify #fedidev #ActivityPub

洪民憙 (Hong Minhee) 🤏🏼

@hongminhee@todon.eu · Reply to 洪民憙 (Hong Minhee) 🤏🏼's post

FEP-521a has been implemented in #Fedify.

Actors now have the #assertionMethods property, and the #Multikey class has been added. For example, if you look at the the actor from the Fedify Example Blog (https://fedify-blog.deno.dev/users/fedify-example), you can see that it has the assertionMethods property in addition to the publicKey property.

You can try it out in version 0.10.0-dev.196+55cc34d1.

https://jsr.io/@fedify/fedify@0.10.0-dev.196+55cc34d1

https://github.com/misskey-dev/misskey/pull/13950

洪民憙 (Hong Minhee) 🤏🏼

@hongminhee@todon.eu · Reply to 洪民憙 (Hong Minhee) 🤏🏼's post

#Misskey throws an error when a remote actor has multiple public keys, so I sent a patch to fix this bug.

This is my first patch for Misskey!

https://jsr.io/@fedify/fedify@0.10.0-dev.190+4dffb89a

洪民憙 (Hong Minhee) 🤏🏼

@hongminhee@todon.eu

As a first step towards adding Object Integrity Proofs (FEP-8b32) to #Fedify, I've made it support #Ed25519 keys. I've also enabled multiple keys to be associated with an actor. For example, if you look at the actor from the Fedify Example Blog (https://fedify-blog.deno.dev/users/fedify-example), you'll see that it has two public keys, one for RSA and one for Ed25519.

You can try it out in version 0.10.0-dev.190+4dffb89a.

洪民憙 (Hong Minhee) 🤏🏼

@hongminhee@todon.eu

Version 0.9.0 of #Fedify, an #ActivityPub server framework, has been released! Here are the main changes:

• Added Tombstone, Hashtag, and Emoji classes.
• Added normalizeActorHandle() function to normalize an actor handle. This is needed when the domain of the actor handle is an IDN, or when the domain contains capital letters.
• Added an option to the sendActivity() function, excludeBaseUris, to exclude specified servers from sending activities. This can be used when you don't want to send activities to your own server.
• Added Context.parseUri(), a method to parse actor, object, inbox, and collection URIs.
• The time window for HTTP Signatures verification is now configurable.
• The @fedify/fedify/httpsig module has been renamed to . This is in preparation for implementing additional object integrity proofs other than HTTP Signatures.
• Improved interoperability with #Misskey.

https://github.com/dahlia/fedify/releases/tag/0.9.0

洪民憙 (Hong Minhee) 🤏🏼

@hongminhee@todon.eu · Reply to 洪民憙 (Hong Minhee) 🤏🏼's post

Now #Hollo has several more features:

• Following/unfollowing accounts
• Following/unfollowing hashtags
• Post visibility
• Post language
• Editing profile
• Mentions
• Likes
• Bookmarks
• Notifications
• Markers

洪民憙 (Hong Minhee) 🤏🏼

@hongminhee@todon.eu

I'm rebuilding #Hollo from scratch, and I've implemented some #Mastodon-compatible APIs to let me do the following actions with #Phanpy and #Elk now:

• Logging in
• Composing a post
• Writing a reply
• View posts
• Public timeline
• Home timeline

✌️

https://funfedi.dev/support_tables/generated/object_types/

Jeff Sikes

@box464@mastodon.social

I really like these support tables on the FunFedi website. Seeing the support grid and example responses is very helpful.

I know a lot of devs are jumping from chat room to chat room, looking for someone to reply back in their timelines, etc. to get help when a specific platform isn't working quite right.

#FediDev

Jeff Sikes

@box464@mastodon.social

If you're curious how ActivityPub works exactly (like me) this site does a great job of show and tell.

On the surface it looks like any other Mastodon instance, but on closer inspection, provides you insight into the ActivityPub back and forth going on behind the scenes!

Check out the great work by @crepels

https://activitypub.academy/