Turn a .md file into a read-only page with an address you can send — with a password and an end date when you want them, a count of opens, and a link you can end at any moment.
Share a document from your history
Drop the `.md` file on the converter, or paste the text into the live preview and press Convert and keep. Signed in, press Save to keep the document in your account, then press Share, choose Anyone with the link, and copy the address it gives you: `/s/` and a token nobody can guess. That address is all your reader needs — no account, no app, nothing to install.
What opens there is the document, rendered by our server as a plain read-only page, with downloads of the self-contained HTML file and of the Markdown source for anybody who wants to keep working on it. Shared pages are served with `noindex`, so they stay out of search results, and each one carries a link for reporting it.
Publishing to a public link needs a confirmed email address on the account. Sharing with named people works either way.
A link can ask for a password of eight characters or more. The reader meets a short form before the page, and the right answer is remembered in that browser for a day. After ten wrong tries in a minute from one machine, or thirty for the link from everywhere at once, the form asks them to wait.
The password is kept only as a hash, so it can be changed or removed but never shown, and a new one ends every earlier entry at once. It can be set while the document is still private, so the link is protected from the moment it exists. Signed in as the owner, you are never asked for it.
A link can also end: in an hour, a day, seven days or thirty, or on a day you pick. After that the page and its downloads say the link has expired, and when, and Save a copy stops working too. A new end date, or none, opens the same link again.
The Share dialog says how many times the link has been opened and when it last was. The Views tab beside Check lists the latest 200 opens, newest first and grouped by day, with whether each came through the shared page or the app.
It counts opens, not people, and your own are among them. For a link anyone can open, nothing is kept about who opened it: an open is recorded as its time and whether it came through the page or the app, no cookie is set to count it, and the bots that fetch a link to draw a preview in a chat are not counted. The opens belong to the link, so revoking it deletes them, and none is kept longer than a year.
For a document that should not travel, choose Specific people and add addresses one at a time. Each person is emailed the link, and opening it means signing in as that address, so anybody else who gets hold of the link is turned away. There is no password in this mode, because signing in is already the stronger check.
Because those readers signed in, the Views tab can say which of them opened the document, how often and when last, or that somebody has not opened it yet — and the page they read tells them that you can see this. Documents other people address to you appear in your history under Shared with me, with who shared each one.
Switching a document back to Private deletes its token. The address you sent stops working for everybody, its end date and its count of opens go with it, and sharing again makes a different link: the old one never comes back. Because that cannot be undone, it is the one change the dialog asks you to confirm.
Revoking controls the address, not the copies: what a reader downloaded or printed stays with them. A public page may be cached at the edge for up to a minute, so a revoked link can take that long to stop everywhere; a page behind a password, or shared with named people, is never cached.
A folder is shared the same way, from Share in its menu: the same three modes, the same end date and password, at an address under `/f/`. The reader gets the whole tree, every page opens inside it, and links between pages stay inside the shared folder. A reader who is signed in can press Save to my account and keep a copy of all of it — a copy, so what you change later does not reach theirs.
A document can also take new text without changing its address. Publishing in place — `PUT /api/v1/documents/:id` from a script, `tp push --update` from a terminal, the Obsidian plugin, or an assistant — replaces the text and keeps the link, the password, the end date and the named readers. The text it replaced is kept as a revision, the newest ten of them.