A tool for tailing a labelers' firehose, rehydrating, and storing records for future analysis of moderation decisions.

Fix post blob hydration to use proper AT Protocol API #1

open
opened by scoiattolo.mountainherder.xyz

Problem#

Post blob hydration is currently broken - it's got the wrong endpoint

Current Implementation#

The BlobProcessor is fetching from CDN URLs:

https://cdn.bsky.app/img/feed_thumbnail/plain/${did}/${cid}@jpeg
https://cdn.bsky.app/img/feed_fullsize/plain/${did}/${cid}@jpeg

Solution#

  1. Resolve the user's PDS endpoint from their DID document via plc.wtf (or whatever is specified in .env)
  2. Use the proper AT Protocol API: ${pdsEndpoint}/xrpc/com.atproto.sync.getBlob?did=${did}&cid=${cid}

Reference#

See ProfileHydrationService.processProfileBlob() for the working implementation.

Also check docs/profile-blob-hydration.md section 7 for details on proper blob fetching.

Files to Update#

  • src/blobs/processor.ts - Update processBlob() method
  • May need to add PDS resolution logic or import from profile service
sign up or login to add to the discussion
Labels
good-first-issue
assignee

None yet.

Participants 1
AT URI
at://did:plc:uyqnubfj3qlho6psy6uvvt6u/sh.tangled.repo.issue/3m3ent6tlc622