ActivityPub
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. 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.
Topic | Replies | Views | Activity | |
---|---|---|---|---|
Guide for new ActivityPub implementers
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… |
![]() ![]() ![]() ![]() ![]() |
38 | 65764 | September 22, 2023 |
Guide for ActivityPub users
This collaboratively-edited guide provides information on how to become an ActivityPub user. Adopting ActivityPub as a user can be a great way to start putting a more people-centred Internet into practice. Find and j… |
![]() |
0 | 16764 | February 8, 2020 |
The ActivityPub Recommendation |
![]() |
0 | 755 | September 12, 2019 |
ActivityPub Support for Static Sites |
![]() ![]() ![]() ![]() |
5 | 199 | September 24, 2023 |
Initiative: ActivityPub "Step On Board" Integration Guide |
![]() ![]() ![]() ![]() ![]() |
22 | 622 | September 17, 2023 |
Wiki: Collected feedback on interop testing, methods, living docs and specs
:point_right: This is a wiki post and anyone is encouraged to Edit and add additional sources. ActivityPub Test Suite Needs “Status of a robust ActivityPub test suite?” on SocialHub by Tim Chambers (@tchambers). … |
![]() |
0 | 1137 | September 1, 2023 |
Solved - New implementer looking for help getting Actor to load on Mastodon |
![]() |
1 | 119 | September 16, 2023 |
Web-based protocol handlers for ActivityPub resources |
![]() ![]() ![]() |
3 | 85 | September 16, 2023 |
Account Migration |
![]() ![]() ![]() ![]() ![]() |
74 | 1891 | September 16, 2023 |
Federation Fairness |
![]() ![]() ![]() |
3 | 134 | September 11, 2023 |
Documenting federation behavior in a semi-standard way? |
![]() ![]() ![]() ![]() ![]() |
23 | 4293 | September 11, 2023 |
Nomadic identity for the fediverse? |
![]() ![]() ![]() ![]() ![]() |
45 | 5228 | September 3, 2023 |
Replies: Expectations / Requirements |
![]() |
0 | 61 | September 2, 2023 |
Account Migration: Expectations / Requirements |
![]() ![]() ![]() ![]() ![]() |
13 | 717 | September 2, 2023 |
Flow for publishing first post to federation |
![]() ![]() ![]() |
4 | 118 | August 30, 2023 |
Signing follow activity requests |
![]() ![]() ![]() |
4 | 107 | August 28, 2023 |
The complex ways of interpreting the specs |
![]() ![]() ![]() ![]() |
3 | 115 | August 26, 2023 |
Property under tag |
![]() ![]() ![]() ![]() ![]() |
19 | 231 | August 18, 2023 |
Use cases of fep-8b32: Object Integrity Proofs |
![]() ![]() |
8 | 410 | August 16, 2023 |
Toward ActivityPub 2.0 |
![]() ![]() ![]() ![]() ![]() |
23 | 1107 | July 31, 2023 |
Preventing 'Extend, Extinguish': via License rules for specs + protocols |
![]() ![]() |
1 | 130 | July 27, 2023 |
Yet another HTTP signature Mastodon POST problem (golang) |
![]() ![]() |
5 | 119 | July 26, 2023 |
Disambiguating various interpretations of a "quote" feature [pre-FEP] |
![]() ![]() ![]() |
5 | 427 | July 25, 2023 |
Like Activity |
![]() ![]() ![]() ![]() |
15 | 388 | July 21, 2023 |
C2S/S2S Update Issues |
![]() ![]() ![]() |
4 | 135 | July 20, 2023 |
Making the Mention subtype more useful |
![]() ![]() |
1 | 98 | July 20, 2023 |
Formally defining a Hashtag type? |
![]() ![]() |
1 | 122 | July 20, 2023 |
Reconciling different roots of identity |
![]() ![]() ![]() ![]() ![]() |
13 | 465 | July 19, 2023 |
Using tags for microsyntax |
![]() |
0 | 79 | July 19, 2023 |
Stricter specifications for pagination of Collections and OrderedCollections |
![]() ![]() ![]() ![]() ![]() |
18 | 923 | July 18, 2023 |