Command line

PSippr is serverless — every phone, desktop and browser tab is a full node on the same peer-to-peer network. The CLI app is the same node with no screen: a small Java program you run on a server, a Raspberry Pi, or in a CI pipeline. It joins the network like any other device, with its own identity, and talks to it from the terminal instead of a UI.

It ships in the downloads above as PSippr-cli.zip (Linux, macOS, Windows — needs Java 17). This page is about what it does, not how to get it.

What it can do today

• psippr serve — starts the node and keeps it running; every other command below talks to this running node over a local API.
• psippr login [--name LABEL] — one-time device authorization (see below): prints a code, opens your browser to confirm it, and remembers the result.
• psippr status — this node's id, display name, and how many peers it sees.
• psippr wall list / wall post <text> / wall delete <id> — read the public wall, post to it, or remove your own post.
• psippr users [--online] [--filter TEXT] — list known users and their ids.
• psippr msg send <id> <text> / msg list [--unread] [--from <id>] / msg read <id> — send and read direct messages by user id.
• psippr profile --name NAME [--photo FILE] [--prefs a,b] [--looking-for a,b] [--age N] — set up the node's own profile.

What it is for

A headless node is useful anywhere a screen doesn't make sense: a small server that stays online to help the network, a bot that watches for messages, or — what we're building it for first — reporting the status of our own build pipeline (started, failed, which platform is done) straight to the public wall, the same way any person would post it. No cloud dashboard, no email: the same network everyone already uses.

How it is authorized

A CLI node is not a trusted admin account — PSippr has no admin. Getting it running is two separate steps:

1. One-time confirmation — psippr login. The CLI asks our server for a short code, opens your browser to confirm it (the same idea as gh auth login), and the page asks for an e-mail just to prove the installation belongs to a reachable person. The confirmation code is only ever e-mailed — it is never shown on this site or to anyone else. Once confirmed, running login again just reports back — no need to repeat it.
2. Per-action approval. Run psippr serve --approver <nodeId> and every wall post first asks that account to approve it — a translated prompt pops up in their app immediately, with a warning that it is safe to ignore if they do not recognize it, and a confirmation code exchanged separately, so an accidental tap cannot approve anything on its own. Skip --approver and the node posts without asking, same as before — useful for local, manual use where you are already the one running it.

Every wall post or change a registered installation makes is logged; see your CLI's activity with the two codes from your local cli-auth.json.

Registered installations

Every CLI installation that completed step 1 above is listed here — just a label and a date, nothing that identifies who is behind it.