remove actor mapping proposal
This commit is contained in:
parent
464534f8a3
commit
9af648673f
1 changed files with 1 additions and 15 deletions
|
@ -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
|
||||
|
||||
|
|
Loading…
Reference in a new issue