Feature Request: add addressing/visiblity to locally created comments

[Menrath]

What

Having more control for locally made comments.

1. Whether a comment should get federated at all
2. Set audience (addressing)

Why

The "Polls For ActivityPub" plugin, allows local WordPress users to vote even if for example only the Blog-Actor is active. But then all votes which are stored as a custom comment_type get federated.

Meanwhile I use a hack to set comment_meta->protocol to 'activitypub', but this is no clean solution.

Also I cannot just press "Reply in the Fediverse" and select something like "mentioned users only".

How

Provide a filters/hooks.

[Jiwoon-Kim]

https://kowporg.wordpress.com/?c=123

[Jiwoon-Kim]

Maybe each poll answer should have its own permalink like /?a=123. That way, it wouldn’t matter whether the actor is a remote user or a local WordPress user.

However, to correctly render the poll results on a proxy profile, perhaps we should prevent local WordPress users without ActivityPub capabilities from voting — especially if those votes can’t be federated properly.

Alternatively, we might need to separate the vote storage into different fields — although, personally, I wouldn't recommend that approach.

[Jiwoon-Kim]

"Perhaps it would be better if each ActivityPub object type had its own unique permalink structure?
For example:

• Post (article): ?p=123
• Note (long/short): ?n=123
• Media (Image, Video, Audio): ?m=123
• Poll (question): ?q=123

This could help distinguish object types more clearly, both for rendering and federation purposes."

[Jiwoon-Kim]

For activity types like Answer, I think a rough distinction could be made using comment_type = answer and protocol = local/remote. However, the problem is that even among local users, some may have ActivityPub capabilities while others do not — so it's not a clean separation after all

"Personally, I feel that a mid-level abstraction like is_activitypub_actor($user) isn't the cleanest solution. Instead, I think it makes more sense to refine the federation rules for user profiles more explicitly — for example, having separate toggles for enabling the blog profile, enabling user profiles globally, and enabling ActivityPub individually per user profile."

Federation Options

• Blog Profile – Enable federation for the site-wide blog actor (e.g., @blog@yourdomain.com)
• Admin Profile – Enable federation for the site administrator’s user profile. Serves as the superuser actor for instance-level identity and control.
• User Profiles – Allow individual users to federate their personal profiles (requires user-level opt-in)
• Moderation Bot Profile – Optional automated actor for federation of moderation logs or system messages.