OpenDNA

Provides a General Settings menu option to define a fediverse:creator in metatags for the whole site and also individual contributors.
<h4>Admin fediverse:creator</h4>
The plugin will add a field at the bottom of the General Settings page (Admin Dashboard > Settings>General Settings), labelled “Site fediverse:creator”. The field should accept any valid mastodon username up to three sub-domains deep. i.e <code>user@mastodon.social</code> to <code>user@my.mastodon.del.icio.us</code> The plugin does not accept Mastodon addresses (https://domain.tld/user)
When a valid username has been saved, a <code>name="fediverse:creator"</code> meta tag for that username will be added to the site’s metadata (between <code><head></code> elements). When a link to the WordPress instance is posted to Mastodon, the Mastodon (should) include the username in the link profile.
<h4>Author fediverse:creator</h4>
If an Administrator turns on the “Enable Authors’ fediverse:creator” option on the General Settings page (Admin Dashboard > Settings>General Settings), a field labelled “fediverse:creator” will be added to users’ profile pages (under “contact info”).
When a valid URL has been saved, a tag containing a <code>name="fediverse:creator"</code> meta tag will be added to the metadata (between <code><head></code> elements) of every pose authored by that Author. When a link to the WordPress instance is posted to Mastodon, the Mastodon (should) include the username in the link profile.
<h4>Plugin Development</h4>
Simple fediverse:creator development is managed on GitHub, with official releases published on WordPress.org. The GitHub repo can be found at https://github.com/mckinnon/simple-fediverse-creator.

Simple fediverse:creator

Provides a General Settings menu option to define a fediverse:creator in metatags for the whole site and also individual contributors.

Automattic

Matthias Pfefferle

Jeremy Herve

Brandon Kraft

Ryan C.

ATmosphere 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>.
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.
<h4>What you get</h4>
<ul>
<li>Your posts on Bluesky, automatically. Hit “Publish” on WordPress, and a moment later your post appears on Bluesky. Links, @-mentions, and #hashtags are detected for you.</li>
<li>Long posts done right. 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>Use your own domain as your Bluesky handle. 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>Bluesky reactions become WordPress comments. 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>WordPress comments become Bluesky replies. 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>Catch up on older posts. A <code>wp atmosphere backfill</code> command can publish posts you wrote before installing the plugin.</li>
<li>Per-post control. You can opt individual posts out of cross-posting straight from the editor sidebar.</li>
<li>No middleman. 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>Translation-ready. Help translate ATmosphere into your language.</li>
</ul>
<h4>How it works</h4>
<ol>
<li>Install ATmosphere and activate it.</li>
<li>Go to Settings → ATmosphere 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>
Note: Cross-posting only kicks in for posts you publish after connecting. To bring older posts across, run <code>wp atmosphere backfill</code> from WP-CLI.

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.

Simple fediverse:creator vs ATmosphere