Sjmarf

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

Here’s the relevant issue on the Lemmy-ui repo https://github.com/LemmyNet/lemmy-ui/issues/2579

Thanks! We’re glad you’re enjoying Mlem :)

This feature is now available on the TestFlight :)

We’ve added this back to Mlem on the TestFlight version :)

This feature is now available on the TestFlight :)

Sure, we can implement that 👍

a) accidentally tapping the Feeds button in the corner of the screen with the heel of my palm

Apollo’s solution to this was to allow swiping left from the right edge to go “forward” to the page that was just closed. We’ve got an issue open for this feature here, but unfortunately this feature is rather tricky to implement so it’s unlikely to be added anytime soon.

b) accidentally tapping the article body (either while actively scrolling or just holding my phone), which collapses the post.

We’ll add a setting to disable collapsibility of post content in this week’s TestFlight (issue here) 👍

In Mlem, go to the Settings tab. Then, tap on the link at the very top of the page with your account name. Then tap “Content & Notifications”, and turn off “Show NSFW Content”.

That setting will hide all NSFW content that is marked as such by the user who posted it. If you see some NSFW content that is not marked as NSFW, you should report the content so that the moderators can deal with it.

Welcome to Lemmy :)

In 2.0 we rewrote the whole app from the ground up, and just forgot to re-implement that feature haha. We’ll add it back in for next week’s beta 👍

Settings -> Media & Links -> Share Links

Edit: Oops, we put up a slighter older build than we meant to, lol. The setting isn’t in that build. It’ll be available shortly 👍

Sharing links using your own instance is now the default behavior in the latest weekly build :)

Thanks for letting us know, we’re looking into it. I’m also having the same issue. Lemmy.ml seems to be working fine on the website, but is currently broken when using Mlem. Other clients (I’ve tried Voyager and Arctic) appear to be having the same issue, so I think the Lemmy.ml admins might have changed something server-side.

I’m glad you’re enjoying it :)

The image type label is only shown when Developer Mode in switched on under Settings -> Advanced. If you turn off that setting, you won’t see the label. We’ve got an issue open to move the image type label out of the way of the image when developer mode is on (link).

You’re welcome! 😄

You can enable gestures under Settings -> General -> Swipe Actions. You cannot have swipe actions enabled at the same time as the “Swipe Anywhere to Navigate” setting.

You can change the text size for the app as a whole by going to System Settings -> Accessibility -> Per-App Settings (at the very bottom) -> Mlem -> Larger Text. We don’t currently offer a way to change this for only part of the app, such as for comments only.

Thank you for your feedback. We’re sorry that you aren’t completely satisfied with the update.

And the cards seem to unnecessary.

We decided to switch to the card styling to provide better visual separation between posts in the feed. This was in response to feedback from some of our users that posts (and comments) felt too squished together. Is there anything in particular that you don’t like about the cards?

If you don’t like the background color of the cards in dark mode, you can revert to the pure black background by enabling the OLED theme under Settings -> Theme.

It feels very clunky and bloated

“Bloated” as in “too many unnecessary features”? We’re trying to strike a balance between having a wide array of features to tailor to everyone’s needs, and providing a simple, clean experience that’s approachable to new users. If you have anything specific in mind that you think we should revisit, let me know.

It takes even more clicks to share a link post now, and it was already annoying enough already.

The UX of the post composer has been tricky for us to work out - we’ve tried many different designs so far. I’ll do some more prototyping and see if I can cut it back down from 3 -> 2 taps :)

Nope, it should still be there: