I'm writing a #Fedify tutorial, and I keep saying things like “you don't need to know what Ed25519 is” and “you don't need to know what JWK is for this tutorial.” Would this be okay?
Edited 39d ago
fedidev
I feel that the current abstraction level of #Fedify is not high enough which makes the tutorial lengthy, so I'm considering adding a higher-level API. One way would be to add a façade to the @fedify/fedify package, and another way would be to create a sort of metaframework as a separate package (e.g., @fedify/start?).
Which way would be better?
Options: (choose one)
Edited 39d ago
What's the biggest thing that makes you hesitant to use #Fedify, an #ActivityPub server framework?
Options:
A good issue to contribute to #Fedify for the first time. Anybody interested?
Does anyone know of any docs or specs for the #EmojiReact activity type that #Misskey and #Pleroma use?
Q: Which does your #ActivityPub implementation implement, HTTP Signatures, Linked Data Signatures, or Object Integrity Proofs?
👀 Very interesting post visibility comparison table by Stefano, on this code review for adding Akkoma/Pleroma's Local-only posting on Phanpy https://github.com/cheeaun/phanpy/pull/657#discussion_r1745903955
I'm working on a Rust library for building ActivityPub apps:
https://codeberg.org/silverpill/mitra/src/branch/main/apx_sdk
This code was originally a part of Mitra, but over time I moved re-usable functions into independent packages and then started using them in other projects, Activity Connect and fep-ae97-client. Compared to activitypub-federation-rust, it is a low-level library with fewer dependencies, suitable for both servers and clients. The key feature is support for nomadic identity.
Currently there's no documentation and API is not well designed, but I will be improving it. The license is AGPL-3.0