Bluesky's new opt-out asks every AT Proto app to keep your posts out of recommendations

The moment someone goes looking for this setting tends to arrive late. A reply written for followers has been lifted in front of an audience it was never meant for, and the author starts opening menus. Bluesky says the toggle can take up to an hour to fully take effect ^[9]. Paired with its all-or-nothing scope, that makes it a posture you set before trouble rather than a brake on a post already moving ^[14].

What the switch adjusts is ranking, not reachability. Posts on the network are public by default and Discover can currently surface any of them ^[5], so opting out narrows who gets served your posts in one feed while leaving them readable to anyone who opens your profile. That feed is worth something. Engadget calls Discover one of the main places people on Bluesky find accounts they do not already follow ^[12], which means the price of the setting is the post you did want to travel.

The most useful thing on the screen is the wording of the checkbox: "ask apps to hide my posts from algorithmic recommendations" ^[3]. The verb is doing real work. Guaranteed enforcement covers one ranker, Bluesky's own ^[13], and Engadget notes that posts can still turn up in other algorithmically curated feeds and services built on the AT Protocol ^[8]. Engadget also reads fully private accounts as unlikely to ever arrive on Bluesky ^[15], which leaves reach as the thing users are actually handed.

Teams tell themselves that users who worry about reach want fewer impressions. What users do is narrower: they post to the audience they believe they have, and they go quiet when strangers show up in the replies. Bluesky describes the change as one of a few updates meant to give people more control over their experience and help them find their people ^[10], which is a vaguer claim than "privacy setting" and a more accurate one.

Two axes are enough to grade any reach control a vendor ships you. Where enforcement lives: inside the code that does the ranking, or in the goodwill of whoever reads the flag. What granularity it costs: the individual post, or the whole account. This one sits app-enforced and account-wide, the cheap corner on both counts, which is close to the limit of what a public-by-default protocol can enforce today.

So the rollout answer for Monday has two halves. If your users need per-post control, the honest advice is two handles, one for the work that should travel and one for everything else. If they need a guarantee, the honest advice is that the guarantee stops where Bluesky's ranking code stops ^[13], and anything downstream is a courtesy. In a month, the number worth pulling is whether the people who switched it on are still posting as often as they were, which tells you more about whether the setting worked than any count of Discover impressions.