Finger: the 1971 protocol that quietly invented the social network

Long before accounts and algorithms, Finger let anyone read your status straight from a plain-text file you controlled. Born in 1971 at the Stanford AI Lab, it started as a fix for an unreadable WHO command — engineer Les Earnest wrote a tool that reported who was logged in, where, and how long they’d been idle, so colleagues could decide whether it was worth walking down the hall. The protocol was formalized in RFC 742 (1977) and superseded by the definitive RFC 1288 in 1991. It’s about as simple as networked software gets: the client opens a TCP connection to port 79, sends a username (or a blank line) terminated by CRLF, and the server returns plain text and hangs up — no encryption, no headers, no sessions. You can speak it by hand with netcat.

What made Finger a proto-social network was the .plan and .project files in a user’s home directory, which the server would dump verbatim to anyone who queried them. People turned that into the first microblog, keeping dated diary entries with the newest on top. The canonical example is John Carmack’s .plan, where the id Software programmer logged terse development notes from 1996 to 2010 — including the 1997 announcement that Doom’s source would be released, made through his .plan rather than any press channel. Aggregators like Blue’s News collected developers’ plans into a feed, effectively a Twitter of its era. Even an early IoT device spoke Finger: Carnegie Mellon’s networked Coke machine, wired with microswitches around 1982, exposed bottle stock and temperature over the protocol.

The appeal, and the reason it still runs on macOS, Linux, Windows, and Emacs, is radical simplicity and user control: your entire profile is one editable text file, with no database, no history, and no versioning — trim old entries and they’re gone. Hosts like happynetbox.com let people publish without running their own server, and a named pipe (mkfifo ~/.plan) can serve dynamically generated content. Fifty-five years on, Finger persists as both a piece of internet archaeology and a working reminder of how much presence and publishing you can build on a single port and a flat file.