2026-06-20 06:45 UTC
@innocentzero@social.tchncs.de By the way, Jetstreams were not, and still are not, officially standardized atproto objects. In fact, they don't speak atproto to their clients. They were originally a side project by one of the Bluesky team members, and have become a load-bearing side project for many of the apps that are not Bluesky.
In much the same way that some people are kind of irked at Mastodon for adopting some of its own APIs or doing other ActivityPub things in non-standard ways, jetstream is sort of a hack that solves real problems but does so off-protocol.
Replies (1)
-
@angrybards@indieweb.social 2026-06-20 10:48
@ricci@discuss.systems @innocentzero@social.tchncs.de I'm relatively new to the discussion but from what I've seen recently it seems Bluesky is promoting atproto as a layer for app development without discussing where it would be very in-efficient. Do you have thoughts on the chance Bluesky falling over and atproto fragmenting into maybe many large firehoses each with more filters to keep costs down for their app segment?