Isotope60 Gopher Server ======================= This Gopher server runs on a Particle Tachyon (ARM64) running Ubuntu 24.04. It was first deployed on February 28, 2026. Hardware Comparison ------------------- Original University of Minnesota Gopher Server (1991) versus a Particle Tachyon (2026). +----------------------+---------------------------+---------------------------+ | | UMN Gopher Server (1991) | Isotope60 (2026) | +----------------------+---------------------------+---------------------------+ | System Type | Sun SPARCstation IPC | Particle Tachyon (ARM64) | | CPU Architecture | 32-bit SPARC | 64-bit ARM (aarch64) | | CPU Clock | 25 MHz | up to 2.707 GHz | | CPU Cores | 1 | 8 (4×A55 + 4×A78) | | RAM | 16 MB (typical) | 8 GiB (≈ 7404 MB) | | Storage | ~500 MB SCSI disk | 64 GiB microSD | | Network | 10 Mbps Ethernet | Gigabit-class Ethernet | | Operating System | SunOS (BSD UNIX) | Ubuntu 24.04 Linux | +----------------------+---------------------------+---------------------------+ Order-of-Magnitude Differences (Approximate): Clock Speed: 2.7 GHz vs 25 MHz → ~108× higher peak frequency Memory: 7.1 GiB vs 16 MB → ~450× more RAM Storage: 59 GiB vs 500 MB → ~118× more storage CPU Cores: 8 vs 1 → 8× parallel compute units Despite this difference in hardware capability, the protocol served remains structurally identical in principle: • Client sends selector • Server returns menu or file • No client-side execution • Filesystem defines hierarchy The computational capacity of a small embedded module in 2026 exceeds that of early-1990s university workstations by several orders of magnitude, yet the simplicity of Gopher remains sufficient. About Gopher ------------ Gopher is a text-based internet protocol created at the University of Minnesota in 1991, about 0.5 miles from where this server currently runs. It predates the modern web and was designed to organize and distribute documents using a clear hierarchical model. Instead of HTML rendering engines and client-side scripting, Gopher provides: • Plain text menus • Directory traversal • Direct file access • Minimal protocol surface area Each request retrieves a selector (a file or directory) and returns either a menu or raw content. This simplicity yields stability, longevity, and minimal attack surface. Server Model ------------ This server is powered by pygopherd and serves files directly from the filesystem mounted on a micro SD card. Directories become menus. Files become downloadable objects. The structure visible to clients mirrors the on-disk layout. Security Notice --------------- WARNING: Nothing in Gopher is private. Assume all published content is publicly accessible. Welcome to Gopherspace.