Marko Banušić

ecaron

<p>This plugin enables automatic posting of articles to ATProto networks like BlueSky. Also, it enables the display of comments from the ATProto network below the post as comments.</p>
<p>The plugin adds a new section in the Settings -> Writing page where you can enter the login information for your ATProto network.</p>
<p>A new meta box is added to the post editor where you can select weather to share the post to your ATProto network and what status to use.</p>
<p>If no status is selected, the plugin will use the title of the post as the status.</p>
<p>The plugin shares the post to your ATProto network when the post is published via the WordPress cron system. So make sure you have the cron system working on your WordPress installation.</p>
<p>We recommend hooking up the cron system to a cron job on your server. You can find more information about this in the WordPress documentation.</p>


Neznam Atproto Share


This plugin does a nice job letting me pick which of my blog posts, if not all, should go to Bluesky. It also lets me pick if I want the title, the excerpt, both, or something custom.



I'm anxious to see if the comment system becomes useful, but for now this provides the best way to make sure my blog posts show up on Bluesky.


Lots of features to bring WordPress and Bluesky together

Automatically share to Authenticated Transfer Protocol networks like BlueSky and display comments from that network below the post as comments.

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.

Neznam Atproto Share vs Wireservice