This is the obvious followup to the post.
Introducing firehose.stream - public Jetstream instances for the Atmosphere
Launching with six public Jetstreams globally:
🇺🇸 NYC - nyc.firehose.stream - 72h replay
🇺🇸 SFO- sfo.firehose.stream - 72h replay
🇬🇧 London- london.firehose.stream - 72h replay
🇩🇪 Frankfurt- frankfurt.firehose.stream - 24h replay
🇮🇳 Chennai - chennai.firehose.stream - 24h replay
🇨🇦 Jet - jet.firehose.stream - 24h replay
The first five run a slightly customized Jetstream with additional filters, each connected to their nearest firehose.network relay. Jet(Canada) runs stock Bluesky Jetstream code against bsky.network relay.
Jetstream:
Jetstreams aren't strictly part of the protocol but are lightweight than relays and can be used for apps that don't need full cryptographic verification.
More info:
https://jazco.dev/2024/09/24/jetstream/
https://docs.bsky.app/blog/jetstream
Extra filters:
Firehose.Stream instances support few extra filters beyond the default:
Exclude specific collections or DIDs
Filter by event kind: commit, identity, account
Filter commits by operation: create, update, delete
Preview:
Each instance has a live preview with configurable filters in the UI.
They're really addicting to watch.
These are new additions to the Atmosphere complementing what Bluesky and Microcosm already offer. Most of these instances have been running stable for last several months. They run on VPSes (unlike relays), and I’ll scale them up / tweak based on demand. Also huge thanks to for guiding and answering all my questions.
Follow for updates/announcements.