From 6b444e2d4388ae844bafcd0d38c9e4c933a19217 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Andr=C3=A9=20Menrath?= Date: Tue, 10 Oct 2023 13:01:26 +0200 Subject: [PATCH] Make actor-attributedTo relation more clear in actor mapping --- architecture design proposal.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/architecture design proposal.md b/architecture design proposal.md index ac876ff..99d80f9 100755 --- a/architecture design proposal.md +++ b/architecture design proposal.md @@ -179,7 +179,7 @@ The specifications allow for a lot of flexibility in their use. As WordPress web ## What features does our event federation project need? - For maximum Mobilizon compatibility we would love to have simply an actor of type `Application`, preferable called `@relay@wordpress.site`, that announces all events. Nonetheless, in theory, a Mobilizon instance should have the capability to follow any other actor as well. More or less this can already be achieved with the current blog-actor. -- Additionally, for example, organizers in [The Event Calendar](https://wordpress.org/plugins/the-events-calendar/) could also offer their own actor of type `Organizer` or `Group` to publicize events, or create events if the `author`-actors are not enabled. +- Additionally, for example, organizers in [The Event Calendar](https://wordpress.org/plugins/the-events-calendar/) could also offer their own actor of type `Organizer` or `Group` to publicize events ([attributedTo](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-attributedto)), or create events if the `author`-actors are not enabled ([actor](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-actor)). - Optional: As events are sometimes published a long time before they start, adding the posibility that events get announced again at a scheduled time before the start, e.g. by sending an `Announce` activity. ## Other features