Bluesky Adds Per-Account Repost Hiding and Thread 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 lives on an individual user's profile page. Clicking the three-dot menu on that profile reveals an option labeled "Hide reposts in feeds." Once selected, reposts from that account stop appearing in the calling user's feeds. The control works per-account, so a user can quiet reposts from one source without turning off reposts everywhere.
The thread post-numbering feature is currently in beta. It automatically attaches a post number to each entry in a thread, giving readers a sense of sequence for longer multi-post chains. 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, asking for the ability to hide reposts and quote posts on a per-account basis GitHub. The feature as shipped covers reposts specifically; the original request also included quote posts, which the current implementation does not appear to address.
For feed management, the per-user repost toggle is a meaningful step forward in granularity. Social platforms have long struggled with the signal-to-noise problem that reposts create: a handful of prolific reposters can flood a feed with second-hand content, pushing original posts out of view. Most major platforms offer either an all-or-nothing repost toggle or no per-source control at all. Bluesky's approach lets users surgically quiet the most aggressive reposters without unfollowing them or disabling reposts platform-wide.
The three-year gap between the GitHub issue and the shipped feature is itself worth noting. Bluesky runs on the AT Protocol, a federated architecture — meaning the network is spread across multiple servers rather than controlled by one company. In that kind of setup, feed-level controls must work across multiple clients (the apps people use to access the network), and a filter applied in one client may not carry over to another. The underlying protocol has to support the idea of "hide this class of content from this user" in a way that holds up across the network. That architectural constraint 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 arguments or breaking-news threads across multiple posts, readers often lose track of sequence, particularly when individual posts are shared or embedded on their own. Automatic numbering provides ordinal context — a sense of where each post sits in the chain — making threads easier to follow and cite.
Both features land as Bluesky continues to refine feed and thread ergonomics. The repost-hiding control, in particular, gives users a tool that most competing platforms have not offered at this level of granularity, and it addresses a complaint 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, is an open question.
