dfb1636be5
Replace c2s/s2c/s2s taxonomy with IRC-native structure: - schema/commands/ — IRC command schemas (PRIVMSG, NOTICE, JOIN, PART, QUIT, NICK, TOPIC, MODE, KICK, PING, PONG) - schema/numerics/ — IRC numeric reply codes (001-004, 322-323, 332, 353, 366, 372-376, 401, 403, 433, 442, 482) - schema/message.json — base envelope mapping IRC wire format to JSON Messages use 'command' field with IRC command names or 3-digit numeric codes. 'body' is a string (IRC trailing parameter), not object/array. 'from'/'to' map to IRC prefix and first parameter. Federation uses the same IRC commands (no custom RELAY/LINK/SYNC). Update README message format, command tables, and examples to match.
18 lines
712 B
JSON
18 lines
712 B
JSON
{
|
|
"$schema": "https://json-schema.org/draft/2020-12/schema",
|
|
"$id": "https://git.eeqj.de/sneak/chat/schema/commands/NOTICE.json",
|
|
"title": "NOTICE",
|
|
"description": "Send a notice. Like PRIVMSG but must not trigger automatic replies. RFC 1459 §4.4.2.",
|
|
"$ref": "../message.json",
|
|
"properties": {
|
|
"command": { "const": "NOTICE" },
|
|
"from": { "type": "string" },
|
|
"to": { "type": "string", "description": "Target: #channel, nick, or * (global)." },
|
|
"body": { "type": "string", "description": "Notice text." }
|
|
},
|
|
"required": ["command", "to", "body"],
|
|
"examples": [
|
|
{ "command": "NOTICE", "from": "server.example.com", "to": "*", "body": "Server restarting in 5 minutes" }
|
|
]
|
|
}
|