at.turtleme.chat.message

turtleme.at

{
  "$type": "com.atproto.lexicon.schema",
  "defs": {
    "main": {
      "description": "A single message sent to a turtle meat chat room. Messages live in the author's own repository; a room is assembled by reading the backlinks that point at it.",
      "key": "tid",
      "record": {
        "properties": {
          "createdAt": {
            "description": "Timestamp declared by the sending client. It is not verified, so readers that care about ordering should prefer the record key.",
            "format": "datetime",
            "type": "string"
          },
          "facets": {
            "description": "Rich text over byte ranges of 'text', in Bluesky's facet shape. turtle meat writes and reads only mentions (app.bsky.richtext.facet#mention), each pointing at the DID the handle in the text meant when the line was sent. There is no threading: a mention points at an account, not at a message. Byte offsets count the whole of 'text', colour and effect codes included.",
            "items": {
              "ref": "app.bsky.richtext.facet",
              "type": "ref"
            },
            "maxLength": 20,
            "type": "array"
          },
          "room": {
            "description": "The room the message was sent to. 'https://turtleme.at/chat/global' is the global room. Because this is a link, a backlink index can list a room's messages without a dedicated AppView. A message written into a clan, an at.turtleme.chat.clan permissioned space, carries that space's at:// URI here instead; it lives in the author's permissioned repository for the space rather than their public one.",
            "format": "uri",
            "type": "string"
          },
          "text": {
            "description": "The message body. It may carry Old School RuneScape style chat codes in the form 'colour:effect:message', for example 'red:wave:hello there'. A client that does not recognise the codes should display the string verbatim rather than stripping it.",
            "maxGraphemes": 200,
            "maxLength": 1000,
            "type": "string"
          }
        },
        "required": [
          "text",
          "room",
          "createdAt"
        ],
        "type": "object"
      },
      "type": "record"
    }
  },
  "id": "at.turtleme.chat.message",
  "lexicon": 1
}

Validate Record

Validate a record against at.turtleme.chat.message

Validation Options
Automatically resolve and include external schemas for full validation
Treat any remaining unresolved references as valid

Metadata

DID
did:plc:f4h4tl43o4vx4hv2xps6siuz
CID
bafyreibt2lgiomvkp24nkr3szilzedtuqlxevkpbuqy4cthub5df444ape
Indexed At
2026-09-25 23:54 UTC
AT-URI
at://did:plc:f4h4tl43o4vx4hv2xps6siuz/com.atproto.lexicon.schema/at.turtleme.chat.message

Version History (3 versions)

Referenced Schemas (1)

Similar Lexicons

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

  • A message in a channel or DM space. The record lives in the *author's* repo within the space, so a message has no single owning collection to sort by — it is identified by (authorDid, tid). One collection serves chann…

  • A chat message. Lives in the sender's repo, points to a channel.

  • Record containing a Streamplace chat message.

  • fyi.opensocial.chat.message recordnot from the namespace authority

    A message in a group's chat, in its author's own repo in the group's chat space.

  • org.4906.temp.message recordnot from the namespace authority

    A message sent in a channel.

Lexicon Garden

@