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. 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. Threadiverse Working Group Social Web Task Force for Threaded Discussions on the Fediverse

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…	44	93659	August 8, 2024
The ActivityPub Recommendation ActivityPub about	0	1057	September 12, 2019
Followers OrderedCollectionPage example ActivityPub	1	2	November 22, 2024
Minutes from 7 November 2024 WG Meeting Threadiverse Working Group	8	26	November 19, 2024
NextGen ActivityPub Social API Client to Server	17	208	November 17, 2024
Agenda Prep for November 2024 WG Meeting Threadiverse Working Group	2	44	November 17, 2024
Starter Kits ActivityPub	1	52	November 13, 2024
Disambiguating various interpretations of a "quote" feature [pre-FEP] ActivityPub	9	1176	November 13, 2024
Autonomous identity for the pluriverse based on OAuth/OIDC ActivityPub	19	3171	November 10, 2024
Negotiating protocols between actors or clients ActivityPub	45	146	November 10, 2024
Fediverse Relays ActivityPub	38	278	November 9, 2024
Status of a Robust ActivityPub Test Suite? Testing	17	2035	November 7, 2024
Events Interoperability: Validation, minimum requirements, common extensions ActivityPub	20	448	November 5, 2024
Update on pyfed library (for python) ActivityPub client , server	0	17	November 1, 2024
FEP Convergence (400e, 7888, 171b/Conversation Containers, 76ea) Threadiverse Working Group	160	130	October 31, 2024
Can we add a generated JSON list of FEPs to the repo? ActivityPub fep	12	77	October 28, 2024
ActivityPub: A Linked Data spec or JSON spec with Linked Data profile? ActivityPub	27	3006	October 28, 2024
What can a context collection contain, objects or activities? Threadiverse Working Group	0	13	October 25, 2024
Desired changes for a future revision of ActivityPub and ActivityStreams ActivityPub	138	530	October 25, 2024
Signaling clients attached to, and servers responsible for, the current actor ActivityPub	0	13	October 24, 2024
Murmurations protocol for directories and maps Server to Server	15	2314	October 23, 2024
Nomadic identity for the fediverse? ActivityPub	72	9181	October 11, 2024
Mechanism for representing Account Notes in Actor objects or relationships ActivityPub	3	42	October 9, 2024
Mastodon follow request (strange inbox path) Server to Server	10	42	October 9, 2024
Image fetching - is DOFV (Download on First View) AP-compliant? ActivityPub	17	108	October 8, 2024
Replacing AP+[reverse-engineering Mastodon defaults] with AP+FEPs ActivityPub	38	119	October 6, 2024
Does a maximally extensible/"extension-first" protocol even make sense? ActivityPub	3	21	October 6, 2024
Pre-FEP: Evolving OrderedCollection to be more useful ActivityPub	0	43	October 5, 2024
Minutes from 3 October 2024 WG Meeting Threadiverse Working Group	61	31	October 5, 2024
Pre-FEP: How to claim that an Object is part of a given Collection ActivityPub draft	6	26	October 4, 2024