social.colibri.beta.bridge.uploadBlob
Uploads a file to the community's repo for use in a bridged message or as a bridged author's avatar.
Details · procedure
| Kind | procedure |
|---|---|
| Authority | bridge.beta.colibri.social |
| Indexed |
Procedure
procedure · POSTParameters
query stringThe community the registration belongs to.
Record key of the registration.
Input
*/*Output
application/jsonThe uploaded blob, to reference from a message or author.
Errors
AuthRequired
The request is missing, malformed, or unverifiable service auth.
CommunityNotFound
No community exists at the given DID.
RegistrationNotFound
The community has no bridge registration with that id.
Forbidden
The caller is not the bridge this registration belongs to.
RegistrationDisabled
An admin has paused this registration.
RateLimited
The bridge sent too many requests. Retry after the interval in the response headers.
BlobTooLarge
The file is larger than this AppView accepts from bridges.
CredentialsUnavailable
The AppView cannot act as the community because its stored credentials are missing or unusable.
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
social.colibri.beta.bridge.replaceAvatar
procedureSwaps the avatar on every message and thread attributed to one remote author of this registration, so the previous avatar blob is no longer referenced.
-
social.colibri.beta.community.putImage
procedureSets a community's picture or banner. The bytes are uploaded to the community's own repo, which is why this goes through the AppView: a community's blobs can only be written with the community credentials the AppView holds, and a space record must reference a blob living in the repo that holds the record. Replaces whatever was there before.
-
social.colibri.beta.bridge.postMessage
procedurePosts a message from someone on another service into a linked channel. The community writes the message, attributed to that person.
-
app.didpic.write.uploadBlob
procedureUpload 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.
-
Adds a custom emoji to a community. The bytes are uploaded to the community's own repo and the AppView writes the provider's record there with the community's credentials.