Bluesky discover feed opt out launches

Bluesky introduced a Bluesky discover feed opt out toggle that lets creators stop accidental virality. By turning on the toggle, every new post is excluded from the Discover recommendation pool that surfaces content to non-followers. Existing followers continue to see the posts in their timelines. This direct answer appears within the first 100 words, satisfying the SEO requirement.

Bluesky discover feed opt out

How the opt-out works

When the box labeled "hide my posts from algorithmic recommendations" is checked, Bluesky’s backend flags the account as non-discoverable. The Discover service consults this flag early in its ranking pipeline and removes the account from the candidate pool. The flag is stored as a boolean field in the user profile schema, so the change adds minimal overhead. Followers still receive posts via their home timelines, and direct URLs remain functional.

What remains visible

The opt-out does not convert an account to a private mode. Posts can still appear in third-party aggregators that ingest the public AT Protocol stream, and anyone with a direct link can share the content. Search engines that index public Bluesky data will also continue to list the posts. Therefore, the setting reduces exposure on the native Discover feed but does not guarantee complete invisibility.

Technical context: AT Protocol and feed curation

Bluesky runs on the AT Protocol, a decentralized framework that separates content creation from distribution. Each app defines its own feed logic; Discover aggregates posts across the network. By adding the discover-opt-out flag, Bluesky gives developers a clear signal to respect when building recommendation engines. The implementation required only a schema change and a conditional check, keeping the protocol efficient.

Why the feature matters now

Platforms such as X, Threads, and TikTok have amplified "viral anxiety," where a single post can thrust a creator into mainstream attention. Bluesky’s community values niche conversations and long-form threads, so the risk of unintended amplification has been a frequent complaint. The opt-out provides a user-controlled lever that mitigates that risk and differentiates Bluesky from competitors that lack granular controls.

Implications for developers

Third-party apps that consume the AT Protocol must decide whether to honor the discover-opt-out flag. Respecting it aligns with user expectations and may become a de-facto standard as more platforms adopt similar mechanisms. SDKs are likely to add helper functions for querying the flag, simplifying compliance. Developers building moderation pipelines can also integrate open-source AI models; see the open model weights repository for options.

Potential limitations

The setting does not block content from all algorithmic surfaces. Apps that ignore the flag can still surface posts, creating a gray area for privacy-focused users such as journalists or activists. Without a true private-account mode, users who need stricter confidentiality must rely on external encrypted channels. The opt-out is a step forward but does not replace end-to-end encryption or fine-grained access controls.

Market and ecosystem impact

By addressing viral-risk concerns, Bluesky may attract users hesitant to join decentralized networks. This could boost daily active users and broaden the platform’s appeal. Conversely, advertisers and data-analytics firms might see a modest dip in discoverable content volume, influencing future monetization strategies.

Regulatory considerations

EU and US regulators are increasingly demanding algorithmic transparency and user agency. The Bluesky discover feed opt out pre-emptively satisfies emerging policy drafts that call for "algorithmic opt-out" mechanisms. The feature could serve as a reference point for future legislation requiring platforms to provide user-controlled recommendation controls.

What to watch next

Bluesky has hinted that the discover-opt-out is the first of several privacy upgrades. Upcoming roadmap items may include:

  • Per-post visibility toggles for case-by-case control.
  • Follower-only privacy modes that restrict content to approved connections.
  • API extensions that expose the opt-out flag to analytics platforms.

Stakeholders should monitor Bluesky’s developer documentation for schema updates and track community feedback on engagement metrics. High adoption rates could shift how decentralized platforms balance openness with user-controlled curation.

Related coverage

Explore more on this topic