@rotur/cli
v1.4.0
Published
Manage your Rotur account from the terminal
Readme
@rotur/cli
Manage your Rotur account from the terminal.
Install
npm install -g @rotur/cliFrom source:
cd ~/rotur-cli
npm install && npm run build && npm linkQuick start
rotur login
rotur whoami
rotur me
rotur friends
rotur friend alice
rotur daily
rotur connect
rotur logoutLogin uses the device link flow. Your token is stored at ~/.config/rotur/config.json.
Sections
| Section | What it does |
|---------|----------------|
| auth | login, logout, whoami |
| account | profile, credits, blocks, notes |
| friends | list, request, accept, remove |
| following | follow / unfollow |
| posts | post, feed, like |
| notifications | inbox |
| tokens | scoped sub-tokens |
| keys | keys you own |
| gifts | gift codes |
| identity | public/private identity keys, signing, encryption |
| cosmetics | cosmetic shop, inventory, equipment, gifts |
| avatars | avatars, banners, custom backgrounds and overlays |
| emojis | custom emoji collection |
| trust | trust scores and account verification |
| profiles | public profiles and media URLs |
| groups | groups, members, roles, announcements, tips |
| items | marketplace items |
| storage | app-scoped key/value storage |
| files | virtual account files |
| stats | public network statistics |
| connect | connect devices and forward local ports |
rotur help
rotur help account
rotur help friendsShortcuts
login · logout · whoami · me · friend · unfriend · follow · unfollow · post · feed · daily · transfer · block · unblock
Connect
Keep this device online in the rotur connect dashboard:
rotur connectCreate a forward immediately:
rotur connect --port 3000 --public --forward-name devDevice identity persists at ~/.config/rotur/connect.json. Forward configuration persists on connect server and returns after restarts.
Remote shell access is disabled by default and controlled only from connected computer:
rotur connect --shell
rotur connect --no-shellChoice persists in local connect config.
File access is also disabled by default:
rotur connect --files
rotur connect --no-filesIncoming device-to-device files are saved into local Downloads folder.
Identity encryption
Sign and verify JSON using your Rotur identity key:
rotur identity key
rotur identity sign "hello world"
rotur identity verify @proof.json @message.jsonEncrypt for the key ID from another user's signing proof, then decrypt with the matching private key:
encrypted=$(rotur identity encrypt alice "secret message")
rotur identity decrypt "$encrypted"The CLI automatically resolves the recipient's current public key. A recipient
only needs to run rotur identity key once to initialize their identity. Plain
text and JSON content are both accepted; prefix a filename with @ to read it
from disk. Encryption produces one URL-safe rotur_enc_v1.… string containing
the authenticated envelope. --key-id is available only for selecting a
specific historical key.
Use --json when redirecting structured output. Key rotation requires
--yes, because envelopes addressed to the previous key cannot be decrypted
through the API afterward.
Profile cosmetics and media
rotur cosmetics shop --type background
rotur cosmetics equip sunset
rotur cosmetics gift sunset alice --note "Enjoy!"
rotur avatars upload-background ./background.mp4
rotur avatars upload-overlay ./overlay.gif
rotur emojis upload party ./party.gif
rotur trust score aliceOptions
rotur whoami --json # machine-readable outputLicense
MIT
