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

Compare commits

merge into: Event-Federation:main
Branches Tags
Event-Federation:main
Event-Federation:remove-actor-mapping-proposal
Event-Federation:actor_collision_new_actors
Event-Federation:delete_maybe_actos
...
pull from: Event-Federation:delete_maybe_actos
Branches Tags
Event-Federation:main
Event-Federation:remove-actor-mapping-proposal
Event-Federation:actor_collision_new_actors
Event-Federation:delete_maybe_actos

1 commit
main ... delete_may

Author SHA1 Message Date
ruru4143
a9a1875c2d changed 'maybe implementing actortypes' to 'implementing actor types' in princibles of changes 2023-10-03 16:23:35 +02:00
1 changed files with 2 additions and 2 deletions
Show stats Expand all files Collapse all files

4
architecture design proposal.md
View file

@ -43,7 +43,7 @@ The WordPress ActivityPub plugin
- should be aware (or even control) the whole chain from creating some content within WordPress to being published via ActivityPub. For sure, it should be the only plugin that directly sends and receives ActivityPub. - should be aware (or even control) the whole chain from creating some content within WordPress to being published via ActivityPub. For sure, it should be the only plugin that directly sends and receives ActivityPub.
- should not get any more complex by default, the out-of-the box functionality/features and simplicity should be similar to version 1.0.0. - should not get any more complex by default, the out-of-the box functionality/features and simplicity should be similar to version 1.0.0.
- offers other plugins the possibility to register custom transformers. - offers other plugins the possibility to register custom transformers.
- (maybe) offers other plugins the possibility to register new WordPress actor types, e.g. the `tribe_organizer` post type of [The Event Calendar](https://wordpress.org/plugins/the-events-calendar/). - offers other plugins the possibility to register new WordPress actor types, e.g. the `tribe_organizer` post type of [The Event Calendar](https://wordpress.org/plugins/the-events-calendar/).
- handles the controls collisions of actor names: - handles the controls collisions of actor names:
* collisions that are already present during activation of a WordPress actor type on the settings page * collisions that are already present during activation of a WordPress actor type on the settings page
* collisions that happen afterwards (e.g. a new user registering with the same username as the blog-wide actor) * collisions that happen afterwards (e.g. a new user registering with the same username as the blog-wide actor)
@ -261,4 +261,4 @@ The registration of an actor type also registers every actor that is currently i
## The approach of youtube-dl ## The approach of youtube-dl
[youtube-dl](https://github.com/ytdl-org/youtube-dl) is solving a similar problem with "extractors" that return data to the processing-chain of youtube-dl. They provide a base class that includes useful functions for common issues e.g. automatic testing, geo-bypassing, login/cookie/header management. [youtube-dl](https://github.com/ytdl-org/youtube-dl) is solving a similar problem with "extractors" that return data to the processing-chain of youtube-dl. They provide a base class that includes useful functions for common issues e.g. automatic testing, geo-bypassing, login/cookie/header management.
They can also chain extractors recursivly, like a extractor for mastodon videos, that gets the video from the post and returns the source of the video, that could be youtube, vimeo or anything else youtube-dl supports. They can also chain extractors recursivly, like a extractor for mastodon videos, that gets the video from the post and returns the source of the video, that could be youtube, vimeo or anything else youtube-dl supports.