@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!
@hongminhee@fosstodon.org
It's the output of the fedify node command for fosstodon.org.
@aliceif@mkultra.x27.one
post your neofetch fedify node outputs!
https://fedify.dev/cli
@fedify@hollo.social
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@hollo.social
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)!
@thisismissem@hachyderm.io · Reply to colin mitchell's post
@muffinista that's quite sad news, but I understand it.
Is your fork of Mastodon open-source? (it should be but y'know)
I'm thinking maybe the next-generation botsin.space could be running something more specialised for bots?
e.g., something written on @fedify instead of mastodon
@fedify@hollo.social
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.
@fedify@hollo.social
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.
@thisismissem@hachyderm.io
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)
@fedify@hollo.social
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.)
＠技術・雑談@monaco_koukoku@fedibird.com
Fedify本、飛行機の中で7割くらい読んだ。
丁寧に順を追って解説されていて、すんなり内容が入ってきた。以前ActivityPubの実装を調べたことがあるからかもしれないが、すぐ作れそうな印象を受けた。実装の動作確認方法が豊富なのも良い。（こんなサービスあったんだ、ってなった）
Fedifyの役割はAPを喋ることだけなので、UIもDBへの保存処理も自分で書く必要があるが（それぞれ実装例は付いている）、逆に言えば好きなUIフレームワークやRDBを使えるということを意味しており、応用可能性が広がる。しかしFedifyが何もしなさすぎても面倒なだけなので、そこのバランスがよくできているということだろう。（※まだ自分で手を動かす前の段階で言っている）
@thisismissem@hachyderm.io · Reply to Emelia 👸🏻's post
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
@thisismissem@hachyderm.io
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.
@hongminhee@fedibird.com · Reply to 洪 民憙（ホン・ミンヒ）'s post
@hongminhee@fedibird.com · Reply to 洪 民憙（ホン・ミンヒ）'s post
@nt776@sv1.in-deep.blue
初手Holloさん！！
＠技術・雑談@monaco_koukoku@fedibird.com
#osc24tk でFedify本を入手した！ 
明日の飛行機の中で読もうかな。
朝が早いので爆睡の可能性もあるが…
@evanprodromou@threads.net · Reply to Anil Dash's post
The main way to do that is to use a library that implements ActivityPub for you, like Fedify. https://fedify.dev/
@pablo@sivar.cafe
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!
@fedify@hollo.social
10月26日（土）に開催されるOSC 2024 Tokyo/FallにFedify/Hollo合同で出展します！可愛いFedifyのロゴのシールと『自分だけのフェディバースのマイクロブログを作ろう！』日本語版の紙の本を持って行く予定です。よろしくお願いします。
@hongminhee@fosstodon.org · Reply to 洪 民憙 (Hong Minhee)'s post
I'm bringing along the Japanese version of the #Fedify tutorial, Creating your own federated microblog.
@hongminhee@fosstodon.org
I'm off to Tokyo tomorrow to attend OSC2024 Tokyo/Fall this Saturday!
@fedify@hollo.social
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.
@internetarchive@mastodon.archive.org
Latest update from @brewsterkahle (Oct 17, 5:58pm): https://blog.archive.org/2024/10/18/internet-archive-services-update-2024-10-17/
@eallion@e5n.cc
Fedify 越来越强大了，官方甚至还出了一篇教程： https://fedify.dev/tutorial/microblog
#Fedify
@dampuzakura@fedibird.com
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.
だけどこれ普通に使えたら便利そう
@hongminhee@fosstodon.org · Reply to 洪 民憙 (Hong Minhee)'s post
Want to build your own #ActivityPub software? Follow the tutorial for #Fedify, the ActivityPub server framework!
@fedify@hollo.social
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 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!
@fedify@hollo.social
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 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!
@hongminhee@fosstodon.org
Let's create your own #ActivityPub implementation using #Fedify!
@hongminhee@fosstodon.org
@hollo@hollo.social
@fedify@hollo.social
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!
@hongminhee@fedibird.com · Reply to 洪 民憙（ホン・ミンヒ）'s post
印刷所に注文した『自分だけのフェディバースのマイクロブログを作ろう！』の紙の本、到着した‼️
