"Please don't complain about tangential annoyances—things like article or website formats, name collisions, or back-button breakage. They're too common to be interesting."
> Not to humblebrag or anything, but my favorite part of getting posted on hackernews or reddit is that EVERY SINGLE TIME there's one highly-ranked reply that's "jesus man, this could have been a blog post! why make 20 tweets when you can make one blog post?"
> CAUSE I CAN'T MAKE A BLOG POST, GOD DAMN IT.
I have ADHD. I have bad ADHD that is being treated, and the treatment is NOT WORKING TERRIBLY WELL.
I cannot focus on writing blog posts. it will not happen.,
You can append to a blog post as you go the same way you can append to a Twitter feed. It's functionally the same, the medium just isn't a threaded hierarchy. There's no reason it has to be posted fully formed as he declares.
My own blog posts often have 10+ revisions after I've posted them.
"Fix" what? That the medium or style they choses to express themselves doesn't work well for you? Well, tough; that's your problem, not his. They're not your bitch. The entitlement...
> That the medium or style he choses to express himself doesn't work well for you
It doesn't work well for thousands of people, which is why there are always complaints.
You can say the exact same things about his post asking them to fix the controller. Oh "the entitlement" and "that's his problem, not the controller manufacturers". We're asking him to fix his posts. He's asking them to fix the controller.
When something is suboptimal, you're well within your rights to complain about it. Posting long rants as Twitter threads is suboptimal for the consumers of said threads, just as a controller you can't turn off is suboptimal for the consumer of the controller.
> "When something is suboptimal, you're well within your rights to complain about it."
You can complain about it on your own Twitter. Here, it's explicitly against the HN guidelines: "Please don't complain about tangential annoyances—things like article or website formats, name collisions, or back-button breakage. They're too common to be interesting." - https://news.ycombinator.com/newsguidelines.html
generally speaking coming out hot with a "whatever you're doing is wrong and you need to do it the way I want you to do it" is always a hard sell - regardless of how valid your original argument may be
It’s strange I have no issue reading posts like these but every time they come up someone complains about the format of twitter and I still have no idea what makes it so difficult for people and I definitely did not grow up with it.
Well first of all you need to be familiar with the format. Or better said, with the abuse of the format. Because while it might look like replies, you need to figure out it was used to post an article and not actually additions/corrections what would be a common use for someone replying to themselves. But it's still hard to figure where it ends as the replies from the author seamlessly blend into other users' replies. It doesn't help this particular author doesn't number those tweets (which in itself is ridiculous) or even use punctuation or capitals. It just seems like random rant, not something we're supposed to be be reading when someone shares a tweet.
And then there's the noise. Why do I need to skip icons, names, numbers, padding, dividers after every sentence? And while our brains are relatively good at it, I still need to process it as it gives clues into where the "article" ends.
Twitter is the worst format to post articles. At least it was until someone came up with the idea to post them as videos with computer voiceover.
(I'm using the word article here, but I'm still not convinced it isn't just a random rant)
I just tried and I could read that whole thread without being logged in. Maybe twitter lets you read the whole thing if you've ever logged in with that browser?
I guess if this is actually a problem, anyone who's bothered by it, who doesn't have a twitter login could look into rewriting twitter.com links to nitter.net instead.
If you scroll a little too far at the end, it'll lock you out and prompt you to login. Basically as soon as the first "recommended" tweet is displayed mid-screen.
The way I scroll as I read, I often have to go back and reload the page just to read the last tweet in a thread.
Because it's actively user-hostile. It's not that we can't figure it out, it's that it takes extra effort and creates a problem that shouldn't be there in the first place. If things like ThreadReaderApp or Nitter can present the content in a more accessible & pleasant form, Twitter should be able to do so as well.
I see this and would argue it’s not user hostile. Rather twitter’s target users are those who sign up and log in to view and consume content so they can target. It’s not a hostility towards user but rather a non-catering to its non-users. For the majority of content , tweets and threads are not an issue. They easily consume it and if they don’t want to deal with the format they utilize tools that utilize Twitter’s API.
I kind of appreciate the signal: When someone chooses to blog on twitter you know it's facile at best, and more likely simply stupid (as in this case).
It's fine to prefer different approach to content publishing, but there are lots of solutions to this problem – use them instead of complaining about the ways that other people choose to publish their content.
