How to Hide Reposts on Bluesky 2026: Curate a Clean Feed

On August 10, 2026, Bluesky shipped a small control that changes how you can clean up a messy timeline: hiding reposts from an individual account without unfollowing, muting, or blocking that person. Covered by wersm.com and by The Verge, the update fits Bluesky’s longer-running bet that users should be able to shape the signal before the platform decides what the signal means.

This guide explains what the new feature actually does, the second change that shipped with it (post numbering for long threads), and a four-step curation workflow that turns a noisy feed into a clean one — then archives the posts worth keeping as Markdown so the signal survives past the algorithm.

Why “Hide Reposts From Specific Users” Matters

Reposts are one of the most common ways a social feed gets messy. A repost is not just an endorsement — it is a distribution event. One active account can pull an entirely different set of conversations, jokes, links, and niche obsessions into your timeline every single day. Historically, platforms treated that as part of the bargain: follow a person, get the whole package.

Bluesky’s new control separates those layers. You can keep the person and reject one specific behavior — their reposts. As wersm.com summarized the update, it gives users “a smaller lever than mute, block, or unfollow.” For creators and brands the implication is sharp: distribution is becoming more conditional. Reposting aggressively may still drive reach, but it can also train followers to cut that behavior out of their feed.

How the Hide-Reposts Feature Works

The feature is a read-side filter. When you hide reposts from a specific account, only your feeds change. The account you filter from gets no notification, and their overall posting reach is unaffected. It is local to your home timeline and any custom feeds you control.

• Not unfollow. You still see the account’s original posts, replies, and quote posts.
• Not mute. Muting hides everything a person posts; hiding reposts removes only the reposts.
• Not block. The relationship stays intact and two-way — you just stop receiving that one behavior.

The result is a feed you can tune at the behavior level rather than the account level. It is the same philosophy behind Bluesky’s custom feeds and moderation controls: the experience should be adjustable, not dictated from the top down by one opaque feed system.

Post Numbering for Long Threads

The same update shipped a second, quieter change: post numbers for threads.

Long Bluesky conversations often carry their value across replies, quote posts, and running threads. Numbering each post makes those conversations dramatically easier to follow and reduces the friction of staying with a long discussion. It does not change what people post — it changes how readable a thread becomes. wersm.com called both changes “very Bluesky”: small, user-facing controls that lean into readability and agency.

A Four-Step Feed Curation Workflow

Here is a repeatable workflow for turning a noisy Bluesky feed into a clean one, then keeping what matters:

1. Audit your noise. Spend a day watching which accounts flood your timeline with reposts you skip anyway.
2. Hide, don’t cut. For each account, hide reposts instead of unfollowing or muting — you keep the person and drop the behavior.
3. Curate your feeds. Lean on custom feeds for the specific signal you want, and use the new per-account filter on top.
4. Archive the survivors. Save the posts that matter as Markdown before they disappear, change, or get edited.

A small Python script using Bluesky’s public atproto API turns the posts you keep into durable Markdown, no account or token required for public content:

import json, urllib.request
did = "did:plc:z72i7hdynmk6r22z27h6tvur"
url = ("https://public.api.bsky.app/xrpc/app.bsky.feed.getAuthorFeed"
       "?actor=" + did + "&limit=10")
data = json.load(urllib.request.urlopen(url))
for item in data["feed"]:
    rec = item["post"]["record"]
    print("## " + rec.get("createdAt", "")[:10])
    print(rec.get("text", "") + "\n")

For a full account or timeline, add pagination with the cursor field so no post is skipped. The official feed endpoint documentation describes the exact response fields, including the text, timestamp, and cursor.

Curate, Then Archive — Save the Signal, Not the Noise

Feed curation and archiving are two halves of the same job. Curation decides what reaches your eyes; archiving decides what survives. A free account can edit or delete a post, a handle can change, and an algorithm can move on. If a well-curated post matters — a research note, a useful thread, a reference you will cite later — the only copy you truly control is the one on your own disk.

Markdown is the right format for that because it is plain text: searchable, versionable in git, indexable by an LLM, and readable in any notes app now and in ten years. A screenshot preserves the pixels; Markdown preserves the words, the structure, and the links.

bluesky-archive/
  profile.json
  2026-08-11-feed-curation.md
  media/
    image-01.jpg

Name each file by the post’s date and slug, store the handle in a small profile.json alongside, and keep image links relative so the folder mirrors cleanly anywhere. Because everything is plain text plus files, you can read the archive without a Bluesky server — and it feeds into any AI, notes, or publishing workflow you add later.

How Feed Curation Compares Across Platforms

Bluesky is not the first platform to offer a per-account boost filter — Mastodon has long let you hide boosts from individual accounts. What makes the Bluesky update notable is that it lands inside a product already pushing hard on user agency, and it signals where distribution is heading: conditional, behavior-level, and user-controlled. For anyone building a cross-platform archive, that means the feed you curate and the posts you save are increasingly the same curated set.

The Bottom Line

Hiding reposts from specific users is a small control with a clear direction. It lets you follow people for what they actually post and reject the behavior you do not want — without the blunt hammer of unfollow, mute, or block. Pair it with post numbering for long threads and you have a noticeably cleaner, more readable Bluesky experience.

The larger lesson is about ownership. A curated feed still lives on someone else’s server, and the posts you enjoy can vanish at any time. Decide what the signal is, then archive it. Markdown gives you a copy that no algorithm, account change, or platform decision can take away.

FAQ