Hi! I’m a developer for the Mlem iOS client. Join us on !mlemapp@lemmy.ml!
Thanks for the bug report - we weren’t aware of this issue. Some more information would help us to track this bug down, if that’s okay.
If you try to edit the same comment in the same way on the website interface (feddit.org), does it also fail? If so, does it give you an error message?
Thanks! This is the first I’ve seen them call it “1.0”, they’d been calling it “0.20” on the developer repo for a while. Exciting! We will of course be supporting Lemmy 1.0.
This is planned; we’re tracking the issue here.
It’s possible to view this list in the search tab on the Mlem beta. To do so, open the search bar and type a space, then tap on the filter button (just below the cancel button) and choose an instance to filter for.
The App Store version of Mlem doesn’t support gifs just yet, but the beta version does.
Hey! At the moment this isn’t (easily) possible. We’ll add a way to do this in the next update 👍
Yep, this is a known issue. When a comment chain gets too long, Lemmy doesn’t send all of the comments in the initial API response. When this happens, the web UI displays a “show n more replies” button that can be tapped to load the remaining comments:
We just haven’t got around to adding this button to Mlem yet, but it’s something we will certainly look into in future. We’re tracking the issue here.
Sorry I didn’t see your comment until now; your post didn’t federate to lemmy.ml properly for some reason so I only just saw it whilst using my alt account.
Nope; we haven’t got one yet. We hope to add one sometime in the future though.
That’s what I use in mlem.
Mlem dev here - we added a button for this to both the post editor and comment editor in our 1.3 update.
| Post | Comment |
|---|---|
 |
 |
This is related to a change in Lemmy v0.19.4. We’ve fixed this issue; it’ll be live in a day or two.
Adding widgets is something we’re interested in; we’re keeping track of the feature here. Right now, it’s not high on our priority list as it doesn’t directly impact the core functionality of the app. Therefore, it’s unlikely to happen in the next few updates, though we do plan to explore it in future.
Not yet, I’m afraid. We’re tracking the issue here. The next major update will include a complete rewrite of large sections of backend the app, in which we aim to solve this issue.
This isn’t possible in Mlem right now, but we can add it to the next beta 👍
We’re aware of a bug in which Mlem sometimes crashes when moving into the background on iPad when “Lock with Face ID” is on. Do you have that setting enabled? We’ve looked into that issue and now know why it happens, but it’s unfortunately rather tricky to fix with our current architecture. In the next major update we’re rewriting a large part of our codebase, which should allow us to fix this.
Mlem doesn’t have this option just yet, but we’re adding it the next beta. Memmy and Arctic have had it for a while.
Adding such an option is very easy to do for iOS apps - Apple provides a simple API for it, so we just have to add a settings toggle. I’m not familiar with how it works in Android development, but it may be more complicated.
Does this happen on every comment you post, or just some? I’m not able to reproduce this either yet, unfortunately.
Hey there! We’re aware that the comment-collapse animation is a little jarring; this is something we want to improve in future.
You can simplify the animations used when switching pages and when opening the image viewer by going into System Settings -> Accessibility -> Per-App Settings (right at the bottom) and enabling “Reduce Motion” and “Prefer cross-fade transitions” for Mlem.
Disabling the comment-collapsing animation isn’t yet possible. I’ve opened an issue for this on our GitHub, and will look into disabling it when “Reduce Motion” is enabled 👍
Yep, that’s another way it could be done. We’re hoping to add a text-selecting popup in the next major update, which will make this possible. However, it’s not quite as seamless as having a dedicated “Translate” button that replaces the post/comment content inline, which I’d prefer to use if implementing it proves to be feasible.
This would certainly be a useful feature. Unfortunately, Apple does not make their translation API available for us to use, so we’d have to use someone else’s API instead. I haven’t looked too deeply into potential options just yet, but have created an issue here to keep track of the suggestion 👍
Thanks, that’s super helpful! We’ll try to get this fixed for the next TF release.