Maira Foresto

<p>Social Publisher helps you publish WordPress content to multiple social networks from one place inside your dashboard.</p>
<p>Connect your accounts, choose where each post should be shared, customize the message, attach an image, and publish without jumping between platforms.</p>
<p>Designed for a simple workflow, Social Publisher supports manual publishing from its main screen and auto-post options from the WordPress editor.</p>
<h4>Main features</h4>
<ul>
<li>Publish to multiple social networks from one dashboard</li>
<li>Connect and manage accounts in one place</li>
<li>Write a custom message before publishing</li>
<li>Use the built-in image cropper before posting</li>
<li>Trigger auto-post options from the Gutenberg editor</li>
<li>Disconnect accounts and restart a connection from zero when needed</li>
<li>Review debug logs when troubleshooting a connection or publish attempt</li>
</ul>
<h4>Supported networks</h4>
<p>Social Publisher currently supports:</p>
<ul>
<li>Bluesky</li>
<li>Mastodon</li>
<li>Tumblr</li>
<li>Pinterest</li>
<li>Threads</li>
<li>Instagram</li>
<li>LinkedIn</li>
<li>Blogger</li>
<li>Telegram</li>
<li>Facebook Pages</li>
</ul>
<p>Support for some networks may depend on the account type, app approval status, or provider requirements.</p>
<h4>Who is this plugin for?</h4>
<p>Social Publisher is a good fit for:</p>
<ul>
<li>bloggers who want a simpler social publishing workflow</li>
<li>site owners who publish to more than one network</li>
<li>content creators who want to manage sharing from WordPress</li>
<li>admins who want account connections and publishing tools in one place</li>
</ul>
<h3>External services</h3>
<p>Social Publisher connects to external services only when a site administrator enables a provider, starts an authorization flow, tests a connection, opens a share action, or publishes content to that provider.</p>
<p>The plugin stores the credentials returned by each provider in the WordPress database for the current site. It uses those credentials only to validate the connection and publish content chosen by the administrator. Debug logs are sanitized to avoid storing access tokens or OAuth secrets in clear text.</p>
<p>No data is sent to a social network unless that specific integration is configured and used.</p>
<h4>Bluesky</h4>
<p>Service provider: Bluesky Social, PBC.</p>
<p>Domains/endpoints used: https://bsky.social/xrpc/</p>
<p>What it is used for: authenticating with a Bluesky handle and app password, uploading images, and creating Bluesky posts.</p>
<p>Data sent and when: when the administrator saves or tests the Bluesky connection, the plugin sends the configured handle and app password to Bluesky. When publishing, it sends the post text, link, optional image data, and the authenticated account identifier to Bluesky.</p>
<p>Terms: https://bsky.social/about/support/tos<br />
Privacy policy: https://bsky.social/about/support/privacy-policy</p>
<h4>Mastodon</h4>
<p>Service provider: the Mastodon server/instance selected by the site administrator. Mastodon is federated, so the exact provider, terms, and privacy policy depend on the selected instance.</p>
<p>Domains/endpoints used: the plugin connects over HTTPS to the administrator-selected Mastodon instance. Example endpoints include https://mastodon.social/api/v1/accounts/verify_credentials, https://mastodon.social/api/v1/statuses, https://mastodon.social/api/v1/media, and https://mastodon.social/api/v1/apps. The domain changes when the administrator enters a different instance.</p>
<p>What it is used for: registering or connecting an app on the selected Mastodon instance, validating the account, uploading media, checking uploaded media, and publishing statuses.</p>
<p>Data sent and when: when the administrator saves, tests, or connects Mastodon, the plugin sends the selected server name, callback/redirect details, OAuth app data, authorization code, client credentials, and access token to that selected instance. When publishing, it sends the status text, link, optional media files, visibility settings, and account token to that selected instance.</p>
<p>Terms: each Mastodon instance publishes its own terms. Review the selected instance terms before connecting it. Example for mastodon.social: https://mastodon.social/terms<br />
Privacy policy: each Mastodon instance publishes its own privacy policy. Example for mastodon.social: https://mastodon.social/privacy-policy</p>
<h4>Tumblr</h4>
<p>Service provider: Tumblr.</p>
<p>Domains/endpoints used: https://www.tumblr.com/oauth/ and https://api.tumblr.com/v2/.</p>
<p>What it is used for: OAuth authentication, validating the configured blog, retrieving basic account/blog information, and publishing posts to the selected Tumblr blog.</p>
<p>Data sent and when: during connection, the plugin sends the Consumer Key, Consumer Secret, OAuth verifier, callback URL, token, token secret, and blog identifier to Tumblr. When publishing, it sends the post title/text, link, tags, optional image/media data, and blog identifier.</p>
<p>Terms: https://www.tumblr.com/policy/en/terms-of-service<br />
Privacy policy: https://www.tumblr.com/privacy/en</p>
<h4>Pinterest</h4>
<p>Service provider: Pinterest.</p>
<p>Domains/endpoints used: https://www.pinterest.com/oauth/, https://api.pinterest.com/v5/, and https://api-sandbox.pinterest.com/v5/ when sandbox mode is selected.</p>
<p>What it is used for: OAuth authentication, validating account access, selecting boards when available, and creating Pins.</p>
<p>Data sent and when: during connection, the plugin sends the configured App ID, App Secret, redirect/callback URL, authorization code, requested scopes, and token data to Pinterest. When publishing, it sends the Pin title/description, destination link, selected board, and optional image URL or media data.</p>
<p>Terms: https://policy.pinterest.com/en/terms-of-service<br />
Developer/API terms: https://developers.pinterest.com/terms/<br />
Privacy policy: https://policy.pinterest.com/en/privacy-policy</p>
<h4>Threads</h4>
<p>Service provider: Meta Platforms, Inc. / Threads.</p>
<p>Domains/endpoints used: https://threads.net/oauth/ and https://graph.threads.net/. Example endpoints include https://graph.threads.net/v1.0/me, https://graph.threads.net/v1.0/{user-id}/threads, and https://graph.threads.net/v1.0/{container-id}/publish.</p>
<p>What it is used for: OAuth authentication, account validation, media container creation, checking media container status, and publishing Threads posts.</p>
<p>Data sent and when: during connection, the plugin sends the configured App ID, App Secret, redirect/callback URL, authorization code, requested scopes, and access token data to Meta/Threads endpoints. When validating or publishing, it sends the post text, link, optional media URL/data, container IDs, account identifier, and access token to Meta/Threads endpoints.</p>
<p>Meta Platform Terms: https://developers.facebook.com/terms/dfc_platform_terms/<br />
Threads API documentation: https://developers.facebook.com/docs/threads/<br />
Meta Privacy Policy: https://www.facebook.com/privacy/policy/</p>
<h4>Instagram</h4>
<p>Service provider: Meta Platforms, Inc. / Instagram.</p>
<p>Domains/endpoints used: https://www.instagram.com/oauth/, https://api.instagram.com/oauth/, and https://graph.instagram.com/.</p>
<p>What it is used for: OAuth authentication, account validation, media container creation, and publishing Instagram content when the configured account and permissions allow it.</p>
<p>Data sent and when: during connection, the plugin sends the configured Client/App ID, Client/App Secret, redirect/callback URL, authorization code, requested scopes, and token data to Instagram/Meta endpoints. When publishing, it sends the caption/text, link when supported by the provider, optional image/media URL/data, container IDs, and account identifier.</p>
<p>Meta Platform Terms: https://developers.facebook.com/terms/dfc_platform_terms/<br />
Meta Privacy Policy: https://www.facebook.com/privacy/policy/</p>
<h4>Facebook Pages</h4>
<p>Service provider: Meta Platforms, Inc. / Facebook.</p>
<p>Domains/endpoints used: https://www.facebook.com/v20.0/dialog/oauth and https://graph.facebook.com/v20.0/.</p>
<p>What it is used for: OAuth authentication, retrieving available Pages for the authorized account, storing the selected Page token, and publishing to Facebook Pages. The plugin can also open Facebook’s public share dialog when the administrator uses the Facebook share action.</p>
<p>Data sent and when: during connection, the plugin sends the configured App ID, App Secret, redirect/callback URL, authorization code, requested scopes, and token data to Facebook/Meta endpoints. When loading available Pages, it sends the account token and receives Page identifiers and Page names. When publishing, it sends the selected Page ID/token, post message, link, and optional image/media data. When using the public share action, it opens a Facebook URL containing the page URL to share.</p>
<p>Meta Platform Terms: https://developers.facebook.com/terms/dfc_platform_terms/<br />
Meta Privacy Policy: https://www.facebook.com/privacy/policy/</p>
<h4>LinkedIn</h4>
<p>Service provider: LinkedIn.</p>
<p>Domains/endpoints used: https://www.linkedin.com/oauth/v2/ and https://api.linkedin.com/.</p>
<p>What it is used for: OAuth authentication, retrieving basic member/profile information when available, validating the configured person or organization URN, initializing image uploads, uploading images, and publishing posts.</p>
<p>Data sent and when: during connection, the plugin sends the configured Client ID, Client Secret, redirect/callback URL, authorization code, requested scopes, and token data to LinkedIn. When validating or publishing, it sends the person/organization URN, post text, link, optional image data, upload URL data, and access token.</p>
<p>User Agreement: https://www.linkedin.com/legal/user-agreement<br />
API Terms of Use: https://legal.linkedin.com/api-terms-of-use<br />
Privacy policy: https://www.linkedin.com/legal/privacy-policy</p>
<h4>Blogger / Google</h4>
<p>Service provider: Google / Blogger.</p>
<p>Domains/endpoints used: https://accounts.google.com/o/oauth2/v2/auth, https://oauth2.googleapis.com/token, and https://www.googleapis.com/blogger/v3/.</p>
<p>What it is used for: OAuth authentication, selecting the destination Blogger blog, reading basic blog information, refreshing tokens when needed, and publishing Blogger posts.</p>
<p>Data sent and when: during connection, the plugin sends the configured Client ID, Client Secret, redirect/callback URL, authorization code, requested Blogger scopes, refresh token, and access token data to Google. When selecting or publishing to a blog, it sends the blog ID, post title/content, labels when used, and token data to the Blogger API.</p>
<p>Google APIs Terms of Service: https://developers.google.com/terms<br />
Google Terms of Service: https://policies.google.com/terms<br />
Google Privacy Policy: https://policies.google.com/privacy</p>
<h4>Telegram</h4>
<p>Service provider: Telegram Messenger Inc. / Telegram Bot API.</p>
<p>Domains/endpoints used: https://api.telegram.org/. Example methods include getMe, getChat, sendMessage, and sendPhoto.</p>
<p>What it is used for: validating the configured bot token and chat destination, then publishing posts to the selected Telegram group, supergroup, channel, or forum topic.</p>
<p>Data sent and when: when the administrator saves or tests Telegram, the plugin sends the Bot Token and configured chat ID to Telegram Bot API endpoints to validate the connection. When publishing, it sends the post title/text, link, hashtags, optional image URL, optional topic/thread ID, and the destination chat ID.</p>
<p>Terms: https://telegram.org/tos<br />
Bot API documentation: https://core.telegram.org/bots/api<br />
Privacy policy: https://telegram.org/privacy</p>
<h4>Flipboard</h4>
<p>Service provider: Flipboard.</p>
<p>Domains/endpoints used: https://share.flipboard.com/.</p>
<p>What it is used for: opening Flipboard’s public share window when the administrator uses the Flipboard share action.</p>
<p>Data sent and when: when the administrator uses the Flipboard share action, the plugin opens a Flipboard URL containing the public page URL to share. The plugin does not store Flipboard credentials.</p>
<p>Terms: https://about.flipboard.com/terms-of-service/<br />
Privacy policy: https://about.flipboard.com/privacy-policy/</p>


Social Publisher

Publish WordPress posts to multiple social networks from one simple dashboard.

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.

Social Publisher vs Wireservice