Hacker News Reader

Just tested with 7000 books in the want-to-read list so passes the scalability test. Recommendations in decreasing priority: 1. Age > 75 is important, many older but super valuable books didn't show up as a result. Upto 200 years ago is good enough but we'd still miss Aristotle etc. 2. Ratings and Reviews should also have a higher or infinite upper bound, I'm not sure how the front end would look.

View on HN

ah cool that you uploaded 7000 books: did not do that myself. A good tip for next time :)

What do you mean by "decreasing priority"?

I was struggling with the filters UX: - the age is capped at 75 years - Ratings/reviews take the 90th percentile (like a median) of your book set This last one ensured the filters would be more dynamic. If you had a book with 100k ratings, it would have been hard to use the slider (as this was linear). Any suggestions to change the UX?

Before you could only target a lower limit. But for more functionality, I had the idea to add a max and min. However, this combination does now work

Reply on news.ycombinator.com