pipe — ephemeral cross-machine copy/paste (in-RAM, <=5 min TTL)

PUSH (machine A):
  echo hi | curl --data-binary @- https://pipe.0exec.com
  cmd 2>&1 | curl --data-binary @- https://pipe.0exec.com/my-slot        # named slot
  cmd 2>&1 | curl --data-binary @- 'https://pipe.0exec.com?burn=1'       # one-time (deleted on first read)
  cmd 2>&1 | curl --data-binary @- 'https://pipe.0exec.com?ttl=60'       # shorter TTL (seconds, capped at 300)
  cmd 2>&1 | curl --data-binary @- 'https://pipe.0exec.com?words=1'      # say-it-out-loud link (otter-maple-…)
  cmd 2>&1 | curl --data-binary @- 'https://pipe.0exec.com?qr=1'         # push + print a scannable QR

PULL (machine B):
  curl https://pipe.0exec.com/<id>
  curl 'https://pipe.0exec.com/<id>?qr'            # print a QR of the link — scan it with your phone

SHELL HELPER (bash or zsh, macOS or Linux — drop into ~/.bashrc / ~/.zshrc):
  eval "$(curl -s https://pipe.0exec.com/shell)"     # the /shell path has no '?', so no zsh quoting
  cmd | p                 # push, prints the URL
  cmd | p my-slot         # push to a named slot
  p get my-slot           # pull a slot / id
  cmd | p -e              # END-TO-END ENCRYPT: prints https://pipe.0exec.com/#<id>~<key>
  p open 'https://pipe.0exec.com/#<id>~<key>'   # pull + decrypt (quote it — the # is a shell comment)

ENCRYPT WITH ONE LINE (no helper, just curl + openssl — pick any password):
  echo 'my secret' | openssl enc -aes256 -pbkdf2 -k PASS | curl -s --data-binary @- https://pipe.0exec.com
  # → https://pipe.0exec.com/oCwOc4q4    ... then on the other machine, SAME password:
  curl -s https://pipe.0exec.com/oCwOc4q4 | openssl enc -d -aes256 -pbkdf2 -k PASS
  The server only ever sees a scrambled blob — never your text or password.
  Wrong password just prints "bad decrypt". A whole file: add -in file.jpg.
  Hide the password from shell history: drop "-k PASS" and openssl prompts.

END-TO-END ENCRYPTION, browser-openable link (one flag: -e, via the helper):
  echo 's3cr3t' | p -e
  # → https://pipe.0exec.com/#Xq7k2aPb~2f9c…   (open in ANY browser to decrypt, or: p open '<link>')
  The key rides in the URL's #fragment, which curl/browsers NEVER send to the
  server, so the server stores only ciphertext and a passive ISP never sees it.

KNOW WHEN IT'S READ (?notify):
  W=$(echo secret | curl -sD - --data-binary @- 'https://pipe.0exec.com/?notify=1' | awk 'tolower($1)=="x-pipe-watch:"{print $2}' | tr -d '\r')
  curl -s "$W"      # long-polls; returns {"read":true,"readAt":...} the moment it's opened

RICHER CLIENT — wormhole + universal clipboard (one install):
  curl -s https://pipe.0exec.com/install | sh
  echo hi | pipe send       # prints a short code (otter-maple-…); share it
  pipe recv <code>          # fetch + decrypt on another machine (one-time)
  pipe pc  /  pipe pp        # copy here, paste there (end-to-end clipboard)

BROWSER:
  Open https://pipe.0exec.com in a browser for an in-page encrypt/paste app, or to "Ask someone
  for a secret" — they fill a form, it's sealed to you, only you can read it.

Notes:
  * --data-binary @- streams stdin verbatim; plain -d would mangle newlines.
  * Max body 10 MiB. Served as text/plain, never executed.
  * Anyone with the URL can read it within the TTL — use ?burn=1 for secrets,
    or encrypt (above) so the server never sees the plaintext.
  * ?words links are shorter to say but lower-entropy — pair with ?burn or -e.
  * zsh "no matches found"? Quote any URL with a ?  e.g. 'https://pipe.0exec.com/?shell=1'.