Digital literacy · 2026-10-29
A File Name Is Not a Release Record
Renaming a file to latest.apk changes its label, not its contents. A date in the file name is not proof that the file is current, authentic or safe. Compare the claim with an…
Renaming a file to latest.apk changes its label, not its contents. A date in the file name is not proof that the file is current, authentic or safe. Compare the claim with an attributable release record rather than reading the name as a certificate.
External labels and actual evidence
Two files can have the same name and different contents. Different names can also refer to identical contents. File size adds another observable detail, but a larger file is not necessarily newer, genuine or safer.
What a checksum comparison can show
A matching checksum can support a content comparison when the algorithm, expected value and reference source are properly identified. It does not independently prove that the reference file is trustworthy. The source of the expected value remains part of the evidence.
Keep these claims separate: what the file is called, what record identifies its release and who vouches for that record.
A matching hash does not identify who should be trusted
If a file and its advertised checksum are supplied by the same unknown sender, a match can indicate consistency between those two items. It does not independently authenticate the sender. Keep content matching and publisher verification as different claims. A long hexadecimal string can look authoritative while leaving the central provenance question unanswered.