You may have noticed that when you reply to your own post on Bluesky, the platform sometimes creates a threaded chain of posts instead of a flat list of replies. This behavior is called self-reply skeet threading, and it differs from how standard replies work in both structure and visibility. The cause lies in how Bluesky’s AT Protocol distinguishes between a reply to another user and a continuation of your own thread. This article explains exactly how self-reply threading works, how it differs from normal replies, and what it means for your feed and notifications.
Key Takeaways: Self-Reply Threading vs Standard Replies on Bluesky
- Reply to your own skeet: Creates a visible thread chain that groups posts together, unlike replies to others which appear in a flat timeline.
- Thread visibility: Self-replies appear in a dedicated thread view on your profile, while standard replies appear in the original post’s reply section.
- Notification behavior: Self-replies do not trigger a notification to yourself, but they do notify followers who engaged with the thread.
How Self-Reply Skeet Threading Works on Bluesky
Bluesky’s AT Protocol treats every post as an independent record. When you reply to another user’s post, your reply is linked to that parent post via a reply field in the record. This creates a flat reply tree where all replies to the same post appear in chronological order under that post.
When you reply to your own post, Bluesky’s client interface detects that the author of the parent post matches the author of the new post. Instead of placing the new post in the flat reply section, it creates a threaded chain. This chain is displayed as a connected sequence of posts, often with visual indicators like vertical lines connecting them. The thread is stored as a linear series of records, each referencing the previous one as its parent.
The key difference lies in the user interface rendering. Standard replies are grouped under the original post in a list sorted by time. Self-replies are rendered as a thread where each new post appears as a continuation of the previous one, creating a narrative flow. This allows you to post longer thoughts, add sequential updates, or create tutorial-like content without cluttering the main reply section.
What Happens When You Reply to Your Own Skeet
When you tap the reply button on your own skeet and type a new post, Bluesky creates a record with the reply.parent field set to your original post’s URI. Because the author of both records is the same, the client treats this as a thread continuation. The new post appears directly below the original in your profile’s thread view, not in the general replies list.
This behavior is consistent across the official Bluesky app and most third-party clients. Some clients, like Deck.blue or Skeetdeck, may display thread chains with additional visual nesting. The underlying protocol does not differentiate between self-replies and other replies at the data level, only at the display level.
Key Differences Between Self-Replies and Standard Replies
The most important difference is how the two types of replies appear in feeds and notifications. Standard replies to another user’s post appear in the reply count of that post and are visible to anyone viewing the original post’s replies. Self-replies do not increment the reply count of the original post. They appear only in the thread view on your profile.
Another difference is notification behavior. When you reply to another user, that user receives a notification. When you reply to your own post, you do not receive a notification. However, followers who have engaged with your thread may see your self-reply in their Following feed, depending on their notification settings. This can lead to unexpected visibility: a self-reply might appear in a follower’s feed even if they did not interact with the original post.
A third difference is moderation. Standard replies can be hidden or reported by the original post author. Self-replies cannot be hidden by anyone except you, the author, because they are part of your own thread. This gives you full control over the thread content.
When to Use Self-Reply Threading
Self-reply threading is useful when you want to post a series of connected thoughts without creating separate skeets. For example, you might use it to write a multi-part analysis, a step-by-step guide, or a live event commentary. It keeps the content organized in a single thread that followers can easily follow.
It is also useful for creating polls or interactive threads where you post options as self-replies. Followers can then reply to individual options. The threading keeps the options visually connected.
Common Mistakes and Misunderstandings
Self-Replies Appear in Followers’ Feeds Unexpectedly
Some users are surprised when their self-replies appear in their followers’ Following feeds. This happens because Bluesky treats self-replies as new posts, not as replies. To avoid this, you can post a single thread starter and then use the reply button on that post. This still creates a self-reply, but it is less likely to appear in feeds if followers have not engaged with the thread.
Threads Break When You Delete a Middle Post
If you delete a post that is in the middle of a self-reply thread, the thread breaks. The posts after the deleted one remain visible but lose their connection to the original thread. They appear as orphaned replies. To avoid this, do not delete posts mid-thread. Instead, archive the entire thread if needed.
Self-Replies Do Not Count as Replies in Analytics
If you use third-party analytics tools, self-replies do not appear in reply counts. They are classified as new posts. This can skew your engagement metrics if you rely on reply counts to measure interaction. Be aware that self-replies inflate your post count but not your reply count.
Self-Reply Threading vs Standard Replies: Feature Comparison
| Feature | Self-Reply Threading | Standard Replies |
|---|---|---|
| Visibility in profile | Threaded view under the original post | Flat reply list under the original post |
| Notification to original author | No notification to yourself | Notification sent to the original poster |
| Appearance in Following feed | Appears as a new post | Appears only if the follower follows both users |
| Moderation control | Only the author can hide or delete | Original poster can hide or report |
| Reply count increment | Does not increment the original post’s reply count | Increments the reply count |
This table summarizes the core differences. Use it to decide which method fits your posting goal. For sequential storytelling, use self-reply threading. For direct conversation with another user, use standard replies.
How to Create a Self-Reply Thread
- Post your first skeet
Type your initial message in the composer and tap Post. This becomes the thread root. - Tap the reply icon on your own skeet
Find the speech bubble icon below your post. Tap it to open the reply composer. The composer shows a reference to your original post. - Type your continuation
Write the next part of your thread. The composer will show a small indicator that you are replying to yourself. - Tap Post
Your new post appears directly below the original in a threaded view. Repeat steps 2 through 4 to add more posts. - View the thread on your profile
Go to your profile and find the original post. Tap it to see the full thread with all self-replies connected.
You can also create a thread by replying to your own post from the thread view. The result is the same. The key is that the parent post must be yours.
Conclusion
You now understand the difference between self-reply skeet threading and standard replies on Bluesky. Self-reply threading creates a visible chain of posts on your profile, does not send notifications to yourself, and does not increment reply counts. Use it for long-form content, tutorials, or sequential updates. For direct conversations, stick with standard replies. One advanced tip: if you want to prevent a self-reply from appearing in your followers’ feeds, post the thread starter and then reply to it immediately. The first self-reply often stays within the thread context and is less likely to appear in feeds than subsequent ones.