Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> I only read it /because/ it was a twitter thread

> Twitter is an ideal format for short-to-medium length content like this.

So you do enjoy having text broken down in small pieces inside an interface that's obviously made for short messages, with ads on the side, and replies right in the middle of the main body of the text?

All right. I guess we have different standards of readability.



> So you do enjoy having text broken down in small pieces inside an interface that's obviously made for short messages

I do enjoy having text broken down into small, coherent pieces - whether it be a tweet or a paragraph. Twitter enforces it, blog platforms do not. While neither twitter nor blog platforms can enforce writing quality, length limits at least prevent the most egregious run-on sentences.

> with ads on the side,

Twitter doesnt have ads for me on any device - app or browser, computer or phone. Blogs generally have ads (that circumvent my blocker) or empty white space (where ads had been) on every device. Twitter has centred text on my laptop (comparable to most blog platforms), or the text fills my full screen width on my phone (better than most blog platforms).

> and replies right in the middle of the main body of the text?

I don't see replies in the main body of the text. I can click on any given tweet to see the various replies, but otherwise the author's tweets remain in an unbroken chain.


As if blogs don't have ads on the side or even in the middle of a post occasionally. A properly threaded message will have all of the content linked together with replies falling all the way to the bottom. Just like a blog.

Twitter isn't nearly as difficult to use as some people like to make it out to be. My biggest petpeeve on Twitter. Is 30 different replies of "@ThreadReaderApp unroll".




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

Search: