51–53 of 53 posts
This is PrivateBin for markdown, right? Same URL fragment trick. My actual problem with markdown isn't previewing, it's search. I've got maybe 50 .md files scattered across different project directories from AI coding sessions. Three weeks from now when I'm trying to remember where I wrote down how to fix some specific issue, grep -r is all I've got and it's terrible for this.
Thanks very much, maybe I can add something to ‘sdoc’ to make that easier
Earlier quoted context omitted.
That direction makes a lot of sense. If sdoc could output raw content — or parsed frontmatter and body separately — to stdout, agents could consume it directly without a browser step. Something like sdoc get --format json piped into whatever the agent needs next. The frontmatter-as-structured-data angle is where it gets interesting: an agent reading frontmatter as JSON could use it for routing, status checks, depende…
Interesting idea, do you have any ideas of states that could be particularly useful to have? It's not something I have thought of before
I am excited about this really cool idea. I read the update, but does it mean there are two approaches: one where you pack all the content into fragments, and another where you encrypt it on the client side, save it to the server, and reduce the content to data containing only the key? Also, wouldn't it be better if the encryption and fragmented compression could also be handled on the web client side?
That’s exactly what happens. We encrypt client side. The sever only gets encrypted data. You can inspect the network request to see what the sever receives. Your decryption key always stays client side (in the url fragment). Also, the short URL (which saves the content in cypher format on the server) is optional. It only triggers if you specifically trigger it (by clicking “Generate” at the top of the rendered docume…