Bluesky now lets you hide reposts from that annoying person you follow

Bluesky introduced a user-controlled setting that lets each account decide whether to see reposts from a particular followee. The option is accessed via the three-dot menu on the target profile, mirroring a similar control on another platform. This gives end users a finer grain of feed curation without altering the core content delivery pipeline.

From a development perspective, the change is confined to the client layer. No new server-side endpoints or payload formats are mentioned, so existing feed-fetching logic can remain unchanged. The only requirement is to render the toggle and honor the user’s preference when rendering the feed list.

The hide-reposts flag applies exclusively to the main feed view. It does not suppress the original posts of the muted account, nor does it affect reposts that might appear in notifications, search results, or third-party integrations. Engineers should be aware that any downstream services that repurpose feed data will still receive the full set of reposts unless they also respect the new client flag.

Because the feature is a per-author setting, it scales linearly with the number of accounts a user chooses to mute. There is no indication of rate limits or performance impact, but UI designers should consider how to present potentially long lists of hidden accounts. The toggle’s simplicity suggests minimal overhead for both the client and the server.

Overall, the addition improves user experience by reducing unwanted noise, while keeping the platform’s data model stable. Teams maintaining Bluesky clients will need to add the hide-reposts control and ensure the feed renderer filters accordingly, but no broader architectural changes appear necessary.