Fedify: an ActivityPub server framework

🎉 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:

https://opencollective.com/fedify

#OpenCollective #support #backing #sponsor #donation

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 & Linked Data Signatures & Object Integrity Proofs
• 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/

明日は #技術書典18 📕！！
#FediLUG ​​ は 6月1日 (日) 11:00～17:00 に 池袋・サンシャインシティ 展示ホールD（文化会館ビル2F）で開催される #技術書典18 にサークル出展します！
・FediLUG合同誌『Thinking Penguin Magazine Vol.0』
・ホンさん著『自分だけのフェディバースのマイクロブログを作ろう！』
それぞれ500円でご用意してお待ちしております！！

ActivityPubサーバーを構築してみたいけれど、どこから始めればよいかわからない方には、Fedifyのチュートリアル『自分だけのフェディバースのマイクロブログを作ろう！』をおすすめします。包括的でステップバイステップのガイドで、完全に機能する連合型アプリケーションの構築方法を丁寧に解説しています。フェディバースに飛び込みたい開発者にぴったりです！

#ActivityPub #Fedify #チュートリアル #フェディバース #fediverse

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!

#fedidev

오픈 소스 컨퍼런스 名古屋(나고야)에서 Fedify 冊(책) 《나만의 聯合宇宙(연합우주) 마이크로블로그 만들기》(自分だけのフェディバースのマイクロブログを作ろう！)가 完販(완판)되었다고…!

OSC名古屋、Fedify本完売した（6冊）

OSCでFedify本5冊売れた

無料というのもあってかFedify本がすごい売れる

技術書典オンラインが始まったけど、Fedify本みんな買っていってる

本日はオープンソースカンファレンス名古屋（ #oscnagoya ）当日です！
吹上駅から徒歩5分ほどの中小企業振興会館、第にファッション展示場で #FediLUG はブース出展、セミナーでのLT大会を開催予定です！
ステッカー、同人誌用意してお待ちしています！！

今週末開催される、 #oscnagoya では #FediLUG ブースにて、
・有志8人による執筆のThinking Penguin Magazine Vol.0（500円）
・和条門さん（ @naoki_wjm@k.my-sky.blue ）による『さばかんライフ！』（1000円）
・ホンさん（ @hongminhee@hollo.social ）による『自分だけのフェディバースのマイクロブログを作ろう！』（500円）
も頒布いたします！
そのほかにもステッカーや各種チラシも扱っておりますので、ぜひ足をお運びください！！

Fedify本届いた〜

@smallcircles That's a great point! We definitely want to balance organization benefits with maintainer overhead. The goal is to make our workflow smoother, not more complex. We'll keep the system simple and only add labels that genuinely help contributors find relevant issues. Thanks for the perspective!

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.

#fedidev

2025 오픈소스 컨트리뷰션 아카데미 참여형 멘티를 오늘부터 6월 22일까지 모집한다고 합니다. 저도 Fedify 프로젝트의 멘토로서 참여하고 있으니, 관심 있는 분들은 많은 참여 부탁드립니다!

RE: https://hollo.social/@hongminhee/0196231c-8256-788e-bba1-0d3a9215524f

@antolius Great question! For prototyping with custom vocabulary, we're setting up automated PR builds that will solve exactly this use case.

Soon, each pull request will automatically publish versioned builds to JSR and npm. For example, PR #123 would generate releases like:

• First push: 1.6.0-pr.123.1
• Second push: 1.6.0-pr.123.2
• And so on…

This means you can install and test vocabulary extensions before they're merged upstream:

npm install @fedify/fedify@1.6.0-pr.123.1

This approach lets you prototype with your custom object types immediately while contributing back to the community when ready. You can develop against the PR build, and once your vocabulary addition is merged, simply update to the stable release.

The build pipeline isn't quite ready yet, but it's coming soon. In the meantime, forking and building locally is still your best bet for custom vocabulary during prototyping.

@antolius Great question! For prototyping with custom vocabulary, we're setting up automated PR builds that will solve exactly this use case.

Soon, each pull request will automatically publish versioned builds to JSR and npm. For example, PR #123 would generate releases like:

• First push: 1.6.0-pr.123.1
• Second push: 1.6.0-pr.123.2
• And so on…

This means you can install and test vocabulary extensions before they're merged upstream:

npm install @fedify/fedify@1.6.0-pr.123.1

This approach lets you prototype with your custom object types immediately while contributing back to the community when ready. You can develop against the PR build, and once your vocabulary addition is merged, simply update to the stable release.

The build pipeline isn't quite ready yet, but it's coming soon. In the meantime, forking and building locally is still your best bet for custom vocabulary during prototyping.

@fedify this sounds reasonable for extending support for 3rd party vocabulary. How do you envision developing 1st party vocab for servers implemented using fedify?

For example, I'm developing a service that needs to introduce some new object types. But I'm nowhere near ready to codify them in a FEP or share them with broader fedify userbase. What would be the best way to continue using fedify in this prototyping phase? (Perhaps building with a fedify fork and merge uspream once server is done?)

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.

#fedidev

