This guide shows the work behind sharing a screen-name sign-in across services. Dated July 3, 2002, it covers sign-in and registration, profile synchronization, sign-out, privacy and partner branding. The 67-page reference combines a technical overview with programming material. These selected pages preserve the original document layout.
You'd find one good personal site and immediately check its links page. Then somebody else's links page. Then another one. An hour later you were reading a stranger's update about their broken computer. No algorithm had decided you needed to see it. Some person put a tiny button on their website and you followed it into the woods.
Remote access once came with a telephone directory. This 19-page SERA 2.0 list, last updated in December 2000, organized dial-up access numbers by state and city. It is a period reference from the archive. The listed numbers are historical and are not presented as working access numbers today.
The personal site had three posts on it, but the layout was already on version 8. New banner. New colors. New navigation. A dramatic announcement explaining the redesign. The actual update was still coming soon. First we needed to spend another evening moving a table two pixels to the left.
AOL’s help desk had its own training material for getting employees connected. This March 2002 SERA 2.5 module runs to 44 pages, covering the client, troubleshooting and remote-access support. The cover and selected interface pages preserve the training document’s original appearance. It is a historical look at AOL’s internal support tools, rather than current connection instructions.
An e/n site could have a new layout, a long update about a terrible day, and a list of links to people who were also having terrible days. That was the whole thing. Everything and nothing. Usually posted after midnight. No niche. No content strategy. Just a small website announcing that school sucked and the new layout wasn't finished yet. I'd read that.
SERA was the other kind of AOL sign-on: a way for employees to reach the corporate intranet remotely. The enclosed user guide is dated November 8, 2001 and covers Windows, Linux, Solaris and Mac clients. The archive includes the 19-page guide alongside platform-specific installers. The screenshots here come from that guide; the old software has not been installed or tested.
Leaving IRC wasn't enough. You needed a custom quit message so everyone knew you were leaving in a very specific and interesting way. A joke, a quote, something that made closing a program sound important. Nobody announced going to the kitchen with that much effort. Disconnecting from a chat server got a whole closing statement.
Backordered, canceled or shipped? AOL’s OrderINQ reference gave support staff a list of codes for checking an order’s progress. This two-page document explains statuses such as backorder notices, cancellations and completed payments. The pictured page is the original reference table, not a customer’s order history.
Somebody gave you ops in an IRC channel with six people in it and suddenly you had responsibilities. The topic needed updating. The rules needed enforcing. Somebody was using too many capital letters. Five minutes earlier you were asking how to change your nickname. Now you were management.
Not every file in this archive is a prog or publishing tool. This 27-page document is an employee insurance booklet for AOL, with an August 2000 effective date and a January 2002 revision. It belongs in a company-history collection rather than the AOL Progs section. This is a historical document, not information about anyone’s current coverage.
