Markdown that does not appear in the reply box:
Strikethrough:
some ~~strikethrough~~ text
some strikethrough text
Horizontal Rule:
***
Table with alignment:
||X|Y|Z|
|--------|:---|:----:|---:|
|1|X1|Y1|Z1|
|2|X2|Y2|Z2|
X | Y | Z | |
---|---|---|---|
1 | X1 | Y1 | Z1 |
2 | X2 | Y2 | Z2 |
Codeblock:
`**codeblock**`
`enclose in 3 backticks`
**codeblock**
enclose in 3 backticks
**codeblock**
indent with 4 spaces
**codeblock**
indent with 4 spaces
Heading 1:
# heading 1
heading 1
Heading 2:
# heading 2
heading 2
(Heading 3 you get when you press the H button in the reply box)
Markdown that kbin does not yet support but lemmy does:
Spoilers:
::: spoiler hidden or nsfw
spoilers here
:::
hidden or nsfw
spoilers here
Superscript:
some ^superscript^ text
some superscript text
None amongst kbin, lemmy and reddit support subscript as far as I can tell.
What this page looks like in kbin
What this page looks like in lemmy
More info:
https://commonmark.org/help/
https://spec.commonmark.org/dingus/
https://join-lemmy.org/docs/en/users/02-media.html
https://calckey.social/mfm-cheat-sheet
I love markdown, but it’s such a mess. There are too many competing specs out there. @ernest, have you worked with the Lemmy folks on this before? This is probably a lot lower priority than stability/performance/efficiency stuff you’ve got roadmapped, but it might be nice to try to build some consensus on a markdown spec amongst the community.
EDIT: actually, I should check the git repo and see if anyone has filed an issue. You’re already way too busy and I’ve pinged you several times when I should have taken the initiative and filed issues myself. Sorry, Ernest!