ARP-001 — THE CLAIM THAT CAME BACK

Full report

On this page

Executive Summary

The digital era has precipitated a profound epistemological crisis in the fields of historiography, journalism, and forensic chronology: the proliferation of conflicting, fluid, and highly mutable temporal markers attached to a single digital or physical artifact. Artifacts routinely vanish from public accessibility, only to resurface years later in mutated forms. Upon their return, these documents, claims, and images frequently carry inherited, machine-generated, or retrospectively applied metadata that obfuscates their true origin. When researchers attempt to trace the provenance of a specific item, they encounter an archival environment fundamentally hostile to linear continuity. This report designs a rigorous, exhaustive methodological framework for charting the chronology of claims, documents, webpages, quotations, images, accusations, and interpretations that disappear and later reappear. The framework establishes a standardized sequence for tracking volatile information, defined herein as the progressive chain: ORIGINAL → LAST VERIFIED → GAP → ARCHIVE → RETURN → MUTATION → PRESENT STATUS. The primary objective of this framework is to prevent one date from silently impersonating another. Temporal ambiguity, if unmanaged, allows a website crawl date to masquerade as an authorship date, or a database migration epoch to pose as a historical artifact's creation. By operationalizing Extended Date/Time Format (EDTF) standards, establishing a meticulous event-modeling schema, defining explicit chronological states, and proposing user-interface grammar that counters deterministic construal error, this research provides a definitive blueprint for tracing the reappearance of digital and historical artifacts without creating false continuity.

Central Research Problem

Historical and digital records frequently contain multiple competing dates, creating an environment where chronological certainty is often an illusion. The central research problem lies in the ontological friction between an artifact's actual temporal origin and the mechanical timestamps affixed to its digital surrogates. When a physical document is digitized, or when a digital document migrates across content management systems (CMS), it accrues a sedimentary layer of metadata. These dates frequently conflict and compete for primacy. A single digital claim may simultaneously possess a 1970 UNIX epoch timestamp, a 2015 copyright footer, a 2018 Wayback Machine capture date, and a 2021 CMS Last-Modified header. This chronological dissonance is exacerbated by the mechanics of network infrastructure and archival crawling. Server migrations routinely restore backups that overwrite file-creation metadata with the time of the restoration event. Web archives capture distinct elements of a page—such as HTML, cascading style sheets (CSS), and images—at entirely different times. This discrepancy creates anachronistic composite pages where, for instance, a 2012 text is wrapped in a 2016 layout and paired with a 2024 image1. Search engine algorithms index pages long after their initial publication, often treating the discovery date as the inception date in search snippets2. Furthermore, bad actors intentionally manipulate publication dates within CMS databases to simulate predictive foresight or retrospectively alter history. The core methodological challenge is the formulation of a system that qualifies every date with its exact provenance, explicitly distinguishing between machine-generated metadata, human-assigned publication dates, and externally verified archiving events. A rigorous chronology must isolate the specific temporal state of an event, ensuring that the limits of what is known are structurally embedded in the data model itself, thereby preventing automated systems and human analysts from drawing continuous lines across undocumented voids.

Date-Type Glossary

To prevent categorical confusion, chronological modeling requires a highly granular taxonomy of date types. The following glossary defines the distinct temporal markers frequently encountered in forensic chronology, explicitly outlining why they must never be conflated.

Required Chronology States

Chronological modeling must accommodate the inherent uncertainty of historical and digital records. The Extended Date/Time Format (EDTF), which has been formally incorporated into the international standard ISO 8601-2:2019, provides a rigorous syntax for expressing these nuances11. EDTF specifically addresses the long-standing need in archival communities to express dates that are uncertain, approximate, or only partially known11. The following time states must be utilized to qualify dates within the reappearance chronology, ensuring exactness is never simulated where it does not exist.

Required Event Model

To accurately map the reappearance sequence, a standardized object model is required. This model prevents temporal flatlining by demanding metadata for every assertion. An event is not merely a date; it is a complex intersection of time, actor, location, and epistemological certainty.

