back

by xenodium·2y ago·view on hn ↗
Relying on markdown links to local images works well on my machine, but breaks as soon as I'd like to share that markdown file with someone else.

Sure, I can zip everything and send them over, but it's not as friendly for recepient as receiving a document handled by popular viewers, specially if they have to modify it and send it back.

With wide adoption of something like TextBundle, we get to have our cake (keep using plain text) and eat it too (send, view, and edit richer files).

2 comments
I've never had the usecase of sending markdown with images attached.

I use markdown for personal notes and in the rare case I shared them in the past, either there were no (relevant) links or I shared with e.g. confluence and I could just add the image.

My other usecase for markdown is Readmes and those are shared in git including the files.

I understood this spec mostly for sharing with local apps. Is that a missed usecase by me? Markdown documents instead of word/pdf/powerpoint/whatnot?

I have in the past run markdown through an exporter that base64-encoded the images into the document before sharing with someone

solves this one issue at least