Okay, thanks for the feedback. We’ll add a toggle for it in this weekend’s TestFlight beta :)

The green leaf icon indicates that an account was created in the last 30 days.

We don’t currently offer a way to disable this, but we can add a setting for it. Is it the bright green color that you find distracting, or do you find the information unnecessary? :)

Thanks for letting us know, we’ll look into it. I’ve created an issue here to keep track of this.

Hey again. We’ve updated the app to add a gray bar to the left of all comments in the profile feed, to give them similar styling to the comments that you’d see when reading the replies of a post.

Example:

I hope this makes them easier to distinguish from posts in the profile feed. Let us know if you have any further feedback :)

It is app-wide at the moment - if you enable “Hide Read” from a certain community, it is enabled in all communities. The button is available from the feed, rather than from settings, because it is an option that users may want to toggle on the fly. We also have the “post size” and “blur NSFW” settings available from the feed for the same reason.

In future, we’d like to make community sorting and filtering options (incl. hide read) saved per-community for ease of use, or at least the option for it to work that way. Issue here

A post is marked as read when you open, upvote, downvote, save, or reply to it. If you enable “mark read on scroll” it’ll mark posts as read when you scroll past them. Posts that are marked as read will have a slightly dimmer title text.

I would maybe want some indication that there are hidden posts available to unhide.

Yeah, this is something we’d like to do. “Hide read” is enabled has proven to be a very common cause of confusion; we need to make it more obvious somehow.

Might you have “hide read” turned on? You can turn if off by tapping on the (…) button in the top-right of a community, then tapping “show read”.

Do you know where you installed the app from? Or, if you can post a screenshot of the app I can find out which one it is.

Edit: Ah, I see you’ve figured it out. :)

Thanks! I’ve created an issue on our GitHub repo to keep track of this.

I’ve not seen this error before. Some guesses at what might be causing this: Maybe your report reason is too long? Or maybe it contains special characters? You could try changing your report reason to rule those out. If it’s caused by one of these, let me know and we’ll add a better error message for that eventuality.

If changing the report reason doesn’t fix the issue, it would be helpful if you could message me a link to the content you’re trying to report, if you’re comfortable doing so. No worries if not, though :)

Mlem dev here. Mlem shows this warning for instances that require registration applications to be approved first (which, these days, is all instances).

The aim here was to make it clear to users that they won’t be able to use their account immediately after signing up - otherwise, users may be confused that they can’t log in. I do agree that it’s a little scary though… we’ll think about some ways to tone it down. I’m open to suggestions for better wording.

I wasn’t aware that lemmy.world automated their process. It’s possible that we could provide a different UI for certain instances that use similar systems, but we’d have to hard-code each case which isn’t ideal.

The ability to sign up in Mlem was only added a month ago - before that, we directed users to the web browser to sign up. Our current implementation leaves much to be desired, but is more user-friendly than requiring the user to visit a website. I’m planning to make some improvements to the system in future. I was reading this Lemmy post the other day, which I think has some good ideas.

Here’s an overview of our current sign-up flow, fyi:

That’s a good idea - we’ll see if we can get this fixed for the next TestFlight version 👍

The only other thing I could think of is going to the way back machine and getting one of the earlier apps like Mlem or Memmy

Unfortunately, this is unlikely to work because lemm.ee is using a much newer Lemmy version than such versions would be designed for. Newer Lemmy versions introduced breaking changes that caused many older clients to stop working.

Tthe oldest iOS version that the oldest version of Mlem supports is iOS 16, and for Memmy I seem to remember that it’s iOS 13 (though I can’t find a reference to that right now). So I don’t think either would be viable for OP. Arctic currently supports iOS 15 and later; I’m not familiar with whether it supported older versions in the past.

The Lemmy developers are implementing support for this in Lemmy 1.0 - we’ll update Mlem to support that feature when Lemmy 1.0 releases. And yes, you’re welcome to submit feature requests here :)

Yw :)

Thanks for the kind words! We’re glad you’re enjoying Mlem. Love from… also the UK :)

Yeah, this would be nice to have! It looks feasible from a technical perspective, though we can’t make any promises about how soon this will be implemented. We’ve got an issue open for this feature on GitHub here if you want to keep track of any progress we make :)

If you find it inconvenient to reach over to the other side of the screen, you could consider enabling “swipe anywhere to navigate” under Settings -> General. Though you cannot use swipe actions when that setting is enabled.

We’ve added swipe action customization to the TestFlight version of Mlem. It’ll be live on the App Store in a couple of weeks or so :)

Using Mlem you can insert a spoiler by tapping the spoiler icon (it looks like an eye) in the markdown toolbar above the keyboard. The markdown toolbar can be scrolled left and right; you’ll need to scroll to the see the option for it