Starting this monday, I'm going to work for about 5 months on the ActivityPub module for Drupal: multi-user support, an API allowing you to use any (mobile) client, a new front-end and Drupal recipes, it will rock! Thank you @NLnet!
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…

nlnet.nl
@swentel @nlnet that is awesome news! I’ll keep an eye on the issue queue and help where I can.
Also happy to test with @ivory
@swentel ok, as I was curious why there was no work despite winning multiple grants
Allow any entity to be actor

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.

Drupal.org
That's part of a different grant which was awarded last year, but I haven't heard anything about it. There's a chance thoug that part might come to me, but I'll know more about that in a couple of weeks!
@swentel congratulations !
@swentel Something I've wanted to try for a while is to integrate it in our company website, and essentially have articles/blog posts be posts that are shared, or maybe a bit of automation that creates a post for each article if that's easier. Any opinions on whether that's feasible or a good idea? it's also related to https://www.drupal.org/project/activitypub/issues/3318782 as public author infos are profile nodes and not users, but it might be sufficient if I can just alter it a bit based on the connected profile
Allow any entity to be actor

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.

Drupal.org

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!