@fedify@hollo.social · 9 following · 895 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:
@LaurensHof@fediversereport.com
Fediverse Report – #102
FOSDEM and the fediverse match well together, some issues regarding data privacy and consent, and multi-network client Openvibe gets 800k in funding.
FOSDEM, the free event for open source software was this weekend in Brussels, with a large presence for the fediverse and the social web. There were three events, presentations by various fediverse software developers in the SocialWeb Devroom, an extra smaller event on Sunday for more presentations, and a more casual event on Sunday evening at Brussels Hackerspace. All the events were fully packed, showing the large amount of interest from the community for the fediverse and the social web. The Social Web Foundation has been the main initiator of these events.
Some thoughts and observations:
Two issues regarding consent and data processing this week. The first is with GoToSocial and fediverse statistics sites like fedidb.org and fediverse.observer. Some GoToSocial servers have blocked statistics sites from indexing their platforms via robots.txt, but the crawlers of fedidb.org and fediverse.observer ignore those. In response, the main GoToSocial server decided to serve up randomised numbers, messing up the statistics of these sites. Fedidb developer Daniel Supernault removed GoToSocial altogether from the statistics site, but does not seem to be willing to respect the opting out of crawling via robots.txt. The second is regarding the shutdown of FediOnFire, that displayed public posts from a relay in a format similar to one of Bluesky’s firehose visualisation tools.
The Pixelfed Kickstarter has seen some updates this week. First was the update that setting up a Pixelfed Foundation is now moved to the stretch goal of $200k CAD, and that for $300k CAD the stretch goal is to expand the team to hire additional developers. A few days later, developer Daniel Supernault said that the $300k CAD stretch goal is now to build a Tumblr alternative. That brings the goal of the Pixelfed Kickstarter to build four platforms: Pixelfed, Loops, Sup (an encrypted messaging platform) and an unnamed Tumblr alternative, as well as building a foundation and a developer testing kit with Pubkit. Moving the foundation to a stretch goal that has not been met yet does not feel great to me, as good governance of such large platforms is highly important. Adding a Tumblr alternative to another later stretch goal also makes me concerned that Supernault is taking on too much here, as that is a lot of products to build and maintain.
Openvibe, a client that combines your Bluesky, Mastodon, Nostr and Threads account into a single feed, has raised 800k USD in outside investment, with Automattic among the investors. Openvibe is an early mover in the space, and it’s a name I regularly see pop up when people recommend clients. However, open networks and open APIs means that it is hard to build a competitive moat. Still, most apps are hobby projects, and I’m curious how far Openvibe can push their app with the new funding.
That’s all for this week, thanks for reading!
@fediversereport@mastodon.social
New: Fediverse Report #102
This week's news:
- a large crowd for the #fediverse at #fosdem
- some controversies around data scraping on the fediverse
- @openvibe gets 800k in funding to further work on the multi-protocol client
@fedify@hollo.social · Reply to tesaguri 🦀🦝's post
@silverpill Yeah, as @tesaguri said, it's a property introduced by Fedibird, a Japanese fork of Mastodon.
@tkgka@universeodon.com
I’ve just contributed to Fedify. Consider supporting them too — every little helps! https://opencollective.com/fedify
@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.
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!).
Added the ability to customize WebFinger responses through the new mapAlias() API, giving you more control over how your actors are discovered.
Added support for shares, likes, and emojiReactions properties to the Object class, making it easier to access and traverse these interaction collections.
Document loader and context loader are now configurable through factory functions, giving you more control over how your application handles JSON-LD documents.
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 traversalContext.getNodeInfo() method for easier NodeInfo accessUser-Agent headers now automatically include your instance URL, making it easier for other servers to identify your instanceFor 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.
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!
You can install Fedify 1.4.0 from JSR or npm. Upgrade today and let us know what you think!
@hongminhee@hollo.social
Okay, I'm about to release #Fedify 1.4.0. Probably today or tomorrow?
@julian@fietkau.social · Reply to a Jedi named Thiago's post
@jedi@bolha.us · Reply to Julian Fietkau's post
@julian good to see more projects built on top of Fedify.
I started mine because I needed to dust off backend stuff. And I felt exactly what you are feeling about "looks slow", but it's been a nice journey learning how to create a Fediverse service.
Keep on going!
@markus@skvip.lol
Eg har nett støtta @fedify ! Dei har fleire kule prosjekt. @markus@prosa.skvip.lol køyrer på deira teneste @hollo.
English:
I've just contributed to #Fedify They have several cool projects. @markus@prosa.skvip.lol runs on their service #Hollo.
@fedify@hollo.social · Reply to Fedify: ActivityPub server framework's post
We've just set up our sponsors showcase! You can now find our wonderful sponsors:
These pages are automatically updated every hour. Thank you to all our sponsors for supporting #Fedify's development!
Want to be listed? Support us on Open Collective: https://opencollective.com/fedify.
@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@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/markdown-it-hashtag, a markdown-it plugin that parses and renders Mastodon-style #hashtags, just released 0.3.0! In this release, link, linkAttributes, and label callbacks became to take one more parameter, a markdown-it environment, which enables your hashtag rendering more flexible. For example, now hashtag links can be dynamically determined:
import MarkdownIt from "markdown-it";
import { hashtag } from "@fedify/markdown-it-hashtag";
const md = new MarkdownIt();
md.use(hashtag, {
link: (tag: string, env: any) => `${env.origin}/tags/${tag.substring(1)}`
});
const html = md.render("Your Markdown text with #hashtags!", {
origin: "https://example.com"
});
@fedify/markdown-it-hashtag 0.3.0 is available at both JSR and npm!
@andypiper@macaw.social
This is great - @fedify has launched an @opencollective to help sustain the project. This is a great library and framework that is helping many other projects grow into the #fediverse. Shout-out to @hongminhee! (also to @liaizon for posting about it as well)
@liaizon@social.wake.st
Today @fedify launched an @opencollective to support the project.
@hongminhee has been doing amazing work on it. 
Fedify has shown itself to be one of the most promising ways for other projects to become part of the #fediverse. If you liked seeing Ghost (@index) make such fast progress bringing in potentially thousands (millions?) of blogs and newsletters to the fediverse, this is what they are using behind the scenes! So lets support this project together!
https://opencollective.com/fedify
@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 · Reply to Fedify: ActivityPub server framework's post
We've just set up our sponsors showcase! You can now find our wonderful sponsors:
These pages are automatically updated every hour. Thank you to all our sponsors for supporting #Fedify's development!
Want to be listed? Support us on Open Collective: https://opencollective.com/fedify.
@cocoa_vrc@misskey.io
FediAuth、apsigが地味に未完成 (ActorのJSON-LDの問題もあるだろうけどFedify Inboxでの検証が通らない)なのでFedify使うことを検討中
@yamanoku@hollo.yamanoku.net
I've just contributed to Fedify. Consider supporting them too — every little helps! https://opencollective.com/fedify
@okin_p@si.okin-jp.net
I've just contributed to Fedify. Consider supporting them too — every little helps! https://opencollective.com/fedify
@fedify@hollo.social
@hongminhee@hollo.social
Thank you so much, @dansup! Really appreciate your support! Your work in the fediverse community has been inspiring, and having you as our first supporter means a lot.
@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
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: 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: 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.
