André Menrath

Thanks for reading through all my thoughts. :bow: Doing what you proposed would work almost, but for storing the `id`s of the `Follow` request (not of the Follower actor) one...

> It seems hard to explain it in text. > > It should work without helper tables, because I simply replaced the Follow_Request object (you introduced) with a `activitypub_pending_user_id` post...

If we then realize that nobody uses it we would maybe have a solution, too. ~~Edit: Seems like Mobilizon is not using the id, it is using the object. The...

> One more idea: why not use that to start an inbox/outbox custom post type and use that to store and process the request?!? At the moment I can't exactly...

> I am working on that anyway, because with comments support, we can no longer query the posts table for the Outbox Collection. For reference (I try to explain a...

> I am open to discuss all options. Maybe we should start them in the Discussion Board? I created a board: https://github.com/Automattic/wordpress-activitypub/discussions/623. As this is an import task that affects...

I am currently also preparing a pull request similar to this one with minimal changes to the codebase, but follow-management being restricted to the application actor. Besides that I also...

@pfefferle Any new thoughts on this meanwhile? Now I could find some time to draft an easier version of this focusing on follow management solely for the application actor, which...

> We are currently discussing our possibilities with different DB schemes. I will post an update as soon as we are sure about our options. Great! Than I'll focus on...

[Mobilizon](https://docs.joinmobilizon.org/contribute/activity_pub/#repliesmoderation) uses `repliesModerationOption` with `allow_all`, `closed`, `moderated`. PeerTube has a `commentsEnabled` field with `true` or `false` (Edit: which Mobilizon also has a fallback to!) We are currently investigating this as...