@fedify@hollo.social · 9 following · 788 followers
Fedify is a TypeScript library for building federated server apps powered by ActivityPub and other standards, so-called fediverse. 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.
@fedify@hollo.social
🎉 Excited to announce that #Fedify is now on Open Collective! Support the project's development starting at:
Your support will help us maintain and improve Fedify. Check it out here:
https://opencollective.com/fedify
@fedify@hollo.social
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:
If you're curious, take a look at the #Fedify website! There's comprehensive docs, a demo, a tutorial, example code, and more:
@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!
@julian@fietkau.social · Reply to Fedify: an ActivityPub server framework's post
I build Encyclia as a solo dev, and I consider myself more of a hobbyist developer than a professional (I used my university CS credentials to go into academia instead of the tech industry).
This is why Encyclia's development pace is so uneven: I get around to it when I get around to it. 😉
But having created ActivityPub projects with and without frameworks, let me say that @fedify makes it realistic to build reliable, practical, long-term ActivityPub integrations for someone like me. 👍
@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.
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@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.
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 backoffWorkersMessageQueue — leverages Cloudflare Queues' automatic retry and dead-letter queue featuresAmqpMessageQueue — can now be configured to use AMQP broker's native retry mechanismsThe InProcessMessageQueue continues to use Fedify's internal retry mechanism, while ParallelMessageQueue inherits the retry behavior from its wrapped queue.
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.
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.
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.
@botkit@hollo.social
We're pleased to announce that #Node.js support has been merged and will be available in #BotKit 0.3.0.
Now you can build your #ActivityPub bots with both #Deno and Node.js, giving you more flexibility in choosing your preferred runtime environment.
Stay tuned for BotKit 0.3.0!
@dantescanline@autonomous.zone
the thing that is always revelatory for me about the fediverse is that the fundamental thing (federation) actually just works? yes there are many many issues with the way applications integrate with each other.
but doing the hello world example for the fedify library, running a tunnel so my local code is reachable over a domain and seeing the actor show up in any random fediverse server is like magic. you'd think this is the part that would take 15 years to build, not the UI on top
@fedify@hollo.social
Fedify 1.6.2 has been released as a hotfix to address compatibility issues with certain Mastodon servers.
This release resolves interoperability problems with Mastodon instances running bleeding-edge versions that include RFC 9421 HTTP Message Signatures support. These versions contain a bug that causes 500 Internal Server Error responses when receiving RFC 9421 signatures, affecting communication with several major servers including mastodon.social.
The fix extends Fedify's double-knocking mechanism to retry requests with draft-cavage-http-signatures-12 when receiving 5xx error responses, in addition to the existing 4xx error handling. This ensures continued federation compatibility while Mastodon addresses the underlying issue in their implementation.
This is a temporary workaround that will be reverted in a future release once Mastodon fixes their RFC 9421 implementation and affected servers are updated. The change maintains backward compatibility and does not affect the behavior with servers that properly handle RFC 9421 signatures.
Users are encouraged to update to 1.6.2 to ensure reliable federation with affected Mastodon servers.
@encyclia@fietkau.social
Encyclia was shown as a speed demo at @fediforum on June 7. 🙂 You can find the 5 minute video on Peertube: https://spectra.video/w/tSjP7WnV3pBakD61ccuDH2 or on YouTube: https://www.youtube.com/watch?v=8QipWHAaUEA
In case you've been waiting: the project hasn't been forgotten, @julian is just having a busy few months at the day job since April now. 😓 We'll probably be making more progress again later in the summer!
🍆@Yohei_Zuho@mstdn.y-zu.org
Fedify本の売上80冊超えた
@silverpill@mitra.social
Mitra v4.4.0 supports verification of RFC-9421 HTTP signatures. It is known to be compatible with @fedify, but I haven't tested it with Mastodon or Streams yet.
Outgoing requests are still signed according to the draft-cavage. I don't plan to implement double-knocking, but something like FEP-844e could be supported in the future, though this is not urgent.
My implementation of a parser is available in APx library.
RE: https://mitra.social/objects/01974018-9b83-c1ec-a109-24a72a579235
@mitra@mitra.social
#Mitra v4.4.0
https://codeberg.org/silverpill/mitra/releases/tag/v4.4.0
https://codeberg.org/silverpill/mitra-web/releases/tag/v4.4.0
- Verifying RFC-9421 HTTP message signatures on incoming requests.
- If the default post visibility is "followers", reposts will be followers-only too.
- Edits and deletions are synced in private conversations.
@samvie@chaos.social
Great demo of @encyclia by @julian
Day 3 of #Fediforum starts strong with a great tool for the academic sphere👏
Making #Orcid available for #activitypub via @fedify
Open science communication is very relevant for the future development of the #Fediverse 🚀
@julian@fietkau.social · Reply to @reiver ⊼ (Charles) :batman:'s post
@reiver @hongminhee I ran an unconference session at @fediforum yesterday about "Implementing ActivityPub in 2025" but we were a pretty small group of people and went off topic a bunch, so the session notes is mostly just me trying to advertise @fedify. 🙃
@reiver@mastodon.social
Julian Fietkay ( @julian ) just said nice things about @fedify at FediForum 2025.
cc: @hongminhee
@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.
Fedify 1.6 introduces first-class support for Cloudflare Workers, enabling #serverless deployment of #ActivityPub applications at the edge.
WorkersKvStore: A key–value store implementation using Cloudflare's KV API for persistent storage in Workers environmentsWorkersMessageQueue: A message queue implementation leveraging Cloudflare Queues for reliable message processingqueue() methodFederation.processQueuedTask() methodFor a complete working example, see the Cloudflare Workers example in the Fedify repository.
Fedify 1.6 introduces the FederationBuilder class and createFederationBuilder() function to support deferred federation instantiation. This pattern provides several benefits:
The builder pattern is particularly useful for large applications and environments like Cloudflare Workers where configuration data is only available at runtime.
Fedify 1.6 implements the official HTTP Message Signatures standard (RFC 9421) specification, the final revision of the HTTP Signatures specification.
To ensure maximum compatibility across the fediverse, Fedify 1.6 introduces an intelligent double-knocking mechanism:
This approach ensures seamless communication with both modern and legacy ActivityPub implementations while positioning Fedify at the forefront of security standards.
The RFC 9421 implementation has been thoroughly tested for interoperability with existing ActivityPub implementations that support RFC 9421 signature verification:
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.
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.
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.
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.
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.
For new deployments, consider leveraging Cloudflare Workers support for:
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.
#fedidev #RFC9421 #HTTPSignatures #HTTPMessageSignatures #CloudflareWorkers
@hongminhee@hackers.pub
Fedify 1.6.1のリリースを発表いたします。本バージョンは1.6.0の取り下げを受けた1.6シリーズの最初のリリースとなります。今回のリリースでは、Fedifyのデプロイメント方法を大幅に拡張し、フェディバース（fediverse）全体でのセキュリティ互換性を向上させる重要な新機能を導入しています。
Fedify 1.6ではCloudflare Workersへの正式対応を実現し、ActivityPubアプリケーションをエッジ環境でサーバーレス実行できるようになりました。
WorkersKvStore: Cloudflare KV APIを使用し、Workers環境で永続ストレージを提供するキーバリューストア実装WorkersMessageQueue: Cloudflare Queuesを活用し、信頼性の高いメッセージ処理を実現するメッセージキュー実装queue()メソッドによる自動的なキューメッセージ処理Federation.processQueuedTask()メソッドによる手動キュー処理完全な動作例については、FedifyリポジトリにあるCloudflare Workersのサンプル実装をご覧ください。
Fedify 1.6ではFederationBuilderクラスとcreateFederationBuilder()関数を導入し、フェデレーションの遅延インスタンス化をサポートします。このパターンには以下のメリットがあります。
このビルダーパターンは、特に大規模なアプリケーションや、設定データが実行時に動的に取得されるCloudflare Workersのような環境で有用です。
Fedify 1.6では、HTTP Signatures仕様の最終版となる公式HTTP Message Signatures標準（RFC 9421）仕様を実装しました。
フェディバース全体での最大互換性を確保するため、Fedify 1.6ではインテリジェントなダブルノック機構を導入しています。
このアプローチにより、最新とレガシー両方のActivityPub実装との円滑な通信を確保できます。同時に、セキュリティ標準の最前線にFedifyを位置づけています。
RFC 9421実装は、RFC 9421署名検証をサポートする既存のActivityPub実装との相互運用性について徹底的にテストされています。
これらのテストにより、他のActivityPub実装がFedifyで生成したRFC 9421署名を正常に検証できることを確認し、エコシステムが徐々に公式仕様を採用していく中で、適切なフェデレーションが保証されます。これらの実装は現在RFC 9421署名の検証をサポートしていますが、まだ自身でRFC 9421署名を生成していません。Fedifyはこのモダンスタンダードの生成と検証の両方をサポートする最初のActivityPub実装の1つとなっています。
新しいContext.lookupWebFinger()メソッドにより、WebFingerデータへの直接アクセスが可能になりました。高レベルなContext.lookupObject()メソッドでは実現できない、アカウント発見とリソース解決のより細かい制御を開発者に提供します。
新しいContext.clone()メソッドにより動的なコンテキストデータの置換が可能になり、リクエスト処理やデータフローの管理において、より高い柔軟性を提供します。特にミドルウェアの実装や複雑なリクエストルーティングを行う際に有用です。
Fedify 1.6は既存のアプリケーションとの完全な後方互換性を維持しています。新しいHTTP Message Signaturesとダブルノック機構は、コード変更なしで透過的に動作します。
重要: Fedify 1.6はNode.js環境においてNode.js 22.0.0以降を必要とします。この変更はDenoやBunランタイムを使用するアプリケーションには影響しません。現在Node.jsをご利用の方は、アップグレード前に環境がこの要件を満たしているかご確認ください。
新規デプロイメントでは、以下の利点からCloudflare Workersサポートの活用をご検討ください。
Fedify 1.6は、フェディバース全体での幅広い互換性を維持するというフレームワークのコミットメントを保ちながら、デプロイメント選択肢の大幅な拡張を表しています。Cloudflare Workersサポートの追加により、フェデレーティッドアプリケーションの新しいアーキテクチャパターンが開かれ、RFC 9421実装により、Fedifyは新たなActivityPubセキュリティ標準に対応し続けています。
詳細な移行ガイド、APIドキュメント、サンプルについては、Fedifyドキュメントをご覧ください。サポートとディスカッションについては、MatrixまたはDiscordのコミュニティにご参加ください。
@AmaseCocoa@s.amase.cc
1.6でサポートされるってことはfedify inboxでRFCテストできるようになるのか
@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.
Fedify 1.6 introduces first-class support for Cloudflare Workers, enabling #serverless deployment of #ActivityPub applications at the edge.
WorkersKvStore: A key–value store implementation using Cloudflare's KV API for persistent storage in Workers environmentsWorkersMessageQueue: A message queue implementation leveraging Cloudflare Queues for reliable message processingqueue() methodFederation.processQueuedTask() methodFor a complete working example, see the Cloudflare Workers example in the Fedify repository.
Fedify 1.6 introduces the FederationBuilder class and createFederationBuilder() function to support deferred federation instantiation. This pattern provides several benefits:
The builder pattern is particularly useful for large applications and environments like Cloudflare Workers where configuration data is only available at runtime.
Fedify 1.6 implements the official HTTP Message Signatures standard (RFC 9421) specification, the final revision of the HTTP Signatures specification.
To ensure maximum compatibility across the fediverse, Fedify 1.6 introduces an intelligent double-knocking mechanism:
This approach ensures seamless communication with both modern and legacy ActivityPub implementations while positioning Fedify at the forefront of security standards.
The RFC 9421 implementation has been thoroughly tested for interoperability with existing ActivityPub implementations that support RFC 9421 signature verification:
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.
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.
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.
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.
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.
For new deployments, consider leveraging Cloudflare Workers support for:
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.
#fedidev #RFC9421 #HTTPSignatures #HTTPMessageSignatures #CloudflareWorkers
@fedify@hollo.social
Did you know? #Fedify provides #documentation optimized for LLMs through the llms.txt standard.
Available endpoints:
Useful for training #AI assistants on #ActivityPub/#fediverse development, building documentation chatbots, or #LLM-powered dev tools.
@fedify@hollo.social
#Fedify 1.6 is approaching with three major enhancements: RFC 9421 HTTP Message Signatures support with double-knocking for seamless backward compatibility, a new builder pattern for better code organization in large applications, and native #Cloudflare #Workers support for serverless deployments. These additions strengthen Fedify's standards compliance while expanding deployment flexibility across different environments. Stay tuned for the official release! 🚀
#ActivityPub #fedidev #fediverse #RFC9421 #CloudflareWorkers
@fedilug@msky.ospn.jp
#oscnagoya #技術書典18 のご参加ありがとうございました。
のブースや本、ステッカー、セミナーなどは楽しんでいただけましたでしょうか？次のFediLUGイベントは6月22日の第９回勉強会です！！ご興味がある方はぜひご参加ください。
また、OSC名古屋及び技術書典18リアル会場で頒布した『自分だけのフェディバースのマイクロブログを作ろう！』と『Thinking Penguin Magazine Vol.0』は技術書典18のオンライン通販で全国から購入可能です！この際にぜひご検討ください。
同人誌販売： https://techbookfest.org/organization/7JepZT0g3C6qbddiLmkAwp
第9回勉強会: https://fedilug.connpass.com/event/357642/
@fedify@hollo.social
If you're on the fence about which driver to choose for #Fedify's message queue, here's a benchmark that just came out. In addition to no queue, we compare 5 drivers, for a total of 11 setups:
InProcessMessageQueueDenoKvMessageQueueRedisMessageQueuePostgresMessageQueueAmqpMessageQueueInProcessMessageQueue × 4DenoKvMessageQueue × 4RedisMessageQueue × 4PostgresMessageQueue × 4AmqpMessageQueue × 4Curious to see the results? Check out the GitHub repository!
@hongminhee@fosstodon.org · Reply to 洪 民憙 (Hong Minhee)'s post
@thisismissem Here's the benchmark, and while it contains some questionable results, the overall conclusion is as following:
• Response times are much faster with queues than without.
• Overall throughput is better without queues.
• However, some queue setups can achieve throughput close to that of no queue.
This benchmark assumes communication within a single node, so the effect of queues may be greater in real-world networks.
@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 WorkersMessageQueueTry 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!
@fedilug@msky.ospn.jp
@fedilug@msky.ospn.jp
明日は #技術書典18 📕！！
#FediLUG は 6月1日 (日) 11:00～17:00 に 池袋・サンシャインシティ 展示ホールD（文化会館ビル2F）で開催される #技術書典18 にサークル出展します！
・FediLUG合同誌『Thinking Penguin Magazine Vol.0』
・ホンさん著『自分だけのフェディバースのマイクロブログを作ろう！』
それぞれ500円でご用意してお待ちしております！！
@hongminhee@hollo.social · Reply to 洪 民憙 (Hong Minhee)'s post
ActivityPubサーバーを構築してみたいけれど、どこから始めればよいかわからない方には、Fedifyのチュートリアル『自分だけのフェディバースのマイクロブログを作ろう！』をおすすめします。包括的でステップバイステップのガイドで、完全に機能する連合型アプリケーションの構築方法を丁寧に解説しています。フェディバースに飛び込みたい開発者にぴったりです！
@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!
@hongminhee@hollo.social
오픈 소스 컨퍼런스 名古屋에서 Fedify 冊 《나만의 聯合宇宙 마이크로블로그 만들기》(自分だけのフェディバースのマイクロブログを作ろう！)가 完販되었다고…!
🍆@Yohei_Zuho@mstdn.y-zu.org
OSC名古屋、Fedify本完売した（6冊）
🍆@Yohei_Zuho@mstdn.y-zu.org
OSC名古屋、Fedify本完売した（6冊）
🍆@Yohei_Zuho@mstdn.y-zu.org
OSCでFedify本5冊売れた
🍆@Yohei_Zuho@mstdn.y-zu.org
無料というのもあってかFedify本がすごい売れる