Bluesky Ships Per-User Repost Hiding and Thread Post-Numbering Beta

Bluesky has added the ability for users to hide reposts from specific accounts in their feeds, alongside a beta feature that automatically numbers posts within threads. Both were surfaced on August 10, 2026 The Verge.

The repost-hiding feature is accessed from an individual user's profile page. Clicking the three-dot menu on that profile surfaces an option labeled "Hide reposts in feeds." Once selected, reposts from that account no longer appear in the calling user's feeds. The control is per-account, meaning a user can suppress reposts from one source without disabling reposts globally.

The thread post-numbering feature is currently in beta. It automatically appends a post number to each entry in a thread, providing ordinal context for longer multi-post sequences. Users can enable it from Bluesky's settings menu.

The repost-hiding capability addresses a long-standing community request. Bluesky's official GitHub repository contains issue #1116, opened on August 6, 2023, requesting the ability to hide reposts and quote posts on a per-followed-account basis GitHub. The feature as shipped covers reposts specifically; the issue's broader scope also included quote posts, which the current implementation does not appear to address.

Looking at what this means for feed management, the per-user repost toggle is a meaningful granularity improvement for Bluesky's user base. Social platforms have long struggled with the signal-to-noise problem that reposts create: a handful of prolific reposters can crowd a feed with second-hand content, pushing original posts below the fold. Most major platforms offer either an all-or-nothing repost toggle or no per-source control at all. Bluesky's implementation lets users surgically quiet the most aggressive reposters without unfollowing them or muting reposts platform-wide.

The three-year gap between the GitHub issue and the shipped feature is itself worth noting. Decentralized, federated social platforms face a design constraint that centralized ones do not: feed-level controls must operate across multiple clients and, in Bluesky's case, a federated AT Protocol infrastructure. A mute or filter applied in one client may not propagate to another, and the underlying protocol must support the semantics of "hide this class of content from this user" in a way that respects the user's choice across the network. That architectural consideration likely contributed to the development timeline, though Bluesky has not stated as much.

The thread-numbering beta is a smaller but practical addition. On platforms where users compose long-form arguments or breaking-news threads across multiple posts, readers often lose track of sequence, particularly when individual posts are shared or embedded in isolation. Automatic numbering provides ordinal context that makes threads easier to follow and cite.

Both features land as Bluesky continues to iterate on feed and thread ergonomics. The repost-hiding control, in particular, gives users a tool that most competing platforms have not offered at this granularity, and it addresses a complaint that has been active in Bluesky's own issue tracker since the platform's early open-source days. Whether the feature extends to quote posts, as the original GitHub request proposed, remains an open question.