From a58e716dadc8066b3df6b12cfb15c1991ad605e5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Andr=C3=A9=20Menrath?= Date: Fri, 6 Oct 2023 13:02:37 +0200 Subject: [PATCH] add note on blog-actor/relay actor --- 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 4c05473..7f2b5d5 100755 --- a/architecture design proposal.md +++ b/architecture design proposal.md @@ -181,7 +181,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. +- 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.