The First Find: Solution
autumn-2026-01
Weekly Puzzle #01 kicked off the Autumn 2026 season of DroppedBit under the title The First Find, presented by the archival persona Finder-Spyder. With Weekly Puzzle #02 now active, ranked submissions for Issue 01 have concluded.
Spoiler warning: This post contains the complete solution and historical background for Weekly Puzzle #01. If you have not reviewed the transmission yet, you can inspect the archived puzzle record.
1. The Challenge Artifact
The transmission interface presented an unresolved recovery ticket (CASE // FS-001) with the following premise:
Finder-Spyder indexed a page that should not exist. The result has disappeared from the public index. Its cached data has not.
Guests were presented with a raw cache record (CACHE RECORD // FS-001) containing an unformatted block of printable characters, alongside actions to copy or download finder-spyder-cache.txt.
The interface provided no file headers or metadata labels, leaving solvers to identify the encoding format and reconstruct the missing document.
2. Identifying and Decoding the Base64 Cache
Inspecting the payload revealed the character set: uppercase and lowercase ASCII letters, decimal digits, +, /, and trailing = padding. This structure is standard Base64 encoding as defined in RFC 4648.
Because the cache export contained line wraps and whitespace, decoding required stripping whitespace before converting to bytes.
Decoding with Python
import base64
with open("finder-spyder-cache.txt", encoding="utf-8") as f:
raw_payload = f.read()
# Strip whitespace and line breaks
compact_payload = "".join(raw_payload.split())
# Decode Base64 to UTF-8 HTML
webpage = base64.b64decode(compact_payload, validate=True).decode("utf-8")
with open("recovered.html", "w", encoding="utf-8") as f:
f.write(webpage)
print(f"Recovered {len(webpage)} characters of HTML source.")
Decoding in the Terminal
cat finder-spyder-cache.txt | tr -d '\r\n ' | base64 -d > recovered.html
3. The Recovered Engineering Note
Opening recovered.html displayed an internal engineering note formatted in nostalgic HTML 3.2:
DOCUMENT ID: FS-ARC-01
STATUS: INTERNAL ENGINEERING
INDEXING: PROHIBITED
SUBJECT: ORIGIN OF RETRIEVAL PIPELINE
The document revealed an internal controversy: Finder-Spyder's marketing team had announced their product as "a search engine with no ancestor." Engineering objected, documenting that the underlying pipeline was directly inherited from Archie, the world's first Internet search engine.
Although the document's public index entry was deleted, the cached record survived because the web-rendering service lacked authority over the retrieval archive.
4. Reconstructing the Inherited Search Path
The document included a shuffled service record containing four operations:
| Record | Operation Description |
|---|---|
FS-17 |
Match a user's query against stored filenames and return the server locations. |
FS-03 |
Render a retrieved web page, including its images and visual layout. |
FS-28 |
Collect directory listings from anonymous FTP servers. |
FS-11 |
Organize the collected filenames and paths into a searchable index. |
To solve the puzzle, solvers needed to reconstruct the three-stage pipeline inherited from Archie in chronological execution order:
FS-28(Collection): Gather directory listings from anonymous FTP servers.FS-11(Indexing): Parse and organize the collected filenames and paths into a searchable index.FS-17(Querying): Match user search terms against the index and return server locations.
The Distractor
Operation FS-03 ("Render a retrieved web page, including its images and visual layout") was a deliberate distractor. Archie searched filenames and directory paths across FTP servers before the World Wide Web existed; it never fetched or rendered HTML web pages.
Additionally, the numeric values (03, 11, 17, 28) were simply internal database record keys rather than an execution sequence.
Joining the three valid operations in execution order yields the solution string:
FS-28 FS-11 FS-17
Submitting this path in the transmission terminal completed the issue and awarded solvers their seasonal solve position.
5. Computing History: Alan Emtage and Archie
The historical root of this puzzle lies at McGill University in Montreal. In 1989, systems administrator and postgraduate student Alan Emtage, along with Peter Deutsch and Bill Heelan, faced a challenge: useful software and research papers were scattered across hundreds of independent anonymous FTP servers worldwide. Locating a specific file required connecting to servers individually and manually browsing their directories.
Emtage wrote a script to automate downloading file lists from anonymous FTP sites during off-peak hours and built a central, searchable database of filenames. The tool was named Archie (derived from "archive" with the "v" dropped).
Archie is widely recognized as the very first Internet search engine. It established the core separation between data collection, index construction, and query evaluation that powers search architectures to this day.
For further reading on Alan Emtage and the creation of Archie: - The first internet search engine — McGill University - Search engine pioneer inducted into Internet Hall of Fame — McGill News - Internet Hall of Fame: Alan Emtage Biography
Next Transmission
Autumn 2026 has transitioned to Week 02: The Winning Move, featuring an endgame tactical study from chess history.
Ready for the next challenge? Open the active weekly puzzle →