edit: to everyone saying that this doesn't happen anymore, thanks for the clarification! i guess i stopped fighting the algorithm back when this wasn't the case.
edit: to everyone saying that this doesn't happen anymore, thanks for the clarification! i guess i stopped fighting the algorithm back when this wasn't the case.
Of course, the main way they measure ‘liking’ the site is via engagement, which may actually just measure compulsion to use, not enjoyment. And, of course, the however small, cohort of people who genuinely ‘like’ chronological order are ignored.
But algorithmic feeds are endlessly unique and composing them is vastly more difficult than doing chronological order.
Maybe to improve profitability you'd want to improve how much you can serve out of memory, but I think Twitter has more than enough compute to just generate your page for you when you visit. (I haven't seen a fail whale for over a decade!)
My understanding (from a watching a Twitter Tech talk, maybe about redis?) is that that is actually how it is (was) implemented. They were so focussed on time to first render, they took the efficiency hit.
I think the issue is a little deeper: it's not that people want chronological vs. non-chronological timelines, it's that they want a way to get the "best", "most relevant" content to be surfaced from those timelines and presented in a sane way. Non-chronological timelines are better at producing the "best", content (for some relative definition of "best", at least), but by presenting it out-of-order, it requires more of the user.
Suppose that your feed refreshes itself while you're trying to read a particular tweet. You go back looking for it--now badly ordered, irrelevant content is positively correlated with your amount of scrolling and time spent in-app.
So the app isn't just optimizing against your lazy attention, it's probably in some cases also rewarding itself for actively hindering you.
These software patterns are anti-human. Imagine using a hammer that is trying to maximize your engagement with the hammer itself. Well, I know I'll be more engaged with the hammer if the head keeps falling off, but that isn't what a hammer is for.
It usually takes me a few minutes to notice. I'll see a tweet that I recognize from a previous session, or from someone I don't follow, or something like that.
Perhaps I'm on the wrong end of Twitter's A/B testing.