Command reference
oko contact set
Replaces the person's channels with the ones named, in that order: the one place how a person is asked is chosen. `oko-ios` is an alert on every iPhone signed in to Oko as this person; `imessage` is Oko's own, sent by Oko to the handle `oko contact imessage set` wrote, through the organization's Ultrareach, and also carries the hourly update; `mail` is Oko's own, mailed by Oko through the provider `oko contact mail set` declared, for a machine without Stado; every other name is a channel Stado pages through (`stado alerts channels`), handed in the same order to `stado alerts preferences set`, so Stado's pages and Oko's asks reach the same channels.
Invocation#
oko contact set <channel>...Inputs and options#
- One or more channels, each once. Example: `oko contact set imessage oko-ios skrzynka` — Oko sends `imessage` itself and Stado pages `skrzynka`; `mail` is only for a machine without Stado. Oko iOS's Asked of you toggles add or remove one channel and keep the rest.
Output and state effect#
- Hands the Stado channels to `stado alerts preferences set --channel …` first, then writes all of them and prints them. A choice with no Stado channel leaves Stado's paging channels as they were.
Refusals and safe exits#
- `oko contact set requires at least one channel, in the order to try them: oko-ios, mail, imessage or a channel Stado pages through (stado alerts channels)`; `<channel> is named twice; name each channel once, in order` (exit 2).
- Choosing `imessage` while its handle or relay is missing is refused with the sentence `oko contact imessage show` gives, naming the setting; choosing `mail` with no provider declared is refused naming `oko contact mail set`.
- `Stado refused the channels it would page you on (<channels>), so nothing was changed: <Stado's answer>` — Stado names an unknown channel and the ones it pages through. Nothing is written on a refusal.