The algorithm
is extremely simple at the moment:
activity = voteCount + (10 * numComments)
then there are thresholds for how many bars to show.
software development
I think an ideal sorting for me that we could implement in the short-term would be something like 1. show me any content with trust>0 (new includes new comments on old posts and also includes posts which I haven’t read yet), sorted by trust. Then 2.... I’m a bit skeptical that we can keep going indefinitely using Haskell-guys to do UI. UI can be a ton of work, and most Haskell people seem to not want to spend that much time on UI things, since they’re not as interesting as backend.... I think we can have it all. If we capture our various patterns and abstractions for the frontend in Haskell code, we can hide Tailwind from our frontend developers almost completely while making sure that our styles are consistent across our UI components.... I’m not opposed to the idea in general. My main UX concern is adding too many buttons and which users ignore. Implementation-wise, I’m wondering how the system determines which topic scores to display.... I’m really into the idea of dogfooding; I expect it to help us figure things out quickly (I’m a bit vague on what exactly would improve, though). I’m also worried that dogfooding would have us spend too much time on "stuff that ends up being polish" / "typical" web app features...