Fedify: 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/

The translation of @monaco_koukoku's review on the Japanese version of Creating your own federated microblog:

I read about 70% of the Fedify book on the plane. It was carefully explained step by step, and I could easily understand the contents. Maybe it's because I have researched on implementing ActivityPub before, but I got the impression that I can create it easily. It is also good that there are plenty of ways to check how the implementation works. (I didn't know such a service existed…)

Fedify's only role is to speak ActivityPub, so you need to write your own UI and store data in a database (examples of each are included), but this also means that you can use any UI framework or relational database you like, which opens up a wide range of application possibilities. However, if Fedify does nothing too much, it will just be a hassle, so it is probably a good balance between the two. (Note: I'm saying this before I've even gotten around to doing it myself yet.)

https://fedibird.com/@monaco_koukoku/113378450321946172

This would propagate through @fedify to implementations (e.g., Hollo) where they would fail to lookup the @context for schema.org, which would prevent fetching Actor documents from GoToSocial 0.19.x

cc @gotosocial in case this is something you want to improve on your side

Fixed a rather gnarly bug in @fedify last night where schema.org's @context wasn't being resolved correctly because schema.org doesn't do content-neg and instead using link alternate headers to point to the JSON-LD context document. However, instead of using a fully qualified URL, it used a relative URL to the initial request, which caused Fedify to fail to fetch that context.

https://github.com/dahlia/fedify/pull/155

今日Fedify/Holloのブースに訪問してくれた皆様、本当にありがとうございました‼️機会があれば是非またお会いましょう！

#Fedify #Hollo #osc24tk

FedifyとHolloのブースです！

#Fedify #Hollo #osc24tk

初手Holloさん！！

#osc24tk でFedify本を入手した！​ ​

明日の飛行機の中で読もうかな。
朝が早いので爆睡の可能性もあるが…

The main way to do that is to use a library that implements ActivityPub for you, like Fedify. https://fedify.dev/

As someone who works mainly in the front-end, ActivityPup (and related) always felt quite overwhelming and complicated to understand. I’ve been playing around with #Fedify for the past week or so and the documentation is so good it all just clicked for me! (I think so, at least :p)

Really excited to see what people build as ActivityPub becomes more approachable!

https://fedify.dev

10月26日（土）に開催されるOSC 2024 Tokyo/FallにFedify/Hollo合同で出展します！可愛いFedifyのロゴのシールと『自分だけのフェディバースのマイクロブログを作ろう！』日本語版の紙の本を持って行く予定です。よろしくお願いします。

https://event.ospn.jp/osc2024-fall/

#Fedify #Hollo #osc24tk

I'm bringing along the Japanese version of the #Fedify tutorial, Creating your own federated microblog.

https://github.com/dahlia/fedify-microblog-tutorial-ja

I'm off to Tokyo tomorrow to attend OSC2024 Tokyo/Fall this Saturday!

https://event.ospn.jp/osc2024-fall/

#osc24tk

Due to the Internet Archive's unavailability, the https://purl.archive.org/socialweb/webfinger context is unable to be loaded, so a patch was made to preload (embed) the JSON-LD context. This patch was applied to #Fedify versions 0.15.3, 1.0.5, and 1.1.1, so please update if you are experiencing this issue.

Fedify 越来越强大了，官方甚至还出了一篇教程： https://fedify.dev/tutorial/microblog
#Fedify

dahlia/microblog: A simple federated microblog example using Fedify for educational purpose

https://github.com/dahlia/microblog

Windowsで試してみた

> This program is for educational purposes only. Do not use it for any other purpose, since it has not been tested for security.
だけどこれ普通に使えたら便利そう

https://fedify.dev/
@fedify

Want to build your own #ActivityPub software? Follow the tutorial for #Fedify, the ActivityPub server framework!

https://fedify.dev/tutorial/microblog

The version 1.1.0 of #Fedify, an #ActivityPub server framework, released! The key changes include:

• Added uility functions for traversing remote collections. See also the Traversing remote collections section in the docs.

• Added EmojiReact class to Activity Vocabulary API. [FEP-c0e0]

• Added successor property to the Actor types in the Activity Vocabulary API.

• Added DidService class to Activity Vocabulary API. [FEP-9091]

• Added Export class to Activity Vocabulary API. [FEP-9091]

• Added service property to the Actor types in the Activity Vocabulary API. [FEP-9091]

• The default time window for verifying HTTP Signatures of incoming requests is now an hour (was a minute). This new default window is according to the ActivityPub and HTTP Signatures document.

• In the fedify inbox command's web interface, the Raw Activity tab is added to show the raw JSON object of the received activity.

For details, see the full changelog as well!

#fedidev

The version 1.1.0 of #Fedify, an #ActivityPub server framework, released! The key changes include:

• Added uility functions for traversing remote collections. See also the Traversing remote collections section in the docs.

• Added EmojiReact class to Activity Vocabulary API. [FEP-c0e0]

• Added successor property to the Actor types in the Activity Vocabulary API.

• Added DidService class to Activity Vocabulary API. [FEP-9091]

• Added Export class to Activity Vocabulary API. [FEP-9091]

• Added service property to the Actor types in the Activity Vocabulary API. [FEP-9091]

• The default time window for verifying HTTP Signatures of incoming requests is now an hour (was a minute). This new default window is according to the ActivityPub and HTTP Signatures document.

• In the fedify inbox command's web interface, the Raw Activity tab is added to show the raw JSON object of the received activity.

For details, see the full changelog as well!

#fedidev

Let's create your own #ActivityPub implementation using #Fedify!

Even though I am a slow coder, it only took me about a month to create most of #Hollo's features in #Fedify. Having a framework makes a huge difference in productivity.

#fedidev

We now have #Hollo and #Fedify's official #Discord server! Join us now!

https://discord.gg/hGXXxUq2jK

The Japanese version of the #Fedify tutorial, Creating your own federated microblog, is now available in paperback!

Note that the AsciiDoc source of the book is fully open source, which is available at this repository!

https://fedibird.com/@hongminhee/113331365440336287

印刷所に注文した『自分だけのフェディバースのマイクロブログを作ろう！』の紙の本、到着した‼️

@fedify good to mention: there is also a Matrix space for those who are like "why discord?!"

https://matrix.to/#/#fedify:matrix.org

We now have #Fedify and #Hollo's official #Discord server! Join us now!

https://discord.gg/bhtwpzURwd

#Fedify now has an #AMQP driver! This means you can use #RabbitMQ as Fedify's message queue. To use it, first install the @fedify/amqp package, then set it up like below:

import { createFederation } from "@fedify/fedify";
import { AmqpMessageQueue } from "@fedify/amqp";
import { connect } from "amqplib";

const federation = createFederation({
  queue: new AmqpMessageQueue(await connect("amqp://localhost")),
  // ... other configurations
});

Oh, and we've also added results from AmqpMessageQueue to our benchmarks.

#fedidev

#Fedify takes 20 minutes for GitHub Actions to finish. What do you think?

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/

#Fedify now has an #AMQP driver! This means you can use #RabbitMQ as Fedify's message queue. To use it, first install the @fedify/amqp package, then set it up like below:

import { createFederation } from "@fedify/fedify";
import { AmqpMessageQueue } from "@fedify/amqp";
import { connect } from "amqplib";

const federation = createFederation({
  queue: new AmqpMessageQueue(await connect("amqp://localhost")),
  // ... other configurations
});

Oh, and we've also added results from AmqpMessageQueue to our benchmarks.

#fedidev

The #Fedify repository has reached 500 stars! Thank you everyone!

https://github.com/dahlia/fedify