People don't really read in the same way as you might have previously expected. ("Reading a short blurb or a tweet" is not the same thing.) Can't or don't want to, I don't know, but they don't. You see the edges of it here, too--tl;drs on HN posts, sometimes, that are less than a screenful of text. And people think you're "spending a lot of effort" when you bang out a post about as long as yours is--and, sometimes, try to frame it as a bad thing.

I tend to think Thomas Pettitt has a point[1].

[1] - https://archives.cjr.org/the_audit/the_future_is_medieval.ph...

The ui is bad, the # clicks needed is growing, autoplay random videos vs playing what I actually want to watch[1], all of these issues are getting worse.

[1] If you scroll through a page, and click a video to play it, then keep scrolling, the video comes along with your scrolling. But once you want to watch another video, when you click on the new video in the stream, the old video stops but still stays on the screen frozen. there is some odd interaction between these 2 actions (I'm assuming controlled by javascript) and it's like the videos are fighting each other over what should be shown/played. It's really stupid - I can 100% predict the issue is because the teams working on these 2 features are not communicating with one another, and so are trying to optimize the user to "pay attention" to both things at once. This kind of engineering just turns me off so much that 90% of the time I close facebook and go find the video on youtube and watch it there.