
NLnet, @[email protected]
We are NLnet foundation. We support organisations and people who contribute to an open internet for all. If you are working on a project that helps fix the i…

We are NLnet foundation. We support organisations and people who contribute to an open internet for all. If you are working on a project that helps fix the i…
Problem/Motivation As explained in #3272173 . But focusing on first scenario: >> ... Create a Group (as in multiple users who are members of a Group defined by the Group module) controlled activitypub group type actor. Proposed resolution Be more generic when picking entity for an actor. Replace user by generic entity (but preserving all the existing and working code for user -> person case) Let other modules to implement their own kind of actors. New route proposal.
Problem/Motivation As explained in #3272173 . But focusing on first scenario: >> ... Create a Group (as in multiple users who are members of a Group defined by the Group module) controlled activitypub group type actor. Proposed resolution Be more generic when picking entity for an actor. Replace user by generic entity (but preserving all the existing and working code for user -> person case) Let other modules to implement their own kind of actors. New route proposal.
You could probably get there already with some hooks I think, but the code will change heavily in next couple of months.
That issue you mention has to land first and first steps have been taken to get there! I also need to refactor a couple of internal stuff regarding the plugins to make it even more flexible so everything can easily be configured in the UI and/or altered with a custom plugin.
After that, you will be able to expose any content to the Fediverse!