Axismundi Actors

Axismundi Actors gives every identity this site knows about one stable identity record and one human profile hub (/@handle/), without collapsing that identity into the WordPress user account and without owning the content it points at. Each domain plugin keeps its own storage and screens; Actors holds identity and wires each archive in as a projection (Posts, Media, Notes, ...) under one actor. The identity URI (/actors/{uuid}, with /?ax_actor={uuid} as the plain fallback) is derived from an immutable UUID. The /@handle/ alias is registered once when the Actor is activated and does not follow later WordPress username changes, so an address that has been given out keeps working. What this version does

• An identity record and profile hub for each local person, built from their WordPress user account without becoming that account.
• Managed actors -- a Group, Organization or Service that belongs to no single user and is administered by the people listed as its managers.
• An acting Actor switch in the admin bar, so somebody who manages more than one identity can choose which one they are working as. It is not an account switch: no password is shared and the WordPress user does not change.
• WebFinger and NodeInfo endpoints, so other servers can find the identities this site publishes.
• A cache of remote actors this site has been asked about, with cached copies of their avatar and header images, and their follower/following counts where they publish them.
• Profile links with rel="me" verification, checked against the page the person entered.
• A JSContact Card at /@handle.jscontact for a local public Actor.

What this version does not do Nothing here sends anything to anybody. There is no activity ledger, no likes, no inbox or outbox processing, no follow, no HTTP signatures, and no delivery -- those belong to other plugins in the Axismundi suite. The site's own Instance Actor is seeded in a disabled state and has no screen, because what it should be has not been designed yet. Data, and what happens when a user is deleted Deleting a WordPress user does not delete the identity it belonged to. The identity is tombstoned instead: the record stays, marked as gone, and its URI keeps answering as gone rather than as never having existed. That is deliberate. An address that has been published to other servers should be able to say "this person is no longer here"; an address that simply disappears tells a reader nothing, and the same UUID could later be handed to somebody else.

1. Upload the plugin folder to /wp-content/plugins/, or install it through Plugins > Add New.
2. Activate it through the Plugins screen.
3. Go to Users > Actor Profile and activate an Actor for your account. This is where the handle is chosen; it is fixed once set.
4. Optionally, go to Users > Managed actors to create a Group, Organization or Service that is not tied to one account.

Activation creates this plugin's own database tables. Nothing is contacted on the internet during installation.

0.1.2

• Stop the actor management screen from creating an actor while rendering. It read a user id from the query string and created a record for it, so a link could make an administrator perform that write; the screen now only reads, and creation happens in the activation form, which carries a nonce.
• Sanitize profile-link names and addresses where the form is read, not only where they are saved.
• Pass every custom table name to the database through a prepared identifier placeholder rather than interpolating it into the query text.

0.1.1

• Sanitize filtered Actor display names and biographies immediately before rendering.
• Harden route parsing and align Group Directory render-template variable prefixes.

0.1.0

• First release.
• Identity records and profile hubs (/@handle/) for local people, built from the WordPress user account without becoming it, plus an immutable identity URI at /actors/{uuid} that survives a username change.
• Managed actors -- a Group, Organization or Service belonging to no single user and administered by the people listed as its managers.
• An acting Actor switch in the admin bar, checked again on every read so that a revoked manager stops publishing as that identity immediately.
• WebFinger and NodeInfo endpoints, and a JSContact Card at /@handle.jscontact for a local public Actor.
• Bounded discovery and caching of remote actors, with local copies of their avatar and header images and their published follower and following counts.
• Profile fields with rel="me" link verification.
• Deleting a WordPress user tombstones its identity rather than removing it, so an address that has been published answers as gone instead of as never having existed.