The secret that was never at rest

The database password needs to reach a colleague, so it goes into the chat: where it now lives in two histories, several device caches, and a vendor's export tooling, forever.

Send it through a pipe instead. You: echo the credential into curl -T - against a pipe path. Them: curl the same path into their clipboard or straight into the config file. The bytes route through; nothing lands on a disk between you. When the transfer ends, the channel is simply over: there is no message to delete, no retention setting to audit, no "clear history" ritual to trust.

Two commands your team already knows, and the secret's written trail is zero.

The credential crossed as a stream and exists nowhere now.