JRMora

Recordar for Bluesky & Mastodon is a plugin designed to automate the publication of archive content (ephemeris/on this day) to Bluesky and Mastodon. It integrates with the WordPress CRON system to:
<ul>
<li>Dual Publishing: Connect both Bluesky and Mastodon simultaneously.</li>
<li>Smart Scheduling: Automatically publish old posts (“On a day like today, N years/months ago”) at user-defined times.</li>
<li>Full Multilanguage Support: Detects and allows filtering posts by language (e.g., ‘es’, ‘en’, ‘de’) if using plugins like Polylang or WPML.</li>
<li>Immediate Publication of New Posts: Optionally, send a post to your networks immediately upon publication in WordPress.</li>
<li>Editorial Control: Exclude specific posts (by ID) to prevent automatic publication.</li>
<li>Link Handling (Embeds): Generates the link embed with image, title, and excerpt. Supports native image uploading for both networks.</li>
<li>Diagnostic Tools: Includes connection tests, Archive query tests, and CRON status/reset tools.</li>
<li>Granular Control: Pause the entire system globally, or enable/disable each social network individually.</li>
<li>Lists Laboratory: Create and save draft schedules offline before applying them.</li>
</ul>
Requirements: 
* A Bluesky account (Handle + App Password). 
* A Mastodon account (Instance URL + Access Token).

Recordar for Bluesky & Mastodon

Automate archive (Ephemeris) & new posts to Bluesky & Mastodon. Includes scheduling, lists, editorial control and multi-language support.

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.

Recordar for Bluesky & Mastodon vs Wireservice