From 3e02385fa8000cfeb15cf91e183df4cee69b304a Mon Sep 17 00:00:00 2001 From: silverpill Date: Sat, 17 Feb 2024 19:41:32 +0000 Subject: [PATCH] FEP-7628: Push and pull modes (#267) Better terminology. Credit goes to @bumblefudge Reviewed-on: https://codeberg.org/fediverse/fep/pulls/267 Co-authored-by: silverpill Co-committed-by: silverpill --- fep/7628/fep-7628.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/fep/7628/fep-7628.md b/fep/7628/fep-7628.md index d095a95..d009580 100644 --- a/fep/7628/fep-7628.md +++ b/fep/7628/fep-7628.md @@ -50,10 +50,10 @@ Upon receiving valid `Move` activity, all actors following `object` MAY un-follo This activity comes in two sub-types: -1. `Move` sent by the old actor. In this case, the old server needs to be online. -2. `Move` sent by the new actor. In this case, the old server doesn't need to be online, but the person using the actor SHOULD have a reserve copy of the follower list. +1. `Move` sent by the old actor (**push mode**). In this case, the old server needs to be online. +2. `Move` sent by the new actor (**pull mode**). In this case, the old server doesn't need to be online, but the person using the actor SHOULD have a reserve copy of the follower list. -Example (activity subtype 1): +Example (activity subtype 1, push mode): ```json { @@ -68,7 +68,7 @@ Example (activity subtype 1): } ``` -Example (activity subtype 2): +Example (activity subtype 2, pull mode): ```json {