Sjmarf

Mlem dev here. Tagging is a feature implemented by Voyager and some other clients, Mlem doesn’t have this feature. It isn’t an official feature of Lemmy - clients store the tag information locally on-device rather than on the Lemmy server.

In Lemmy 1.0 (an upcoming version) they’re adding support for adding notes to users, and Mlem will be adding support for it at that point.

TL;DR switch to Voyager or wait for Lemmy 1.0.

Yes, iOS only.

Mlem dev here. We’re working hard on implementing Piefed support, but it’ll be another few weeks before it’s ready. If you want to use both in a single app right now, consider using Interstellar :)

In Mlem, go to the Settings tab. Then, tap on the link at the very top of the page with your account name. Then tap “Content & Notifications”, and turn off “Show NSFW Content”.

That setting will hide all NSFW content that is marked as such by the user who posted it. If you see some NSFW content that is not marked as NSFW, you should report the content so that the moderators can deal with it.

Welcome to Lemmy :)

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.

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