Difference between revisions of "AOL"

From Archiveteam
Jump to navigation Jump to search
(Many new items)
(→‎Protocol: quick note on inspecting packet captures)
Line 18: Line 18:
** Plaintext: http://www.cs.columbia.edu/~ricardo/misc/docs/theaolprotocol.txt
** Plaintext: http://www.cs.columbia.edu/~ricardo/misc/docs/theaolprotocol.txt
* http://sicexcels.tripod.com/rm-vpd.html
* http://sicexcels.tripod.com/rm-vpd.html
== Reverse Engineering ==
The trunk version of Wireshark includes a dissassembler for the AOL protocol that breaks out the basic header information, such as the packet type and the token. It doesn't go into any detail about the contents of the packet, but this is a good start. This isn't available for download yet, so you'll have to build it yourself, from the svn trunk; once built wireshark reports itself as 1.9.0.
http://db48x.net/temp/Screenshot%20-%2001292013%20-%2008:28:31%20PM.png
= URLs =
= URLs =



Revision as of 05:45, 30 January 2013

AOL
AOL Screen Shot 2013-01-27 at 8.42.32 PM.png
Status Online! on January 28, 2013
Archiving status Researching
Archiving type Unknown
IRC channel #aohell (on hackint)

This is about archiving the original AOL, not AOL's current website. The AOL system is currently in major disrepair. It is as if they left the machines sitting in the datacenter, and as they die, they do not fix any issues. There is much broken infrastructure.

Protocol

Reverse Engineering

The trunk version of Wireshark includes a dissassembler for the AOL protocol that breaks out the basic header information, such as the packet type and the token. It doesn't go into any detail about the contents of the packet, but this is a good start. This isn't available for download yet, so you'll have to build it yourself, from the svn trunk; once built wireshark reports itself as 1.9.0.

http://db48x.net/temp/Screenshot%20-%2001292013%20-%2008:28:31%20PM.png

URLs

aol://nnnn

  • 1722: Keywords
  • 2719: Chatrooms
  • 3548: User profiles
  • 4344: Interactive page
  • 4400: File libraries
  • 4401: Files
  • 586x: ???

Examples

  • aol://4344:1264.a2main.10029531.514525857
  • aol://4400:8287
  • aol://4344:1264.a2abt.10037404
  • aol://4344:117.mtv.591130
  • aol://4344:226.llll.2755674.520114429 (Access code: 3675)

Sources

Lots of sources: Documents covering how to make AOL forms and various such things:

Samples of custom forms:

Some FDO lessons:

About the class names:

Token list:

Here is an early version of aol-files.com:

Atoms list:

Structure

           <balrog_> yes, but aol://4344:nnnn doesn't work without the extra
   [19:52] <balrog_> aol://4344:1264.a2main.10029531 also works
           <balrog_> simply aol://4344:1264.a2main does not work.
   [20:17] <DrainLbry> so to summarize we've got aol://4400:ID (from
                       spreadsheet), for file libraries, and
                       aol://4344:uniqueidentifier for interactive content
   [20:18] <balrog_> aol://4344:uniqueidentifier:ID
           <balrog_> as per
                     http://web.archive.org/web/20060207004722/http://daol.aol.com/aolatoz
                     keywords used to be aol://1722:keyword
           <balrog_> but that's no longer working

Software

Plans

wget-aol

Modify wget to support the AOL protocol. Ambitious, but it would let us create warc files, which will save us the trouble of figuring out how to organize everything on disk. Warc files make it much easier to create a server than can pretend to be the AOL server, or that can translate into http to allow anyone with a web browser to see what AOL was like.

script the client

Drive the real AOL client, perhaps with debugging tools installed, in order to capture both the FDO sources and screenshots of the rendering. Probably more fragile, but we wouldn't have to understand the actual protocol.