The reverse chronological feed is the laziest algorithm. Puts the burden of...

@mistersql

The reverse chronological feed is the laziest algorithm. Puts the burden of filtering drek onto the user.

The algorithmic feed that optimizes time-on-site and engagement is just evil and cheap tricks, the equivalent of saying "wait there's more" when someone is about to leave the site.

Self-replies

For my custom mastodon client, I'm adding filters, like "storms, shorts, discussions, etc" and there are so many API and db query expensive things to do, like for discussions, if I can't see the root user's post maybe I don't care to see the replies in the discussion tab.

Storms/shorts/news I just need that last month of posts, but for "cool software" I really need the entire post history of the user.

Storms/shorts should be read on a per user basis. But news, videos (i.e. recommended content) is better viewed with all users data mixed up.

Anyhow, just saying I'm getting some sympathy for engineers that have to figure out how to make these features work for 1 million, 1 billion users.