Max sends follow request to jon

This UseCase shows the flow of a follow activity from an actor '@max@rdfpub.org' who wants to follow an actor '@jon@mast.org'

The UseCase describes the flow of a Activity-Pub Server that implements fep-4ccd
uc_follow1_follow-follow_activity
{
   "@context":"https://www.w3.org/ns/activitystreams",
   "id":"https://activitypub.academy/4d4070a9-522f-4117-ac66-e8d7dd8e2751",
   "type":"Follow",
   "actor":"https://activitypub.academy/users/john",
   "object":"https://dev.rdf-pub.org/resource/max"
}

  • The follow activity must have the target actor as a recipient. The target actor can be contained in one of the following predicates: as:to, as:bto, as:cc, as:bcc, as:audience

  • The activity pub server (in our case rdfpub.org) is responsible for delivering the activities to the recipients of the activity. Even if the target server is currently unavailable. The activity should then be stored and sent at a later time.
uc follow1 follow diagram1
Figure 1. uc_follow1_follow: Max sends follow request to jon

  1. The Actor @max@rdfpub.org tells SomeApp that he wants to follow @jon@mast.org.

  2. SomeApp sends a C2S as:Follow Activity to the outbox of Actor @max@rdfpub.org.

  3. The Activity-Pub Server 'rdfpub.org' sends a S2S as:Follow Activity to the inbox of @jon@mast.org

  4. The Activity-Pub Server 'rdfpub.org' add the as:Follow Activity to the pendingFollowing collection of Actor @max@rdfpub.org.