Chronology Object Schema

The following schema defines the minimum required fields for any event committed to the chronology database.

Event Types

The timeline progresses through specific, discrete actions. An event type categorizes the precise nature of the interaction with the artifact. Conflating these events guarantees chronological failure.

Date-Selection Protocol

When determining how a stage should be dated, the fundamental protocol dictates that a researcher must never invent a midpoint or representative year for an uncertain range. A range of 1960 to 1969 must never be recorded mathematically as 196513. Doing so creates a false specific data point that downstream algorithms and analysts will treat as historical fact. The primary framework for selection and formatting relies on the Extended Date/Time Format (EDTF) ISO 8601-2:2019 standard, utilizing Level 1 and Level 2 extensions.

1. Unspecified Digits: If the exact year is unknown but the decade is certain, utilize the X (or u) notation. A document known to be from the 1980s is recorded as 198X rather than defaulting to 198012.

2. Uncertain and Approximate: If a date is a guess based on strong contextual clues, it must be tagged as approximate (\~), uncertain (?), or both (%). For example, a file creation date that looks like a default system epoch but is suspected to be earlier must not be blindly trusted. If a researcher estimates the true date is around 2004, it is recorded as 2004\~13.

3. Open Intervals: If an artifact is known to have been published prior to a specific archive capture, but the start date is completely unknown, it must be logged as an open interval: \[..2014-04-15\]14. This explicitly communicates that 2014-04-15 is a terminus ante quem, not the origin.

4. Date Hierarchies and Trust: When multiple dates conflict, the protocol mandates selecting the date with the highest cryptographic or third-party archival integrity for the Event Type in question. An archive-capture date supersedes a CMS modification date for establishing a terminus ante quem. However, a claimed publication date supersedes an archive-capture date only if corroborating external citations or primary evidence supports the claimed date. If corroboration is absent, the archive-capture date is the only verifiable temporal anchor.

Gap Taxonomy

A chronology is defined as much by its silences as by its events. A line should never be drawn continuously across a gap unless continuity is independently documented. Inferring uninterrupted publication from a sequence of disparate captures is a profound methodological error. The taxonomy of gaps classifies the nature of the silence.

Theoretical Constraints on Gaps

Analysts must navigate several statistical and cognitive traps when assessing gaps:

• Interval censoring occurs when an artifact disappears sometime between two observed archive captures (e.g., present in 2012, missing in 2015); the exact deletion event is censored within that interval. We know the deletion occurred, but we only have a time bracket, not a timestamp.
• Right censoring occurs when an artifact remains accessible at the end of the study period; we do not know when or if it will disappear in the future. The timeline must explicitly remain open-ended.
• Survivorship bias leads researchers to mistakenly assume that the surviving artifacts accurately represent the totality of published claims. In web archiving, this means assuming a claim originated on the high-traffic site where it was captured, ignoring the likelihood it was born on a smaller, un-archived forum that subsequently died.
• Preservation bias reflects the reality that well-resourced, English-language, or highly trafficked websites are heavily archived, while peripheral data is lost.

Crucially, a gap in an archive denotes "not observed," which must never be mathematically or logically conflated with "did not exist"5. Absence of evidence in a web crawl is not evidence of absence on the live web.

Case Studies

The following six case studies illustrate the catastrophic consequences of date confusion, demonstrating how the reappearance of mutated artifacts can fundamentally alter historical, scientific, and legal interpretations.

**1. Archive Timestamp Mistaken for Original Publication: Valve Corp. v. Ironburg Inventions (Born-Digital/Legal)**

