Sjmarf

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 :)

Mlem dev here. This’ll be fixed in the next version, apologies for the inconvenience :)

If it’s the bug where the submit button is greyed out, you can work around it by adding a space to the title and then removing it again. That issue is fixed in the beta :)

Mlem dev here. Mlem shows this warning for instances that require registration applications to be approved first (which, these days, is all instances).

The aim here was to make it clear to users that they won’t be able to use their account immediately after signing up - otherwise, users may be confused that they can’t log in. I do agree that it’s a little scary though… we’ll think about some ways to tone it down. I’m open to suggestions for better wording.

I wasn’t aware that lemmy.world automated their process. It’s possible that we could provide a different UI for certain instances that use similar systems, but we’d have to hard-code each case which isn’t ideal.

The ability to sign up in Mlem was only added a month ago - before that, we directed users to the web browser to sign up. Our current implementation leaves much to be desired, but is more user-friendly than requiring the user to visit a website. I’m planning to make some improvements to the system in future. I was reading this Lemmy post the other day, which I think has some good ideas.

Here’s an overview of our current sign-up flow, fyi:

Using Mlem you can insert a spoiler by tapping the spoiler icon (it looks like an eye) in the markdown toolbar above the keyboard. The markdown toolbar can be scrolled left and right; you’ll need to scroll to the see the option for it

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 :)

The App Store version of Mlem doesn’t support GIF rendering just yet, but the TestFlight version does.

The App Store version of Mlem doesn’t support gifs just yet, but the beta version does.

I use Ice Cubes for Mastodon.

I’m one of the Mlem developers; I’m glad you’re enjoying it :) You could also consider trying the Mlem beta if you haven’t already. It’s about 8 months’ worth of development ahead of the App Store version. The reason why we haven’t updated the App Store version in so long is because the beta version doesn’t have all of the moderation tools yet (due to it being a full rewrite), and we don’t want to take those tools away from moderators who use Mlem.

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.

Yw :)

You might have “Show NSFW Content” turned off in your Lemmy account settings. If that setting is off you won’t be able to see any NSFW posts, even in your own profile. You’d still be able to open the post via a link, but they won’t appear in any feeds.

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.

Mlem dev here. It shows strikethrough, but not superscript. Lemmy has got a unique dialect of Markdown - in the current version we’re using an open-source Github-dialect parser, which is close to Lemmy’s dialect but not perfect. In the next update we’ve written a custom parser that handles all of Lemmy’s Markdown elements, including superscript and spoilers.

Octopus-Accelerated Machine Learning

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 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.

deleted by creator