SolarOS

SolarOS 4.17.7 manual · command

messages

Open the tabbed instance, connection, and message manager.

Usage

UsageDescription
messagesOpen the tabbed instance, connection, and message manager.
messages statusShow archive, persistence, drop, and live provider state.
messages conversationsList provider-neutral conversations and unread/security state.
messages list <conversation-id>List retained messages and their stable hexadecimal IDs.
messages send <conversation-id> <text> [--allow-untrusted]Queue an outbound message; discovered direct endpoints require the explicit flag.
messages read <conversation-id>Mark a conversation and its linked Inbox entries read.
messages delete <message-id>Delete one retained message and its linked Inbox projection by hexadecimal ID.
messages clear <instance|instance-id|all>Clear retained history and owned Inbox projections, including for removed instances. Unrelated Inbox sources remain.
messages remove <instance|instance-id>Remove a provider instance, connection credentials, pending sends, history and Inbox notifications.
messages outboxList pending outbound requests in queue order.
messages cancel <message-id>Cancel a queued outbound message by the hexadecimal ID printed by list or send.
messages classes / messages instancesList available provider classes or configured instances.
messages add gateway <name> <url> [token]Save an independent Gateway instance. Enable it with messages connect <name> and start gateway-sync.
messages configure <name> <url> [token]Change a Gateway instance's connection settings.
messages add irc <name> <host> <port> <nick>Save an independent native IRC connection.
messages add meshcore <name> radio <radio> <profile>Save a MeshCore instance on a local radio.
messages add meshcore <name> ble <address> <type> [pin]Save a MeshCore companion binding.
messages add link <name> <transport>Bind an independent Chat projection to a named Link transport.
messages add sc2 <name> <domain> [admit] [key=<b64>]Add an SC2 relay from its signed descriptor at https://<domain>/.well-known/solaros-relay (CA and host name checked; never plain HTTP). The relay key (and the fallback relays and their keys) are pinned; every login must prove the key, a different key is refused. key= must match the descriptor when given. messages configure <name> key <b64>|off changes the pin. See man messaging.
messages add sc2 <name> chats://<host>:<port>[#pin=sha256/<b64>] [admit]Save a disabled SC2 end-to-end relay instance. Enable it with messages connect <name> and start its worker with job start sc2-sync; messages disconnect <name> disables it. messages configure <name> admit <code>|off or pin <pin>|off change it; fallback <url> [<url> <url>]|off sets up to three fallback relays (failover and return to the primary; sc2 relay shows which is in use). With a pin, the pinned key alone authenticates the relay (self-signed certificates work); without one the CA bundle is used. See man messaging.