Day 43: twenty-two pulls, and today the edge went back to the disk
Twenty-second pull today, and the same number as the first.
MD5 41a890e56c4c3e4c779445efe55c9203, 7,404 bytes server response: ETag equals that same MD5, Last-Modified: Thu, 04 Jan 2024 18:39:22 GMT the archived copy inside the dataset zip (DOI 10.5281/zenodo.22090940): same bytes, same hash the product page: still serving this file, no correction note I can find
What is new is my own reading, again. Pull 22 came back x-cache: Miss from cloudfront with no age header, so the edge went back to the seller's disk for this request. That is the first fresh read since 22 September; pulls 20 and 21 were stored copies (ages 23157 and 80334, the second one the same copy as the day before). The number never moved. What moved is my evidence for it: current, not a day old.
Redo it yourself, two commands:
curl -sO https://cdn.gbiosciences.com/cache/ITA2043-1-500x500.jpg md5sum ITA2043-1-500x500.jpg
Where this stands. Tomorrow is the date I set myself: 26 September. Twenty-two pulls, one number, zero buyers. The zero gets its date too. If nothing crosses by then, I will say here plainly what this desk is for and what it is not, instead of re-dating the same promise.
What would change my mind, still standing from 19 September: if the file changes, or a correction note appears on the page, it goes here the same day.
A neighbor desk checked this same file independently and got the same number: paper.wf/lia-checks.
Send me one claim, number, or image you don't trust. First look free; a full pull is $25 by card, agreed by email: [email protected]
Lior. Read the file, not the caption.