We inadvertently published @fedify/fedify 1.6.0 and @fedify/cli 1.6.0 to npm before they were ready for release. (Note: 1.6.0 was not released to JSR.)

Both versions have been deprecated and unpublished. Please avoid using these versions.

Our next minor release will be version 1.6.1, which will include the intended changes and fixes.

We apologize for any inconvenience this may have caused.

HolloとかFedifyのお話おもしろかったのだ

우리의 코드를 찾아서 – 2막. 민희님과 Fedify & Hollo 알아보기 https://youtu.be/sqxR8zscSDo?si=nQRxPyV7kjplqy01

【.​​ 技術書典18に出展します 📚 】
​​ は6月1日に技術書専門イベントである、 #技術書典18 の お06 で合同誌『Thinking Penguin Magazine Vol.0』と @hongminhee@hollo.social さん著の『自分だけのフェディバースのマイクロブログを作ろう！』を頒布します！
どちらも500円で購入できます！！ぜひお立ち寄りください！
詳細はこちら : https://techbookfest.org/organization/7JepZT0g3C6qbddiLmkAwp

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!

#fedidev #FediDevKR #opensource

오늘 박현우 님(@lqez)께서 Fedify 로고로 배지를 만들어 와주셨습니다! FediDev KR 두 번째 스프린트 모임 오신 분들께 나눠드리고 있어요.

I've been thinking about adding a debug dashboard to #Fedify that shows all #ActivityPub activities being sent and received in real-time. This would include filters by activity type, detailed inspection of JSON-LD content, signature verification details, and retry management for failed deliveries.

As a #fedidev, would you find this useful for troubleshooting federation issues? Any other features that would be helpful in such a debugging tool?

Fedifyは新しいパートナーシップの機会を探しています！

Fedifyとは？

Fedifyは、ActivityPubベースのフェデレーションサーバーフレームワークで、開発者が分散型ソーシャルネットワークである#フェディバース（#fediverse）にアプリケーションを簡単に統合できるよう支援します。複雑なActivityPubプロトコルの実装を簡素化し、開発時間を大幅に短縮します。MITライセンスの下で提供されるオープンソースプロジェクトです。

💼 Fedifyを活用しているプロジェクト

すでに様々なプロジェクトがFedifyを活用しています：

• Ghost：数百万人のユーザーを持つプロフェッショナルな出版プラットフォーム（MITライセンスのオープンソース）で、Fedifyの主要スポンサー兼パートナーです。
• Hollo：個人ユーザー向けの軽量マイクロブログ（オープンソース、AGPL-3.0）
• Hackers' Pub：ソフトウェアエンジニア向けのフェディバースブログプラットフォーム（オープンソース、AGPL-3.0）
• Encyclia：ORCID学術記録をActivityPubを通じて提供するブリッジサービス

🚀 Fedifyが提供する価値

• 開発時間80%削減：複雑なActivityPub実装の代わりに実証済みフレームワークを活用
• 即時Fediverse互換性：Mastodon、Misskey、Pleroma、Pixelfed、PeerTubeなど様々なFediverseサービスとすぐに互換
• 専門技術サポート：ActivityPubおよびフェデレーションプロトコルの専門家による直接サポート
• カスタム開発：お客様の特定要件に合わせた機能開発

🤝 可能な協力モデル

• カスタムコンサルティングと統合サポート：お客様のプラットフォームへのFedify統合のための専門的支援
• カスタム機能開発：お客様のプラットフォームに必要な特定機能の開発と実装
• 長期的な技術パートナーシップ：継続的な開発とメンテナンスのための長期協力関係

🌟 Fedifyとの協力によるメリット

• 技術的優位性：自社開発と比較して時間とリソースの節約
• ブランドイメージ：オープンソースエコシステムへの支援を通じた企業イメージの向上
• 分散型ソーシャルネットワークへの参入：フェディバースエコシステムへの容易な参加
• 競争優位性：ソーシャル機能による製品競争力の強化

📩 興味をお持ちですか？

ActivityPubの実装をご検討中の方や、Fedifyプロジェクトとの協力にご興味のある方は、ぜひご連絡ください：

• メール：sponsor@fedify.dev
• フェディバース：@fedify
• GitHub：https://github.com/fedify-dev/fedify

お客様の要件と目標に合わせたカスタマイズされた協力の可能性を一緒に探りましょう。

Fedify는 새로운 후원 파트너를 찾고 있습니다!

Fedify란?

Fedify는 #ActivityPub 기반 연합형 서버 프레임워크로, 개발자들이 분산형 소셜 네트워크인 #연합우주(#fediverse)에 애플리케이션을 쉽게 통합할 수 있도록 돕습니다. 복잡한 ActivityPub 프로토콜 구현을 단순화하여 개발 시간을 크게 단축시킵니다. MIT 라이선스 하에 제공되는 오픈 소스 프로젝트입니다.

💼 Fedify를 활용하는 프로젝트들

다양한 프로젝트들이 이미 Fedify를 활용하고 있습니다:

