One reactor's reaction to one message. Written into the reactor's own repo within the message's space, so counts are an aggregate the view computes across the space's repos — never a mutable field on the message, which nobody but the author could write.
tid
Timestamp-based ID
Properties
createdAt
string
datetime
Required
An RFC 3339 formatted timestamp.
emoji
string
Required
The reaction itself, as a literal emoji cluster. Graphemes are capped rather than bytes alone because a single emoji with modifiers is many bytes and one visual unit.
maxLength: 64 bytesmaxGraphemes: 8 graphemessubject
ref
com.atproto.repo.strongRef
Required
The message being reacted to.
View raw schema
{
"key": "tid",
"type": "record",
"record": {
"type": "object",
"required": [
"subject",
"emoji",
"createdAt"
],
"properties": {
"emoji": {
"type": "string",
"maxLength": 64,
"description": "The reaction itself, as a literal emoji cluster. Graphemes are capped rather than bytes alone because a single emoji with modifiers is many bytes and one visual unit.",
"maxGraphemes": 8
},
"subject": {
"ref": "com.atproto.repo.strongRef",
"type": "ref",
"description": "The message being reacted to."
},
"createdAt": {
"type": "string",
"format": "datetime"
}
}
},
"description": "One reactor's reaction to one message. Written into the reactor's own repo within the message's space, so counts are an aggregate the view computes across the space's repos — never a mutable field on the message, which nobody but the author could write."
}