dev.atfs.repo.getFile

Fetch a file previously uploaded to this atfs instance. Compatible with com.atproto.sync.getBlob — also mounted, unmodified, under that name, for callers that have no reason to know atfs has its own name for it — with one deliberate difference: did is optional here. Requiring a did the way a PDS does is a repo-scoping artifact (a PDS's blobs live inside a specific account's repo); atfs content is content-addressed by cid alone, and the /ipfs/<cid> gateway path already serves it that way, so a did-less getFile exposes nothing a full IPFS client couldn't already reach. When did is supplied, the file is served only if that account holds a claim on it — pin-set membership (see dev.atfs.repo.deleteFile), which any claimant satisfies whether or not it was the one that originally uploaded the file — a mismatch is reported identically to a missing file — matching com.atproto.sync.getBlob's own scoping exactly; the com.atproto.sync.getBlob alias always requires it, to stay PDS-compatible. Does not require auth, on either name.

Repository @atfs.dev did:web:atfs.dev namespace authority
Details · query
Kindquery
Authorityrepo.atfs.dev
Indexed

What's different

same NSID · two revisions from the same publisher
repo.atfs.dev · namespace authority
repo.atfs.dev · namespace authority
1 change, all backward compatible

Records and requests that were valid against the base schema stay valid against this one.

Query · errors

#main
Added

ContentPending

compatible

New error.

ContentPending
2 properties and 1 error unchanged Open the full schema diff →