Sjmarf

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.

This isn’t directly possible. You can add an image to the body of the post using the ![alt text](https://example.com/image.png) formatting. Lemmy automatically chooses an image to display on link posts. You can’t override this on Lemmy 0.18.4, which Beehaw uses (I believe it’s possible on later Lemmy versions, but the official UI doesn’t support it on those versions).

Mlem dev here - we do not and will never run ads, sell data or lock functionality behind a paywall :)

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

Footnotes^[1] are also undocumented.

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

Yeah, I’ve got an alert set up. I’m from the UK :)

That’s correct, it only shows the first page at the moment. In the next Mlem update it’ll load infinitely.

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

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

Mlem dev here! Admin features aren’t live quite yet, but they should be available as part of an upcoming beta in a couple of weeks or so.

Mlem dev here! I can’t reproduce this issue at the moment. Do you mind sharing the model of iPad you are using, and iOS version? Does the crash happen with every comment, or seemingly randomly, or only under some condition? Thanks!

deleted by creator

deleted by creator