{ "version": "https://jsonfeed.org/version/1", "title": "Bluesky Protocol Services", "home_page_url": "https://bsky.network/ja/blog", "description": "Service changes, deprecations, and operational notes for Bluesky Protocol Services.", "items": [ { "id": "https://bsky.network/ja/blog/content-visibility-declaration", "content_html": "

A key principle of the atproto ethos is giving people control of their data online. The Bluesky app expresses this value with features like custom feeds and composable moderation to give people more control over their experience using the app.

\n

This week, the Bluesky app shipped a setting to allow people to ask apps to hide their posts from algorithmic recommendations. This is designed to accommodate a longstanding feature request to prevent posts from, for example, going viral via the Discover feed.

\n\n

\"A

\n

Of course, Bluesky posts don’t simply live on Bluesky, and in an effort to provide other apps, feed generators, and services with access to this setting, the app will write a new app.bsky.actor.contentVisibilityDeclaration record to a person’s repo when they activate the setting. The record itself is minimal:

\n
{ 
\"$type\": \"app.bsky.actor.contentVisibilityDeclaration\", 
\"hideFromAlgorithmicRecommendations\": true 
}
\n

There’s a single required boolean value, hideFromAlgorithmicRecommendations and if it’s set to true, apps should respect the declaration by limiting their posts in algorithmic feeds like Bluesky’s Discover. If the record doesn’t exist, treat it the same as the value being set to false. For accounts that haven’t activated the setting, nothing changes.

\n

The contentVisibilityDeclaration is not meant to hide all posts or even prevent someone’s posts from showing up in any feed. Feeds based on lists of users, or around specific topics like Science or BookSky, don’t need to use the setting. Those feeds give posts organic reach to people who have sought out posts around a specific topic.

\n

Bluesky’s Discover feed, which has the ability to make a post go viral and invite potentially unwanted attention, will respect the setting.

\n

How to use the new declaration in your apps​

\n

The intention of this setting is to let people opt out of having their posts get actively distributed outside of their own known network. In the case of the Bluesky Discover algorithm, this means setting the option to true will prevent someone’s posts from showing up in a stranger’s Discover feed, however their posts might still show up in the Discover feed of a follower.

\n

What constitutes an “algorithmic recommendation” is fairly broad and open to interpretation. Feeds built around a specific topic are not the intended audience for this setting. Aggregators that cast a wide net and perform a version of “based on your profile, interests or activities, we thought you might enjoy these posts” should consider adopting this setting.

\n

When evaluating whether to implement this feature, it may be helpful to think of the feature across two axes: intent and reach.

\n

Intent is whether the person who shows up in your app or feed wants to be there. If they are posting pictures of moss with the hashtags #forest #photography it’s probably safe to assume they are ok with their post appearing in a feed dedicated to nature photos. If someone is just posting bons mots about the trials and tribulations of modernity, you might want to check the declaration before including their post in an off-site aggregator of slice-of-life posts.

\n

Reach is how far beyond someone’s existing social network a post might travel. If you’re building an internet reader app just for yourself, the reach is very small and won’t result in anyone’s posts unexpectedly going viral. If you’re watching the atproto firehose to collect the all time funniest posts for a digital media website filled with the best viral content, you’ll absolutely want to check for the declaration.

\n

The Discover feed built in to Bluesky is both low intent (no one is able to actively signal they want their post in Discover) and high reach (because it’s the default, it has the potential to reach millions of people instantly). Discover is the canonical feed this declaration was designed for. Even feeds that perform a similar function to Discover might not meet the same threshold for intent and reach.

\n

We’re asking apps and feed operators to use their best judgment, respond to good-faith feedback with care, and reach out with questions. If you manage an app, feed, or service that uses algorithmic recommendations to discover posts that are low intent and high reach, please adopt this declaration.

\n

Bluesky is adding this to help people add a bit of nuance to how their posts show up and are distributed across the app. The Atmosphere is different from centralized social media, we don’t have to rely on the old binaries of “all public vs. all private” and can offer people new ways of being online that better capture that fullness of being a person.

", "url": "https://bsky.network/ja/blog/content-visibility-declaration", "title": "Using the Content Visibility Declaration", "summary": "The Bluesky app is shipping a new content visibility declaration setting to give people more control over where and how their posts show up via algorithmic recommendation engines.", "date_modified": "2026-09-01T00:00:00.000Z", "author": { "name": "Jim Ray", "url": "https://bsky.app/profile/did:plc:lysqukqdu6hsrhet5v2brjgo" }, "tags": [] }, { "id": "https://bsky.network/ja/blog/welcome", "content_html": "

Bluesky Protocol Services manages infrastructure built on AT Protocol. This includes the Bluesky API, the firehose of public content on the network, and the Jetstream for filtering the firehose.

\n

This blog is where we'll announce new features, post operational updates, and let you know about any deprecations. Expect the volume to be pretty low.

\n\n

Bluesky product announcements will continue to happen on the company blog and writing about the protocol will likewise continue on the atproto blog.

\n

BPS is its own thing and deserves a place for announcements.

\n

Subscribing​

\n

Follow @bsky.network on Bluesky for updates.

\n

Alternatively, subscribe to the RSS,\nAtom, and/or JSON\nfeeds.

", "url": "https://bsky.network/ja/blog/welcome", "title": "A Blog for Bluesky Protocol Services", "summary": "Where service changes, deprecations, and operational notes for Bluesky Protocol Services get written down.", "date_modified": "2026-08-30T00:00:00.000Z", "author": { "name": "Jim Ray", "url": "https://bsky.app/profile/did:plc:lysqukqdu6hsrhet5v2brjgo" }, "tags": [] } ] }