Event-Federation/documentation
7
1
Fork 0
Code Issues 2 Pull requests Projects Releases Wiki Activity

Make actor-attributedTo relation more clear in actor mapping

Browse source
This commit is contained in:
André Menrath 2023-10-10 13:01:26 +02:00
parent 26a2ef658e
commit 6b444e2d43
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
architecture design proposal.md
View file

@ -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