docsget pocketty

Reference

Versions

Why the App, the daemon and the relay never need matching versions, and what happens when one is older.

pocketty’s parts update on their own schedules: the App from the App Store, the daemon from its install script, the relay on Cloudflare. None of them needs another to match.

The Rules

pocketty owns four interfaces: pocketty pair, code setup, the relay API and the sealed note. All four follow the same rules:

  • The first message carries a range of versions. The other side picks the highest version both know, and lists what it can do.
  • Within a major version, fields are only added. Unknown fields are ignored, and a field never changes its meaning.
  • A feature turns on only when both sides list it.
  • The relay keeps every API path it ever served.
  • A sealed note with an unknown major version shows the placeholder text, never an error.

What You Will See

  • New App, old daemon. Everything the old daemon knows works. Features that need a newer daemon stay off.
  • Old App, new daemon. The same, the other way around.
  • No daemon. Shells and herdr Panes work. Notifications and code setup are off for that host.

herdr

herdr has its own versions. pocketty reads what the herdr on each host can do, and falls back when a feature is missing.

    Type to search keys, notifications, the CLI, and more.