#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
• #Node.js, #Deno, and #Bun support

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/

#fedidev

Fedify

Fedify is a TypeScript library for building federated server apps powered by ActivityPub and other standards, so-called fediverse.

^fedify.dev

Hello fedi. i am trying to solve the "fetch all replies" problem once and for all that makes the fedi feel a lot more desolate and with a lot more reply guys in it than it should be. this is take two, where before i had it triggered by a button, but now i think it should happen on the server-side whenever you expand a post. can anyone help me out figure out how to make this more efficient by only fetching posts that the server doesn't already have? i am not sure what the best strategy would be, and if anyone with experience doing efficient rails and SQL stuff could give me some pointers that would be gr8. the patch is actually extremely simple it just needs a few nice things to make it not DDoS everyone.

https://github.com/NeuromatchAcademy/mastodon/pull/44

Issue that describes approach: https://github.com/NeuromatchAcademy/mastodon/issues/43
Wiki page: https://wiki.neuromatch.social/Fetch_All_Replies

#MastoDev #FediDev #FetchAllReplies

Fetch all replies · Issue #43 · NeuromatchAcademy/mastodon

Pitch When expanding a post, the instance should fetch all replies from the host server. This issue is to move more general conversation out of #8 because i think that's the wrong approach Previous...

^GitHub

Woo Hoo! Check out Baby's first FEP...

If you're a #Fedidev developer, please check out FEP-3b86 at https://codeberg.org/fediverse/fep/src/branch/main/fep/3b86/fep-3b86.md

I'm working on "Remote Likes" and "Remote Shares" that help you jump back to your own home server to post when you find something cool on another website.

Imagine those "Share on Facebook" buttons, without all the ick.

I know it needs some work (that's what FEPs are for, yea?) so please read, comment, and help me get this over the finish line.

fep/fep/3b86/fep-3b86.md at main

fep - Fediverse Enhancement Proposals

^Codeberg.org

People like to say it’s all tech… but to really understand Communities on the Fediverse, we’ve done some research.

You can see what we’ve found in our new report, Mapping Fediverse Communities, available for download on our website: https://www.newsmastfoundation.org/blog-mapping-fediverse-communities/

Or check out the thread below for a summary 👇

Please boost and if you have any comments or want to offer your expertise, reach out!

#newsmast #socialmedia #mastodon #fediverse #fedidev #fediadmin #boost #communities

Weird bug in #Akkoma and #Mastodon interaction, thought #FediStaff / #Staff, #FediDev, and #FediMod / #Moderation people might want to see this.

Got a #report about a user saying things that were upsetting people, noticed it was from another instance, realized that I had access to the actual account that had sent it. Not sure what this is or why, didn't even realize #ActivityPub supported signed reports (I'd honestly like to get more), but obviously that's a risky thing if they didn't know it was happening and didn't know why.

Does anyone know what this is?