this post was submitted on 02 Apr 2025
19 points (95.2% liked)
Asklemmy
47186 readers
823 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy π
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- [email protected]: a community for finding communities
~Icon~ ~by~ ~@Double_[email protected]~
founded 6 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Cool idea! AFAIK emails are just sent as text but the client renders them when you read them. Theoretically it wouldn't be hard to send markdown and add a header that indicates the body is markdown. Hard part is integrating support into the client. Since HTML is more verbose than markdown, and you can often mix markdown and HTML, this could actually lead to space and data savings!
I think the idea is for your mail client to translate your Markdown into HTML before sending. To convince the whole worldβs email ecosystem to directly support Markdown would be an impossibly large lift given that HTML is already virtually universally supported.
Yeah, that's the idea.
Yeah, some clients allow you to compose in html so I just copy paste from my markdown editor. But it would be nice to skip the copy paste part and just to parse the markdown directly on the client. Also the markdown renderer fails, the markdown is already human readable. So that would be cool.