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

fix typo

Browse source
This commit is contained in:
André Menrath 2023-10-10 16:05:05 +02:00
parent bd2448d950
commit aaab3ac1a4
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
architecture design proposal.md
View file

@ -117,7 +117,7 @@ All publicly accessible WordPress post types can become active for ActivityPub f
| **page** | O | O | - | - |
| **tribe_events** | O | - | X | O |
| **custom_event** | O | - | - | O |
| **...** | O | - | - | - |
| **…** | O | - | - | - |
**x:** Available transformers
**y:** Public and non-password protected WordPress post types
@ -180,7 +180,7 @@ ActivityPub knows several [actor types](https://www.w3.org/TR/activitystreams-co
The ActivityPub specification allows for immense flexibility in its application. As WordPress websites fulfill a variety of tasks and objectives, it is **challenging to implement control features and options for actor management that are more capable without sacrificing user-friendliness.**
## What features does our event federation project need?
## 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 (getting referred to via [attributedTo](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-attributedto)) if the `author`-actors are enabled, or create events (being the [actor](https://www.w3.org/TR/activitystreams-vocabulary/#dfn-actor) directly) if the `author`-actors are not enabled.
- Optional: As events are sometimes published a long time before they start, adding the possibility that events get announced again at a scheduled time before the start, e.g. by sending an `Announce` activity.