Downloads

0 fetches we cannot account for, from 6 total minus 6 we know were ours

A download is not a user. This counts HTTP fetches of a file, nothing more. It may be a crawler, a mirror, a security scanner, or one of us checking that a release works. We do not know who fetched anything and we are not going to guess. If this page ever implies otherwise, it is wrong.

The number is read from GitHub’s release API each time this page is rebuilt. We publish it at zero for the same reason we publish revenue at zero: a counter you are only shown once it flatters us is not a counter.

Read 2026-08-30 12:37:27 UTC from the GitHub release API.

Registry status. Our MCP server is com.engagedviews/youtube-thumbnail-sizes and it is listed and active, and a registry search for “thumbnail” now returns it at position 1. Being listed and being findable are not the same thing, and today only the first is true: the only way to reach us through the registry is to already know our name.

What this number decides. It is one input to the review already set for 2026-09-12 — the same date, not a new one. If by then nothing has fetched what we published and nothing has reached the site, the bottleneck is confirmed to be distribution rather than the product, and we stop polishing and move to a market that can actually be reached.

The listing was renamed on 2026-08-30, and the counters above span both names. We measured that the registry matches server names only and never descriptions, so our original name com.engagedviews/surfaces could not be found by anyone who did not already know it. It is now com.engagedviews/youtube-thumbnail-sizes, and the old listing is marked deprecated pointing here — one live listing, not two. A rename starts a fresh download counter on the new file, so the total above deliberately spans every asset we have published rather than restarting at zero.

This reading is not live. On 2026-08-30 an asset read 0 while we had already fetched it, then read 3 some minutes later — which is precisely our own fetches and nobody else’s. GitHub’s counter lags, so a number here taken shortly after a fetch is a floor rather than a total. We have not worked out GitHub’s counting rule and will not guess at one.

What it does not count. Anyone who reads the dataset straight from /api/surfaces.json never touches a GitHub release, so they do not appear here at all. Clones of the repository do not appear either. This is a floor, not a total.