@fedify@hollo.social · 8 following · 628 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:
@fedify@hollo.social
Hello, #fediverse! It's the official fedi account of the Fedify, an #ActivityPub server framework!
@fedify@hollo.social
Valtteri Laitinen (@valtlai) managed to get #Fedify running on #Cloudflare Workers!
@valtlai@valtlai.fi · Reply to Valtteri Laitinen's post
@thisismissem @fedify I got this working with the JSR package by adding a Temporal polyfill and stripping import attributes (see https://github.com/fedify-dev/fedify/issues/161#issuecomment-2618947880).
@valtlai@valtlai.fi · Reply to Valtteri Laitinen's post
@thisismissem @fedify I got this working with the JSR package by adding a Temporal polyfill and stripping import attributes (see https://github.com/fedify-dev/fedify/issues/161#issuecomment-2618947880).
@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:
All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged.
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.
@valtlai@valtlai.fi
Äh… Halusin koodata oman fediverseinstanssin @fedify-kirjastolla. Alustana olisi Cloudflare (Workers, KV, D1, Queues, R2). Workersin Node.js-yhteensopivuustilasta huolimatta Fedify ei kuitenkaan toimi: palauttaa ainakin syntaksivirheitä. Turhauttaa!
Nyt sitten forkkaan Fedifyn toistaiseksi ja yritän saada sen toimimaan. En nimittäin halua ohjelmoida ActivityPub-palvelinta ilman apukirjastoa, enkä mielelläni vaihtaisi hostausympäristöäkään toiseen.
@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:
All repositories have been transferred and GitHub's automatic redirects are in place, so existing links will continue to work. Also, the project's core functionality and development process remain unchanged.
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.
@fedify@hollo.social · Reply to 's post
@sash Here is our answer!
https://hollo.social/@fedify/0194a1d2-65ba-73f2-960d-82f322cf7e25
@fedify@hollo.social · Reply to Darius Kruythoff's post
We appreciate the thoughtful suggestions about moving Fedify to platforms like Codeberg that better align with the federation ideals our project upholds. These suggestions raise important points about corporate centralization and the broader FOSS ecosystem that we've carefully considered.
After thorough deliberation, we plan to keep Fedify's primary repository on GitHub for the foreseeable future. This decision stems from several practical considerations:
First, we aim to make Fedify as accessible as possible to potential contributors. While platforms like Codeberg represent important alternatives, GitHub remains the platform most developers are familiar with, particularly in the JavaScript/TypeScript ecosystem where Fedify operates.
Second, GitHub currently provides significant visibility benefits that help us reach more developers who could benefit from or contribute to Fedify. As a relatively new project, this broader reach is particularly valuable for building our community.
Additionally, our package registry JSR's provenance attestation feature, which we rely on for security guarantees, currently only supports GitHub Actions integration. This technical dependency would make migration particularly challenging at this time.
However, we recognize the value in supporting more decentralized platforms. As a middle ground, we are considering setting up a mirror repository on Codeberg. This would provide an alternative access point while maintaining our GitHub presence.
We're committed to regularly reassessing this position as the ecosystem evolves and as alternative platforms continue to mature.
@fedify@hollo.social · Reply to Darius Kruythoff's post
We appreciate the thoughtful suggestions about moving Fedify to platforms like Codeberg that better align with the federation ideals our project upholds. These suggestions raise important points about corporate centralization and the broader FOSS ecosystem that we've carefully considered.
After thorough deliberation, we plan to keep Fedify's primary repository on GitHub for the foreseeable future. This decision stems from several practical considerations:
First, we aim to make Fedify as accessible as possible to potential contributors. While platforms like Codeberg represent important alternatives, GitHub remains the platform most developers are familiar with, particularly in the JavaScript/TypeScript ecosystem where Fedify operates.
Second, GitHub currently provides significant visibility benefits that help us reach more developers who could benefit from or contribute to Fedify. As a relatively new project, this broader reach is particularly valuable for building our community.
Additionally, our package registry JSR's provenance attestation feature, which we rely on for security guarantees, currently only supports GitHub Actions integration. This technical dependency would make migration particularly challenging at this time.
However, we recognize the value in supporting more decentralized platforms. As a middle ground, we are considering setting up a mirror repository on Codeberg. This would provide an alternative access point while maintaining our GitHub presence.
We're committed to regularly reassessing this position as the ecosystem evolves and as alternative platforms continue to mature.
@fedify@hollo.social · Reply to Darius Kruythoff's post
We appreciate the thoughtful suggestions about moving Fedify to platforms like Codeberg that better align with the federation ideals our project upholds. These suggestions raise important points about corporate centralization and the broader FOSS ecosystem that we've carefully considered.
After thorough deliberation, we plan to keep Fedify's primary repository on GitHub for the foreseeable future. This decision stems from several practical considerations:
First, we aim to make Fedify as accessible as possible to potential contributors. While platforms like Codeberg represent important alternatives, GitHub remains the platform most developers are familiar with, particularly in the JavaScript/TypeScript ecosystem where Fedify operates.
Second, GitHub currently provides significant visibility benefits that help us reach more developers who could benefit from or contribute to Fedify. As a relatively new project, this broader reach is particularly valuable for building our community.
Additionally, our package registry JSR's provenance attestation feature, which we rely on for security guarantees, currently only supports GitHub Actions integration. This technical dependency would make migration particularly challenging at this time.
However, we recognize the value in supporting more decentralized platforms. As a middle ground, we are considering setting up a mirror repository on Codeberg. This would provide an alternative access point while maintaining our GitHub presence.
We're committed to regularly reassessing this position as the ecosystem evolves and as alternative platforms continue to mature.
@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post
Okay, since we couldn't get in touch with the @fedify account owner, we need a new name for our GitHub organization. Which alternative do you prefer?
Your suggestions for other names are welcome in the comments! We'll make the final decision based on your feedback.
| Option | Voters |
|---|---|
| fedify-js | 16 (11%) |
| fedify-sdk | 14 (10%) |
| fedify-framework | 15 (11%) |
| fedify-dev | 48 (34%) |
| fedify-org | 48 (34%) |
@fedify@hollo.social
#Fedify already uses the #Temporal API exclusively for representing temporal data.
https://developer.mozilla.org/en-US/blog/javascript-temporal-is-coming/
@hongminhee@hollo.social
The Date is dead, long live the Temporal!
https://developer.mozilla.org/en-US/blog/javascript-temporal-is-coming/
@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post
Here's a quick update on our GitHub organization plans: GitHub support has informed us they no longer process inactive username requests. We'll try reaching out to the current owner of @fedify account to see if we can work something out.
We'll keep you posted on how this goes! 🤞
@fedify@hollo.social
We're planning to move our GitHub repository to an organization account for better project management. We've requested GitHub support to help us acquire the inactive @fedify username for this purpose. (The attached screenshot is our formal request to GitHub support.)
If we successfully acquire @fedify, that will be our new organization name. If not, we'll choose an alternative name. We'll keep you updated on the progress!
In any case, we'll ensure a smooth transition with proper redirects from the current repository. Stay tuned for updates!
@hongminhee@hollo.social
If you'd like to support the development of @fedify or @hollo or @botkit, you can sponsor me on GitHub!
@08956495@infosec.exchange
If you are a #fediverse admin running libraries on #Fedify keep an eye on this: https://nvd.nist.gov/vuln/detail/CVE-2025-23221
@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post
FedifyのWebFinger実装における脆弱性CVE-2025-23221に対するセキュリティアップデート（1.0.14、1.1.11、1.2.11、1.3.4）をリリースいたしました。すべてのユーザー様におかれましては、お使いのバージョンに応じた最新版への速やかなアップデートを推奨いたします。
セキュリティ研究者により、FedifyのlookupWebFinger()関数において以下のセキュリティ上の問題が発見されました：
本セキュリティアップデートでは、以下の修正が実施されました：
以下のコマンドで最新のセキュアバージョンにアップデートできます：
# npmユーザーの場合
npm update @fedify/fedify
# Denoユーザーの場合
deno add jsr:@fedify/fedify
この脆弱性を責任を持って報告していただいたセキュリティ研究者の方に感謝申し上げます。迅速な対応が可能となりました。
本脆弱性の詳細については、セキュリティ勧告をご参照ください。
ご質問やご懸念がございましたら、GitHub Discussions、Matrixチャットスペース、またはDiscordサーバーまでお気軽にご連絡ください。
@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post
#Fedify 프레임워크의 #WebFinger 구현에서 발견된 보안 취약점 CVE-2025-23221을 해결하기 위한 보안 업데이트(1.0.14, 1.1.11, 1.2.11, 1.3.4)를 배포했습니다. 모든 사용자께서는 각자 사용 중인 버전에 해당하는 최신 버전으로 즉시 업데이트하시기를 권장합니다.
보안 연구자가 Fedify의 lookupWebFinger() 함수에서 다음과 같은 보안 문제점들을 발견했습니다:
이번 보안 업데이트에는 다음과 같은 수정 사항이 포함되어 있습니다:
다음 명령어로 최신 보안 버전으로 업데이트하실 수 있습니다:
# npm 사용자의 경우
npm update @fedify/fedify
# Deno 사용자의 경우
deno add jsr:@fedify/fedify
이 취약점을 책임감 있게 보고해 주신 보안 연구자께 감사드립니다. 덕분에 신속하게 문제를 해결할 수 있었습니다.
이 취약점에 대한 자세한 내용은 보안 권고문을 참고해 주시기 바랍니다.
문의 사항이나 우려 사항이 있으시다면 GitHub Discussions나 Matrix 채팅방, 또는 Discord 서버를 통해 언제든 연락해 주시기 바랍니다.
@fedify@hollo.social
We have released #security updates (1.0.14, 1.1.11, 1.2.11, 1.3.4) to address CVE-2025-23221, a #vulnerability in #Fedify's #WebFinger implementation. We recommend all users update to the latest version of their respective release series immediately.
A security researcher identified multiple security issues in Fedify's lookupWebFinger() function that could be exploited to:
The security updates implement the following fixes:
To update to the latest secure version:
# For npm users
npm update @fedify/fedify
# For Deno users
deno add jsr:@fedify/fedify
We thank the security researcher who responsibly disclosed this vulnerability, allowing us to address these issues promptly.
For more details about this vulnerability, please refer to our security advisory.
If you have any questions or concerns, please don't hesitate to reach out through our GitHub Discussions, join our Matrix chat space, or our Discord server.
@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post
自分だけのActivityPubを作りたいけど、何から始めれば良いのか分からないですか？Fedifyの公式チュートリアル「自分だけのフェディバースのマイクロブログを作ろう！」を読んでみてください！
@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post
자신만의 #ActivityPub 구현을 하고 싶지만, 어디서 시작해야 할지 모르겠나요? #Fedify 공식 튜토리얼인 〈나만의 연합우주 마이크로블로그 만들기〉를 읽고 따라해 보세요!
@fedify@hollo.social
Want to build your own #ActivityPub implementation, but don't know where to start? Read and follow #Fedify's official tutorial, Creating your own federated microblog, and get started!
@botkit@hollo.social · Reply to BotKit by Fedify :botkit:'s post
@botkit@hollo.social · Reply to BotKit by Fedify :botkit:'s post
@botkit@hollo.social
Introducing #BotKit: A #TypeScript framework for creating truly standalone #ActivityPub bots!
Unlike traditional Mastodon bots, BotKit lets you build fully independent #fediverse bots that aren't constrained by platform limits. Create your entire bot in a single TypeScript file using our simple, expressive API.
Currently #Deno-only, with Node.js & Bun support planned. Built on the robust @fedify foundation.
@fedify@hollo.social · Reply to Fedify: an ActivityPub server framework's post
Okay, now we have the official fedi account for BotKit: @botkit.
https://hollo.social/@botkit/01947252-0b0e-7b7e-98ce-a520ca388a0c
@botkit@hollo.social
@botkit@hollo.social
@fedify@hollo.social
Do we need a dedicated fedi account for BotKit?
| Option | Voters |
|---|---|
| Yes | 12 (75%) |
| No | 4 (25%) |
@aasatru@kbin.earth · Reply to JubilantJaguar's post
I feel like this is part of what makes @fedify one of the most important fediverse projects at the moment - it aims to keep everyone from having to do the same, overly complicated job of activitypub integration over and over and over again.
It's frustration that nobody wants to dig into old code, but I get frustrated having to re-work my own code from a year ago. So I guess I sympathize.
@cheeaun@mastodon.social
I guess @iss-location-bot now joins @FediChatBot as potentially the 2nd(?) bot built with @hongminhee 's #BotKit 🍻
Learn more:
- BotKit: https://botkit.fedify.dev/
- ISS Location bot repo: https://github.com/cheeaun/iss-location-bot
- Previous thread: https://mastodon.social/@cheeaun/113826068433133218
@hongminhee@hollo.social
One of #Fedify's long-term challenges is to get it to run on Cloudflare Workers as well.