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

@hongminhee

白背景が抜かれてしまっているが、一応弊インスタンスも(-b付きで)fetchできるようになった b付きじゃなくてもいけるように整えていくぞ

If Fedify's docs should be translated, what languages should it be in?

What are your thoughts on Fedify's docs?

#Fedify #ActivityPub #fedidev

Visualize your server in the fediverse with the fedify node command and share it with us using the #FedifyNode hashtag!

(See also how to install the fedify command.)

#ActivityPub #fedidev

いろんな鯖さんのfaviconを描画したくてついにfedifyをインストールした
楽しい！かわいい
#FedifyNode

#FedifyNode
로고 출력 은근 잘 나왔다.

🤔
미스키 / 체리픽 안 됨

​​ #FedifyNode

#FedifyNode

파비콘을 이미지화해주는군요

fosstodon.org/@hongminhee/113401254560735839

#fedify
fedify node -b e5n.cc

https://fedify.dev/cli#fedify-node-visualizing-an-instance-s-nodeinfo

#FedifyNode

여러분의 인스턴스를 `fedify node` 커맨드를 써서 `neofetch` 스타일로 비주얼라이즈 해보고, #FedifyNode 해시태그와 함께 올려보세요!

`fedify` 커맨드를 깔려면 아래 링크에 적힌대로 따라하시면 됩니다!

https://fedify.dev/cli#installation

#FedifyNode

#FedifyNode

#FedifyNode

➜  ~ fedify node -b chpk.kur0den.net
✔ NodeInfo document fetched.
chpk.kur0den.net
================
Software:
  cherrypick v4.12.0
  https://github.com/kokonect-link/cherrypick
  https://github.com/kokonect-link/cherrypick
Protocols:
  activitypub
Outbound services:
  atom1.0
  rss2.0
Users:
  8 (total)
Local posts:
  41,891
Local comments:
  0
Open registrations:
  No

皆さんのフェディバース上のサーバーを`fedify node`コマンドで可視化して「#FedifyNode」ハッシュタグで共有してください！
QT: https://hollo.social/@fedify/0192e1c1-89aa-7915-be2e-4ca8524b5cfc [参照]

Visualize your server in the fediverse with the fedify node command and share it with us using the #FedifyNode hashtag!

(See also how to install the fedify command.)

#ActivityPub #fedidev

#fedify

minat tapi kayaknya terlalu overkill untuk 1 user instance, butuh postgres, redis dll.

misskey.ioに対するfedify nodeコマンドの出力結果。

It's the output of the fedify node command for fosstodon.org.

#FedifyNode

post your neofetch fedify node outputs!
https://fedify.dev/cli

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

• Added InboxContext.recipient property. It's useful for determining whether it is a shared inbox or a personal inbox, and whose personal inbox is invoked.

• Added getNodeInfo() function, a NodeInfo client.

• Added followedMessage property, which corresponds to _misskey_followedMessage, to Actor type in Activity Vocabulary API.

• Log messages now can be traced using LogTape's implicit contexts, which means you can filter log messages by requestId (an HTTP request identifier) or messageId (a background task identifier).

• Now you can choose an AMQP driver (which supports RabbitMQ) for the message queue in the fedify init command.

• Added the fedify node subcommand, which fetches the given instance's NodeInfo document and visualizes it in neofetch-style.

For details, see the full changelog as well!

Fedify 1.2.0 is available at JSR and npm.

#fedidev

Starting with the next release of #Fedify, v1.2.0, we will support traceable logs for easier debugging. Fedify's traceable logs are implemented using the implicit contexts introduced in LogTape 0.7.0, and most of the logs that Fedify records are given a requestId or messageId. This means that logs can be grouped into requests or background tasks for better analysis.

Want to try it out in advance? Try Fedify v1.2.0-dev.468+2e17cd69 (JSR & npm)!

#fedidev #ActivityPub

The next release of Fedify will introduce the fedify node command, which fetches the NodeInfo of the asked instance and visualizes it in neofetch-style.

The next release of Fedify will introduce the fedify node command, which fetches the NodeInfo of the asked instance and visualizes it in neofetch-style.

If you're running GoToSocial prior to v0.17.0, please, for the love of all good developers sanity, please upgrade.

GoToSocial prior to v0.17.0 had a broken JSON-LD context, which prevents federation from working correctly with some servers (e.g., anything built on Fedify)

#GoToSocial

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