@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:
🍆@Yohei_Zuho@mstdn.y-zu.org
技術書典オンラインが始まったけど、Fedify本みんな買っていってる
@fedilug@msky.ospn.jp
本日はオープンソースカンファレンス名古屋（ #oscnagoya ）当日です！
吹上駅から徒歩5分ほどの中小企業振興会館、第にファッション展示場で #FediLUG はブース出展、セミナーでのLT大会を開催予定です！
ステッカー、同人誌用意してお待ちしています！！
@fedilug@msky.ospn.jp · Reply to Fediverse Linux Users Group's post
今週末開催される、 #oscnagoya では #FediLUG ブースにて、
・有志8人による執筆のThinking Penguin Magazine Vol.0（500円）
・和条門さん（ @naoki_wjm@k.my-sky.blue ）による『さばかんライフ！』（1000円）
・ホンさん（ @hongminhee@hollo.social ）による『自分だけのフェディバースのマイクロブログを作ろう！』（500円）
も頒布いたします！
そのほかにもステッカーや各種チラシも扱っておりますので、ぜひ足をお運びください！！
🍆@Yohei_Zuho@mstdn.y-zu.org
Fedify本届いた〜
@fedify@hollo.social · Reply to just small circles 🕊's post
@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!
@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, documentationcomponent/ for different parts of Fedifyactivitypub/ 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.
@hongminhee@hackers.pub
2025 오픈소스 컨트리뷰션 아카데미 참여형 멘티를 오늘부터 6월 22일까지 모집한다고 합니다. 저도 Fedify 프로젝트의 멘토로서 참여하고 있으니, 관심 있는 분들은 많은 참여 부탁드립니다!
RE: https://hollo.social/@hongminhee/0196231c-8256-788e-bba1-0d3a9215524f
@hongminhee@hollo.social · Reply to 洪 民憙 (Hong Minhee)'s post
Fedify 프로젝트의 메인테이너로서 2025年 오픈소스 컨트리뷰션 아카데미 參與型 멘토團에 選拔되었습니다!
5月 21日(水)부터 6月 22日(日)까지 멘티도 募集한다고 하니 많은 參與 바랍니다.
@fedify@hollo.social · Reply to Antolius's post
@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:
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@hollo.social · Reply to Antolius's post
@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:
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@mastodon.social · Reply to Fedify: an ActivityPub server framework's post
@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?)
@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:
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@hollo.social
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.
@kokoi@n-kaiwai.work
HolloとかFedifyのお話おもしろかったのだ
우리의 코드를 찾아서 – 2막. 민희님과 Fedify & Hollo 알아보기 https://youtu.be/sqxR8zscSDo?si=nQRxPyV7kjplqy01
@fedilug@msky.ospn.jp
【. 技術書典18に出展します 📚 】
は6月1日に技術書専門イベントである、 #技術書典18 の お06 で合同誌『Thinking Penguin Magazine Vol.0』と @hongminhee@hollo.social さん著の『自分だけのフェディバースのマイクロブログを作ろう！』を頒布します！
どちらも500円で購入できます！！ぜひお立ち寄りください！
詳細はこちら : https://techbookfest.org/organization/7JepZT0g3C6qbddiLmkAwp
@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!
@sprints.fedidev.kr@ap.sprints.fedidev.kr
(2025-05-24) FediDev KR 스프린트 두 번째 모임
2025년 5월 24일 스프린트 모임의 기록을 남깁니다.
@hongminhee@hackers.pub
오늘 박현우 님(@lqez)께서 Fedify 로고로 배지를 만들어 와주셨습니다! FediDev KR 두 번째 스프린트 모임 오신 분들께 나눠드리고 있어요.
@hongminhee@hollo.social
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@hollo.social · Reply to Fedify: an ActivityPub server framework's post
Fedifyとは？Fedifyは、ActivityPubベースのフェデレーションサーバーフレームワークで、開発者が分散型ソーシャルネットワークである#フェディバース（#fediverse）にアプリケーションを簡単に統合できるよう支援します。複雑なActivityPubプロトコルの実装を簡素化し、開発時間を大幅に短縮します。MITライセンスの下で提供されるオープンソースプロジェクトです。
すでに様々なプロジェクトがFedifyを活用しています：
ActivityPubの実装をご検討中の方や、Fedifyプロジェクトとの協力にご興味のある方は、ぜひご連絡ください：
お客様の要件と目標に合わせたカスタマイズされた協力の可能性を一緒に探りましょう。
@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post
Fedify란?Fedify는 #ActivityPub 기반 연합형 서버 프레임워크로, 개발자들이 분산형 소셜 네트워크인 #연합우주(#fediverse)에 애플리케이션을 쉽게 통합할 수 있도록 돕습니다. 복잡한 ActivityPub 프로토콜 구현을 단순화하여 개발 시간을 크게 단축시킵니다. MIT 라이선스 하에 제공되는 오픈 소스 프로젝트입니다.
다양한 프로젝트들이 이미 Fedify를 활용하고 있습니다:
ActivityPub 구현을 고려 중이시거나, Fedify 프로젝트와 협력하고 싶으시다면 연락 주세요:
귀사의 요구사항과 목표에 맞는 맞춤형 협력 방안을 함께 모색하겠습니다.
@fedify@hollo.social
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.
Various projects are already leveraging Fedify:
If you're considering implementing ActivityPub or wish to collaborate with the Fedify project, please get in touch:
We're excited to explore customized collaboration opportunities that align with your requirements and goals.
@hongminhee@hollo.social · Reply to 洪 民憙 (Hong Minhee)'s post
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.
@hongminhee@hollo.social
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.
@fedify@hollo.social
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.
🍆@Yohei_Zuho@mstdn.y-zu.org
Fedify本、TPM入稿だん！
@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.)
@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:
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@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!
@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!
@fedify@hollo.social
We're pleased to announce that #Fedify has been included in the Nivenly Fediverse Security Fund program!
The @nivenly Foundation has launched a security bounty fund to support contributors who identify and help fix #security vulnerabilities in popular #fediverse software. Both Fedify and @hollo are among the selected projects that meet their responsible security disclosure requirements.
This program will run from April–September 2025, with bounties of $250–$500 USD for high and critical security vulnerabilities.
We're honored to be recognized alongside other established fediverse projects like Mastodon, Misskey, and Lemmy. This further encourages our commitment to maintaining strong security practices.
If you're interested in contributing to Fedify's security, please follow our responsible disclosure process outlined in our SECURITY.md file.
Learn more about the program:
https://nivenly.org/blog/2025/04/01/nivenly-fediverse-security-fund/
@nborboen@social.epfl.ch
What to learn more about the #fediverse and #ActivityPub? This tutorial (https://fedify.dev/tutorial/microblog) from @fedify is a really good starter. It explains how to implement a really simple #federated server and see how communication exchange are done with AP.
@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post
もしかしたらご存じないかもしれませんが、Fedifyには DiscordとMatrixのコミュニティがあります。ここでは、サポートを受けたり、機能について議論したり、ActivityPubやフェデレーテッドソーシャルネットワークについて話し合うことができます。
お好みのコミュニティにご参加ください。どちらのチャンネルでも、Fedifyやフェデレーション関連のトピックについて活発な議論が行われています。