lightweight com.atproto.sync.listReposByCollection

adjacent key completeness #1

open opened by microcosm.blue

so far there has been at least one spurious birth: the detection logic thought it was new, but we already had that collection indexed

these are harmless (long as we don't try to single-delete on death)

need to sit down and understand the edge case better though, in particular to understand if it's possible that any actually important events would get accidentally filtered out.

sign up or login to add to the discussion
Labels

None yet.

assignee

None yet.

Participants 1
AT URI
at://did:plc:lulmyldiq4sb2ikags5sfb25/sh.tangled.repo.issue/3mglntomi4z22