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.

@silverpill If you think there's a link that should be on activitypub.rocks, you can open a ticket here:

https://github.com/swicg/activitypub.rocks/issues

I'm glad to hear that you don't think of AP-next as a fork!

@evan There link was there before you removed it. And I have better things to do than opening tickets

@silverpill OK! I think you know how to get this changed if you want to. Good luck with your work.

@evan @silverpill I see it was @j12t who removed it. Maybe he can add it back? Seems like a trivial thing to do.
https://github.com/swicg/activitypub.rocks/commit/aed87b05133a161877c1e59bf4a7a5c24d64c09e

@liaizon they way to do this is the same way it got removed: whoever cares about it needs to file an issue, make their case in the issue (it does not have to be elaborate) and we see what comments they get. If there are no objections, and it is a small change (which it would be) it gets done. If there are objections, we need to resolve those eg by discussion in the regularly scheduled meeting. That’s what the TF is for.

@evan @silverpill

@j12t @evan
I have followed the procedure and opened a new issue to re-add @silverpill's AP guide... https://github.com/swicg/activitypub.rocks/issues/94