Axismundi Object Projections turns a WordPress object -- a post, an attachment, an\narchive, a folder -- or an Axismundi Actor into an ActivityStreams 2.0 object or\ncollection, so that the URL it already has can answer with JSON-LD when something asks\nfor it.<\/p>\n\n
It owns representation<\/strong> and nothing else: a transformer registry, the URIs objects and\ncollections are named by, and the single renderer that writes the JSON. What a thing is<\/em>\nstays with the plugin that stores it; this decides how it is described to a reader that\nspeaks ActivityStreams.<\/p>\n\n This plugin needs Axismundi Actors.<\/strong> It resolves the identities an object names -- its\nauthor, the accounts it mentions, the Actor documents it serves -- and without that registry\nthere is nobody for any of them to refer to.<\/p>\n\n Axismundi Activities is optional, and adds four things.<\/strong> Without it a published post is\npublic and is projected as such, which is this plugin's own default. With it, the four\nauthored visibility levels decide who a post is addressed to, an Actor's outbox and follow\ncollections have contents rather than being empty, an object states who may quote it, and an\nobject says who published it. Nothing here breaks when it is absent; less is said.<\/p>\n\n That last one is worth stating plainly: who an object is attributed to is decided by whatever\nrecorded its publication, not derived here from the WordPress author. An object nobody has\npublished has no There is no Activity ledger, no inbox write handling, no Follow\/Like\/Announce state, no\nHTTP signatures, and no delivery. Those belong to Axismundi Activities and to the\nActivityPub transport boundary. Nothing here signs or sends an Activity.<\/p>\n\n Both plugins negotiate the same canonical URLs, and two answers for one address is worse\nthan either answer alone. So when the official ActivityPub plugin is active, this plugin's\nstandalone negotiator turns itself off<\/strong> and leaves those URLs to it, while the registry\nand renderer stay available. Nothing here overrides or replaces that plugin's object ids.<\/p>\n\n An observation of a remote object is a cache, not a record<\/strong>: it is keyed by the remote\nURI, which stays canonical, and it can be rebuilt by fetching again. Observations expire,\nand a scheduled daily task deletes the expired ones along with anything left pointing at\nthem.<\/p>\n\n Remote media is never downloaded and never hotlinked<\/strong>. A cached object's attachments are\ndescribed -- type, size, the text the author wrote about them -- and not fetched. Where a\ncached object is shown locally at all, it is shown This plugin reads documents from other websites. Every request is a Requests happen for two reasons, and the second is worth being clear about.<\/p>\n\n Because an administrator asked.<\/strong><\/p>\n\n Because something arrived here naming an address.<\/strong><\/p>\n\n Which servers are contacted therefore depends on which addresses your administrators enter\nand which sites send things to your inbox. This plugin has no service of its own and sends\nnothing to its author. Each server contacted is somebody else's, run under its own terms of\nservice and privacy policy.<\/p>\n\n\n Activation creates this plugin's own database tables. Nothing is contacted on the internet\nduring installation, and deactivation removes the scheduled tasks it added.<\/p>\n\n\nattributedTo<\/code> -- it is readable, it simply was not published by anyone.<\/p>\n\nWhat this version does<\/h4>\n\n
\n
What this version does not do<\/h4>\n\n
Alongside the official ActivityPub plugin<\/h4>\n\n
What is stored about other people's documents<\/h4>\n\n
noindex<\/code>, only for objects that were\naddressed publicly, and only as a courtesy view beside the remote original.<\/p>\n\nExternal services<\/h3>\n\n
GET<\/code> made through\n wp_safe_remote_get(): redirects are not followed automatically, the response size is\ncapped, and any address inside your own network is refused. Nothing about your site's\ncontent or your users is sent as data. As with any outgoing HTTP request the server being\ncontacted receives your site's IP address<\/strong>, and a User-Agent<\/code> header naming this\nplugin, its version, and your site's home URL<\/strong>.<\/p>\n\n\n
\n
Announce<\/code> reaches this site's inbox carrying only\nthe URI of the object it announces, that one address is queued for a single background\nfetch, so that the announcement can be shown as something rather than as a link. The\nobject's author is looked up the same way if this site does not already know them.<\/li>\nhttps<\/code> addresses are considered. Turning the setting off\nalso clears anything already queued.<\/li>\n<\/ul>\n\n\n
\/wp-content\/plugins\/<\/code>, or install it through\nPlugins > Add New<\/strong>, then activate it.<\/li>\nattributedTo<\/code> until\nsomething records who published it. Add Axismundi Activities<\/strong> for that, and for the\nfour authored visibility levels and an Actor outbox with activities in it, and the\nofficial ActivityPub<\/strong> plugin with Axismundi ActivityPub Bridge<\/strong> to send and\nreceive.<\/li>\n0.1.2<\/h4>\n\n
\n
template<\/code> element and the\nInteractivity API directives, so it is not used here.<\/li>\nattributedTo<\/code>,\nrather than refused. It is not published to anyone.<\/li>\n0.1.1<\/h4>\n\n
\n
0.1.0<\/h4>\n\n
\n