#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
• Middleware for handling webhooks
• #NodeInfo protocol
If you're curious, take a look at the Fedify website! There's comprehensive docs, a demo, a tutorial, example code, and more:
Main #Threads differences to date with other #Fediverse platforms (focusing on non debatable issues):
1 - They are not #opensource
2 - They do not publish a #nodeinfo
3 - To date, they are only very partially federated: some accounts and only to be read from outside Threads
EDIT: 4 - Threads accounts are based on Instagram and when one joins they are offered to follow their IG friends, even those without a Threads account yet
This is the first release under the umbrella of #Automattic!
Thanks to Automattic and all the fantastic people who helped with this great release!
@mattwiebe for the amazing new blocks! @mediaformat for the http-signatures @jeremy for several Jetpack compatibilities @nuriapenya for the design of the settings and blocks @donnacavalier for all the texts and documentation @alex for a lot of big and small contributions
Extra-features (disabled by default) is somewhat confusing in #Fedilab.
This option allows to enable features that #Mastodon doesn't support (quotes, reactions, submit messages in a specific format, etc.)
But softwares like #Pleroma, #Akkoma, #GlitchSocial, #FireFish don't support (currently) same features.
We plan to use #NodeInfo to automatically enable features depending on the user's instance (ie: software).
A #Fediverse Enhancement Proposal has reached FINAL status:
FEP-f1d5: NodeInfo in Fediverse Software
" #NodeInfo is a #protocol intended to standardize upon a way to provide server-level metadata to the public. This enables tools and clients to utilize this metadata to assess server health or facilitate end-users choices about servers and software to use on the Fediverse."