Bluesky Thread Viewer
When a public Bluesky thread suddenly looks incomplete, the problem is often not deletion. It is a context break: the thread API returned a blocked or unavailable placeholder and other viewers stopped there.
What people mean by "nuclear blocks"
In Bluesky discussions, people sometimes use the informal term nuclear block for cases where one block relationship causes a much larger thread-viewing failure than expected. The post may still exist publicly, but the normal thread response hides part of the conversation behind a blocked or unavailable placeholder.
That makes the effect feel "nuclear": not only the blocker and blocked account lose context, but unrelated readers can also end up with a broken or incomplete thread view.
This is community shorthand, not an official Bluesky product term.
Official background
Bluesky and AT Protocol documentation already explain the core mechanics behind this. The short version is simple: blocks are public records, and compliant services use them to hide interaction and thread context.
- Bluesky docs: Blocking users explains what blocks do in the app and protocol.
- AT Protocol: Why are blocks on Bluesky public? explains why blocks are public records and why they affect clients, AppViews, and threads.
- Bluesky docs mirror: Why are blocks on Bluesky public? covers the same technical background on the Bluesky docs site.
In practice, that means a post can still exist publicly, but a thread viewer may omit it in context because the block state changed what the AppView is willing to show in that conversation.
Why this viewer is useful
- It shows the whole publicly reachable conversation instead of stopping at the first broken thread node.
- It highlights the exact post or gap that caused the thread response to break.
- It can recover context when the post is still public somewhere, even if the normal thread endpoint omitted it in context.
- It makes long conversations understandable again by preserving reply links and parent jumps.
Why nuclear blocking is a practical problem
- Readers lose context and cannot tell who is replying to whom.
- Public conversations become harder to audit, quote, or understand later.
- The visible thread can make participants look incoherent because key replies are missing.
- Other viewers often stop at the broken node and give up entirely.
- Even when a post still exists publicly, it can become effectively invisible in thread context.
What the thread viewer does
- Starts from one Bluesky post URL or AT-URI.
- Finds the conversation root and expands publicly reachable replies.
- Marks the first post that caused the thread break.
- Links replies back to their parent posts inside the same thread view.
- Opens the break-causing author's public blocking list when available.
How to inspect a broken thread
- Open the thread viewer and paste the post URL that lands inside the broken conversation.
- Load the thread and look for the red thread-break card and the red thread-break banner at the top.
- Use Jump to break to move directly to the post that caused the public thread response to break.
- Use Reply to @handle jump on any reply row to move to the parent post and follow the conversation clearly.
- If needed, open Author's blocking list in a new tab for extra context.
What the colors mean
- Orange: conversation start.
- Blue: the post you originally loaded.
- Red: the post or gap that broke the public thread view.
- Neutral: ordinary posts in the same conversation.
Important limits
- The viewer can detect that a break happened in public thread data.
- It can sometimes recover a post if the post is still publicly reachable outside the broken thread context.
- It cannot truthfully prove who blocked whom from public data alone.
- If a record is actually deleted or no longer public, the viewer can only show the gap.
This is a public-data viewer, not a private moderation inspector. It shows what public Bluesky and AT Protocol endpoints still expose.