News for hackers. Stuff that matters.
Re:Mastodon announces new European non-profit, change of CEO by ekianjo on Tuesday January 14, 2025 @06:14PM (#42705244)
The solution was always: provide several algos on top of chronological order, and let people choose.

Client side Algo cannot be implemented because the API does not give you enough controls (I know, I have written Mastodon clients)

Re:Mastodon announces new European non-profit, change of CEO by mkl on Tuesday January 14, 2025 @07:32PM (#42705899)
If you can get the messages, you can run a client-side algorithm - just download everything in the last 24 hours or whatever, and algorithmically choose what to display in what order.
Re:Mastodon announces new European non-profit, change of CEO by ekianjo on Tuesday January 14, 2025 @09:49PM (#42706764)
That's a huge waste of resources on the client side. If every client does that it will bring the servers to their knees.
Re:Mastodon announces new European non-profit, change of CEO by nyclounge on Tuesday January 14, 2025 @10:14PM (#42706914)
While I agree with you, technically everything can be done with API, but what are the bottle neck of just have everything accessing a db table directly? Cutting out the http API middle man?