Joost

PostCaster publishes WordPress posts to Bluesky and Mastodon when a post goes live. It supports both site-wide accounts and personal author accounts, with previews, test posts, and per-post overrides on the post edit screen.
This plugin is intended for editorial sites that want social posting to stay close to the WordPress publishing workflow.
Key capabilities:
<ul>
<li>Publish automatically when a post moves from unpublished to <code>publish</code></li>
<li>Use site-wide accounts in <code>PostCaster > Global socials</code></li>
<li>Let authors use their own accounts in <code>PostCaster > My socials</code></li>
<li>Preview the exact text before publishing</li>
<li>Override the text per article</li>
<li>Choose featured-image behavior per network</li>
<li>Re-publish manually from the post edit screen when needed</li>
</ul>
Quick start:
<ol>
<li>Activate the plugin.</li>
<li>Enable PostCaster in <code>PostCaster > Settings</code>.</li>
<li>Choose which post types may be published automatically.</li>
<li>Configure one or more site-wide accounts in <code>PostCaster > Global socials</code>.</li>
<li>Send a test post for each configured network.</li>
<li>Publish a test article and confirm the result on the target network.</li>
</ol>
Supported networks:
<ul>
<li>Bluesky</li>
<li>
Mastodon 
Permissions and publishing model:
</li>
<li>
Editors and administrators can publish through configured global accounts.
</li>
<li>Authors can publish through their own personal accounts when personal publishing is enabled for them.</li>
<li>A user who has access to both global and personal targets can choose which targets to use during manual publishing.</li>
<li>If Co-Authors Plus is active, linked co-authors are also recognized for personal publishing.</li>
</ul>
Templates and previews:
<ul>
<li>The default message template is based on post title and URL.</li>
<li>You can set a general template, network-specific templates, and post-specific overrides.</li>
<li>The post edit screen shows previews for the currently available publish targets.</li>
<li>If the final message is still too long for a network, PostCaster skips that target and stores an error on the article.</li>
</ul>
For template details and examples, see <code>docs/templates.md</code> in the plugin repository.
Troubleshooting highlights:
<ul>
<li>Always use the built-in test-post buttons after changing credentials.</li>
<li>If a network is enabled but not posting, first check credentials and article-level errors.</li>
<li>If encrypted credentials can no longer be read, re-save them in <code>Global socials</code> or <code>My socials</code>.</li>
<li>Publishing runs through Action Scheduler in the background; low-traffic sites still benefit from a real server cron job or scheduled task for reliable timing.</li>
</ul>
External services:
PostCaster connects to external social networks only after an administrator or user explicitly configures that network and saves the required credentials.
When configured, PostCaster may send:
<ul>
<li>text rendered from post fields and templates</li>
<li>featured image bytes and alt text</li>
<li>the configured account identifiers required by that network</li>
</ul>
Relevant service documentation and terms:
<ul>
<li>Bluesky developer docs: https://docs.bsky.app/</li>
<li>Bluesky terms: https://bsky.social/about/support/tos</li>
<li>Mastodon API docs: https://docs.joinmastodon.org/api/ 
Privacy note:</li>
</ul>
PostCaster does not send usage analytics or telemetry to the plugin author. Network requests are only made to the configured social networks for test posts and actual publishing.

PostCaster

Publishes WordPress posts with featured images to Bluesky and Mastodon.

tylrfishr

