Common questions about Post.

No. Free and paid plans use the same cryptographic protection. Plans differ by capacity and service limits.

Yes. Post is intentionally command-line driven so it can be used interactively or in scripts.

The product is designed around account and usage limits rather than charging per installation.

Yes. You send a Post to a recipient's Post name. Ask the recipient for the exact name, then use post find <name> to confirm that the name is registered before sending. The find command confirms the Post name exists; it does not by itself prove who controls it, so confirm important recipient names through a trusted method.

Yes. Post can send a text-style message, one or more files, or a message together with files. File-size and annual-transfer limits depend on your plan.

The sender selects a retention period from 1 through 30 days. The current default is 15 days. Expiration removes the relay copy; it cannot remove a copy that the recipient has already downloaded.

Post is designed so content is encrypted on the sender's computer before it reaches the relay and decrypted on the recipient's computer. The relay handles the encrypted transfer without needing the plaintext message or file. It still processes operational metadata needed to route and manage the transfer.

Post uses authenticated encryption. If protected content or authenticated transfer information is altered, authentication fails rather than silently returning modified plaintext.

A Post name is the public name people use to address transfers to you. It is associated with your Post identity and public key. Your private identity key remains local and is not the same thing as your public Post name.

Yes. The number of active Post names depends on your plan. If you have multiple names, you can select which one is your default sender with post names default <postname>.

Usage is shared across the Post account rather than being a separate allowance for every computer or Post name. A transfer counts its original transfer size once against the sender's annual allowance.

No. Post does not automatically charge for additional usage. The service can warn as you approach your allowance, and you decide whether to upgrade or purchase additional capacity when those options are available.

Run post -h or post -help for the built-in quick reference. The Post Docs page provides the more descriptive command reference and examples.