app.didpic.write.createPost

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

• app.didpic.write.createComment

  procedure

  Create an app.didpic.feed.comment record on the authenticated viewer's own PDS, mediated by the AppView using its server-held session (confidential OAuth client only). image, when present, must come from a prior app.didpic.write.uploadBlob call. Either text or image (or both) should be present — matching the underlying record lexicon, this isn't enforced here either.

• app.didpic.write.updatePost

  procedure

  Edit an existing app.didpic.feed.post record via putRecord on the authenticated viewer's own PDS, mediated by the AppView using its server-held session (confidential OAuth client only). The image, aspectRatio, and createdAt are immutable and carried over from the existing record untouched; only text, facets, alt, and labels may change.

• app.didpic.write.uploadBlob

  procedure

  Upload raw image bytes to the authenticated viewer's own PDS, mediated by the AppView using its server-held session (confidential OAuth client only). Mirrors com.atproto.repo.uploadBlob. The returned blob ref is passed into createPost, createComment, or putProfile to attach it to a record. This endpoint applies no per-context size limit beyond a generous ceiling — the PDS enforces the real limit (post/comment 5MB, avatar 1MB, banner 2MB) when the blob is actually attached to a record.

• app.didpic.write.createLike

  procedure

  Create an app.didpic.feed.like record on the authenticated viewer's own PDS, mediated by the AppView using its server-held session (confidential OAuth client only).

• app.didpic.feed.post

  record

  A single-image photo post with optional caption.