sjmarf

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 👍

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

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

There isn't a way to do this at the moment. Apollo had this feature, and we've been keeping track of the idea here. Unfortunately, this is tricky to implement because of limitations imposed by Apple's frameworks. It's certainly possible, but would take some time to work out and isn't on our immediate agenda.

Yes, searching for posts and comments will be in 2.0!

Mlem v2 is a completely different codebase to Mlem v1, so bugs that exist on v1 are likely to be fixed in v2. We're aware of an Mlem v1 crash that occurs on iPad when Face ID Unlock is enabled - this is unfortunately difficult to fix because of the way Face ID Unlock works.

In iOS 18, Apple is introducing native support for Face ID Unlock in any app. This makes our own system redundant, so we'll be removing our version of the feature in favor of the more reliable iOS equivalent.

We're making several quality-of-life tweaks to the iPad layout in 2.0! So far, we've made the image viewer full-screen and updated the sidebar to look a bit more modern. Here's a sneak peek:

There's also a setting for a more compact sidebar layout, if you prefer that:

(This is all WIP, it might change. Ignore the lack of All/Local/Subscribed buttons, those will be back in before the first TestFlight).

We're also adding a setting that displays posts in a grid with two or more columns, which will make the posts look less wide in this format.

Longer-term we're considering some ways that we can improve the iPad layout as a whole - such as having a three-column layout - but there's some navigation problems to work out and we can't promise that anything like that will be in 2.0.

Sure, I'll add one in the next Mlem version 👍

Hey there! This is possible - if you go to Appearance -> Posts -> Customize Widgets, you can drag-and-drop the individual upvote and downvote counters into the post layout.

I'm not sure. Someone had the same issue a couple of months ago; they said that changing their password fixed it. It's possible that certain special characters in the username/password causes issues. In the next Mlem update we're rewriting the login system, and will check to see if that's the problem.