Fedify: an ActivityPub server framework

@[email protected] · 7 following · 377 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.

Website	GitHub	JSR	npm
https://fedify.dev/	https://github.com/dahlia/fedify	https://jsr.io/@fedify/fedify	https://www.npmjs.com/package/@fedify/fedify

Fedify: an ActivityPub server framework

@[email protected] · Reply to Fedify: an ActivityPub server framework's post

내일 행사를 위해 급하게 처음으로 기여하는 분들을 위한 이슈를 만들고 있습니다!

Fedify 저장소의 이슈 목록.

• Display icon/image on fedify lookup [enhancement, good first issue]
• fedify node breaks favicon on terminal emulators without truecolor [bug, good first issue]
• Use Fedify to the latest version in example projects [good first issue]
• Specify engines property to package.json [good first issue]
• More examples [documentation, good first issue, help wanted] — Fedify 저장소의 이슈 목록. • Display icon/image on fedify lookup [enhancement, good first issue] • fedify node breaks favicon on terminal emulators without truecolor [bug, good first issue] • Use Fedify to the latest version in example projects [good first issue] • Specify engines property to package.json [good first issue] • More examples [documentation, good first issue, help wanted]

Fedify: an ActivityPub server framework

@[email protected]

내일 서울 서초구 오픈업 플레이그라운드에서 이뤄지는 Open Contribution Jam 2024에 #Fedify 메인테이너(@hongminhee)가 참여합니다. Fedify에 기여해보고 싶은 분들은 와주시면 메인테이너가 성심껏 도와드리겠습니다! 자세한 행사 정보는 아래 링크를 참고하시면 됩니다.

https://festa.io/events/6342

Fedify: an ActivityPub server framework

@[email protected]

내일 서울 서초구 오픈업 플레이그라운드에서 이뤄지는 Open Contribution Jam 2024에 #Fedify 메인테이너(@hongminhee)가 참여합니다. Fedify에 기여해보고 싶은 분들은 와주시면 메인테이너가 성심껏 도와드리겠습니다! 자세한 행사 정보는 아래 링크를 참고하시면 됩니다.

https://festa.io/events/6342

Fedify: an ActivityPub server framework

@[email protected]

We are going to add instrumentation support for #OpenTelemetry to #Fedify. What kind of spans or events would you like to be instrumented?

Fedify: an ActivityPub server framework

@[email protected]

Have you heard of Val Town? Val Town is a kind of code pastebin + serverless function.

Actually, #Fedify works just fine with Val Town. Here's a piece of ActivityPub software, implemented in about 170 lines of code, running on Val Town. Of course, it's built with Fedify!

Give it a follow @demo, and it will follow you back.

Curious to see how it was implemented? Check out the source code!

https://www.val.town/v/minhee/FedifyOnValTown

#ActivityPub #fedidev

Fedify: an ActivityPub server framework

@[email protected]

Starting with #Fedify 1.3.0, you'll be able to use different message queues for incoming and outgoing activities!

https://unstable.fedify.dev/manual/mq#using-different-message-queues-for-different-tasks

Using different message queues for different tasks

This API is available since Fedify 1.3.0.

In some cases, you may want to use different message queues for different tasks, such as using a faster-but-less-persistent queue for outgoing activities and a slower-but-more-persistent queue for incoming activities. To achieve this, you can pass FederationQueueOptions to the CreateFederationOptions.queue option.

For example, the following code shows how to use a PostgresMessageQueue for the inbox and a RedisMessageQueue for the outbox:

const federation = createFederation<void>({
queue: {
inbox: new PostgresMessageQueue(
postgres("postgresql://user:pass@localhost/db")
),
outbox: new RedisMessageQueue(() => new Redis()),
},
// ... other options
});

Or, you can provide a message queue for only the inbox or outbox by omitting the other:

