Item — HN Reader

> Quota exceeded for quota metric 'Read requests' and limit 'Read requests per minute per user' of service 'sheets.googleapis.com' for consumer 'project_number:849324395320'.

maybe cache this thing my guy you're just doing a bunch of reads

---

constructive suggestions

- you have a pretty cheap process here, and HN exposes historical posts by date. perhaps worth running this back the last 2 years to reconstruct a history of sentiment?

- introduce alternative sorts around the net positive/negative sentiments and absolute positive sentiments, similar to State of JS (https://stateofjs.com) - you'll see the gpt outperformance more

- matching of Opus 4.7 and Opus Latest seems sus?

1 comments

Didn't expect it to get hammered like that, just added caching for the sheets request. Thanks, my guy ;)

Backfilling it further is definitely in the cards, I just want to stabilize the methodology first.

If a comment just mentions Opus without being more specific and in the absence of relevant context clues, it gets mapped to Opus Latest. So it's saying more about the model family than a specific version. Tbh I'll probably remove all "-latest" data points going forward, as I mentioned in another comment.

> If a comment just mentions Opus without being more specific and in the absence of relevant context clues, it gets mapped to Opus Latest

Consider keeping this data point but instead calling it something like "Opus Unspecified". Let the user decide how to interpret it.

you prob just want to map ALL opuses to "opus-all" or somethign - do we really care on 4.5 vs 4.6 vs 4.7, we just want to see trendline over time