<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Bluesky API changes | Schedule Social Media</title><description>New entries in the Bluesky API changelog, each linked to the platform&apos;s own announcement.</description><link>https://schedulesocialmedia.com/</link><language>en</language><atom:link href="https://schedulesocialmedia.com/api-changes/rss/bluesky.xml" rel="self" type="application/rss+xml"/><item><title>Bluesky adds a setting to hide posts from algorithmic recommendations</title><link>https://schedulesocialmedia.com/api-changes/bluesky-content-visibility-declaration/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/bluesky-content-visibility-declaration/</guid><description>Policy. Posts from users who enable the setting should stay out of algorithmic feeds, which can reduce their reach in recommendation surfaces. What to do: Feed developers should read the app.bsky.actor.contentVisibilityDeclaration record and skip posts when hideFromAlgorithmicRecommendations is true. A missing record means false. The post asks for best judgment, not a hard deadline.</description><pubDate>Tue, 01 Sep 2026 00:00:00 GMT</pubDate><category>Bluesky</category><category>Policy</category></item><item><title>Bluesky: AT Protocol Spaces: alpha for non-public data, public beta December 1, 2026</title><link>https://schedulesocialmedia.com/api-changes/bluesky-atproto-spaces-alpha/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/bluesky-atproto-spaces-alpha/</guid><description>New feature, effective 2026-12-01. Developers can build production apps on gated, non-public AT Protocol data from December 1, 2026, when Spaces moves to public beta and Bluesky updates its PDS fleet. Posting to public Bluesky feeds is not affected. What to do: If you run the reference PDS, update to the release of December 1, 2026. Don&apos;t run the alpha PDS in production, and move any test data off the hosted alpha PDS before it shuts down.</description><pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate><category>Bluesky</category><category>New feature</category></item><item><title>Bluesky: Jetstream v2 with network replay and new protocol services docs</title><link>https://schedulesocialmedia.com/api-changes/bluesky-jetstream-v2-protocol-services/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/bluesky-jetstream-v2-protocol-services/</guid><description>New feature, effective 2026-08-13. Developers who need historical events can use Jetstream v2 replay with an API token, while existing Jetstream v1 and @atproto/api code keeps working for now.</description><pubDate>Thu, 13 Aug 2026 00:00:00 GMT</pubDate><category>Bluesky</category><category>New feature</category></item><item><title>Bluesky shows richer link previews for articles published with Standard.site</title><link>https://schedulesocialmedia.com/api-changes/bluesky-standard-site-link-previews-2026-05/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/bluesky-standard-site-link-previews-2026-05/</guid><description>New feature, effective 2026-05-27. Links to blog posts and newsletters that publish a Standard.site record now get an enhanced card in the Bluesky app with the publication and author, which can make shared articles stand out. What to do: If you share your own articles on Bluesky, publish Standard.site records for them (for example with the WordPress plugin or a static-site tool) and check how the link renders in the Bluesky app.</description><pubDate>Wed, 27 May 2026 00:00:00 GMT</pubDate><category>Bluesky</category><category>New feature</category></item><item><title>Bluesky TypeScript SDK packages go ESM-only and drop Node 18 and 20</title><link>https://schedulesocialmedia.com/api-changes/bluesky-ts-sdk-esm-node-support-2026-05/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/bluesky-ts-sdk-esm-node-support-2026-05/</guid><description>Breaking, effective 2026-05. Tools that post to Bluesky with @atproto/api, @atproto/oauth-client-node or other @atproto packages must run on a current Node LTS to use the new releases, which are ESM only. What to do: Upgrade servers and CI to a current Node LTS (Node 22 or later can still require() the ESM packages), then update the @atproto packages. Start new code on the lex SDK; @atproto/api stays supported.</description><pubDate>Thu, 21 May 2026 00:00:00 GMT</pubDate><category>Bluesky</category><category>Breaking</category></item><item><title>Bluesky documents label rate limits and changes default relay limits for new PDS hosts</title><link>https://schedulesocialmedia.com/api-changes/bluesky-label-and-relay-rate-limits-2026-04/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/bluesky-label-and-relay-rate-limits-2026-04/</guid><description>Breaking. Labeling services are capped at 5 labels per second, 10,000 per hour and 100,000 per day, and new self-hosted PDS instances get higher event limits but a default cap of 100 accounts on Bluesky&apos;s relay. What to do: Labelers should batch and pace label output under the published caps. PDS operators who expect more than 100 accounts or more events should contact Bluesky to raise the defaults.</description><pubDate>Wed, 01 Apr 2026 00:00:00 GMT</pubDate><category>Bluesky</category><category>Breaking</category></item><item><title>Bluesky: AT Protocol OAuth permissions and permission sets ship, replacing app-password-level access</title><link>https://schedulesocialmedia.com/api-changes/bluesky-oauth-permission-sets-2026-03/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/bluesky-oauth-permission-sets-2026-03/</guid><description>New feature. Scheduling tools that use OAuth can ask only for what they need, such as writing posts and uploading media, instead of the broad transition:generic scope that equals app password access. What to do: Replace transition:generic with granular permissions (for example repo permissions for the record types you write and blob:*/* for images and video) or published permission sets, and keep the scope in oauth-client-metadata.json identical to the one in your authorization request.</description><pubDate>Tue, 24 Mar 2026 00:00:00 GMT</pubDate><category>Bluesky</category><category>New feature</category></item><item><title>Bluesky: bsky.network firehose moves to a new relay</title><link>https://schedulesocialmedia.com/api-changes/bluesky-relay-transition-firehose/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/bluesky-relay-transition-firehose/</guid><description>Breaking, effective 2026-01-27. Firehose consumers must auto-reconnect and deduplicate events by rev, because the cursor jumps forward and some events repeat.</description><pubDate>Sat, 24 Jan 2026 00:00:00 GMT</pubDate><category>Bluesky</category><category>Breaking</category></item><item><title>Bluesky releases Tap for backfilled, verified repo sync with webhooks</title><link>https://schedulesocialmedia.com/api-changes/bluesky-tap-repo-sync-2025-12/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/bluesky-tap-repo-sync-2025-12/</guid><description>New feature. Tools that read Bluesky data, such as analytics and monitoring, can self-host Tap to backfill accounts&apos; full history and receive verified events as JSON over WebSocket or webhooks. What to do: Consider Tap if you need backfill plus live events for selected accounts or collections, or webhooks for serverless hosting. Jetstream stays available for simpler cases.</description><pubDate>Fri, 12 Dec 2025 00:00:00 GMT</pubDate><category>Bluesky</category><category>New feature</category></item><item><title>Bluesky: AT Protocol OAuth adds email scope, plans longer sessions, fixes client bugs</title><link>https://schedulesocialmedia.com/api-changes/bluesky-oauth-improvements-session-lifetimes/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/bluesky-oauth-improvements-session-lifetimes/</guid><description>Version. OAuth clients get a transition:email scope, longer planned sessions, and must update libraries and DPoP handling. What to do: Update @atproto/oauth-client to 0.3.18 or later, remove the iss field from DPoP JWTs sent to the PDS, and keep the same attestation key for a session&apos;s lifetime. The post gives no deadlines.</description><pubDate>Thu, 12 Jun 2025 00:00:00 GMT</pubDate><category>Bluesky</category><category>Version</category></item><item><title>Bluesky PDS adds OAuth sign-up and an account page for revoking connected apps</title><link>https://schedulesocialmedia.com/api-changes/bluesky-pds-oauth-signup-account-management-2025-05/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/bluesky-pds-oauth-signup-account-management-2025-05/</guid><description>New feature. Apps using OAuth can let new users create an account during login, and users can see and revoke connected OAuth apps at bsky.social/account, so tools should expect revoked sessions. What to do: Handle revoked OAuth grants gracefully and prompt users to reconnect. For sessions that must last more than a few days or weeks, as scheduling tools need, use a confidential OAuth client.</description><pubDate>Fri, 09 May 2025 00:00:00 GMT</pubDate><category>Bluesky</category><category>New feature</category></item><item><title>Bluesky relay software supports Sync v1.1, old firehose message types removed</title><link>https://schedulesocialmedia.com/api-changes/bluesky-relay-sync-v1-1-support/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/bluesky-relay-sync-v1-1-support/</guid><description>Breaking. Firehose consumers must stop relying on #handle, #migration and #tombstone, and expect higher sequence numbers after bsky.network switches. What to do: Handle #identity and #account instead of the removed message types. PDS operators should test against the new relays and upgrade to emit valid Sync v1.1 messages before strict validation is enforced. No date is given for enforcement.</description><pubDate>Fri, 02 May 2025 00:00:00 GMT</pubDate><category>Bluesky</category><category>Breaking</category></item><item><title>Bluesky: AT Protocol deprecates hardcoding bsky.social and relying on default AppView proxying</title><link>https://schedulesocialmedia.com/api-changes/bluesky-deprecated-patterns-bsky-social-proxy-2025-03/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/bluesky-deprecated-patterns-bsky-social-proxy-2025-03/</guid><description>Deprecation. Tools that send every request to bsky.social, or call app.bsky endpoints through a PDS without an atproto-proxy header, may break when Bluesky stops the compatibility proxying it still provides. What to do: Resolve each handle or DID to its PDS and send requests there, and always set the atproto-proxy header (did:web:api.bsky.app#bsky_appview for the Bluesky AppView) on proxied app.bsky calls. No removal date was given.</description><pubDate>Fri, 07 Mar 2025 00:00:00 GMT</pubDate><category>Bluesky</category><category>Deprecation</category></item><item><title>Bluesky: @atproto/api 0.14: stricter types, $type required in records, is* helpers no longer cast</title><link>https://schedulesocialmedia.com/api-changes/bluesky-ts-sdk-v0-14-type-safety-2025-02/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/bluesky-ts-sdk-v0-14-type-safety-2025-02/</guid><description>Breaking, effective 2025-02-13. TypeScript tools that build Bluesky posts with @atproto/api may get new compile errors on upgrade, because union members such as embeds need an explicit $type and is* helpers no longer narrow types unsafely. What to do: When upgrading to 0.14, add $type to embeds and other union values (use $Typed where required), switch to validate* or asPredicate where data is untrusted, mark intentional extra fields, and pin all @atproto packages to one version.</description><pubDate>Thu, 13 Feb 2025 00:00:00 GMT</pubDate><category>Bluesky</category><category>Breaking</category></item><item><title>Bluesky announces a new relay and firehose fan-out, later partly superseded</title><link>https://schedulesocialmedia.com/api-changes/bluesky-relay-operational-changes-2024/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/bluesky-relay-operational-changes-2024/</guid><description>Breaking. Firehose consumers were told to expect different sequence numbers and to support HTTP redirects for websocket connections. What to do: Support HTTP redirects on websocket connections and follow the later relay posts for current guidance. The original post is marked as superseded by the May 2025 relay post.</description><pubDate>Mon, 18 Nov 2024 00:00:00 GMT</pubDate><category>Bluesky</category><category>Breaking</category></item><item><title>Bluesky introduces Jetstream, a JSON alternative to the firehose</title><link>https://schedulesocialmedia.com/api-changes/bluesky-jetstream-launch/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/bluesky-jetstream-launch/</guid><description>New feature. Bots, feeds and small tools can read network events as simple JSON, with filtering by collection or account. What to do: Consider Jetstream for lightweight consumers. Do not use it where you need signed, verifiable data such as mirroring, archives or moderation, because events carry no signatures.</description><pubDate>Wed, 16 Oct 2024 00:00:00 GMT</pubDate><category>Bluesky</category><category>New feature</category></item><item><title>Bluesky pinned posts clash with a field third-party apps already used</title><link>https://schedulesocialmedia.com/api-changes/bluesky-pinned-posts-lexicon-collision-2024-10/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/bluesky-pinned-posts-lexicon-collision-2024-10/</guid><description>Breaking, effective 2024-10-10. Profile records written by some third-party apps became invalid under Bluesky&apos;s new pinnedPost field, causing errors for some users, and Bluesky now tells developers not to add their own fields to Bluesky records. What to do: Treat pinnedPost on app.bsky.actor.profile as a strongRef (URI plus CID). Store custom data in your own sidecar record type, or use a long unique prefix for any extension field.</description><pubDate>Wed, 16 Oct 2024 00:00:00 GMT</pubDate><category>Bluesky</category><category>Breaking</category></item><item><title>Bluesky: AT Protocol publishes its OAuth specification, replacing app passwords over time</title><link>https://schedulesocialmedia.com/api-changes/bluesky-oauth-specification-release/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/bluesky-oauth-specification-release/</guid><description>New feature. OAuth becomes the intended way for apps to sign users in, so new integrations should stop relying on app passwords. What to do: Start building on OAuth now and avoid app passwords for new projects. Use transition:generic for app-password-equivalent access and add transition:chat.bsky for DMs. The post gives no date for ending app passwords.</description><pubDate>Wed, 25 Sep 2024 00:00:00 GMT</pubDate><category>Bluesky</category><category>New feature</category></item><item><title>Bluesky adds video posts: one video per post, up to 60 seconds</title><link>https://schedulesocialmedia.com/api-changes/bluesky-video-posts-2024-09/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/bluesky-video-posts-2024-09/</guid><description>New feature, effective 2024-09-11. Posts can carry one video of up to 60 seconds, so scheduling tools can publish video to Bluesky, within a daily upload cap and only for accounts with a verified email. What to do: Upload video with uploadBlob or, better, through the video service at video.bsky.app, attach it as an app.bsky.embed.video embed with an aspect ratio, and check email verification with com.atproto.server.getSession before offering video.</description><pubDate>Wed, 11 Sep 2024 00:00:00 GMT</pubDate><category>Bluesky</category><category>New feature</category></item><item><title>Bluesky: @atproto/api session refactor: BskyAgent deprecated, some session hooks removed</title><link>https://schedulesocialmedia.com/api-changes/bluesky-ts-api-auth-refactor-2024-08/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/bluesky-ts-api-auth-refactor-2024-08/</guid><description>Breaking, effective 2024-08-12. Tools built on the TypeScript @atproto/api package keep working with app passwords for now, but code that customised fetch, used setSessionPersistHandler or extended BskyAgent breaks or is deprecated on upgrade. What to do: Type agents as Agent, create them with AtpAgent, pass persistSession and any custom fetch in the constructor, replace BskyAgent and default imports with named exports, and make sure fetch, Request and Headers exist globally.</description><pubDate>Mon, 12 Aug 2024 00:00:00 GMT</pubDate><category>Bluesky</category><category>Breaking</category></item><item><title>Bluesky opens federation: accounts can live on PDS hosts outside Bluesky</title><link>https://schedulesocialmedia.com/api-changes/bluesky-self-host-federation-2024-02/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/bluesky-self-host-federation-2024-02/</guid><description>New feature, effective 2024-02-22. Bluesky accounts can now be hosted on independent servers, so tools that post must find each account&apos;s own host instead of assuming bsky.social. What to do: Resolve each handle or DID to its PDS and send requests there, and test login and posting with an account on a non-Bluesky PDS.</description><pubDate>Thu, 22 Feb 2024 00:00:00 GMT</pubDate><category>Bluesky</category><category>New feature</category></item><item><title>Bluesky firehose served via the BGS, and DID keys move to Multikey</title><link>https://schedulesocialmedia.com/api-changes/bluesky-bgs-firehose-and-did-multikey/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/bluesky-bgs-firehose-and-did-multikey/</guid><description>Breaking, effective 2023-10-05. Firehose consumers had to take a new cursor from bsky.network, and code that parses DID document keys had to handle the Multikey format. What to do: Restart consumers against the bsky.network subscribeRepos endpoint with a new cursor, ideally overlapping with the old source to avoid gaps. Test DID key parsing against the sandbox PLC directory.</description><pubDate>Fri, 06 Oct 2023 00:00:00 GMT</pubDate><category>Bluesky</category><category>Breaking</category></item><item><title>Bluesky: AT Protocol repos drop history for a logical clock (repo v3)</title><link>https://schedulesocialmedia.com/api-changes/bluesky-repo-sync-logical-clock-v3/</link><guid isPermaLink="true">https://schedulesocialmedia.com/api-changes/bluesky-repo-sync-logical-clock-v3/</guid><description>Breaking, effective 2023-08-28. Code that relies on commit history or the prev field breaks, and ordering must use the new rev field. What to do: Accept repo version 3, stop treating prev as canonical history, and use rev for ordering and for requesting changes since a known revision.</description><pubDate>Thu, 24 Aug 2023 00:00:00 GMT</pubDate><category>Bluesky</category><category>Breaking</category></item></channel></rss>