clawbot
1e2f0de877
check / check (push) Waiting to run
Each file in schema/ now describes what the HTTP API on next sends and accepts. A numeric reply has its name in command and its number in code. body is always an array of strings. MODE, KICK and JOIN carry their values in body, and TOPIC needs a non-empty body. PING takes no token, and its PONG is the HTTP response. A channel name is limited to 63 characters, and the leading # is optional from a client. PUBKEY.json is deleted, since the server has no such command. The section of schema/README.md that listed the differences is removed, and the sentences it made false are corrected. Model: opus-5-5
23 lines
995 B
JSON
23 lines
995 B
JSON
{
|
|
"$schema": "https://json-schema.org/draft/2020-12/schema",
|
|
"$id": "https://sneak.berlin/go/neoirc/schema/commands/NOTICE.json",
|
|
"title": "NOTICE",
|
|
"description": "A notice: a message to a channel or a user that a client must not answer automatically. The server relays it as it relays a PRIVMSG. A NOTICE to a channel with mode +H needs no hashcash stamp. RFC 1459 §4.4.2.",
|
|
"$ref": "../message.json",
|
|
"properties": {
|
|
"command": { "const": "NOTICE" },
|
|
"from": { "type": "string", "description": "The sender's nick. The server sets it." },
|
|
"to": { "type": "string", "description": "A channel name, which starts with #, or a nick." },
|
|
"body": {
|
|
"type": "array",
|
|
"items": { "type": "string" },
|
|
"description": "The lines of the notice, one string per line.",
|
|
"minItems": 1
|
|
}
|
|
},
|
|
"required": ["command", "to", "body"],
|
|
"examples": [
|
|
{ "command": "NOTICE", "from": "alice", "to": "#general", "body": ["Back in five minutes"] }
|
|
]
|
|
}
|