In patent litigation, establishing the priority date of "prior art" is paramount. A single day's difference can invalidate a multi-million dollar patent. In Valve Corp. v. Ironburg Inventions (2021), Valve attempted to invalidate an Ironburg patent regarding hand-held game controllers during an Inter Partes Review (IPR) by submitting an online review of an Xbox controller (the "Burns article")7. The printed exhibit submitted by Valve bore a publication date of October 20, 2010\. However, the Patent Trial and Appeal Board (PTAB) initially rejected the exhibit because the URL was not an archival URL and the printed access date differed from the publication date, raising severe authentication issues under Federal Rule of Evidence 9017. The PTAB treated the markings on the face of the exhibit as inadmissible hearsay23. The Federal Circuit Court subsequently reversed this decision. The court actively compared the text to authenticated versions and relied heavily on the Internet Archive's Wayback Machine as a "source whose accuracy cannot reasonably be questioned" to prove public accessibility23. This case demonstrates the critical distinction between a document's claimed publication date and its earliest verified public availability. The Wayback Machine timestamp (the crawl date) is heavily relied upon in courts to establish a terminus ante quem for prior art, setting a prima facie case that the art was publicly accessible at the date and time provided in the timestamp25. However, legal battles routinely erupt when attorneys or researchers conflate the Wayback crawl timestamp with the actual date the author pressed "publish"9. The archive date authenticates existence in the public domain; it does not authenticate creation.

2. Migrated Webpage Displaying an Inherited Date: The 1970 UNIX Epoch Bug (Born-Digital/Technical)

The UNIX epoch is defined in computing standards as January 1, 1970, 00:00:00 UTC6. Operating systems, databases, and programming languages (like PHP and Python) store time as the number of seconds (or milliseconds) elapsed since this exact moment6. When digital artifacts undergo database migrations, or when backend scripts encounter null, missing, or malformed date fields, systems frequently default the timestamp value to the integer 027. When this 0 value is parsed by a frontend display and adjusted for negative time zone offsets (e.g., UTC-05:00 for Eastern Standard Time), it outputs a date of December 31, 19696. When early internet forums, legacy CMS databases, or old social media posts are migrated to modern platforms, these null errors surface publicly on the frontend. A user viewing a resurrected blog post actually authored in 2004 might see a highly visible publication date of "December 31, 1969." For non-technical users and researchers lacking computer science literacy, this inherited machine date is taken literally. The artifact is subsequently perceived and cited as a hyper-prescient historical document, or an anomalous impossibility, rather than a victim of a 32-bit integer fallback29. The migration interval replaces the author's timeline with the machine's origin.

3. Republished Text Treated as Newly Authored: The Rothschild COVID-19 Patent (Archival/Scientific)

In 2020, amidst the outbreak of the SARS-CoV-2 pandemic, a patent application (US20200279585A1) filed by Richard A. Rothschild for a "System and Method for Testing for COVID-19" went viral across social media30. Conspiracists pointed to a date explicitly listed on the patent document itself: October 13, 2015\. They claimed this physical evidence proved COVID-19 was a premeditated bioweapon known years before its global outbreak30. This situation represents a profound failure to understand the bureaucratic mechanisms of "priority dates" and "continuation-in-part" (CIP) patent applications. Rothschild filed an initial provisional patent in 2015 for a generalized system processing biometric data30. In May 2020, he filed a continuation patent that updated his existing technology to include specific applications for detecting COVID-19 via pulse oximetry31. Under United States patent law, the 2020 application legally inherited the October 2015 priority date of its parent application31. The specific text regarding COVID-19 was newly authored and added in 2020, but the inherited 2015 date wrapped the entire composite document in false historical continuity30. This case highlights how institutional dating conventions can retrospectively alter the perceived origin of newly mutated claims, creating devastating misinformation if the dates are not subjected to a stratified event model.

4. Quotation or Image Resurfacing Without Original Context: Wayback 302 Redirect Anachronisms (Born-digital/Technical)

