Apparently Bluesky has one centralized service, the "relay"

Post by half-kh-hacker » Mon, Apr 28, 2025, 11:08 AM UTC

yellowapple wrote: post #80

half-kh-hacker wrote: post #74

Earlier quoted context omitted.

- the relay storage volume scales only with the backfill window for consumers that drop briefly - the bluesky pbc operated relays let you reconnect up to 24h later and not miss any events but that requires around 200gb of scratch disk space -- live tailing an rpi relay without dropping a connection can give you events from the full network span (ie the complete set of the firehose) without requiring any backfill wind…

> the relay storage volume scales only with the backfill window for consumers that drop briefly […] bluesky's feed gen post-dropping is about internal operation of their appview and not anything to do with network sync semantics Gotcha; thanks for the clarifications/corrections. Good to know that the firehose bandwidth is a lot less than I thought (though 20Mbps can certainly add up to some hefty pricetags depending…

Post by gkbrk » Sun, May 04, 2025, 7:15 PM UTC

renewedrebecca wrote: post #77

rafram wrote: post #42

Earlier quoted context omitted.

Yup. Mastodon has this issue. Can’t pick a big generic instance because it could get defederated for spam/being too normie; can’t pick a small instance because it could get defederated over some ridiculous drama [1][2]. Normal people (and even some not-normal people) don’t want to deal with that. “Instances” are a bad model. [1]: https://tootworld.social/@lilythelonelygirl/1143999833553083... [2]: https://tau-ceti.sp…

> Can’t pick a big generic instance because Nobody is going to defederate from mastodon.social, but otherwise, this is all true.