Additionally, it can save your stuff for easier recalling, without giant URLs involved.
In the following examples,
is the document encoded in Base-64 as Hashify does it.
To present a document, as Hashify does:
To store this document for easier recalling:
You’ll be given an ID to recall this document later.
You can also make a POST request with the raw Markdown (Base 64 encoded or not) to
To recall a document:
Where 352c706a-bffc-4da0-a75e-e5b429a9c5ae is the ID that was returned in the storing step. If a document with the specified ID doesn’t exist, a 404 is returned.
To recall the Base 64-encoded document, as it was saved (for example, for editing it in Hashify):
But this is not a REST API!? Nobody said it was :) It is designed to be easy to use by a human fiddling with the address bar of any web browser.
Goshify is just a simple, 150 line Go program… Here’s the GitHub. It uses:
DMCA complaints should be directed at
abuse -at- tny.im
We’ll delete any content we don’t like or others don’t like (DMCA, …). Such is life. If you use nothing but the decoding function (/d/ endpoint) we can do nothing about the contents.
When decoding from the URL, the contents are only kept in memory for a brief period and are not stored anywhere. However, this doesn’t protect against connection eavesdropping.