I'd add in projects like Emissary, Bonfire, or https://github.com/evanp/activitypub-bot . They can all be used to build Fediverse servers from building blocks.

I think other parts might be more piecemeal. I thing HTTP Signature libraries are awesome. https://github.com/social-web-foundation/activitystrea.ms is an AS2 library that I've used a lot, even though it's weird.

https://github.com/social-web-foundation/ap-components is a Web Components library for ActivityPub objects. Also kind of cool!

I think a lot of of building a Fediverse server -- or client! -- is implementing behaviour, which an engine like Fedify can do, but most libraries aren't going to do for you.

@julian It's been a great multi-implementer effort, both from the long-form text producers and the microblogging services.

@inkwell@piefed.social one warning about doing ActivityPub development with LLMs: codeberg.org blocks a lot of LLMs for training and for RAG/MCP. Since FEPs are hosted there, I've found that searching for information on FEPs will result in incorrect information.

@inkwell@piefed.social Hey, I'm really sorry for all this dogpile. You shouldn't be getting this kind of flack when you took the time to implement ActivityPub.

Thanks for your work. I'm trying it out as @evan@inkwell.social and I have to say it's a really lovely UI. I'll give any feedback I can on the ActivityPub implementation.