Caching in a way that avoids API calls (for reloads) #7

jacksonchen666 commented 2026年01月10日 02:36:31 +01:00

Reloads of the same repo means fetching the same thing again. That's a waste of API requests.

Idea: Check the current commit SHA displayed on the front page. Use that and the repository as the "key", store that with GM_setValue, maybe storing the entire notification message (or no message) instead of resulting API requests.

I don't exactly like this very much, because it would rely on scraping the page, and page can change. In case of changes, it would be a good idea to just automatically fallback to fetching the data anyways, disregarding the cache. Do lots of double checking (make sure the SHA is a hex encoded SHA of certain length), etc. and hopefully it's not a problem?

There is also "cache" expiry or whatever. I guess 1 hour? 24 hours? Cache eviction when?

Should it be noted that the result is cached?

Reloads of the same repo means fetching the same thing again. That's a waste of API requests. Idea: Check the current commit SHA displayed on the front page. Use that and the repository as the "key", store that with `GM_setValue`, maybe storing the entire notification message (or no message) instead of resulting API requests. I don't exactly like this very much, because it would rely on scraping the page, and page can change. In case of changes, it would be a good idea to just automatically fallback to fetching the data anyways, disregarding the cache. Do lots of double checking (make sure the SHA is a hex encoded SHA of certain length), etc. and hopefully it's not a problem? There is also "cache" expiry or whatever. I guess 1 hour? 24 hours? Cache eviction when? Should it be noted that the result is cached?

jacksonchen666 commented 2026年01月25日 10:57:01 +01:00

Was doing some #6 and it seemed like GitHub was caching API responses, the rate limits decremented from the exact same number every time, at least with same page and same repos

Was doing some #6 and it seemed like GitHub was caching API responses, the rate limits decremented from the exact same number every time, at least with same page and same repos

jacksonchen666 commented 2026年02月06日 18:31:42 +01:00

Although devving now and it seems like after the cache expires, it does eat into my rate limits

So maybe this could be worth it after all

Although devving now and it seems like after the cache expires, it does eat into my rate limits So maybe this could be worth it after all