Publish your posts and pages to the AT Protocol using the standard.site lexicons.
<h3>Requirements</h3>
<ul>
<li>PHP 8.3+</li>
<li>WordPress 6.4+</li>
</ul>
<h3>Setup</h3>
<ol>
<li>Go to Settings > Wireservice.</li>
<li>Connect your AT Protocol account via the OAuth flow.</li>
<li>Configure your Publication settings (name, description, icon, theme colors) and sync to AT Protocol.</li>
<li>Enable Document syncing and configure how post titles, descriptions, and cover images are sourced.</li>
</ol>
<h3>How It Works</h3>
<h3>Publication</h3>
Your WordPress site is represented as a <code>site.standard.publication</code> record on AT Protocol. The plugin syncs site-level metadata including:
<ul>
<li>Name — from WordPress site title, Yoast SEO, or a custom value</li>
<li>Description — from WordPress tagline, Yoast SEO, or a custom value</li>
<li>Icon — from WordPress site icon or a custom upload</li>
<li>Theme colors — background, foreground, accent, and accent foreground. NOTE: these are used by other ATProto platforms to style your content, not on your WordPress site.</li>
<li>Discoverability — opt in or out of discovery feeds. NOTE: these are used by other ATProto platforms to show your publication in algorithmic feeds, not on your WordPress site.</li>
</ul>
The plugin also serves a <code>.well-known/site.standard.publication</code> endpoint that returns the AT-URI of your publication record.
<h3>Documents</h3>
When document syncing is enabled, published posts and pages are automatically synced as <code>site.standard.document</code> records. Each document includes:
<ul>
<li>Title and description (configurable source)</li>
<li>Cover image (featured image, Yoast SEO image, or custom)</li>
<li>Publication date and last-updated date</li>
<li>Relative path (permalink)</li>
<li>Tags and categories</li>
<li>Optionally, full plain-text content</li>
</ul>
Documents are created on publish, updated on edit, and deleted when a post is trashed, deleted, or unpublished.
A <code><link rel="site.standard.document"></code> tag is added to the <code><head></code> of each synced post for verification.
Note that Wireservice does not have a content lexicon yet. This is in development.
<h3>Per-Post Overrides</h3>
A Wireservice meta box appears on the post editor, allowing per-post overrides for:
<ul>
<li>Title source</li>
<li>Description source</li>
<li>Cover image source</li>
<li>Whether to include full content</li>
</ul>
<h3>Yoast SEO Integration</h3>
When Yoast SEO is active, additional source options become available for both publication and document settings:
<ul>
<li>Publication: Yoast organization name, website name, homepage meta description</li>
<li>Documents: Yoast SEO title, social title, X title, meta description, social description, X description, social image, X image</li>
</ul>
<h3>Self-Hosting the OAuth Service</h3>
Wireservice authenticates with AT Protocol through an external OAuth service. By default it uses <code>https://aip.wireservice.net</code>, but you can run your own instance using <a href="https://github.com/graze-social/aip" rel="nofollow ugc">AIP</a>, a high-performance OAuth 2.1 authorization server with native AT Protocol integration.
<h3>Running AIP</h3>
AIP requires Rust 1.87+. To run locally:
<ol>
<li>
Generate an OAuth signing key with <code>goat</code>: <code>goat key generate -t p256</code>. Save the public and private keys somewhere safe.
</li>
<li>
Clone AIP: <code>git clone https://github.com/graze-social/aip.git</code>
</li>
<li>
Setup environment variables:
<code>EXTERNAL_BASE=https://your-domain.com 
DPOP_NONCE_SEED=$(openssl rand -hex 32) 
STORAGE_BACKEND=sqlite 
ATPROTO_OAUTH_SIGNING_KEYS=</code>did:key:${YOUR_PRIVATE_KEY}<code>OAUTH_SIGNING_KEYS=</code>did:key:${YOUR_PRIVATE_KEY}<code>ENABLE_CLIENT_API=true 
OAUTH_SUPPORTED_SCOPES="atproto:atproto atproto:repo:site.standard.publication atproto:repo:site.standard.document 
atproto:blob:*/*"</code>
</li>
<li>
Run AIP: <code>cargo run --bin aip</code>
</li>
</ol>
Or with Docker:
<pre><code>`
</code></pre>
docker build -t aip . 
docker run -p 8080:8080 \ 
 // all of the above env vars here 
 aip 
 `
For production, use the <code>postgres</code> storage backend instead of <code>sqlite</code>. Depending on your hosting environment, you may need to manually set the <code>DNS_NAMESERVERS</code> env var so that your AIP service can resolve handles properly. (Wireservice uses <code>8.8.8.8,1.1.1.1</code>).
<h3>Configuring Wireservice</h3>
Once your AIP instance is running, update the OAuth Service URL in WordPress:
<ol>
<li>Go to Settings > Wireservice.</li>
<li>Set the OAuth Service URL to your AIP instance (e.g., <code>https://your-domain.com</code>).</li>
</ol>
This is stored as the <code>wireservice_oauth_url</code> option and can also be set programmatically:
<pre><code>`
</code></pre>
update_option(‘wireservice_oauth_url’, ‘https://your-domain.com’); 
 <code><h3>Filters</h3></code> 
// Customize which post types are synced (default: post, page) 
add_filter(‘wireservice_syncable_post_types’, function ($types) { 
 $types[] = ‘custom_post_type’; 
 return $types; 
});
// Control whether a specific post should sync 
add_filter(‘wireservice_should_sync_post’, function ($should_sync, $post) { 
 return $should_sync; 
}, 10, 2); 
 `
<h3>License</h3>
<a href="LICENSE.md" rel="nofollow ugc">AGPL 3.0</a>

Wireservice

Publish your posts and pages to the AT Protocol using the standard.site lexicons.

PostCaster vs Wireservice