Share a document with someone who does not use Tisty
Someone needs to read one of your documents: the notes for a handover, a recipe, the minutes of a meeting. They do not use Tisty, and you would rather the copy did not outlive the reason you sent it.
What people usually do
- 1
Attach it to an email or a chat
Quick, and the file stays in their inbox and on the provider's servers for as long as they keep it. A Markdown file also arrives as raw text.
- 2
Upload it to a cloud drive and share a link
The link works until you remember to take it back, and the provider holds the file readable.
- 3
Paste it into a message
Fine for a paragraph. The tables, diagrams and pictures stay behind.
What that leaves behind
- A copy you no longer control, readable by whoever stores it.
- No end: it stays until somebody deletes it, if anybody does.
- Nothing that tells the reader the copy really came from you.
How to share it from Tisty
- Open the document and, in the panel beside it, press Share… in the Shared row.
- The first time, Tisty makes the key that signs what you share, backed up with your 24-word phrase, and asks you to accept Folio's terms.
- Choose what the other person can do and how long it lasts without use, 15 days at most, and copy the link.
- Whoever gets it reads it in a browser, with no account. The page says which key signed it, and anything that should not be there can be reported.
- Folio keeps only encrypted bytes: the key travels in the link, after the #. Your document stays in your Tisty.
To learn about Folio, the service behind the link, visit its home: folio.tisty.app
Frequently asked questions
Does the other person need Tisty or an account?
No. The link opens in any browser, with no account and nothing to install.
Can Folio read what I share?
No. Tisty encrypts it before it leaves, and the key travels in the link, after the #, which browsers never send. The exception is a report that hands the operator the link to read it, in the cases Folio's terms list.
What if I lose the link?
Nobody can recover it, because the server never had its key. While the document is shared, Tisty keeps its links: copy them again from its Shared row.