From 064092c37313c5010ea8acb310130dac865174d3 Mon Sep 17 00:00:00 2001
From: Petitminion <petitminion@riseup.net>
Date: Mon, 2 Sep 2024 13:28:06 +0200
Subject: [PATCH] updated to use pod servie actor

---
 docs/specs/domain-follow/index.md | 14 ++++++++------
 1 file changed, 8 insertions(+), 6 deletions(-)

diff --git a/docs/specs/domain-follow/index.md b/docs/specs/domain-follow/index.md
index 201cc39ab..c4cc02bfe 100644
--- a/docs/specs/domain-follow/index.md
+++ b/docs/specs/domain-follow/index.md
@@ -29,20 +29,22 @@ enterURL=>operation: User enters a remote pod URL
 reachable=>condition: Is the pod reachable?
 handleError=>subroutine: Backend handles the error
 showError=>subroutine: Frontend displays an error message
-processContent=>operation: The pod scans all accessible content
-userPlay=>operation: The user selects a card
-userFollow=>operation: The user follows the library or channel
-serverLoad=>operation: The pod follows loads the content into cache
+APfollowrequest=>operation: The pods are added to the DomainFollow table is the follow request succed
+activities=>operation: The followed pod send activities to the followers pods
 
 start->enterURL->reachable
-reachable(yes)->processContent
+reachable(yes)->APfollowrequest
 reachable(no)->handleError(right)->showError(top)->enterURL
-processContent->userPlay->serverLoad->end
 ```
 
 ### Backend
 
 FUNKWHALE_OBJECT_TYPES `Domain`
+`DomainFollow` table :
+- `target` : the remote pod service actor
+- `actor` : the pod service actor (maybe its not needed since it will alway be the local service actor. maybe instead of using db entrie we could add this has a model property)
+
+The follow request should respect AP protocol. 
 
 ### Frontend