silverpill@silverpill@mitra.social

The ap-next developer guide was removed from the https://activitypub.rocks website: https://github.com/swicg/activitypub.rocks/issues/63 (by the father of the Fediverse, no less).

The reason:

It's a fork outside the SocialCG.

This is utter nonsense. The guide refers to the original ActivityPub specification and even to SocialCG reports covering Webfinger and HTTP signatures. The other ap-next project is NomadPub - a collection of FEPs that significantly expand the capabilities of the protocol but don't diverge from the original spec.

However, since dissenting opinions about the present and the future of ActivityPub are now openly censored, a fork may indeed be necessary.

Summary card of repository ap-next/ap-next, described as: ActivityPub NextCodeberg.orgap-next/guide.md at mainap-next - ActivityPub Next
Phantasm@phnt@fluffytail.org

Replying to an earlier post

@silverpill You see, you can't have a good guide on our protocol that probably will give you a functional implementation at the end. It causes too much fragmentation in the network and competition for Mastodon, we can't have that. Instead, you must read the three specification documents, get more questions than answers in the end and give up with a disfunctional implementation.