Actor reject that someone wants to follow him (incl. follower info)

This UseCase shows the flow of rejecting that another actor follows you.

The UseCase describes the flow of a Activity-Pub Server that implements fep-4ccd
uc_reject_follow_activity
{
  "id" : "https://rdfpub.org/0819",
  "type" : [ "Reject" ],
  "actor" : "https://rdfpub.org/max",
  "attributedTo" : "https://rdfpub.org/max",
  "object" : {
    "id" : "https://rdfpub.org/0717",
    "type" : [ "Follow"],
    "actor" : "https://rdfpub.org/max",
    "attributedTo" : "https://rdfpub.org/max",
    "object" : "https://rdfpub.org/0815",
    "to" : "https://mast.org/jon"
  },
  "to" : "https://mast.org/jon",
  "@context" : [ "https://www.w3.org/ns/activitystreams" ]
}
uc reject follow diagram1
Figure 1. uc_reject_follow: Max reject the follow request to jon

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

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

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

  4. The Activity-Pub Server 'rdfpub.org' removes the C2S as:Reject Activity from the pendingFollowers Collection.