app.bivri.feed.createComment

Bivri refuses content longer than 200 graphemes, which is stricter than the 1000 the record schema permits: the record admits what any client may write, this method admits what this service accepts. A refusal is InvalidComment and nothing is written.

Details · procedure
Kindprocedure
Authorityfeed.bivri.app
Indexed

Procedure

procedure · POST

Input

application/json

content

requiredstring

Comment text.

  • maxLength: 10000
  • maxGraphemes: 1000

Strong reference to the comment being replied to. Omit for a top-level comment.

subject

requiredref

Strong reference to the artwork to comment on.

Output

application/json

cid

requiredstring · cid

CID of the comment record that was written.

uri

requiredstring · at-uri

AT URI of the comment record that was written.

Errors

ConsentRequired

The authenticated member has not confirmed age and accepted the Terms and Privacy Policy.

Unauthenticated

Nobody is authenticated, so there is no repository to write to.

InvalidComment

The comment is not one this service accepts — longer than 200 graphemes, or otherwise refused by the write boundary. Nothing was written.

Blocked

The commenter and the Artwork's author, or the author of the comment being replied to, have a block between them in either direction. Nothing was written.

Similar lexicons

semantic match

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

  • Edit the text of a comment the authenticated member owns. The artwork and reply parent remain unchanged.

  • Create a comment on a post or another comment. Comments support nested threading, rich text, embeds, and self-labeling.

  • Record containing a comment on an artwork.

  • 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.

  • Like a record from the authenticated member's repository.