Thanks for the suggestion!

We try to only deprecate support once a version is basically unused—beehaw was the only major instance still on 0.18, so we maintained support until they recently upgraded. There are still a few personal instances running 0.18, but that’s an extremely small fraction of the user base.

We have an issue open to handle those cases—we’ll take your thoughts into account!

Thanks for the bug report! We’ll look into it

This happens when there isn’t enough room on the interaction bar—we have some common sense limits on how many items can be added to the bar to try to prevent this, but the emphasis on customization means that we can’t always account for every configuration and screen size. Handling this overflow elegantly is still an active topic in our design conversation.

Thank you!

@sjmarf@lemmy.ml deserves equal credit :)

I’ve created an issue to track this. I haven’t looked deeply into the technical feasibility–SwiftUI has some powerful tools for reversing layouts to accommodate languages that scan right-to-left, but I can’t promise this is a feature we can deliver without doing a bit more research.

We haven’t changed anything, but it’s possible your instance admins have made some configuration changes–there are some configuration settings that can mess with image proxying. The Voyager dev brought attention to this last week, plus put up a nice page about it–it’s possible that the sopuli admins fixed their config in response to that.

We’re also on the App Store, but every App Store release goes through TestFlight first.

This is correct. The GitHub releases feature doesn’t make a lot of sense for Mlem, since we primarily deliver through the App Store rather than via source downloads.

I’m currently working with the admins to resolve this issue.

Update: We’ve identified the root cause and a fix is in development. A patch will be out as soon as possible.

Update 2: The fix is ready and just waiting on App Review to release.

Update 3: The fix is live. Thank you for your patience!

Mlem is written in SwiftUI, which unfortunately is not compatible with Android. There are some promising projects to port Swift apps to Android, but nothing mature enough that we could feasibly support both platforms, though we’d like to if/when the cross platform Swift ecosystem matures enough for that to be realistic.

Thanks! I totally fell for the “crosspost” label—I didn’t realize Lemmy just uses that term to mean “posts with the same link.”

The merged crossposts feature we have planned is actually exactly what you’re asking for then, since that’s what Lemmy means by a crosspost.

Do you have an example of a post where lemmy-ui does this? I’d love to look into how they implement it but I can’t find an example of the feature in action.

Test

Mlem dev here.

This feature, as suggested, presents a fundamental technical problem: frontend clients load posts a page at a time, and so are only aware of the posts you’ve already scrolled past and the ~20-50 posts ahead in the feed. It’s therefore not possible to find all posts with the same URL and aggregate their comments into a single chain under the first occurrence of the URL, at least not without loading infeasible amounts of data ahead of time.

We do have a merged crossposts feature planned, which achieves the same basic functionality but using the backend crosspost data rather than absolute URLs; our comments view also currently shows the list of crossposts and indicates the number of comments on each one.

Alternatively, a filter that only shows posts with comments

That’s a good idea, we’ll add it to a future build.

Thanks! I’ve tracked down the issue, it should be fixed in the next build.

Thanks for the bug report! There isn’t a setting–it should just work. Some questions to help us reproduce and debug:

• Are you on iOS or iPad?
• Which iOS/iPadOS version are you using?
• Can you dismiss images correctly with the X button?

Mlem has this feature planned–we have a clear path towards implementation, but there’s a lot of groundwork and design to do first so it probably won’t be delivered for at least several months.

This is one of Mlem’s guiding principles! We strive to offer options to show as much–or as little–information as the user wants, with options to show/hide:

• Author
• Author instance
• Community instance
• Community subscription status
• Thumbnails
• Score
• Display downvotes separately
• Time posted
• Saved status
• Number of replies

Plus a fully customizable interaction bar–and that’s all just for posts.

If you’re on iOS, I’d encourage you to give us a try!

This feature is in development for the upcoming Mlem 1.3 build.