Lexicon Garden

social.wips.comment

Native wips.social comment / reply record.

Repository @wips.social did:plc:sodoi37wr44i3ypdwwlqqeup namespace authority
Details · record, key tid
Kindrecord
Record keytid
Authoritywips.social
Indexed
Compare Edit in builder → Fork →

Record

record · key tid

Properties

createdAt

requiredstring · datetime

Client-declared timestamp when the comment was originally created.

facets

array

Rich-text annotations (mentions, links, tags) over text, using official app.bsky.richtext.facet. Application validators enforce UTF-8 codepoint-aligned byte ranges, per-facet feature caps, and http(s) link URIs. Ceiling keeps worst-case DAG-CBOR under the explicit record budget.

  • maxLength: 30
itemsref
Reference

labels

union

Open union for forward compatibility. Current app authoring/validation requires com.atproto.label.defs#selfLabels when present; unknown variants are not treated as self-labels. External moderation labels stay out of the record.

One of

langs

array

Indicates human language(s) of the comment primary text content (BCP 47).

  • maxLength: 3
itemsstring · language

media

array

Ordered media items. May freely mix images and videos using shared social.wips.defs media objects. Same app media safety policy as updates.

  • maxLength: 50

parent

ref

When present, AT URI of the immediate parent social.wips.comment. Omitted for top-level comments.

Reference

subject

requiredref

AT URI of the root social.wips.update.

Reference

text

string

Optional comment body text. Required by application semantics when facets are present; at least one of non-whitespace text or known image/video media is required overall.

  • maxLength: 80000
  • maxGraphemes: 8000

Similar lexicons

semantic match

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

  • at.upvote.comment

    record

    A Markdown comment on a canonical subject or a reply to another comment.

  • social.wips.update

    record

    A project update with optional text, ordered mixed media, ordered links, and optional rich-text facets. Application validators require at least one of non-empty text, known image/video media, or links (media union stays open; unknown variants alone do not satisfy content). Optional allowComments defaults to true when omitted (enforced by application/comment semantics). Protocol ceilings are generous and non-product-shaped while keeping worst-case DAG-CBOR size under the explicit record budget.

  • app.didpic.feed.comment

    record

    A comment on a post. Optionally includes a single image with alt text and self-applied labels — same image shape as feed.post. Either text or image (or both) must be present in practice; the lexicon doesn't enforce that since 'one of N required' isn't expressible.

  • social.coves.community.comment

    record

    A comment on a post or another comment. Comments live in user repositories and support nested threading.

  • social.grain.comment

    record