HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
chriskearney
wiretap
Java2025–2025
chriskearney / wiretap

wiretap

AOL Protocol Wiretap Tool - Packet capture and analysis for AOL protocol reverse engineering

2Distinct people
2Mentions
0Explicit recommenders
12GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

AOL Protocol Wiretap Tool - Packet capture and analysis for AOL protocol reverse engineering

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by 3-hour interval2 dated mentions

Observed mentions: 2025-12-28 12:56:13 UTC to 2025-12-31 06:23:06 UTC.

012025-12-28 12:00:00 UTC to 2025-12-28 15:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsDec 28, 12:002025-12-28 15:00:00 UTC to 2025-12-28 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-28 18:00:00 UTC to 2025-12-28 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-28 21:00:00 UTC to 2025-12-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-29 00:00:00 UTC to 2025-12-29 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-29 03:00:00 UTC to 2025-12-29 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-29 06:00:00 UTC to 2025-12-29 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-29 09:00:00 UTC to 2025-12-29 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-29 12:00:00 UTC to 2025-12-29 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-29 15:00:00 UTC to 2025-12-29 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-29 18:00:00 UTC to 2025-12-29 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-29 21:00:00 UTC to 2025-12-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsDec 29, 21:002025-12-30 00:00:00 UTC to 2025-12-30 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-30 03:00:00 UTC to 2025-12-30 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-30 06:00:00 UTC to 2025-12-30 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-30 09:00:00 UTC to 2025-12-30 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-30 12:00:00 UTC to 2025-12-30 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-30 15:00:00 UTC to 2025-12-30 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-30 18:00:00 UTC to 2025-12-30 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-30 21:00:00 UTC to 2025-12-31 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-31 00:00:00 UTC to 2025-12-31 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-31 03:00:00 UTC to 2025-12-31 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-31 06:00:00 UTC to 2025-12-31 09:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsDec 31, 06:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Dec 28, 12:002025-12-28 12:00:00 UTC2025-12-28 15:00:00 UTC101
Dec 28, 15:002025-12-28 15:00:00 UTC2025-12-28 18:00:00 UTC000
Dec 28, 18:002025-12-28 18:00:00 UTC2025-12-28 21:00:00 UTC000
Dec 28, 21:002025-12-28 21:00:00 UTC2025-12-29 00:00:00 UTC000
Dec 29, 00:002025-12-29 00:00:00 UTC2025-12-29 03:00:00 UTC000
Dec 29, 03:002025-12-29 03:00:00 UTC2025-12-29 06:00:00 UTC000
Dec 29, 06:002025-12-29 06:00:00 UTC2025-12-29 09:00:00 UTC000
Dec 29, 09:002025-12-29 09:00:00 UTC2025-12-29 12:00:00 UTC000
Dec 29, 12:002025-12-29 12:00:00 UTC2025-12-29 15:00:00 UTC000
Dec 29, 15:002025-12-29 15:00:00 UTC2025-12-29 18:00:00 UTC000
Dec 29, 18:002025-12-29 18:00:00 UTC2025-12-29 21:00:00 UTC000
Dec 29, 21:002025-12-29 21:00:00 UTC2025-12-30 00:00:00 UTC000
Dec 30, 00:002025-12-30 00:00:00 UTC2025-12-30 03:00:00 UTC000
Dec 30, 03:002025-12-30 03:00:00 UTC2025-12-30 06:00:00 UTC000
Dec 30, 06:002025-12-30 06:00:00 UTC2025-12-30 09:00:00 UTC000
Dec 30, 09:002025-12-30 09:00:00 UTC2025-12-30 12:00:00 UTC000
Dec 30, 12:002025-12-30 12:00:00 UTC2025-12-30 15:00:00 UTC000
Dec 30, 15:002025-12-30 15:00:00 UTC2025-12-30 18:00:00 UTC000
Dec 30, 18:002025-12-30 18:00:00 UTC2025-12-30 21:00:00 UTC000
Dec 30, 21:002025-12-30 21:00:00 UTC2025-12-31 00:00:00 UTC000
Dec 31, 00:002025-12-31 00:00:00 UTC2025-12-31 03:00:00 UTC000
Dec 31, 03:002025-12-31 03:00:00 UTC2025-12-31 06:00:00 UTC000
Dec 31, 06:002025-12-31 06:00:00 UTC2025-12-31 09:00:00 UTC101

What Hacker News says

2 sources
Hey all — thanks for checking out Dialtone. I plan to open-source the server code eventually; for now I’m just having fun with it and continuing to iterate. I’m a firm believer that a reverse-engineered system like this — especially something so historically “90s internet” — ultimately needs to exist in an open-source way. To show I’m serious about the reverse-engineering work (and not just the nostalgia), here are two critical tools I’ve built for understanding AOL and its protocols: • WireTap: https://github.com/iconidentify/wiretap A packet-level tracing tool for capturing and analyzing the conversations between an AOL client and server. • AtomForge: https://github.com/iconidentify/atomforge A full-blown FDO → ATOMSTREAM compiler. FDO is the bespoke scripting language AOL used to define “forms.” Before forms are transmitted over th
Read the rest
e wire (wrapped in a “P3” frame), they’re serialized down into bytes — AtomForge handles that whole pipeline.
In Dialtone – AOL 3.0 Server

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.