tylrfishr

<p>Publish your posts and pages to the AT Protocol using the standard.site lexicons.</p>
<h3>Requirements</h3>
<ul>
<li>PHP 8.3+</li>
<li>WordPress 6.4+</li>
</ul>
<h3>Setup</h3>
<ol>
<li>Go to <strong>Settings > Wireservice</strong>.</li>
<li>Connect your AT Protocol account via the OAuth flow.</li>
<li>Configure your <strong>Publication</strong> settings (name, description, icon, theme colors) and sync to AT Protocol.</li>
<li>Enable <strong>Document</strong> syncing and configure how post titles, descriptions, and cover images are sourced.</li>
</ol>
<h3>How It Works</h3>
<h3>Publication</h3>
<p>Your WordPress site is represented as a <code>site.standard.publication</code> record on AT Protocol. The plugin syncs site-level metadata including:</p>
<ul>
<li><strong>Name</strong> — from WordPress site title, Yoast SEO, or a custom value</li>
<li><strong>Description</strong> — from WordPress tagline, Yoast SEO, or a custom value</li>
<li><strong>Icon</strong> — from WordPress site icon or a custom upload</li>
<li><strong>Theme colors</strong> — 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><strong>Discoverability</strong> — 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>
<p>The plugin also serves a <code>.well-known/site.standard.publication</code> endpoint that returns the AT-URI of your publication record.</p>
<h3>Documents</h3>
<p>When document syncing is enabled, published posts and pages are automatically synced as <code>site.standard.document</code> records. Each document includes:</p>
<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>
<p>Documents are created on publish, updated on edit, and deleted when a post is trashed, deleted, or unpublished.</p>
<p>A <code><link rel="site.standard.document"></code> tag is added to the <code><head></code> of each synced post for verification.</p>
<p>Note that Wireservice does not have a content lexicon yet. This is in development.</p>
<h3>Per-Post Overrides</h3>
<p>A <strong>Wireservice</strong> meta box appears on the post editor, allowing per-post overrides for:</p>
<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>
<p>When Yoast SEO is active, additional source options become available for both publication and document settings:</p>
<ul>
<li><strong>Publication</strong>: Yoast organization name, website name, homepage meta description</li>
<li><strong>Documents</strong>: 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>
<p>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.</p>
<h3>Running AIP</h3>
<p>AIP requires Rust 1.87+. To run locally:</p>
<ol>
<li>
<p>Generate an OAuth signing key with <code>goat</code>: <code>goat key generate -t p256</code>. Save the public and private keys somewhere safe.</p>
</li>
<li>
<p>Clone AIP: <code>git clone https://github.com/graze-social/aip.git</code></p>
</li>
<li>
<p>Setup environment variables:</p>
<p><code>EXTERNAL_BASE=https://your-domain.com<br />
DPOP_NONCE_SEED=$(openssl rand -hex 32)<br />
STORAGE_BACKEND=sqlite<br />
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<br />
OAUTH_SUPPORTED_SCOPES="atproto:atproto atproto:repo:site.standard.publication atproto:repo:site.standard.document<br />
atproto:blob:*/*"</code></p>
</li>
<li>
<p>Run AIP: <code>cargo run --bin aip</code></p>
</li>
</ol>
<p>Or with Docker:</p>
<pre><code>`
</code></pre>
<p>docker build -t aip .<br />
docker run -p 8080:8080 \<br />
  // all of the above env vars here<br />
  aip<br />
    `</p>
<p>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>).</p>
<h3>Configuring Wireservice</h3>
<p>Once your AIP instance is running, update the OAuth Service URL in WordPress:</p>
<ol>
<li>Go to <strong>Settings > Wireservice</strong>.</li>
<li>Set the <strong>OAuth Service URL</strong> to your AIP instance (e.g., <code>https://your-domain.com</code>).</li>
</ol>
<p>This is stored as the <code>wireservice_oauth_url</code> option and can also be set programmatically:</p>
<pre><code>`
</code></pre>
<p>update_option(‘wireservice_oauth_url’, ‘https://your-domain.com’);<br />
    <code><h3>Filters</h3></code><br />
// Customize which post types are synced (default: post, page)<br />
add_filter(‘wireservice_syncable_post_types’, function ($types) {<br />
    $types[] = ‘custom_post_type’;<br />
    return $types;<br />
});</p>
<p>// Control whether a specific post should sync<br />
add_filter(‘wireservice_should_sync_post’, function ($should_sync, $post) {<br />
    return $should_sync;<br />
}, 10, 2);<br />
    `</p>
<h3>License</h3>
<p><a href="LICENSE.md" rel="nofollow ugc">AGPL 3.0</a></p>


Wireservice

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

Automattic

Matthias Pfefferle

Jeremy Herve

Brandon Kraft

Ryan C.

<p><strong>ATmosphere</strong> turns your WordPress site into a first-class citizen of the AT Protocol — the open network behind <a href="https://bsky.social/" rel="nofollow ugc">Bluesky</a>.</p>
<p>When you publish a post, ATmosphere automatically shares it on Bluesky and stores the full article on your AT Protocol account so any compatible app can read it. When people on Bluesky reply, like, or repost what you shared, those reactions show up as comments on your post. And approved comments your readers leave on WordPress are sent right back to Bluesky as replies under your original post — so the same conversation happens in both places without you having to copy anything by hand.</p>
<h4>What you get</h4>
<ul>
<li><strong>Your posts on Bluesky, automatically.</strong> Hit “Publish” on WordPress, and a moment later your post appears on Bluesky. Links, @-mentions, and #hashtags are detected for you.</li>
<li><strong>Long posts done right.</strong> A long article becomes a short, readable Bluesky thread that links back to the full piece on your site. Edits are kept tidy so existing replies and reposts on Bluesky don’t get orphaned.</li>
<li><strong>Use your own domain as your Bluesky handle.</strong> With one click, your handle becomes something like <code>@yourblog.com</code> instead of <code>@you.bsky.social</code>. ATmosphere does the technical bit; Bluesky verifies it.</li>
<li><strong>Bluesky reactions become WordPress comments.</strong> Replies appear in your comments. Likes and reposts show up alongside them with their own counts so the engagement is visible to your readers.</li>
<li><strong>WordPress comments become Bluesky replies.</strong> When a logged-in reader leaves an approved comment on a cross-posted article, it’s sent to Bluesky as a reply under the original post.</li>
<li><strong>Catch up on older posts.</strong> A <code>wp atmosphere backfill</code> command can publish posts you wrote before installing the plugin.</li>
<li><strong>Per-post control.</strong> You can opt individual posts out of cross-posting straight from the editor sidebar.</li>
<li><strong>No middleman.</strong> ATmosphere talks directly to your Bluesky account using modern, secure sign-in. Nothing is routed through a third-party service, and your tokens never leave your WordPress site.</li>
<li><strong>Translation-ready.</strong> Help translate ATmosphere into your language.</li>
</ul>
<h4>How it works</h4>
<ol>
<li>Install ATmosphere and activate it.</li>
<li>Go to <strong>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> ATmosphere</strong> and click “Connect” — sign in to Bluesky in the normal Bluesky window, then come back to WordPress.</li>
<li>Fill in a name, description, and icon for your “publication” — this is how your site is represented on the AT Protocol.</li>
<li>Publish a post.</li>
<li>Open Bluesky — your post is there. People can reply, like, repost, and follow as they normally would.</li>
<li>Replies, likes, and reposts will start appearing as comments on your WordPress post. Comments you approve on WordPress will appear as replies on Bluesky.</li>
</ol>
<p><strong>Note:</strong> Cross-posting only kicks in for posts you publish <em>after</em> connecting. To bring older posts across, run <code>wp atmosphere backfill</code> from WP-CLI.</p>


ATmosphere


At this point (v 1.1.1) it is rather basic, but it does what it promises.


Does what it says on the tin.

Share your WordPress posts on Bluesky and the wider AT Protocol network — and let conversations there come back as comments on your site.

Wireservice vs ATmosphere