It’s currently live on the TestFlight beta! We’re planning to roll it out to the App Store in the next few days.

1. Yes! We aren’t happy with the current state of our media viewer. 2.0 is a backend-focused rewrite, so probably won’t have a new media viewer on launch, but it’s without a doubt high on our list of important features.
2. Hard to say. Our iOS compatibility policy guarantees compatibility until iOS18 reaches 75% market share; after that, I can’t make any promises. We take the decision to drop compatibility very seriously, and try to only do so when the features offered by the newer iOS are valuable enough that we would be compromising the potential quality of the app by ignoring them.
3. Yes. We’re still working out some UX concerns stemming from the fact that it’s very slow to search posts and comments compared to communities, but it’s in the plans.

We’re reluctant to give concrete time estimates since our development time is constrained by our day jobs and other responsibilities, but we hope to have 2.0 in early TestFlight on a schedule roughly in line with our release cadence (~2mo).

We don’t plan to release any new features to the 1.x codebase after 1.3, but we will continue to fix major bugs and maintain compatibility against changes to the Lemmy API while we bring 2.0 up.

We maintain a client-side list of instances supported by lemmy-status.org. Looks like we just forgot to add toast.ooo–should be fixed in the next build.

Update to Sjmarf’s earlier comment: I have finally tracked down the source of the slowdown, and the fix should be out in the next TestFlight build.

It was not, nice catch! Should be fixed in the next build.

We plan to completely overhaul our markdown handling for the next major release, which will include both properly handling Lemmy’s dialect quirks and integrating markdown editing tools into the composer.

Link

App Store Connect reports there are a couple hundred empty spots, but we’ve had issues in the past with it reporting empty spots on the dev side but not letting more users join.

It wasn’t, sorry about that! We’ve merged the fix for the next build, so hopefully that won’t happen again.

deleted by creator

You can show/hide read posts from the ellipsis menu in the top right of your Feeds tab.

Thanks for the bug report! We’re looking into it.

Does this happen on all sort modes, or only specific ones?

Is it affected by toggling “show unread?”

Progressing well! We’re hoping to have the next TestFlight build out soon.

That’s unfortunately not currently supported by the Lemmy backend. There is an issue open for it, though it doesn’t appear particularly active right now.

We have some major changes in development that might make this feasible to implement client-side–I’ve put up an issue for it, but can’t make any promises pending a more thorough technical investigation.

Mark read on scroll is coming in the next build!

As for searching within community, it’s in the plans but I can’t give a more precise delivery estimate.

Thanks for the bug report!

I’m not able to reproduce this behavior–would you mind sharing:

• Mlem version
• iOS version
• device
• a comment that produces this behavior

Thanks!

Thanks for the feedback! We’ll take it under consideration.

There are both technical and design reasons for the change.

Technically, it lets us rip out a lot of logic that handled the differences involved in loading and displaying your own profile vs someone else’s; from a design perspective, this makes your profile page a much more logical grouping: “content you created” instead of “content you created and also content you saved.” Feeds is already the root category for “content other users created,” with each item (All/Local/Subscribed/Community) displaying a filtered subset of that content, a grouping into which Saved fits much more naturally.

Saved posts have moved to Feeds—you can find them alongside All/Local/Subscribed.

My bad, forgot a piece of the path! It’s Settings -> General -> Open Links in Browser (first item in the list).