On Connect, sub and up (which, I assume, was supposed to say sup) don’t get formatted.

One thing I’ve never been enthusiastic about has been Markdown’s auto-renumbering support. I have never seen someone really being happy with the implementation and lots of people frustrated as they try to embed numbered items and get them renumbered.

1. First

1. Second

Yields:

1. First

2. Second

Usually came up on Reddit when someone wants to quote a single item in a numbered list from some external text, quotes only that, and it gets renumbered…and they don’t know how to backslash-escape the period to avoid the thing:

1\. First

1\. Second

Yields:

1. First

2. Second

It looks like kbin also does the auto-renumbering. Dunno about lemmy. Kind of the one element of Markdown that I’d be happy to see die. I don’t mind having a syntax for auto-numbered lists – I just don’t think that using an actual number as prefix to indicate that that should happen is a reasonable way to go about it.

Thanks alot

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: !fediverse@lemmy.ml→[email protected] (link ref: /c/fediverse@lemmy.ml)
    • Kbin-style is also supported: /m/fediverse@lemmy.ml→/m/[email protected]
  • Users: /u/chaorace@lemmy.sdf.org→ /u/[email protected] (link ref: /u/chaorace@lemmy.sdf.org)
• Typography substitutions:
  • (c)→©
  • (tm)→™
  • (r)→®
  • +-→±
  • ...→…
  • ---→—
  • --→–
  • ???? (>= 4x)→???
  • !!!! (>= 4x)→!!!
• Github-flavor Markdown extensions:
  • Tables
  • Strikethrough: ~~example~~→example (image)
• Subscript/Superscript:
  • Sub: example~sub~→example_sub (image)
  • Super: example^super^→example^super (image)
• Footnotes:
  • Inline part: example[^notename]→example^[1] (image)
  • Bottom part: [^notename]: Note text→(see bottom of post) (image)
    • Important: the bottom part must be at the very end of the post, otherwise both halves of the footnote will break!
• Ruby Text: {example base text|example ruby text}→example base textexample ruby text (image)
  • “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:

  ::: spoiler visible part example
  hidden part example
  :::
  

  • See below ⤵️ (collapsed image) (expanded image)
    visible part example

    hidden part example

• Image/Video embedding: ![accessibility alt-text example](https://i.imgur.com/9nVMRqa.jpeg) => (image)

Curiously enough, it only has Markdown support once you are inside the Thread:

That reminds me of the threads/comments about the spoiler tagging in Lemmy being broken in many apps, hopefully that’ll be worked out sooner than later.

Just tested and it doesn’t seem to work in neither Connect, Voyager/wefwef, Liftoff nor even in Jerboa… Only worked in the Lemmy PWA.

Kbin’s implementation differs from Reddit’s in at least one way that I’ve run into: Reddit permitted a link to be italicized using asterisks inside the link. Like:

I read a [book called *Arabian Nights*](https://en.wikipedia.org/wiki/One_Thousand_and_One_Nights).

Valid in Reddit Markdown, but in kbin’s Markdown – dunno what lemmy does – that’s not permitted, and gives this:

I read a book called .

You can do:

I read a book called *[Arabian Nights](https://en.wikipedia.org/wiki/One_Thousand_and_One_Nights)*.

Which yields this:

I read a book called Arabian Nights.

What about tables ?

Everything except code block works for me on liftoff.

_sub should have two ~

sub

I guess ^up should have two ^ as well?

^^up^

^^ doesnt seem to do anything

Memmy seems to have slightly different markdown rendering

Code Block is broken, but the rest works on kbin.

error loading comment

it works yeah!