I’m posting on behalf of another user on Reddit,u/TasmanianHorse, who’s exploring the possibility of integrating their platform (Echo, Pinterest alternative) into the Fediverse using ActivityPub.

I recommended the Fediverse to them earlier on,
and they’re interested in making their platform interoperable with existing services (like Mastodon, Lemmy, Peertube, Pixelfed, Loops, etc.), but are still in the early stages and looking for guidance.

Some of the questions that they had:

• What are the main challenges when implementing ActivityPub from scratch?
• Are there recommended libraries, frameworks, or starter projects to build on?
• How difficult is it to ensure compatibility with multiple Fediverse platforms?
• Any common pitfalls or things to avoid early on?
• Are there best practices for moderation, federation control, or scalability?

If anyone here has experience developing for the Fediverse or has worked with ActivityPub, your insights would be really appreciated.

Thanks in advance!

EDIT: They also have an e-mail address, that they have said that users can reach them at, if they have feedback /feature suggestions regarding Echo.

Email Address: sebastiantasmanian@gmail.com

I can only comment on tooling: fedify is very good, easy to get in and powerful enough for any usecase

https://fedify.dev/

Im no Dev, so I can't answer any of this.

But there is an active matrix group with LOTS of devs you can talk to: https://matrix.to/#/%23fediverse-developer-network:matrix.org

For a fediverse based technical support hub, have them post to @technical-discussion

More than happy to help. Fedify is good, but they might not be using js 🙂

Thanks very much

Thanks very much

You can find some useful tips in this guide: https://codeberg.org/ap-next/ap-next/src/branch/main/guide.md.>Any common pitfalls or things to avoid early on?Don't use JSON-LD.

implementing ActivityPub from scratch?

Why do that though? As someone mentioned there is https://fedify.dev/ but also Fedbox itself relying on microfed. So you can rely on existing small servers and libraries https://socialdocs.org/docs/ecosystem/libraries-overview

I would precisely suggest NOT to make your own solution if it's not your focus. If you are a Pinterest alternative, focus on the photo sharing experience (I naively assume that's the core) and rely on something well maintained to federate.