Firehose: Difference between revisions
Add Firehose page |
m Add alternative name for firehose |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
A '''firehose''' is a real-time, one-directional event streaming API. It distributes record changes to authenticated clients, which clients use to synchronize records. In contrast to a traditional request-response web API, this model of disseminating changes enables real-time updates while reducing the request load on firehose providers. | A '''firehose,''' also called '''repository event stream''', is a real-time, one-directional event streaming API. It distributes record changes to authenticated clients, which clients use to synchronize records. In contrast to a traditional request-response web API, this model of disseminating changes enables real-time updates while reducing the request load on firehose providers. | ||
Bluesky Social provides a firehose, commonly referred to as '''the firehose''', through their [[relay]] at <code>bsky.network</code>. It aggregates and streams all record changes from the Bluesky network and is used by different services, such as [[Feed generator|feed generators]] or [[Labeller|labellers]]. | [[Bluesky Social]] provides a firehose, commonly referred to as '''the firehose''', through their [[relay]] at <code>bsky.network</code>. It aggregates and streams all record changes from the Bluesky network and is used by different services, such as [[Feed generator|feed generators]] or [[Labeller|labellers]]. | ||
Starting in October of 2024, Bluesky has started offering an alternative to the firehose called [[Jetstream]].<ref>[https://docs.bsky.app/blog/jetstream "Introducing Jetstream"]. Bluesky. Retrieved March 12, 2025.</ref> It promises to use less bandwidth by allowing clients to preselect a subset of records to receive updates for. By using [[wikipedia:JSON|JSON]] instead of the binary encoding format [[wikipedia:CBOR|CBOR]], it is also more approchable for developers. | Starting in October of 2024, Bluesky has started offering an alternative to the firehose called [[Jetstream]].<ref>[https://docs.bsky.app/blog/jetstream "Introducing Jetstream"]. Bluesky. Retrieved March 12, 2025.</ref> It promises to use less bandwidth by allowing clients to preselect a subset of records to receive updates for. By using [[wikipedia:JSON|JSON]] instead of the binary encoding format [[wikipedia:CBOR|CBOR]], it is also more approchable for developers. | ||
| Line 7: | Line 7: | ||
== References == | == References == | ||
<references /> | <references /> | ||
== External links == | |||
* [https://atproto.com/specs/sync#firehose AT Protocol specification: Firehose] | |||
Latest revision as of 22:26, 12 March 2025
A firehose, also called repository event stream, is a real-time, one-directional event streaming API. It distributes record changes to authenticated clients, which clients use to synchronize records. In contrast to a traditional request-response web API, this model of disseminating changes enables real-time updates while reducing the request load on firehose providers.
Bluesky Social provides a firehose, commonly referred to as the firehose, through their relay at bsky.network. It aggregates and streams all record changes from the Bluesky network and is used by different services, such as feed generators or labellers.
Starting in October of 2024, Bluesky has started offering an alternative to the firehose called Jetstream.[1] It promises to use less bandwidth by allowing clients to preselect a subset of records to receive updates for. By using JSON instead of the binary encoding format CBOR, it is also more approchable for developers.
References[edit | edit source]
- ↑ "Introducing Jetstream". Bluesky. Retrieved March 12, 2025.