← Commit history

README: note the visible priority score on each billboard + that heroes are cached keyed on updated_at (so updated heroes re-fetch).

John Lauer ·469d917931 ·4mo ago ·parent 75a1c99
1 file changed +3−1
README.md+3−1
@@ -58,7 +58,9 @@ Each slide gets a score, and the highest scores play first: - **Novelty** (how many times you've already seen it): never seen = +60, dropping by 20 per view, gone after about three views. - **A little randomness** (+0 to +12) so the order isn't identical every run and nothing gets stuck at the top or bottom. -So a brand-new drop you've never seen floats to the very top (and wears a teal **"New today"** badge), while something old you've watched ten times sinks to the bottom. Freshness comes from a **lightweight** check of each page's last-updated timestamp, so new content surfaces within minutes, and unchanged heroes are served straight from the local cache without re-downloading.+So a brand-new drop you've never seen floats to the very top (and wears a teal **"New today"** badge), while something old you've watched ten times sinks to the bottom. Every billboard even prints **its own priority score and the breakdown** in the footer (`priority 142 (fresh 100 + new 42)`), so the ranking is fully transparent.++Freshness comes from a **lightweight** check of each page's last-updated timestamp, so new content surfaces within minutes. Hero images are cached to disk **keyed on that timestamp**, so an updated hero is re-fetched the next time the page changes, while unchanged heroes are served straight from cache with no pointless re-downloading.  ---