Tag: Web Evidence

Posted on by

Preserving context when only screenshots remain

A screenshot is often what survives after everything interactive is gone.

It can preserve a headline, layout, username, photograph, comment, error message, or strange little piece of interface that no crawler captured. That makes screenshots valuable. It also makes them dangerously easy to overread.

A screenshot preserves pixels. A website is more than pixels.

What the image actually proves

With sound provenance, a screenshot can show that a particular screen displayed particular visible material at a recorded moment. It can preserve typography, relative placement, colors, advertisements, timestamps printed by the site, and content that was visible only after interaction or login. Without provenance, the pixels alone cannot prove when, where, or even whether the image came from the claimed live page.

What it usually does not preserve is the target of a hyperlink, the HTML source, hidden text, alt text, JavaScript state, network requests, content below the captured viewport, or the difference between something rendered by the server and something inserted by a browser extension.

That difference is why professional web archiving normally saves structured web material rather than only taking pictures of it. The Library of Congress describes the WARC web-archive format as a container for harvested resources plus record information such as target URI, date, type, and other metadata. Its preservation guidance also says archived content should identify the archiving institution, capture time, and limitations in functionality.

A PNG by itself carries far less context.

Provenance makes a screenshot stronger

Suppose the only surviving evidence of a deleted forum post is Screenshot_2024-03-11.png.

That is better than nothing, but a researcher immediately wants more. What was the full URL? Who took the screenshot? Was the user logged in? What time zone did the site’s displayed timestamp use? Was this the whole thread or a cropped section? Was the image edited after capture?

A useful preservation package records the original URL, capture date and time, browser or app, account state if relevant, and a short explanation of what was being documented. Keeping the uncropped original alongside any annotated derivative is better than saving only the version with arrows and circles added later. A checksum can help show that the preserved image itself has not changed since it entered the collection.

Nearby screenshots can also restore context. Capturing the page above and below the disputed item, the profile that posted it, or the navigation that led there can be more useful than one perfectly framed viral rectangle.

Screenshots are evidence, not a replacement website

Sometimes nothing better survives. In that case the screenshot deserves preservation precisely because it may be the last visible trace of the artifact.

But the limits should travel with it.

A screenshot cannot normally prove that a link worked. It cannot reconstruct a deleted video. It may not reveal whether text was selectable, dynamically loaded, or changed seconds later. And without provenance, future researchers may be unable to distinguish a genuine capture from a mockup.

The proper conclusion is not that screenshots are useless. It is that they need witnesses.

When the living webpage is gone, a screenshot may be the body. URLs, timestamps, capture notes, surrounding files, and independent corroboration are what give it a name.

Posted on by

Content drift: working links whose evidence has changed

The link works; the evidence does not

A URL that still loads is no guarantee that the page behind it still supports what you linked. The request succeeds, the browser renders, and the fact you relied on is gone. Researchers call this content drift: a resource keeps its address while its content changes until it no longer represents what someone cited.

Broken links are honest; drift is not

A dead link announces its failure. A 404 or an expired domain tells you something is missing. Content drift never announces itself. The click succeeds, the page looks normal, and nothing warns you that the sentence you came to check was rewritten a day, a month, or a decade ago.

The stockpile page that changed overnight

One documented example comes from the early pandemic. The Strategic National Stockpile page described the stockpile as supporting “state, local, tribal, and territorial responders.” Archived versions from April 3 and April 4, 2020 show the wording changing immediately after public controversy over how the stockpile was supposed to serve states. A Los Alamos web-preservation report uses the two captures as a concrete example of content drift: the live URL survived while the policy language at that URL changed.

How often it happens

Drift is common. In 2016, Shawn Jones and colleagues published Scholarly Context Adrift, examining web references drawn from millions of scholarly articles. Among references for which a representative archived copy could be compared with the live resource, more than three quarters had changed.

Dated records are the workaround

That is why dated captures and version records matter. The Wayback Machine and the Memento protocol are built around the same basic need: reaching a version of a web resource as it existed at a particular time. Recovery has limits. Most references in that 2016 study had no usable archived copy near the publication date, and an archive only preserves what someone captured, whenever they captured it.

When a URL still works, the instinct is to trust it. The fix is a timestamp: save a copy the day you read it, note the date, and link to the capture alongside the address. Drift is silent by default; the way to hear it is to keep a record of what you saw.