Axismundi Object Projections

Axismundi Object Projections turns a WordPress object -- a post, an attachment, an archive, a folder -- or an Axismundi Actor into an ActivityStreams 2.0 object or collection, so that the URL it already has can answer with JSON-LD when something asks for it. It owns representation and nothing else: a transformer registry, the URIs objects and collections are named by, and the single renderer that writes the JSON. What a thing is stays with the plugin that stores it; this decides how it is described to a reader that speaks ActivityStreams. This plugin needs Axismundi Actors. It resolves the identities an object names -- its author, the accounts it mentions, the Actor documents it serves -- and without that registry there is nobody for any of them to refer to. Axismundi Activities is optional, and adds four things. Without it a published post is public and is projected as such, which is this plugin's own default. With it, the four authored visibility levels decide who a post is addressed to, an Actor's outbox and follow collections have contents rather than being empty, an object states who may quote it, and an object says who published it. Nothing here breaks when it is absent; less is said. That last one is worth stating plainly: who an object is attributed to is decided by whatever recorded its publication, not derived here from the WordPress author. An object nobody has published has no attributedTo -- it is readable, it simply was not published by anyone. What this version does

• Content negotiation on the URL a post already has. Ask for application/activity+json and the same address answers with JSON-LD instead of HTML.
• A Core Post to Article transformer, and an optional adapter for Axismundi Media Library attachments.
• A post's own media, listed as attachments so a reader can fetch what the body shows: the featured image and the media blocks the author placed. Only media this site holds -- a hotlinked image is left in the text, because its type and size cannot be stated.
• Collections: an Actor's outbox, followers and following, a shared media folder at a stable UUID route, and a replies collection. An Actor document always names them; without an Activity ledger they answer empty rather than 404.
• The relations that make a document readable in context -- hashtags, mentions, thread edges, reply context, and quote context -- kept as their own records rather than parsed out of content each time.
• A remote object repository: URI-keyed, rebuildable observations of objects this site has been told about, for administrators to inspect under Tools > Remote Objects.
• An administrator can probe a remote collection and its first page without storing the collection, following its item URLs, or downloading anything binary.

What this version does not do There is no Activity ledger, no inbox write handling, no Follow/Like/Announce state, no HTTP signatures, and no delivery. Those belong to Axismundi Activities and to the ActivityPub transport boundary. Nothing here signs or sends an Activity. Alongside the official ActivityPub plugin Both plugins negotiate the same canonical URLs, and two answers for one address is worse than either answer alone. So when the official ActivityPub plugin is active, this plugin's standalone negotiator turns itself off and leaves those URLs to it, while the registry and renderer stay available. Nothing here overrides or replaces that plugin's object ids. What is stored about other people's documents An observation of a remote object is a cache, not a record: it is keyed by the remote URI, which stays canonical, and it can be rebuilt by fetching again. Observations expire, and a scheduled daily task deletes the expired ones along with anything left pointing at them. Remote media is never downloaded and never hotlinked. A cached object's attachments are described -- type, size, the text the author wrote about them -- and not fetched. Where a cached object is shown locally at all, it is shown noindex, only for objects that were addressed publicly, and only as a courtesy view beside the remote original.

1. Install and activate Axismundi Actors first. This plugin projects identities from that registry and does very little without it.
2. Upload this plugin folder to /wp-content/plugins/, or install it through Plugins > Add New, then activate it.
3. Nothing else is required. A published post is projected straight away; ask its URL for application/activity+json to see the result. It carries no attributedTo until something records who published it. Add Axismundi Activities for that, and for the four authored visibility levels and an Actor outbox with activities in it, and the official ActivityPub plugin with Axismundi ActivityPub Bridge to send and receive.
4. Remote observations, where there are any, are listed under Tools > Remote Objects.

Activation creates this plugin's own database tables. Nothing is contacted on the internet during installation, and deactivation removes the scheduled tasks it added.

0.1.2

• Server-rendered block output is escaped where it is printed, with an allowlist that covers what these blocks emit. The stock post allowlist removes the template element and the Interactivity API directives, so it is not used here.
• Body decoration filters run before sanitizing rather than after it, so nothing a filter adds can reach the page unsanitized.
• Who an object is attributed to now comes from whatever recorded its publication instead of being derived from the WordPress post author. The two agree only while every account has one identity, and they stop agreeing as soon as anyone publishes as an organisation.
• A post whose author has no Actor is projected and readable, without an attributedTo, rather than refused. It is not published to anyone.
• The site Actor is no longer a fallback author. It is an application identity, not a person who writes posts.

0.1.1

• Background acquisition is now a setting, off by default. While it is off this site contacts a remote server only when an administrator asks it to under Tools > Remote Objects. Turning it off also clears anything already queued.
• A post publishes its own media as attachments: the featured image and the media blocks the author placed, and only media this site holds.
• A published post is projected with Axismundi Actors alone; an Actor document always names its outbox, followers and following, which answer empty without an Activity ledger.
• A product can claim this projection for an object whose context it owns, instead of rebuilding it. Axismundi Forum publishes its Topics that way.
• A quote of the author's own post is recognised as approved, as FEP-044f allows, when both authors are known here.
• Filtered card templates and interaction controls are now named blocks rather than markup, so what reaches the page is always something a registered block rendered.

0.1.0

• First release.
• Content negotiation on existing WordPress object URLs, so a post's own address answers with ActivityStreams JSON-LD when asked for it, and a transformer registry with a single renderer behind it.
• A Core Post to Article transformer, and an optional adapter for Axismundi Media Library attachments.
• Collections: shared media folders on a stable UUID route, a replies collection, and the representation of an Actor outbox where Axismundi Activities supplies one.
• Hashtags, mentions, thread edges, reply context and quote context stored as their own records rather than re-derived from content.
• A URI-keyed repository of remote object observations, with administrator inspection under Tools > Remote Objects and a remote collection probe that stores nothing.
• Cached remote media is described and never downloaded or hotlinked; observations expire and are purged daily.
• The standalone negotiator disables itself when the official ActivityPub plugin is active, so that one URL keeps one answer.