Mastodon threads are built with the traditional method used on many other social networks.
Here’s how to do this manually in any app:
- Post the first part of your thread, and mention that it is the start of the thread
- Reply to the post with the second part of the thread
- Reply to this reply with the third part etc
- Just keep replying to your last previous reply to add the next part, and go through all your posts in order
- When you get to the final reply, mention that it’s the end of the thread
I can see a post shared from a thread, but how do I see the thread it comes from?
Just click on a post to view the thread it comes from. After you’ve clicked on the post, scroll up and down to see the rest of the thread.
Should I number the thread I’ve created?
It’s probably a good idea to number the posts in your threads, because people may see the individual posts shared out of context and not realise it is part of a bigger whole:
- Some people number threads by just putting a number at the bottom of each post in order (1 on first post, 2 on second etc).
- Some people take this further by indicating how many posts are in the thread in total (1/5 on first post, 2/5 on second etc). If you’re not sure how many parts a thread will have, you can just number them as 1/X, 2/X, 3/X and then END on the final post. As Mastodon has an edit function, you can also add the numbering to a thread afterwards too if you want.
- Some add a cotton reel emoji 🧵 next to a post’s numbering as a visual pun to indicate a thread.
What visibility setting should I use for threads?
If you are posting a public thread, it’s considered polite to use a public visibility setting for the first post but an unlisted visibility setting for the replies in the thread. This means that only the start of the thread shows up on public timelines, and makes them easier to browse. However, if you’re unsure about how to do this don’t worry.
Is there an easier way to create threads? Can I create them in advance in one go instead of manually bit-by-bit?
Some apps and scheduled posting services may include thread-creation systems which let you write the thread in full and then post the thread in one go, but at a technical level they are just doing the above process of replies-to-replies automatically.
If you’re on a computer, you can use a notepad application to type the whole thread in one go, then split it into bits by copying and pasting sections of your text over to Mastodon.
Should I create a thread by only replying to the original post instead of replying to my previous reply? I heard this displays threads better?
No, there is no point in doing this. Threads display best if you use the method at the beginning of the article where each part is a reply to the previous part.
It’s unclear where this “only reply to the original post” suggestion comes from, it doesn’t bring any advantages, only disadvantages. If you click on a post in an “only reply to original post” thread it hides all the other parts of the thread, which makes things very confusing.
Is this anything to do with Meta’s “Threads” platform?
No. Meta chose an annoyingly confusing generic name for their social media platform, and it has nothing to do with creating threads in general. The name “threads” for strings of posts started decades before Meta even existed.