Web archives are highly susceptible to anachronistic rendering due to the way web pages are fundamentally built from composite elements. When the Wayback Machine archives an HTML page, it must also separately fetch and store the CSS files, images, and JavaScript1. These elements are distinct resources with their own capture timestamps. Furthermore, historical HTTP 302 (Found/Moved Temporarily) or 301 (Moved Permanently) redirects create massive chronological contamination within the archive. A researcher seeking a 2015 quotation on a domain might click a blue 2015 Wayback snapshot link, only to encounter a 302 redirect that silently pushes the crawler to a green 2018 snapshot, or worse, dynamically pulls active image assets from the live 2024 web into the 2015 HTML frame35. An image or quotation thus resurfaces wrapped in the HTML context of the past, but the media itself is modern. If a researcher does not forensically audit the timestamp of the specific element (using the Wayback Machine's specific timestamp feature)1, they will falsely conclude that the 2024 element existed in the 2015 context. The artifact mutates inside the archive itself.

5. Print and Copyright Mismatch: The "First Edition" Fallacy (Print/Historical)

While digital timestamps are highly volatile, print media suffers from equivalent structural obfuscation regarding the difference between copyright dates, printing dates, and publication dates4. In physical books, the publication date is the official date a work is made available to the public, whereas the copyright date is the year the intellectual property was registered. A critical misinterpretation occurs with revised editions or delayed distributions. A book authored and copyrighted in 1995, but subsequently revised with a new introduction in 2005, may still only display the 1995 copyright date on the copyright page if the publisher did not register a new copyright for the minor revisions4. If a researcher isolates a quotation from the 2005 introduction and attributes it to 1995 based on the copyright page, they commit a chronological error that places the author's insights a decade prior to their actual conception. Similarly, older works digitized into bibliographic databases like Google Books often mistakenly inherit the publication year of an anthology rather than the original printing date4. In physical artifacts, the copyright date establishes a legal boundary, not a historical event timeline.

6. Overwritten Original Authorship: CMS Last-Modified Header Erasing History (Born-Digital/SEO)

Content Management Systems (CMS) like WordPress and Drupal routinely betray chronological integrity for the sake of Search Engine Optimization (SEO). When a website owner updates a site's theme, runs a bulk database optimization, or simply updates a copyright footer widget to the current year, the CMS frequently updates the dateModified schema or the HTTP Last-Modified header for every single page on the domain simultaneously2. When these pages are subsequently crawled by search engines, algorithms often replace the original search-snippet publication date with the new Last-Modified crawl date2. A deeply reported investigative article authored in 2012 may suddenly appear in Google search results with a "published" or "updated" date of 2024\. If the article contains predictions or historical context, the altered date completely destroys the document's utility, framing old news as contemporary analysis or invalidating a perfectly valid historical timeline2. The original date often remains hidden deep in the HTML as a token, but the casual reader and the search algorithm prioritize the mutation38. The artifact is stripped of its historical context by automated SEO maintenance.

User-Facing Chronology

Designing a public interface for complex chronologies requires overcoming "Deterministic Construal Error" (DCE), a deeply ingrained cognitive bias where non-expert users interpret probabilistic, uncertain, or variable visual data as deterministic and absolute39. If a timeline shows a gap as a solid straight line connecting two known points, users assume unbroken continuity. If an uncertain range is provided (e.g., 1940-1945), users mentally average it to a midpoint (1942.5) and treat it as a hard fact. A rigorously designed user interface (UI) must communicate the nature of the temporal state seamlessly at both millennial (macro) and day-level (micro) zoom scales, actively blocking DCE through visual friction.

Visualizing Exact Dates and Ranges

Exact dates are plotted as sharp, high-contrast nodes (e.g., solid filled circles or diamonds) on the timeline axis. When dealing with an inferred or known date range (e.g., \[2012-01..2012-12\]), the interface must never drop a single pin in June 2012\. Instead, it must utilize a bracketed span or a continuous bounding box that visually occupies the entire twelve-month horizontal space, forcing the user to recognize the span rather than a point.

Visualizing Unknown Intervals and Disputed Dates

To actively counter DCE, uncertainty must be rendered using graphical techniques that trigger intuitive hesitation in the user's mind. Disputed dates should utilize techniques like "wandering dots" or "morphing icons"—animations that cycle through the possible dates or jitter randomly within the bounding box of the variance margin40. For static displays, print techniques such as fading, sketchiness, or blurred gradient edges effectively communicate that a boundary is soft or speculative, whereas solid, sharp lines communicate certainty39. If a date is highly speculative, it should be rendered with lower color saturation or transparency.

Visualizing Archive Captures and Multiple Competing Dates

Archive captures (like Wayback Machine snapshots) should be rendered on a parallel axis immediately below the primary "Claimed Event" axis. This structurally segregates machine-crawled verification dates from human-asserted publication dates. When multiple competing dates exist (e.g., a 2015 copyright footer on a file bearing a 2020 upload date), they must stack vertically at their respective points on the timeline, joined to the primary artifact node by dashed hierarchical lines. This explicitly shows the chronological divergence, preventing the dates from collapsing into a single false point.

Periods of Disappearance and Reappearance Events

The sequence from ORIGINAL → GAP → RETURN must be starkly visible at any zoom level. A verified existence is represented by a solid timeline track. When the artifact enters a "Gap" (e.g., Domain Expiration or Known Removal), the solid track breaks. The gap must be rendered as empty negative space, or a hatched, low-contrast "No Data" zone41. The line does not connect the disappearance point to the reappearance point. When the artifact returns (e.g., Republication), a new solid track begins, assigned a unique ID to denote it as a mutated descendant of the original, rather than a seamless continuation.

Sample Reappearance Chain

To demonstrate the methodology, the following tracks the lifecycle of a hypothetical controversial manifesto predicting a global geopolitical event. 1\. ORIGINAL

• Event Type: Authored & Published.
• Date: 2011-04-12 (Exact).
• Date State: Exact.
• Evidence: Original blog post published on author-site.com. The author claims this date in the text, and server headers from 2011 corroborate it.

2\. LAST VERIFIED

• Event Type: Archived.
• Date: 2013-09-05T14:22:00Z (Machine-derived).
• Date State: Exact (Machine-derived).
• Evidence: The final Wayback Machine capture of the blog post before the site goes dark. This establishes the ultimate terminus ante quem for the original text.

3\. GAP

• Event Type: Domain expired / Unresolved interval.
• Date: \[2013-09-06..2017-02-14\] (Inferred).
• Date State: Inferred Interval.
• Evidence: WHOIS records show the domain registration lapsed in late 2013\. No surviving captures exist during this window. The artifact experiences Interval Censoring; it is unobservable.

4\. RETURN

• Event Type: Republished / Mirrored.
• Date: 2017-02-15T09:15:00Z (Upload date).
• Date State: Exact (Machine-derived).
• Evidence: The text is pasted onto a Pastebin-style anonymous hosting site. The server generates a precise timestamp for the upload.

5\. MUTATION

• Event Type: Retrospectively claimed / Mutated.
• Date: 1999-01-01 (Retrospectively Claimed / Speculative).
• Date State: Disputed / Retrospectively Claimed.
• Evidence: The anonymous poster adds a preamble claiming the text was actually written in 1999, heavily editing the body to appear more predictive of recent events. The 1999 date is injected into the text, competing directly with the 2017 upload date and the 2011 verified archive.

6\. PRESENT STATUS

• Event Type: Current status checked.
• Date: 2026-08-24T19:46:22Z (Exact).
• Date State: Exact.
• Evidence: The Pastebin link remains active. The original 2011 blog is permanently dead. A researcher must use the 2013 Archive capture to prove the 1999 mutation is a retrospective forgery, while simultaneously proving the text did exist prior to the 2017 upload. The timeline visually separates the 1999 claim as a mutation, maintaining the integrity of the 2011 origin.

WHERE THE TIMELINE BREAKS

To maintain the epistemological integrity of forensic chronology, analysts and algorithms must abide by strict boundaries. Violating these rules fundamentally breaks the timeline, transforming a historical record into a generative fiction.

• DO NOT create a false exact date from an approximate range. If the temporal boundary is the 1990s (199X), setting the database integer to 1995 permanently poisons the data set. Future algorithms will ingest 1995 as a verified fact, compounding the error.
• DO NOT treat the first archive capture as the first publication. An Internet Archive crawl date of August 2014 simply means the crawler reached the URL in August 2014; the text may have been published in 2008\. The archive authenticates survival, not birth.
• DO NOT treat a file timestamp as self-authenticating. EXIF data, HTTP Last-Modified headers, and UNIX epoch values are trivially overwritten by CMS migrations, image compressors, and malicious actors. They are starting points for investigation, not definitive evidence.
• DO NOT infer uninterrupted publication from a sequence of captures. Just because a page was captured in 2010 and 2014 does not mean it was accessible in 2012\. A gap between captures is an interval of total darkness.
• DO NOT infer suppression from disappearance alone. Link rot, server migration, lapsed credit cards, and abandoned projects are the strongest ordinary explanations for data loss. Occam's razor applies; proving suppression requires positive evidence of an intentional takedown (e.g., a DMCA notice or a legal injunction).
• DO NOT infer current endorsement from present accessibility. A corporation or author may leave an outdated claim on a legacy server out of negligence or technical debt, not active contemporary endorsement.
• DO NOT produce predictive timelines or current-target monitoring. The methodology detailed herein is strictly retrospective and forensic. It reconstructs the past; it does not forecast the future.

Validation Checklist

Before a reappearance chain is committed to the public or integrated into an analytical database, it must pass the following validation protocol to ensure methodological soundness.

Source Audit Appendix

The rigorous execution of this chronology method relies on a critical intersection of international timekeeping standards, intellectual property legal precedents, and the cognitive science of data visualization. For the representation of uncertain time, the framework heavily leverages the Extended Date/Time Format (EDTF), which originated at the Library of Congress to address archival limitations and was formally incorporated into ISO 8601-2:201911. Standard ISO 8601 handles precise dates well but fails spectacularly when a photograph is dated "sometime in the 1940s"11. EDTF provides the semantic architecture necessary to digitally encode doubt—using qualifiers like ?, \~, and %, alongside unspecified digit markers (X) and open-ended intervals (..)12. By operating at Level 2 compliance of the EDTF standard, this framework prevents relational databases from forcing uncertain historical ranges into absolute POSIX timestamps, thereby preserving the epistemological limits of the data. In the realm of legal authentication and digital forensics, the Internet Archive's Wayback Machine remains the premier tool for establishing public accessibility dates, but its application requires extreme methodological nuance. As demonstrated in US Federal Court decisions such as Valve Corp. v. Ironburg Inventions (2021) and Weinhoffer v. Davie Shoring, Inc. (2022), the admissibility of web archive captures hinges on Federal Rule of Evidence 9017. Archive timestamps represent crawl events, not publication dates. Courts increasingly demand expert affidavits or judicial comparison to authenticate that a captured artifact represents true prior art7. Furthermore, the technical mechanics of the Wayback Machine—particularly its handling of HTTP 302 redirects and asynchronous element capturing, where images are captured days or years apart from the HTML base URL—pose massive risks of anachronistic timeline contamination1. Analysts must audit at the element level, not just the URL level. Finally, the cognitive psychology of data visualization dictates the user interface design of the proposed chronology. Research into "Deterministic Construal Error" (DCE) by Joslyn and Savelli demonstrates that non-expert users, and even domain experts, routinely interpret probabilistic data (like error bars or uncertain ranges) as deterministic, absolute metrics39. If they see a cone of uncertainty, they perceive it as the physical size of a storm, not a range of possible paths39. To counter this psychological reflex, visual grammars must employ sketchiness, fading, and animation (such as "wandering dots" or "morphing icons") to force the user to cognitively register the uncertainty of the timeline40. By embedding these visual frictions into the frontend, the chronology protects the integrity of the backend data.

A GAP MUST REMAIN A GAP UNTIL EVIDENCE CROSSES IT.

Works cited

1. Mark Graham | Internet Archive Blogs | Page 2, https://blog.archive.org/author/mark/page/2/

2. How to Check When a Website Was Last Updated \- SEOmator, https://seomator.com/blog/how-to-check-when-a-website-was-last-updated

3. 7.5.4 Disclosures which have no date or an unreliable date \- EPO, https://www.epo.org/en/legal/guidelines-epc/2026/g\_iv\_7\_5\_4.html

4. What Is The Publication Date Of A \- LaGarde Law Firm, https://lagardelaw.com/CA/issuu/V5mQ0VlbktmUtp0QhZEaXVGRnlnWG5EMSFDcVV1akNVVthXWWNjVL1kRWl1VrZValVEcYVVb0NnVxwGWjZkWUZlMoNnVWR2SiVUMIdFbaV1VYhGdZZlU3JmVKZ0YEZ0UipHbYZFSONnVsFUP

5. How Do I Find Out When a Webpage Was Created? \- Ask Leo\!, https://askleo.com/when-a-webpage-was-created/

6. Unix Timestamp Converter \- Epoch Time Converter | Post Affiliate Pro, https://www.postaffiliatepro.com/affiliate-tools/timestamp-converter/

7. Valve Corporation v. Ironburg Inventions Ltd., 8 F.4th 1364 (2021) | Sterne Kessler, https://www.sternekessler.com/news-insights/insights/valve-corporation-v-ironburg-inventions-ltd-8-f4th-1364-2021/

8. How to Check When a Website Was Last Updated: 7 Easy Ways \- Flamingo Agency, https://www.flamingoagency.com/blog/how-to-check-when-a-website-was-last-updated/

9. Proceed With Caution When Using Wayback Machine® Prior Art \- PTAB Litigation Blog, https://www.ptablitigationblog.com/proceed-with-caution-when-using-wayback-machine-prior-art/

10. How can I find when a domain was first registered? Standard whois doesn't seem to work., https://www.reddit.com/r/linuxadmin/comments/1b0sbp2/how\_can\_i\_find\_when\_a\_domain\_was\_first\_registered/

11. Extended Date/Time Format (EDTF) \- Metadata Standards Index, https://msi.dublincore.org/standards/edtf

12. How to write dates part 2: EDTF \- Pilsudski Institute in America, https://www.pilsudski.org/en/news/blog/849-how-to-write-dates-part-2-edtf

13. Extended Date/Time Format (EDTF) Specification \- The Library of Congress, https://www.loc.gov/standards/datetime/

14. Extended Date Time Format Help \- MormonPlaces, https://mormonplaces.byu.edu/edtf.html

15. Extended Date/Time Format (EDTF) 1.0 Submission, https://stuff.coffeecode.net/www.loc.gov/standards/datetime/pre-submission.html

16. why Unix Time Stamp for same time is different in different timezone \- Stack Overflow, https://stackoverflow.com/questions/17716367/why-unix-time-stamp-for-same-time-is-different-in-different-timezone

17. Wayback Machine \- Wikipedia, https://en.wikipedia.org/wiki/Wayback\_Machine

18. Internet Archive \- Archiveteam, https://wiki.archiveteam.org/index.php/Internet\_Archive

19. Wikipedia:List of web archives on Wikipedia, https://en.wikipedia.org/wiki/Wikipedia:List\_of\_web\_archives\_on\_Wikipedia

20. richardg867/WaybackProxy: HTTP proxy for tunneling requests through the Internet Archive Wayback Machine \- GitHub, https://github.com/richardg867/WaybackProxy

21. How to See When a Website Was Last Updated \- Maxobiz, https://maxobiz.com/how-to-see-when-a-website-was-last-updated/

22. What is UTC time zone in PHP? \- CMTech, https://www.cmtech.com.au/blog/web-design-development/What-is-UTC-time-zone/

23. Federal Circuit Provides Guidance On Prior Art Authentication And Publication Challenges, https://www.dority-manning.com/news/federal-circuit-provides-guidance-on-prior-art-authentication-and-publication-challenges/

24. Judge-Permitting, A Way(back) to Find Online Publication Dates, https://ucipclj.org/2025/05/21/judge-permitting-a-wayback-to-find-online-publication-dates/

25. What is the Wayback Machine and How is it Used in Patent Law \- BlueIron IP, https://blueironip.com/ufaqs/what-is-the-wayback-machine-and-how-is-it-used-in-patent-law/

26. PTAB: Merely Showing That a Reference Was Available on the Internet Does Not Establish 'Public Accessibility' \- Akin Gump, https://www.akingump.com/en/insights/blogs/ip-newsflash/ptab-merely-showing-that-a-reference-was-available-on-the-internet-does-not-establish-public-accessibility

27. Working with timestamp with time zone in your Amazon S3-based data lake, https://aws.amazon.com/blogs/big-data/working-with-timestamp-with-time-zone-in-your-amazon-s3-based-data-lake/

28. What's the difference between Epoch Timestamp and Unix time? \- Stack Overflow, https://stackoverflow.com/questions/72800683/whats-the-difference-between-epoch-timestamp-and-unix-time

29. Musk's claim of 150 year old's is due to COBOL's default date system. \- Reddit, https://www.reddit.com/r/theprimeagen/comments/1isdpr5/musks\_claim\_of\_150\_year\_olds\_is\_due\_to\_cobols/

30. Patent application doesn't show COVID test was developed in 2015 \- AP News, https://apnews.com/article/fact-check-covid-test-patent-application-2015-774568141358

31. Claims COVID tests invented before virus emerged are patently wrong \- AAP, https://www.aap.com.au/factcheck/claims-covid-tests-invented-before-virus-emerged-are-patently-wrong/

32. Rothschild did not secure a patent for a COVID-19 test in 2015 or 2017 \- FACTLY, https://factly.in/rothschild-did-not-secure-a-patent-for-a-covid-19-test-in-2015-or-2017/

33. COVID-19 misinformation \- Wikipedia, https://en.wikipedia.org/wiki/COVID-19\_misinformation

34. US20200279585A1 \- System and Method for Testing for COVID-19 \- Google Patents, https://patents.google.com/patent/US20200279585A1/en

35. Wayback: How to deal with redirects \- Internet Archive Forums, https://archive.org/post/1012493/wayback-how-to-deal-with-redirects

36. Re: Wayback: Constantly redirected to live site \- Internet Archive Forums, https://archive.org/post/2433781/wayback-constantly-redirected-to-live-site

37. “302 response at crawl time” is confusing \- Internet Archive Forums, https://archive.org/post/544453/302-response-at-crawl-time-is-confusing

38. Ask HN: Is the past disappearing on the web? \- Hacker News, https://news.ycombinator.com/item?id=30083783

39. Paper: Visualizing Uncertainty for Non-Expert End Users \- ferd.ca, https://ferd.ca/notes/paper-visualizing-uncertainty-for-non-expert-end-users.html

40. Animating Uncertainty \- Jim Vallandingham, https://vallandingham.me/animating\_uncertainty.html

41. Visualizing Uncertainty in Sets \- reposiTUm, https://repositum.tuwien.at/bitstream/20.500.12708/188227/1/other-197764.pdf

42. GitHub \- nharren/ExtendedDateTimeFormat: A .NET Implementation of the Extended Date/Time Format, https://github.com/nharren/ExtendedDateTimeFormat

43. Certified Web Evidence vs Wayback Machine: Three Evidentiary Scenarios \- TrueScreen, https://truescreen.io/insights/wayback-machine-forensic-capture-web-evidence/

44. Visualizing Uncertainty in Hurricane Forecasts with Animated Risk Trajectories in \- AMS Journals, https://journals.ametsoc.org/view/journals/wcas/15/2/WCAS-D-21-0173.1.xml