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.

Hey! We haven’t implemented post searching yet, though we’ll be implementing it in the next version of Mlem (2.0).

To block an instance, you need to go to the instance page. You can do this by searching for the instance in the “Search” tab, or by tapping the (…) button in the top-right of a community page or profile page and tapping the instance name. In the instance page, you can tap the (…) button in the top-right and then choose “block” to block the instance.

To view blocked instances go to the Settings tab, then tap the button at the top of the page (your username), then tap “Blocklist”.

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.

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.

We're aware of a bug in which Mlem sometimes crashes when moving into the background on iPad when "Lock with Face ID" is on. Do you have that setting enabled? We've looked into that issue and now know why it happens, but it's unfortunately rather tricky to fix with our current architecture. In the next major update we're rewriting a large part of our codebase, which should allow us to fix this.

Uploading images in comments will be in the next update, along with a fix for the inbox count bug! We're also working on a Mark Read on Scroll option, a Modlog page and support for moderator actions (which have all been highly requested features).

Unfortunately, full markdown support is rather tricky to do. We've done some deeper research into how we might implement this since the last time it was suggested; it's a large undertaking that would require some significant time input, but it should be possible. It's not something we're scoping for the upcoming update, but it's something we hope to dedicate time to further down the line.

The Saved feed has moved to the Feeds list, just below “All”, “Local” and “Subscribed”.

Yep, this isn’t possible right now. We’re tracking the issue here, and I’ll try to get it working in the next major update 👍

This isn’t supported by Lemmy yet. It would be relatively easy to let our users follow other users on the client-side, and show your followed users on the subscriptions page. However, as this isn’t supported by Lemmy, your followed users unfortunately wouldn’t sync with the web app or other clients.

It would get a little more tricky to show notifications when a user posts, or create a “followed” feed that only shows posts from users you follow. To do either of these, we’d have to make a separate API request for each user that you follow. If you follow a large number of users, this could be problematic.

One potential way to mitigate this would be to have a separate “send notifications” option for followed users, and we’d only allow you to enable this setting for ~5 users.

I think this is a cool idea. Following users isn’t on our immediate roadmap, but it’s something we could look into in future.

Thanks for the feedback!

We are aware that swiping to collapse the top-level comment would be a useful feature and are tracking the issue here. The swipe action to collapse comments was added back in September, and isn't a new feature in this release.