ActivityPub

Testing This category serves to broadly discuss test practices that help increase Fediverse interoperability. Server to Server This protocol is used to distribute activities between actors on different servers, tying them into the same social graph. 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	102727	August 8, 2024
The ActivityPub Recommendation ActivityPub about	0	1070	September 12, 2019
FEP-4f05: Soft Deletion ActivityPub draft , fep	4	34	May 5, 2025
Oneboxes and URI separators are not synchronised when federated Server to Server discourse	1	23	May 4, 2025
Exposing edit history via Activitystreams ActivityPub	5	409	April 29, 2025
Friendship and other non-follow relationships ActivityPub fep	9	50	April 18, 2025
The Block activity, how's that supposed to work? Server to Server	15	699	April 18, 2025
Posts are only showing in replies and not in profile ActivityPub	2	21	April 9, 2025
FEP-1024 Peer to Peer Fediverse Identities ActivityPub draft , fep	5	202	April 9, 2025
Changeable usernames? Server to Server	62	5513	April 4, 2025
Agenda Prep for April 2025 WG Meeting Threadiverse Working Group	2	28	April 3, 2025
Moving topics Threadiverse Working Group	6	17	April 2, 2025
Who should I send Delete activities to? Server to Server	11	42	March 25, 2025
FEP Implementation Metadata ActivityPub fep	1	39	March 16, 2025
Fediverse Relays ActivityPub	46	639	March 13, 2025
Static file ActivityPub ActivityPub server	22	3213	March 12, 2025
Can we add a generated JSON list of FEPs to the repo? ActivityPub fep	15	109	March 12, 2025
FEP-1d80: Feed Actor - a way to federate a collection of Group actors ActivityPub draft , fep	16	92	March 12, 2025
Algorithmless content sorting ActivityPub fep	3	49	March 11, 2025
The state of conversational contexts (February 2025) Threadiverse Working Group	34	103	March 11, 2025
Multi - dimensional reputation / expertise ActivityPub fep	1	19	March 9, 2025
Minutes from 6 March 2025 WG Meeting Threadiverse Working Group	0	20	March 6, 2025
Agenda Prep for March 2025 WG Meeting Threadiverse Working Group	2	19	March 6, 2025
Addressing confusion between `Create` and contained object Server to Server	4	45	March 3, 2025
Negotiating protocols between actors or clients ActivityPub	46	177	March 1, 2025
Key pair for every actor vs single instance-wide key pair Server to Server	10	80	February 26, 2025
Is there a specification for location attributes? ActivityPub	4	63	February 24, 2025
Content formatting when federating out Threadiverse Working Group	22	335	February 24, 2025
What is the current spec for remote follow? Server to Server	22	2278	February 23, 2025
Help debugging why mastodon isn't finding an actor Testing	12	126	February 21, 2025