sorted by: new top controversial old
[-] sjmarf@lemmy.ml 7 points 2 weeks ago* (last edited 2 weeks ago)

Mlem dev here. You can attach a link to the post directly by clicking the link button in the post editor toolbar then tapping "Paste" (with a link copied to clipboard). We're aware that this isn't the most obvious UI, and are improving the design in the next version.

[-] sjmarf@lemmy.ml 4 points 1 month ago* (last edited 1 month ago)

Mlem dev here! Lemmy has a custom "flavor" of Markdown that is distinct from other social media platforms. Open-source markdown parsers and renderers exist for popular flavors of Markdown (e.g GitHub-flavor), but not for Lemmy-flavor. Most Lemmy clients choose to use an existing GitHub-flavor parser that is close enough to Lemmy's to be indistinguishable in most cases. Mlem uses swift-markdown-ui to render markdown, which uses cmark-gfm as its parser.

Lemmy's spoiler format is unique to Lemmy-flavor markdown, so that's one of the places where use of a third-party markdown parser is noticed by users. Other common parsing errors are ~subscript~ and footnotes.

Adding spoiler support is not particularly easy, unfortunately. You can't really apply spoiler-parsing logic on-top of another markdown parser - it has to be integrated into the parser itself. This is because the app needs to ignore spoiler markdown in certain situations, such as inside of a code block. The only good option is to write a custom markdown parser from scratch, or modify an existing markdown parser to support Lemmy's markdown dialect. Both options can be difficult for developers for several reasons:

  • cmark-gfm is written in C, which the developer of the Lemmy client may not be familiar with.
  • If the app is using a third-party renderer, and not just a parser, that renderer also needs to be rewritten to support the new parsing logic.

This takes a significant amount of time for comparatively little value for users, so most client developers didn't prioritise it.

In an upcoming Mlem version, we're replacing our markdown parser renderer with a custom one that can render spoilers and subscripts, but we've got a way to go before we achieve full parity with Lemmy. If any developers of other apps are using cmark-gfm, you're welcome to use our code from that repo under the terms of the licence.

Sorry this is kinda long, I hope this answers your question

[-] sjmarf@lemmy.ml 2 points 2 months ago

Footnotes^[Hello world!] are also undocumented.

[-] sjmarf@lemmy.ml 2 points 2 months ago

Yeah, it's rather inconsistent. I opened an issue for it a while ago.

[-] sjmarf@lemmy.ml 5 points 4 months ago

Nope; we haven't got one yet. We hope to add one sometime in the future though.

[-] sjmarf@lemmy.ml 3 points 4 months ago

That’s what I use in mlem.

Mlem dev here - we added a button for this to both the post editor and comment editor in our 1.3 update.

Post Comment
[-] sjmarf@lemmy.ml 1 points 6 months ago* (last edited 6 months ago)

Mlem doesn't have this option just yet, but we're adding it the next beta. Memmy and Arctic have had it for a while.

Adding such an option is very easy to do for iOS apps - Apple provides a simple API for it, so we just have to add a settings toggle. I'm not familiar with how it works in Android development, but it may be more complicated.

sjmarf

joined 1 year ago