summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorzPlus <zplus@peers.community>2019-06-21 22:17:08 +0200
committerzPlus <zplus@peers.community>2019-06-21 22:17:08 +0200
commit686bcbf104d49dddb47bfc2da5b5b03c4ac59b99 (patch)
tree854944898f2abb7fc84da927e07a3f13da440b18
parent19e6d98aafe8ceb472c0a9ca711fe92f604bf2f9 (diff)
Add Follow and Push activities description.
-rw-r--r--specification/forgefed.md18
1 files changed, 17 insertions, 1 deletions
diff --git a/specification/forgefed.md b/specification/forgefed.md
index 6d5968d..ae376f9 100644
--- a/specification/forgefed.md
+++ b/specification/forgefed.md
@@ -70,9 +70,25 @@ ActivityPub. A client will send objects (eg. a Ticket) wrapped in a Activity
(eg. Create) to an actor's outbox, and in turn the server will take care of
delivery.
+5.1. Follow Activity
+
+The Follow activity is used to subscribe to the activities of a Repository.
+The client MUST send a Follow activity the a Person's outbox. The server
+in turn delivers the message to the destination inbox.
+
+5.2. Push Activity
+
+The Push activity is used to notify followers when somebody has pushed changes
+to a Repository.
+The client MUST send a Push activity the a Repository's outbox. The server
+in turn delivers the message to the Repository followers.
+
6. Server to Server Interactions
- TODO: how are these different than AP?
+6.1. Follow Activity
+
+The server receiving a Follow activity in a Repository's inbox SHOULD add the
+sender actor to the Repository's followers collection.
7. Acknowledgements