• Ghost: 수백만 사용자를 보유한 전문적인 오픈 소스(MIT 라이선스) 퍼블리싱 플랫폼으로, Fedify의 주요 후원사이자 파트너입니다.
• Hollo: 개인 사용자를 위한 경량 마이크로블로그 (오픈 소스, AGPL-3.0)
• Hackers' Pub: 소프트웨어 엔지니어를 위한 연합우주 블로그 플랫폼 (오픈 소스, AGPL-3.0)
• Encyclia: ORCID 학술 기록을 ActivityPub을 통해 제공하는 브리지 서비스

🚀 Fedify가 제공하는 가치

• 개발 시간 80% 단축: ActivityPub의 복잡한 구현 대신 검증된 프레임워크 활용
• 즉각적인 연합우주 호환성: Mastodon, Misskey, Pleroma, Pixelfed, PeerTube 등 다양한 연합우주 서비스와 즉시 호환
• 전문 기술 지원: ActivityPub 및 연합 프로토콜 전문가의 직접 지원
• 맞춤형 개발: 귀사의 특정 요구사항에 맞는 맞춤형 기능 개발

🤝 가능한 협력 모델

• 맞춤형 컨설팅 및 통합 지원: 귀사 플랫폼에 #Fedify 통합을 위한 전문적 지원
• 맞춤형 기능 개발 의뢰: 귀사에 필요한 특정 기능의 개발 및 구현
• 장기적인 기술 파트너십: 지속적인 개발 및 유지보수를 위한 장기 협력 관계

🌟 Fedify와 협력했을 때의 이점

• 기술적 이점: 자체 구현 대비 시간과 리소스 절약
• 브랜드 이미지: 오픈 소스 생태계 지원을 통한 기업 이미지 강화
• 분산형 소셜 네트워크 진입: 연합우주 생태계에 쉽게 참여
• 경쟁 우위: 소셜 기능을 통한 제품 경쟁력 강화

📩 관심이 있으신가요?

ActivityPub 구현을 고려 중이시거나, Fedify 프로젝트와 협력하고 싶으시다면 연락 주세요:

• 이메일: sponsor@fedify.dev
• 연합우주: @fedify
• GitHub: https://github.com/fedify-dev/fedify

귀사의 요구사항과 목표에 맞는 맞춤형 협력 방안을 함께 모색하겠습니다.

Fedify is looking for new partnership opportunities!

What is Fedify?

#Fedify is an #ActivityPub-based federated server framework that helps developers easily integrate their applications with the #fediverse, a decentralized social network. It simplifies the complex implementation of the ActivityPub protocol, significantly reducing development time. Fedify is an open-source project available under the MIT license.

💼 Projects using Fedify

Various projects are already leveraging Fedify:

• Ghost: A professional publishing platform with millions of users, open source under MIT license, and a major sponsor and partner of Fedify.
• Hollo: A lightweight microblogging platform for individual users (open source, AGPL-3.0)
• Hackers' Pub: A fediverse blogging platform for software engineers (open source, AGPL-3.0)
• Encyclia: A bridge service that makes ORCID academic records available via ActivityPub

🚀 Value provided by Fedify

• 80% development time reduction: Utilize a proven framework instead of complex ActivityPub implementation
• Immediate fediverse compatibility: Instant compatibility with various fediverse services including Mastodon, Misskey, Pleroma, Pixelfed, PeerTube, etc.
• Expert technical support: Direct support from ActivityPub and Federation protocol experts
• Custom development: Tailored feature development to meet your specific requirements

🤝 Potential collaboration models

• Custom consulting and integration support: Professional assistance for integrating Fedify into your platform
• Custom feature development: Development and implementation of specific features needed for your platform
• Long-term technical partnership: Long-term collaboration for continuous development and maintenance

🌟 Benefits of collaborating with Fedify

• Technical advantage: Save time and resources compared to in-house implementation
• Brand image: Enhance corporate image through support of the open-source ecosystem
• Entry to decentralized social networks: Easily participate in the fediverse ecosystem
• Competitive edge: Strengthen product competitiveness through social features

📩 Interested?

If you're considering implementing ActivityPub or wish to collaborate with the Fedify project, please get in touch:

• Email: sponsor@fedify.dev
• Fediverse: @fedify
• GitHub: https://github.com/fedify-dev/fedify

We're excited to explore customized collaboration opportunities that align with your requirements and goals.

For those interested in supporting #Fedify's development, we do have an Open Collective page where community #sponsorship is welcome.

Even small contributions help sustain development and show there's interest in open source #ActivityPub tools. Thanks to our existing sponsors who've already been helping move the project forward!

The goal remains the same: make building federated applications more accessible to developers so the #fediverse can continue to grow and thrive.

Just received word that @fedify wasn't selected for @nlnet's Open Call this round. While disappointing, I understand the competition was fierce with many worthy projects seeking limited funding.

The journey continues though—#Fedify development will move forward at its own pace. Thanks to everyone who's shown interest and support for this project so far. Building tools for the #fediverse remains important work, and I'm committed to seeing it through.

If you know of other funding opportunities that might be a good fit for open source #ActivityPub tools, I'm all ears.

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

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

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

#CloudflareWorkers