ActivityPub

Server to Server This protocol is used to distribute activities between actors on different servers, tying them into the same social graph. Testing This category serves to broadly discuss test practices that help increase Fediverse interoperability. Threadiverse Working Group Social Web Task Force for Threaded Discussions on the Fediverse Client to Server This protocol permits a client to act on behalf of a user. E.g., a mobile app to interact with a social stream of the user’s actor.

Topic	Replies	Views	Activity
Guide for new ActivityPub implementers ActivityPub documentation , explanation This is an informal guide to help new implementers get up to speed with the ActivityPub specification (published as a W3C Recommendation) and how to build projects with ActivityPub support. :information_source: No…	47	118009	July 11, 2025
The ActivityPub Recommendation ActivityPub about	0	1101	September 12, 2019
FEP-be68: Audio Objects Server to Server	10	56	April 5, 2026
FEP-1a11: Send Announces Containing Many Activities ActivityPub	8	29	April 2, 2026
Events Interoperability: Validation, minimum requirements, common extensions ActivityPub	38	779	March 23, 2026
implement account portability ActivityPub	0	19	March 22, 2026
PortaFed: Cryptographic Account Portability for ActivityPub — FEP Draft for Review ActivityPub fep	0	14	March 22, 2026
Proposal: Explore page with filterable FEP table ActivityPub	7	54	March 22, 2026
FEP-2a62: signed account migration ActivityPub draft , fep	0	15	March 22, 2026
Loops ships federated Starter Kits ActivityPub	0	13	March 22, 2026
How to participate in the W3C Working Groups on AP ActivityPub	11	93	March 22, 2026
FEP-db70: RemoveAll Collection Activity ActivityPub	5	79	March 21, 2026
Fep-c07e: add product type to object ActivityPub draft , fep	12	78	March 18, 2026
FEP-34ec: Notification Collection Endpoint ActivityPub	18	46	March 17, 2026
ActivityPub API: Avoid Misconception Client to Server w3c , client	0	15	March 17, 2026
FEP-34c1: Collection Filtering using TREE Hypermedia Vocabulary ActivityPub	9	54	March 15, 2026
Replacing HTTP Signatures with Bearer tokens (or OCaps)? ActivityPub	5	87	March 14, 2026
Using AP federation to re-unify fediverse dev discussion across multiple forums Client to Server	3	35	March 5, 2026
FEP-a427: Server Domain Move ActivityPub	18	71	March 4, 2026
Could Hypermedia-Driven Application architecture be useful for AP C2S? Client to Server	4	39	March 2, 2026
FEP-ee3a: Exif metadata support ActivityPub fep	8	126	March 1, 2026
Possible C2S Implementation in LAUTI Client to Server	3	46	February 27, 2026
ActivityPub versus Fediverse. Interoperability in Practice ActivityPub fediverse	0	34	February 22, 2026
How to federate warnings? Server to Server	3	71	February 9, 2026
Thoughts on ActivityPub + Dating apps Server to Server	8	264	February 9, 2026
FEP-4f05: Soft Deletion ActivityPub draft , fep	24	169	February 7, 2026
Follow application actor has a way to get public activities Server to Server	1	21	February 5, 2026
RFC 9421 HTTP signatures in 2026 Server to Server	23	203	February 3, 2026
Nomadic identity for the fediverse? ActivityPub	97	10060	February 2, 2026
FEP-8c13: Context-Authority Routing with Object Integrity Proofs for Restricted Threads ActivityPub	3	40	January 23, 2026