Hacker News new | past | comments | ask | show | jobs | submit login

#1 reason has to be the low overhead. You could say having to include a counter is overhead, but it's still less than setting up your own blog and fragmenting your online presence into some other platform that wants you to publish there all the time.

#2 is that your followers are much more likely to read a thread, since a thread of length N will appear in your timeline at least N times. I often scroll through my feed and see a (28/30) marker, view the thread and read the rest of it. (Yes, 30 whole tweets!) If you tweeted out a link to an article you wrote 30 times, nobody would follow you. Some people will tweet twice for people in other timezones, but that's all you can get away with for out-of-band links.

#3 is that a thread often evolves out of discussion that's already on Twitter, and must participate where that discussion is happening at the time. Reacting to fast-paced news is a key one. Take this example: Josh Chafetz (the constitutional law professor, not the Congressman) watches Twitter respond to the Arpaio pardoning, and tweets a thread on why people are hot-taking it wrong[^1]. The next day, he turns it into an op-ed[^2]. But what good is an op-ed about rushed hot-takes a day late?

[^1]: https://twitter.com/joshchafetz/status/901244717115080706

[^2]: https://www.washingtonpost.com/news/posteverything/wp/2017/0...

Edit: I wouldn't be surprised if Twitter made thread counters a first-class feature. People use the platform how they want, and it will stretch to do what is needed.

Regarding #1, you could post it to some site like JustPaste.it (no affiliation, just found it via Google) and tweet the link. Chirr App itself could publish it on its servers and tweet the link with a single button.

#2 and #3, fair enough, though both of them sound like anti-features (spam, and fast soundbites over longer explanations) to me.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact