Changes touching this path

• the install page stops saying the script fetches from dl.millerbyte.com first, because as of the hop it does not: the paragraph is titled Where the bytes actually come from, and it said the download list is rewritten to put dl.millerbyte.com first and the script then fetches the archive from there. 1647 put a COUNTED hop in front of that, so both halves were false the moment the hop landed - and the page had no mention anywhere that a download is now counted at all. that is the flattering direction again, on the page that exists to tell people where their bytes come from, and queued for a deploy that has not happened. the notice, the terms and now this are three pages in two days where a true sentence outlived the code under it. the replacement names all three entries in order and what each is for: the hop counts and redirects, R2 is where the bytes come from either way, GitHub needs a credential. it says the hop records the release, the platform and the time and does not record who you are, and it points at /privacy rather than restating it. the order is named as the fallback too, since a reader who learns their download is counted will reasonably ask what happens when that thing breaks - one failed request and a direct-R2 install, nothing about the install changes. ⭐ the all-platforms TABLE links are deliberately left pointing straight at R2, and the manual-install note saying those links serve anonymously stays true because of it. 1647 asks for the table to point at the hop with the direct URL still visible; doing that would falsify that sentence in the same breath, so it is recorded as the remaining half rather than done half-way. a page that counts a click it calls anonymous is the defect this change exists to avoid (#1647) c7a16b2e · dbf3dbe6…

Renames are not followed. loot's tree maps a path to an address, so a rename is a delete and an add. This list is the history of the name, not of the bytes.