sjmarf

We did consider this in the past, but decided against it. Implementing this would mean that we - the Mlem developers - would have to decide who gets the flair and who doesn't. As the development teams of those projects change over time, we'd have to keep up with ensuring their current developers are correctly flaired. This would take time that could be spent developing new features for Mlem instead. There are also many Fediverse projects, and we don't want people asking "why don't the [XYZ] developers have flairs?" if we start giving out flairs to only the developers of certain projects. I hope that makes sense :)

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

Mlem 2.0 is missing a lot of features at the moment, which we'll be re-adding before the final 2.0 release. You can find a full list in the "Roadmap" section on the 2.0 release post :)

Yeah, we're aware. We're making it clearer in the next version :)

Thanks for the bug reports! We'll look into it :)

Also if more room could be added after the bottom response in a thread. Currently the up/down vote and reply buttons are so close to the nav bar at the bottom I click the nav bar by mistake sometimes.

Sure 👍 Mlem v1 had this; we'll be adding it back in

Thanks for the feedback!

Please add more breathing room/padding to posts — it’s stressful how close posts are to each other (could mostly be solved with just a few more pixels of negative space under the interaction bar before the divider).

Yeah, I'm not happy with the padding there either and we're experimenting with some ways to improve this.

Also, some text feels like it’s cropped by the edges of my iPhone. There is more than enough room to spare on the iPhone Pro Max for that additional comfort.

I'm not sure what you mean by this. Would you mind providing a screenshot?

The interaction bar customization doesn’t allow me to customize it the way I want because it doesn’t consider that I have more space for actions if I remove some readouts. Also, I’d like to reorganize readouts.

I'll look into allowing more space for actions if readouts are disabled. Reorganising readouts is planned in the future, though it may not be in v2.

Almost all settings should be specific to the account they were changed under, like settings of users on a pc. Currently, a change under one account is made to the other accounts.

We're considering applying this to certain settings, such as the "Blur NSFW" setting. We're hesitant to apply this for all settings, because we don't want the settings system to become too complicated for the user. Users might find it annoying if they have to go through all of their accounts to apply a setting change that they want to make globally.

Upon returning to my list of subscriptions (from my All feed for example), my subscribed feed may be highlighted, even though that’s not the page I’m on, coming from, or have selected.

We're looking into it 👍

Mlem dev here! You can click the link button in the top-right of the post creator and then tap "Paste" to paste a link. You can also upload an image from that menu.

We'll no longer be supporting iOS 16 from Mlem 2.0 onwards, I'm afraid. We're sorry if that means you can't use newer versions of Mlem. You can read more about our reasons for doing so here.

Thanks for the feedback! I've created issues for these features :)

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^[Hello world!] are also undocumented.