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.

Mlem is fully FOSS!

GitHub

App Store

❤️

Thanks for the bug reports! Looks like there’s an error in the refresh logic for save–posts should remain in the view when initially unsaved (to avoid losing them forever on accidental unsave), but should disappear when the view is refreshed (which does not appear to be happening).

As far as community blocking goes, that’s mostly handled server-side–once you block a community, the app should filter posts from that community out of the currently displayed feed, and relies on the server-side block functionality to keep those posts from appearing in subsequent loads. We load in pages of ~50 posts, so if you block a community from, say, the profile page, it won’t update that over on the Feeds tab (yet, we’re looking at ways to implement that behavior but it’s fairly involved) and so you’ll still see those posts in the feed until the next load. In theory, simply refreshing the feed will clear them out because it’ll fetch the page fresh from the server.

Thanks for the bug reports!

Highlighting new comments is a good idea! I’ll have to take a look at what support there is API-side for it.

We’d like to remember collapse state, though that one’s a little trickier technically–collapse state is client-side, so we have to do some caching tricks to make that work. We’re reworking our backend modeling for 1.3 to include, among other things, a caching system, so we’ll see if we can work that in.

Unfortunately the API doesn’t support that and it’s infeasible to do client-side, so not for now. They have an issue for it but it’s closed as not planned, though they’ll reopen it if anybody wants to work on it so hopefully we will be able to offer this feature in the future.

Unfortunately not–Mlem is written entirely in Swift and SwiftUI, which as of right now doesn’t work on Android.

Hmm, that’s odd–App Store Connect reports 1.2 as live for all of our testing groups. It might just be a little slow to propagate the build out to all the servers.

As Sjmarf mentioned, we’re in bugfix mode for the upcoming 1.2 update. 1.3 is now properly scoped, and will focus on admin and mod tools–we plan to add support for mod actions and build a nice mod tool page to centralize moderation activities.

I’m truly sorry. If there were another way, we’d have taken it, but it’s just not feasible for a team as small as ours working in our free time in an ecosystem that evolves as fast as SwiftUI to offer long-term backwards compatibility without seriously compromising the quality of the app.

Yes. As soon as we know that a pending update is going to break compatibility, we’ll put a post up announcing it.

We have an update coming down the line soon that fixes this–it’s taking longer than expected because I’ve needed to rewrite pretty much all of our post loading code, which has been operating on the same core since early beta and at this point is stretched past its limit. We’re hoping to enter TestFlight within the next week.

It is the system blue–that appears to be the shade the system uses when “increase contrast” is enabled.

Thanks for the bug report, and glad to hear you got it resolved! I just got my sopuli account approved so I can debug it properly–it looks like there’s a problem adding accounts on 0.19 instances if you’re already logged into an instance, which would explain why uninstalling/reinstalling works. Should be fixed in the next build.

Reporting here works well! You can also directly open GitHub issues, but there’s not much to choose between the two.

Thanks for the bug report! We’ve got a PR open to fix this, should be working in the next build.

Thanks!

Glad to hear the icons are working–I’m going to put that down as an iOS issue and reopen it if it reappears. We’ll take a look at compact posts, customization should work in the next build.