Jetstream turns the firehose into filtered JSON without signatures, and since version two can replay the past, so you trust its operator; Tap keeps verification and fetches a repository's past from the host before live events; choose by how much you must verify.

Most developers never touch the raw firehose.

The raw firehose is heavy: binary blocks, signatures, thousands of events a second.

Jetstream turns it into plain JSON, lets you filter by collection, and since version two can replay the past. It drops the signatures, so you trust the Jetstream you connect to.

Tap goes the other way: it keeps the verification. Track a repository, and Tap fetches its past from the host, checks every commit, then hands you the live events.

A bot or a prototype can live on Jetstream. Archives, moderation, and anything that must prove authorship need the signed stream.

Three taps on one pipe. Same events, three ways to receive them. Pick by how much you need to verify.

Check yourself. What does Jetstream drop that the firehose carries?