Sjmarf

Not at the moment, no.

Ideally, this would be implemented on the Lemmy backend. This is something we could do without requiring changes to the backend, but it would only work with relatively small numbers of communities. Our Github issue for this feature is here.

We dpon’t have any immediate plans to implement this without backend support, because it seems likely that Lemmy will implement it in future, which would make it a lot easier to add this feature to Mlem. The GitHub issue on the Lemmy repository is here, and it has a bounty of €6000.

Thanks for letting us know, I’ve created an issue here to keep track of this :)

Oops, we just forgot to re-implement this when we rewrote the app for 2.0. Thanks for letting us know! It’ll be back in the next TestFlight version 👍

This is now available on the TestFlight version. Response times aren’t shown by default; you can turn them on under Settings -> Accounts.

Sure, we’ll implement this for the TestFlight release this weekend :)

Yw, I’m glad you like it :)

Welcome to Lemmy! We’re glad you’re enjoying Mlem :)

It’s under account settings (the very top option in the “Settings” tab, with your username).

Option to see overall ‘user rating’ for other accounts. Basically as you’re scrolling g you see a number next to their name, possibly color coded, showing how you’ve rated them in the past. Could be posts on their posts and comments on their comments, or even just an aggregation of both in both places.

This is something we’d like to do in future, though it isn’t on our immediate roadmap. We’ve got an issue open on GitHub for this here, if you want to keep an eye on any progress we make :)

Here is a link to the TestFlight. To crosspost a post to another community, tap on the ellipsis menu (...) in the top-right of a post, then tap “Share…”, and then tap “Crosspost”.

You can then choose a community by tapping “Choose community” in the top-left of the sheet that opens.

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” 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”.

Thanks! I’ve created an issue here 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 :)

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