ATmosphere

Yes — or an account on any AT Protocol provider. Most people sign up at bsky.app, but the plugin works with any compatible AT Protocol service.

Yes. ATmosphere signs in to Bluesky directly from your WordPress site. Nothing is routed through Automattic or any other intermediary, and your sign-in tokens are stored encrypted on your site.

Your Bluesky sign-in tokens are stored encrypted using your site's WordPress security keys. If those keys change — after a site migration, or when a security plugin rotates them — the saved login can no longer be read, and ATmosphere asks you to reconnect. Reconnecting on the settings page fixes it in one step. If it keeps happening, look for a security plugin that rotates your keys on a schedule.

Yes — that's one of the headline features. Once you've connected, open Bluesky's app settings, choose "Change Handle", pick "I have my own domain", and enter your WordPress site's domain. Bluesky will check that it really is your site (ATmosphere takes care of the verification file) and switch your handle.

Yes. In the post editor sidebar there's an "ATmosphere" panel where you can opt the current post out before publishing.

Long posts are turned into a short Bluesky thread of a few connected posts, with the last one linking back to the full article on your site. The full text of your post lives on your AT Protocol account, so other AT Protocol-aware apps and readers can show it too.

Yes — approved comments left by WordPress users who are allowed to publish posts are sent to Bluesky as replies under your original post. Comments from Subscribers and other comment-only accounts stay local, as do anonymous comments, trackbacks, and pingbacks.

Yes. Under Settings → ATmosphere → Reactions, turn off Publish eligible WordPress comments as Bluesky replies. New comment changes will stay on WordPress; replies already published to Bluesky are left unchanged. Incoming Bluesky replies, likes, and reposts continue to follow their own settings. Plugins can enforce this with the atmosphere_should_publish_comments filter, which overrides the saved setting without changing it.

Yes. ATmosphere checks Bluesky periodically and turns replies, likes, and reposts into WordPress comments on the matching post. Likes and reposts have their own comment types so they show up as engagement counts, not as duplicate comment text. ATmosphere also checks a small rolling batch of published posts each day, so older missed replies are recovered automatically without requiring post IDs. To check a specific post immediately, run wp atmosphere replies backfill <post-id> from WP-CLI. Both paths scan replies currently visible through Bluesky's public API and import those that are not already present.

By default, only new posts are shared. You can publish older ones on demand by running wp atmosphere backfill from WP-CLI.

Yes. If you delete or unpublish a WordPress post, the matching Bluesky post and AT Protocol records are removed too. If you trash a post and then restore it, ATmosphere re-publishes it.

Every post ATmosphere shares gets an ID on Bluesky: a 13-character string like 3mn3kzvtns72d. It has to be unique, and your site already stores it so the post can be edited or deleted later. That makes it a perfectly good address, so your site also answers at example.com/post/3mn3kzvtns72d and sends visitors to the full article. It is the same shape Bluesky uses. A post on Bluesky lives at bsky.app/profile/yourhandle/post/3mn3kzvtns72d, so if you drop the profile part and put your own domain in front, you land on the same post on your own site. This works best if you use your own domain as your Bluesky handle, which ATmosphere can set up for you in one click. Then your handle is your domain, and the two addresses are the same but for the bsky.app/profile/ in front. There is no lookup table to maintain and no third-party shortener that can disappear and take your links with it. The address also survives a rename: it finds the post by its Bluesky ID, not by its title, so changing either leaves it working. The idea comes from Felix Schwenzel's write-up on short URLs, which weighs up several candidate identifiers for a personal short link and concludes the best one is whatever your site already has. The broader pattern is the IndieWeb's permashortlink: an address on your own domain that expands to your own permalink, so it cannot rot the way a third-party shortener does. Under Settings → ATmosphere there is an option to use the Bluesky ID as the short URL, which tells browsers and other tools to prefer this address over the ?p=123 one WordPress provides. It is off unless you turn it on, so a site already running a shortener such as Hum keeps control. The address itself works either way. These addresses need pretty permalinks turned on under Settings → Permalinks.

Not at this time. ATmosphere is designed for a single WordPress site. On a Network-activated install only the current site's data is read and written, and uninstall only cleans the current site — credentials and records on other sites in the network are left intact.