Borrowing from @[email protected]'s post and @[email protected]'s post:
For anyone interested, here’s the Lemmy markdown configuration. As you can see, Lemmy’s website UI supports the full commonmark spec (tutorial / official spec), plus a bunch of extensions. I don’t think anyone’s fully documented these yet, so I’ll try doing so below. Apologies in advance to mobile users, this is probably gonna get ugly (see included image links for how it should look):
- URL autolinking (plaintext URLs automatically turn into links)
- Lemmy autolinking:
- NOTE: No link will be inserted if the viewer is browsing an instance where the resource is not yet known/blocked
- Communities:
[[email protected]](/c/[email protected])→ [email protected] (link ref: /c/[email protected])- Kbin-style is also supported:
/m/[email protected]→ /m/[email protected]
- Kbin-style is also supported:
- Users:
/u/[email protected]→ /u/[email protected] (link ref: /u/[email protected])
- Typography substitutions:
(c)→ ©(tm)→ ™(r)→ ®+-→→ ±...→ …---→ —--→ –????(>= 4x) → ???!!!!(>= 4x) → !!!- horizontal rule (line between paragraphs)
---→
**bold**→ bold*italics*→ italics# Headings→ # Headings (1 # for level1 heading, up to 5 #'s; must be at start of new line)[Link text](https://link.com/)→ Link text- Github-flavor Markdown extensions:
- Tables
- Strikethrough:
~~example~~→ ~~example~~
- Subscript/Superscript:
- Sub:
example~sub~→ example~sub~ - Super:
example^super^→ example^super^
- Sub:
- Footnotes:
- Inline part:
example[^notename]→ example[1]
- Inline part:
- Ruby Text:
{example base text|example ruby text}→ example base text- “Ruby” is an html-ism for special pronunciation aids which frequently appear within young person’s media where the language includes non-phonetic characters (e.g.: Chinese characters)
- Japanese Furigana example: {凄|すご}い！→凄い！(image)
- Spoilers:
visible text
hidden part example
visible text
hidden part example
- Code:
- `
inline code` →inline code - code block:
- `
``` println(“Hello World!”) ``` becomes
println(“Hello World!”)
Finally:
If I want to write a character that will normally be interpreted as any of the above, I can escape the character with a backslash → \ ...
So you can write something like \^this → ^this
That’s a pretty good post. Makes sense and sounds like, just ipv6, we’ve got a long time before the internet starts making vast changes.