The WordPress ActivityPub plugin by Matthias Pfefferle has been updated. It now allows you to @mention ActivityPub users and they will be notified of the mention in your blogpost, through ActivityPub.

This is useful. Yet, I’m holding out on using the plugin myself until three things are possible:

• Set the user name of the ActivityPub account: Now the username is the login name of the user doing the posting. I recognise using WP user names is a straightforward way of turning WP into an ActivityPub client, and prevents having to add addditional stuff to the database. As I use non-obvious user names for additional website security, having those exposed as ActivityPub users is undesirable however.
• Refuse follow requests: currently the plugin allows follows, and defaults to accepting all follows. As on my separate AP account I want to decide personally on follow requests.
• Determine flexibly which postings get shared through ActivityPub, and through which ActivityPub user account. The current set-up is that all postings get shared through ActivityPub. I’d rather be able to determine not just on a post by post basis what gets shared but also to have specific categories of postings to be shared through a specific account.

I want to actively use the affordances ActivityPub allows on top of those WordPress as blogging tool provides. For me that is the ability to use the different activity types that AP can support, and to use dealing with followers and follows to selectively disclose content to different groups of people.

My current usecase for this is to have a separate AP account that shares my travel plans (posted in an unlisted category on my site) with accepted followers. The first part requires selectively sharing a category of postings, the second part doing so to a group of accepted followers on an AP account that is meant for just this type of postings and not my general AP account.

The plugin will develop in this direction, but is not there yet. I am slowly going through the code of the plugin myself to understand its architecture and choices. Perhaps it will give me an idea either on how to build on its core to create the functionality locally I want for myself, or maybe (though my coding skills are likely not adequate for it) add to the plugin itself.