I’m thinking about this whole “missing blobs” problem after migrating between PDSes. Could a server process iterate over all the posts to check for missing blobs, and then import them automatically? What requires the user to manually detect this? The more automated, the better; for more users.
Apr 6, 2026 at 5:40 AM
migrating a did:web to a new pds
mini tutorial on migrating a did:web from one pds to another. this assumes you already have a did:web. start by using pds moover to migrate records to the ...
PDSList - A database of Bluesky PDSes
A database of Bluesky PDSes that are 'open' - by madebydanny.uk
haileyok/cocoon
An ATProtocol PDS (Personal Data Server) written in Go with a SQLite block and blob store
PDS MOOver: The Next Generation - Bailey's Retrospective
PDS MOOver now supports automated backups and account recovery
A blob in the bucket - Hitchhiker's Guide to the Atmosphere
Learn how to setup your self hosted PDS to use an S3 object store for blob storage.
Hey @dholms.at, do you have plans for blobs in spaces? We're chatting about it on @iame.li's stream. The proposal says blobs are uploaded to space host, right? That makes sense when the space host is a PDS because it has `com.atproto.repo.uploadBlob`, but not if the space host is something else.
Attention PDS devs! We merged a lexicon change last week increasing the max image upload for Bluesky posts from 1 MB to 2 MB. This rolled out to our PDSs instances last Friday. We'll begin enabling this in the Bluesky app soon. If your PDS implementation is still validating at 1 MB, plz update! ✌️
Eric
Related to this, we've been slowly rolling out a higher resolution limit for our image uploads, from 2000px^2 to 4000px^2. Until the below image size increase rolls out (soon), image sizes are still capped at 1 MB, so FYI you won't see immediate quality increase in all cases just yet.