const federation = createFederation<void>({
queue: {
inbox: new PostgresMessageQueue(
postgres("postgresql://user:pass@localhost/db")
),
// outbox is not provided; outgoing activities will not be queued
},
// ... other options
}); — Using different message queues for different tasks This API is available since Fedify 1.3.0. In some cases, you may want to use different message queues for different tasks, such as using a faster-but-less-persistent queue for outgoing activities and a slower-but-more-persistent queue for incoming activities. To achieve this, you can pass FederationQueueOptions to the CreateFederationOptions.queue option. For example, the following code shows how to use a PostgresMessageQueue for the inbox and a RedisMessageQueue for the outbox: const federation = createFederation<void>({ queue: { inbox: new PostgresMessageQueue( postgres("postgresql://user:pass@localhost/db") ), outbox: new RedisMessageQueue(() => new Redis()), }, // ... other options }); Or, you can provide a message queue for only the inbox or outbox by omitting the other: const federation = createFederation<void>({ queue: { inbox: new PostgresMessageQueue( postgres("postgresql://user:pass@localhost/db") ), // outbox is not provided; outgoing activities will not be queued }, // ... other options });

taichan

@[email protected]

fedify使ったAPubリレーの実装組みたいと思ってたの急に思い出した

$^Kur0den\d{4}$ :irai_houki_tyuu:'s avatar$

^Kur0den\d{4}$

@[email protected]

暇なときに読もうと思ってもってきたfedify本を読んでる
物理本、やっぱり良き

モナコ広告＠技術・雑談

@[email protected]

Fedify本、ついに完走！
他鯖のフォロイーの投稿を読めるようになったぞい :blobcatalt:

monaco koukoku's microblog
フォローボタン・投稿ボタン・マイクロブログのタイムラインがある。 — monaco koukoku's microblog フォローボタン・投稿ボタン・マイクロブログのタイムラインがある。

もちもちずきん 🍆

@[email protected]

帰ったらFedifyの本読むんや

段風桜 Dampuzakura（わかいい）

@[email protected]

じゃあもうそれこそFedifyでPixelfedみたいなやつ作るか

もちもちずきん 🍆

@[email protected]

Fedify使ってGoogle+そっくりさん作りたいかもしれない

洪民憙 (Hong Minhee)

@[email protected]

Star History of #Fedify, #Hollo, and #LogTape:

https://star-history.com/#dahlia/fedify&dahlia/logtape&dahlia/hollo&Date

Star History of Fedify, Hollo, and LogTape.

Renaud Chaput

@[email protected] · Reply to Renaud Chaput's post

@Montreal_Weather But if you plan to have this many bots, I would encourage you to not rely on Mastodon for those bots, but implement your own (very simple) ActivityPub software, it will be much easier for you.
For example see https://shkspr.mobi/blog/2024/02/a-tiny-incomplete-single-user-write-only-activitypub-server-in-php/, or https://fedify.dev for NodeJS

モナコ広告＠技術・雑談

@[email protected]

ようやくFedifyを触り始めた。WSL+DockerでNode.jsの環境をサクッと作って、コードはVSCodeで書けるようにした。後から環境設定が取っ散らからなくて良さそう。

Fedify: an ActivityPub server framework

@[email protected]

Flyers for #Fedify and #Hollo to be used at an open source event in Japan!

https://mstdn.y-zu.org/@Yohei_Zuho/113440544215822210

もちもちずきん 🍆

@[email protected]

@hongminhee お疲れ様です。HolloとFedifyのチラシが無事届きました〜
KOFなどで配布しますね

Fedify: an ActivityPub server framework

@[email protected] · Reply to Sebastian Lasse's post

@sl007 Okay, we're adding a mention for it!

洪民憙 (Hong Minhee)

@[email protected] · Reply to dansup's post

#FedifyNode for @loops!

The terminal screen of the output of the `fedify node loops.video` command:

loops.video
===========
Software:
loops v0.1.0
https://joinloops.org/
https://github.com/px-loops/loopd
Protocols:
activitypub
Users:
8,726 (total)
8,726 (active half year)
8,726 (active month)
Local posts:
1,195
Local comments:
819
Open registrations:
Yes — The terminal screen of the output of the `fedify node loops.video` command: loops.video =========== Software: loops v0.1.0 https://joinloops.org/ https://github.com/px-loops/loopd Protocols: activitypub Users: 8,726 (total) 8,726 (active half year) 8,726 (active month) Local posts: 1,195 Local comments: 819 Open registrations: Yes

洪民憙 (Hong Minhee)

@[email protected]

#FedifyNode for #PixelFed.social!

The terminal screen of the output of the `fedify node pixelfed.social` command:

pixelfed.social
===============
Software:
pixelfed v0.12.3
Protocols:
activitypub
Users:
124,264 (total)
22,376 (active half year)
7,212 (active month)
Local posts:
35,773,844
Local comments:
0
Open registrations:
No — The terminal screen of the output of the `fedify node pixelfed.social` command: pixelfed.social =============== Software: pixelfed v0.12.3 Protocols: activitypub Users: 124,264 (total) 22,376 (active half year) 7,212 (active month) Local posts: 35,773,844 Local comments: 0 Open registrations: No

💜 Wysteria 🪷🪷🪷

@[email protected]

neofetch, but for ActivityPub servers #FedifyNode

Screenshot of the terminal output of the fedify node command, which resembles Neofetch. Output:

baraag.net
==========
Software:
mastodon v4.3.1
Protocols:
activitypub
Users:
294,891 (total)
66,290 (active half year)
44,517 (active month)
Local posts:
14,734,899
Local comments:
0
Open registrations:
No — Screenshot of the terminal output of the fedify node command, which resembles Neofetch. Output: baraag.net ========== Software: mastodon v4.3.1 Protocols: activitypub Users: 294,891 (total) 66,290 (active half year) 44,517 (active month) Local posts: 14,734,899 Local comments: 0 Open registrations: No

Fedify: an ActivityPub server framework

@[email protected] · Reply to Sebastian Lasse's post

@sl007 That's good idea! We will add a list of projects that use Fedify soon!

Fedify: an ActivityPub server framework

@[email protected]

Starting with #Fedify 1.3.0, you can customize the User-Agent header for every HTTP request that Fedify makes.

https://unstable.fedify.dev/manual/federation#useragent

userAgent

This API is available since Fedify 1.3.0.

The options for making User-Agent header in the HTTP requests that Fedify makes. By default, it contains the name and version of the Fedify library, and the name and version of the JavaScript runtime, e.g.:

Fedify/1.3.0 (Deno/2.0.4)
Fedify/1.3.0 (Node.js/v22.10.0)
Fedify/1.3.0 (Bun/1.1.33)

You can customize the User-Agent header by providing options like software and url. For example, if you provide the following options:

{
software: "MyApp/1.0.0",
url: "https://myinstance.com/"
}

The User-Agent header will be like:

MyApp/1.0.0 (Fedify/1.3.0; Deno/2.0.4; +https://myinstance.com/)

Or, you can rather provide a custom User-Agent string directly instead of an object for options. — userAgent This API is available since Fedify 1.3.0. The options for making User-Agent header in the HTTP requests that Fedify makes. By default, it contains the name and version of the Fedify library, and the name and version of the JavaScript runtime, e.g.: Fedify/1.3.0 (Deno/2.0.4) Fedify/1.3.0 (Node.js/v22.10.0) Fedify/1.3.0 (Bun/1.1.33) You can customize the User-Agent header by providing options like software and url. For example, if you provide the following options: { software: "MyApp/1.0.0", url: "https://myinstance.com/" } The User-Agent header will be like: MyApp/1.0.0 (Fedify/1.3.0; Deno/2.0.4; +https://myinstance.com/) Or, you can rather provide a custom User-Agent string directly instead of an object for options.

wolf aliceif

@[email protected] · Reply to aliceif's post

console output for fedify node hollo.x27.one
on the left, an ascii art version of the orange on black x27 server icon
on the right, information

Software:
hollo v0.2.0
https://docs.hollo.social/
https://github.com/dahlia/hollo
Protocols:
activitypub
Outbound services:
atom1.0
Users:
2 (total)
1 (active half year)
1 (active month)
Local posts:
19
Local comments:
16
Open registrations:
No — console output for fedify node hollo.x27.one on the left, an ascii art version of the orange on black x27 server icon on the right, information Software: hollo v0.2.0 https://docs.hollo.social/ https://github.com/dahlia/hollo Protocols: activitypub Outbound services: atom1.0 Users: 2 (total) 1 (active half year) 1 (active month) Local posts: 19 Local comments: 16 Open registrations: No

Fedify: an ActivityPub server framework

@[email protected]

Starting with #Fedify 1.3.0, you can customize the User-Agent header for every HTTP request that Fedify makes.

https://unstable.fedify.dev/manual/federation#useragent

userAgent

This API is available since Fedify 1.3.0.

The options for making User-Agent header in the HTTP requests that Fedify makes. By default, it contains the name and version of the Fedify library, and the name and version of the JavaScript runtime, e.g.:

Fedify/1.3.0 (Deno/2.0.4)
Fedify/1.3.0 (Node.js/v22.10.0)
Fedify/1.3.0 (Bun/1.1.33)

You can customize the User-Agent header by providing options like software and url. For example, if you provide the following options:

{
software: "MyApp/1.0.0",
url: "https://myinstance.com/"
}

The User-Agent header will be like:

MyApp/1.0.0 (Fedify/1.3.0; Deno/2.0.4; +https://myinstance.com/)

Or, you can rather provide a custom User-Agent string directly instead of an object for options. — userAgent This API is available since Fedify 1.3.0. The options for making User-Agent header in the HTTP requests that Fedify makes. By default, it contains the name and version of the Fedify library, and the name and version of the JavaScript runtime, e.g.: Fedify/1.3.0 (Deno/2.0.4) Fedify/1.3.0 (Node.js/v22.10.0) Fedify/1.3.0 (Bun/1.1.33) You can customize the User-Agent header by providing options like software and url. For example, if you provide the following options: { software: "MyApp/1.0.0", url: "https://myinstance.com/" } The User-Agent header will be like: MyApp/1.0.0 (Fedify/1.3.0; Deno/2.0.4; +https://myinstance.com/) Or, you can rather provide a custom User-Agent string directly instead of an object for options.

Fedify: an ActivityPub server framework

@[email protected]

We're fixing all HTTP requests from Fedify to include the proper User-Agent header.

Poes

@[email protected]

single file activity pub:

1. https://gitlab.com/edent/activity-bot/-/blob/main/index.php?ref_type=heads from @Edent
2. https://www.val.town/v/minhee/FedifyOnValTown from @[email protected]

（仮）

@[email protected]

origin指定で自動的にNodeinfoを取ってきてパースするとか普通に便利な機能が多い

RE: https://misskey.io/notes/a04wampe1y1509us

（仮）

@[email protected]

fedify、既存のアプリにサクっとAP対応させるのに便利かもしれない

（仮）

@[email protected]

fedify、既存のアプリにサクっとAP対応させるのに便利かもしれない

Fedify: an ActivityPub server framework

@[email protected]

Have you heard of Val Town? Val Town is a kind of code pastebin + serverless function.

Actually, #Fedify works just fine with Val Town. Here's a piece of ActivityPub software, implemented in about 170 lines of code, running on Val Town. Of course, it's built with Fedify!

Give it a follow @demo, and it will follow you back.

Curious to see how it was implemented? Check out the source code!

https://www.val.town/v/minhee/FedifyOnValTown

#ActivityPub #fedidev

네이버 타이머

@[email protected]

Fedify lookup 생각보다 유용해 보이긴 하는데
(이거저거 들쑤셔볼때 액터 사이닝 안되어있어서 존나귀찮은적 많음)