Contemporary evidence
Source, manifests, readmes, archived web pages, screenshots and distribution metadata made during the period. It can prove presence or wording, not automatically successful runtime.
Provenance / safety / limits
How this history knows what it knows
Twenty-year-old source code and a vivid memory answer different questions. This site keeps them together without pretending they are the same kind of proof.
Four labels do most of the work
The narrative remains readable; these definitions are here when a claim needs checking.
Present-day recollection
Jay’s account in 2026. It is the right source for lived experience, motive and remembered scenes, but it is not silently converted into a period document.
Archive-supported inference
A conclusion drawn from several surviving traces—for example, likely relationships between a project, screenshot and website page. The supporting boundary is stated.
Uncertain
A genuine gap: missing source, an ambiguous version, an unverified release state or a memory the archive cannot date. Uncertainty qualifies the sentence rather than blocking publication.
A read-only historical pass
The preservation work was designed to learn from the material without reviving it.
The canonical source was used for filesystem identity and metadata only. Historical content inspection took place against a validated same-storage working mirror. The catalogue records 689,302 files and 46,976 folders and repairs broad folder-level guesses into manifest-granular project boundaries.
No recovered application was run or built. No recovered DLL or OCX was registered. No installer or archive was unpacked. No Yahoo or other historical endpoint was contacted. Safe text, source, manifests, ordinary filesystem metadata and selected images were inspected statically.
Potentially harmful software is still historical evidence. Darks Revenge’s core purpose, the deceptive remote-control material around it and the unlicensed skinning component are recorded candidly. Reusable attack details, payloads, cracking instructions and recovered binaries are not published.
Claims that require restraint
Common archival shortcuts would turn this story into something cleaner—and less true.
A file is not a release
An executable, setup package or finished-looking source tree does not establish public distribution. Jay remembers three releases during the Elite Prodigy era. XP Search is separately confirmed as a later c0ld.net release by a September 2005 file-database entry and earlier tester discussion.
A screenshot is not a runtime test
A screenshot can establish a visible interface, control or presentation state. Source establishes implementation; contemporary distribution records establish release. Supplied project screenshots were inspected statically and displayed at their natural aspect ratios.
A label is not a feature
A menu item can survive without event wiring or complete implementation. Confirmed source features require implementation inside the preserved project boundary; runtime claims remain narrower still.
A counter is not an audience model
The archived page displays 11855 Today. It does not reveal how a visitor was counted. Jay’s memory that this meant unique visitors across the whole site is retained as recollection.
A folder is not authorship
Vendor packages, SDKs, libraries and backups lived beside Jay’s own work. Manifests, credits, source context and site records establish boundaries and relationships.
A timestamp is not a creation date
NAS precision, archive extraction, restoration and copying can flatten or distort filesystem dates. They remain evidence of uncertain quality.
A handle is not an identity
Public historical handles can be credited in context. They do not establish a person’s real name, present identity or consent for private material.
Recovering the site’s public face
Local copies supplied structure; dated Wayback captures supplied chronology.
The preservation pass reviewed saved capture material, queried the live Wayback capture index and opened representative replays in a browser. When a captured route stopped at a disclaimer, the corresponding main.php page was used to reach the archived shell. Software download links were not followed.
The record supports a late-2001 black/gray/red era, a pale-lavender 2002 portal, a late-2002/2003 silver era and domain parking in 2004. It does not supply a surviving visual for the remembered black-and-pink Tripod builder page, or securely place the remembered purple and brown designs. Those memories remain text, not false reconstructions.
Public history, bounded access
“Do not omit anything” means keeping the difficult history—not publishing sensitive or dangerous material.
Jay approved public-safe historical handles and screenshots. The site still withholds passwords, cookies, licence keys, private email or street addresses, private network information, credentials and unrelated correspondence. One 2003 web replay contains private-looking contact material; the site uses a safe summary instead of reproducing it.
Recovered executable and archive files remain unavailable. The goal is to preserve the story and the evidence relationships, not to make obsolete or harmful applications operational again.
Honesty is not certainty everywhere. It is knowing which kind of evidence is speaking.Elite Prodigy preservation method