we are looking in to problems with search indexing of some accounts. this impacts type-ahead search of handles, for example, and has been ongoing for a couple days. not any intentional suppression, just an operational bug.
#atproto devs and protocol folks! looking for feedback on options for Lexicon Resolution. we have a broad sketch, but still some open questions and truely not sure which way we are leaning [RFC: Lexicon Resolution · blue...]( )
bet a bunch of folks are curious, so a bit more transparency around firehose/relay woes: one top area of concern has been managing outbound bandwidth and noisy consumers. the rainbow system has basically solved this.
some more details on public firehose stuff: you can/should reconnect now! note that the sequence is different (lower, like 274908607-ish at the moment) if you scroll back to the start of this backfill window, consumers *should* see all events (aka, not miss anything)
it's been a rough couple hours for the firehose! it has been flapping around in volume and offset. the bsky app has been smoother because we are using an alternative internal relay (starting a couple days ago). 🧵
oh jeez, this was worse than thought. recommend folks just disconnect from firehose for a bit and we'll give the all clear soon RE: View quoted note →
folks consuming from firehose: we are debugging a few distinct issues caused by misconfigured rate-limits. 🧵 definitely some fraction of accounts created in the past 8 hours were not having events go though, or as tooBig (meaning no records on the firehose). roughly 20k accounts.
haven't tried this before, but offering a $150 bug bounty if anybody can fix this docusaurus build/deploy issue. donation to charity of choice, or via github sponsor. might need to set up a temp [render.com]( ) account to debug the last issue [Docusaurus Build/Deploy Broken...]( )
devs! want to build something on #atproto but not sure where to start? check out this "Call for Projects" with a bunch of ideas, ranging from protocol frameworks, to entire apps, to bots [Call for Developer Projects · ...]( )
#atproto devs and firehose consumers! we have changes coming soon with our relay service, which will result in a sequence number reset/update. all that and more inside... [Relay Operational Updates · bl...]( )