From 9af648673fa23ea4584bf283ce2a945ea19ad7c3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Andr=C3=A9=20Menrath?= Date: Thu, 5 Oct 2023 14:35:02 +0200 Subject: [PATCH] remove actor mapping proposal --- architecture design proposal.md | 16 +--------------- 1 file changed, 1 insertion(+), 15 deletions(-) diff --git a/architecture design proposal.md b/architecture design proposal.md index 393927e..4947dac 100755 --- a/architecture design proposal.md +++ b/architecture design proposal.md @@ -250,21 +250,7 @@ Anyway it seems the question has to be raised wheter activitypub should store a ## Conclusion - Anyway it seems the question has to be raised whether the ActivityPub plugin should store a history of all past and currently mapped actors. - Additionally, shouldn't the user have a detailed overview in each case if the actor management should get more complex? - - -## Proposal of how plugins register WordPress-actor types -TODO: This gives no information of how posts get dispatched to which actor. - -```php -interface ActorType { - public function getActorTypeName(); // returns name of the ActorType - public function listActorsOfThisType(); // returns array of actors of this type - public function listPostsForThisActor($actor); // returns array of posts -} -``` - -The registration of an actor type also registers every actor that is currently in the `listActorsOfThisType()`-list. - + # Appendix