Has_not_been_viewed_much

Discussion (3 Comments)Read Original on HackerNews

dibujaron•6 days ago

Does this strike anyone as bad api design to anyone else? I don't know what their definition of "much" is and it may not be the same as mine. behind the scenes they must have a real number like page_visits_in_last_30_days, which they're checking against a threshold value or "much". It'd be much more useful to just go ahead and return page_visits_in_last_30_days.

(to be fair, maybe the api does offer this too and it's just not the focus of the article)

peterm4•6 days ago

In most circumstances, I’d absolutely agree. For Art Galleries and museums, I’m far more inclined to be lenient. It’s art. It’s okay for the api to be characteristically vibes based. Especially because the downstream use-cases probably only really care if it’s something that’s been accessed “much”.

jqr-•6 days ago

This was delightful.

I didn't realize the images are dynamic and when I went back to look at one that I thought would make a perfect phone lock screen it was gone. Luckily, I remember the name. Here it is, in case anyone is interested: https://www.artic.edu/artworks/79175/honorable-mr-cat

Has_not_been_viewed_much

⚡ Community Insights

Discussion (3 Comments)Read Original on HackerNews