Posts on third-party ATProto PDS accounts appear on origin servers before Bluesky's app index shows them
A test on October 14, 2026 found that a post written to a third-party Personal Data Server was readable from the origin immediately, yet absent from the main Bluesky app's feeds and search for about forty minutes. The origin served the content byte-for-byte while the public AppView returned an empty feed or a profile-not-found error at the same time. An independent recheck confirmed the split, with the author-feed index still lagging for all new records. By the 23:35 UTC re-probe, identity resolution had caught up but content indexing had not. The authors frame this as a distinction between where data lives and what the network displays, which matters for operators running their own accounts.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in