• Added "Send to Lemmy User" to the share sheet
Admins, developers and mods are about to get pinged way more!
Official community for Mlem, a free and open-source iOS Lemmy client.
Rules
FAQ
• Added "Send to Lemmy User" to the share sheet
Admins, developers and mods are about to get pinged way more!
Editing a post or comment sometimes currently fails for me with the following message:
The operation couldn’t be completed. (MlemMiddleware.ApiClientError error 2.)
Is this something that is already on the roadmap to be fixed?
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?
Interestingly enough - I checked again. The message is different when trying to edit a comment. I tried for testing purposes with my comment here: https://feddit.org/post/7542299/4550121
Mlem gives error message when pressing the copy button "The operation couldn’t be completed. (MlemMiddleware.ApiClientError error 2.)" In the message itself, it says "response error: ApiErrorResponse(error:"language_not_allowed") with status 400
I finally edited the comment with the feddit.org default web interface, and it worked fine.
Version info of the instance: BE: 0.19.5 Mlem app: 2.0 (222) (weekly beta Testflight)
Thanks, that's super helpful! We'll try to get this fixed for the next TF release.
Thank you so much 💪 😄
Just installed and poked around a bit. So far so good! I like the new look and feel.
Viewing cross posts is probably my favourite feature for 2.0 so far. It’s been a little over a week, and I can’t believe I used Lemmy without it!
We're glad you like it 😄
It’s great to read up on more conversations!
New comment counts are back! Thanks.
I also submitted a bug report on GitHub, Mlem is marking posts read on scroll even when that option is unchecked in settings.
~~As I am typing this it appears the unearthly loud sounds are fixed too. Again, thank you.~~ I spoke too soon about the sound.
The loud sounds should be fixed on the latest weekly TF.
Is the weekly still coming out today? I have been refreshing test flights more than I should be looking for it.
Something went wrong with the auto build, it should have gone out hours ago. I’m working to get it restored, should be up within the hour.
Edit: new weekly is now live
Search by post works great 🫡🫶💪
Now we just need search by comment. The only reason why I still have Voyager.
The latest beta update is great!
Is Mlem supposed to have sound in videos? I literally thought that people were uploading gifs, but apparently all of the “gifs” I’ve been watching have actually been videos that are supposed to have sound.
It is planned but not implemented yet—video support is still very preliminary. Better controls and sound handling is one of the core outstanding items keeping 2.0 from the App Store; I’m hoping to make good progress on it in the next couple weeks.
Oh ok, so it’s not just on my side then, that’s good to know! Thank you! Mlem is definitely the best app available for lemmy!
Finally Mlem has link support!
I used to be a TestFlight tester but I got removed and all I can see now when clicking the join link is that I was removed from the program ):
Never mind, it fixed itself just now, thanks for the great app!
Hmm, that's strange. Have you tried manually opting out of testing ("Stop Testing" in the TestFlight app) and clicking the link again?
Please add more breathing room/padding to posts — it’s stressful how close posts are to each other (could mostly be solved with just a few more pixels of negative space under the interaction bar before the divider). Also, some text feels like it’s cropped by the edges of my iPhone. There is more than enough room to spare on the iPhone Pro Max for that additional comfort.
The interaction bar customization doesn’t allow me to customize it the way I want because it doesn’t consider that I have more space for actions if I remove some readouts. Also, I’d like to reorganize readouts.
Almost all settings should be specific to the account they were changed under, like settings of users on a pc. Currently, a change under one account is made to the other accounts.
Upon returning to my list of subscriptions (from my All feed for example), my subscribed feed may be highlighted, even though that’s not the page I’m on, coming from, or have selected.
Thanks for the feedback!
Please add more breathing room/padding to posts — it’s stressful how close posts are to each other (could mostly be solved with just a few more pixels of negative space under the interaction bar before the divider).
Yeah, I'm not happy with the padding there either and we're experimenting with some ways to improve this.
Also, some text feels like it’s cropped by the edges of my iPhone. There is more than enough room to spare on the iPhone Pro Max for that additional comfort.
I'm not sure what you mean by this. Would you mind providing a screenshot?
The interaction bar customization doesn’t allow me to customize it the way I want because it doesn’t consider that I have more space for actions if I remove some readouts. Also, I’d like to reorganize readouts.
I'll look into allowing more space for actions if readouts are disabled. Reorganising readouts is planned in the future, though it may not be in v2.
Almost all settings should be specific to the account they were changed under, like settings of users on a pc. Currently, a change under one account is made to the other accounts.
We're considering applying this to certain settings, such as the "Blur NSFW" setting. We're hesitant to apply this for all settings, because we don't want the settings system to become too complicated for the user. Users might find it annoying if they have to go through all of their accounts to apply a setting change that they want to make globally.
Upon returning to my list of subscriptions (from my All feed for example), my subscribed feed may be highlighted, even though that’s not the page I’m on, coming from, or have selected.
We're looking into it 👍
Uploading a photo to any community fails with Error. Anyone getting this issue too?
As Eric said, if you tap on the error it'll give you more info. Have you tried a different image? Some instances impose a maximum file size on the images you can upload. If that happens, it'll show the "error" toast. We'd like to make that error case show a more obvious warning in future.
It was exactly it! Image too large, it says. Fingers crossed Mlem make this process easier in the future🤞
Thanks for the bug report! If you tap the error message at the top of the screen it will give you a more detailed error message—would you mind sharing that message so we can debug further?
Thanks. I tapped the error message and turned out it was image too large. So not a bug:D
Will this version include support for Apple’s translation API? I’d love to be able to read some of the posts that aren’t in my language.
We do plan to integrate the translation API, but it might come after we release 2.0 to the App Store—our primary focus right now is reaching feature parity with the v1 app so we can ship 2.0. That being said, we may build it into 2.0 before then as an excuse to play around with the new API.
I love the icons in settings! I’m hella dyslexic and seeing the individual settings in the long lists of words can be super hard but the icons give me really easy and intuitive touch points that I can scan for instead. Y’all are amazing!
The new comments search and embedded loops clips are massive!
The latest padding updates are great, but the addition of a gray background (on dark mode) has made reading unnecessarily more difficult due to the reduced contrast ratio.
Thanks for the feedback! We've received a couple requests for an oled/"blackout" theme--we'll have one out soon.
May I make a feature request for fediverse project developer flairs for those who are the officially behind Lemmy, Mastodon, Sublinks, Piefed.
We did consider this in the past, but decided against it. Implementing this would mean that we - the Mlem developers - would have to decide who gets the flair and who doesn't. As the development teams of those projects change over time, we'd have to keep up with ensuring their current developers are correctly flaired. This would take time that could be spent developing new features for Mlem instead. There are also many Fediverse projects, and we don't want people asking "why don't the [XYZ] developers have flairs?" if we start giving out flairs to only the developers of certain projects. I hope that makes sense :)
Thank you for the perspective. That is a good point raised.
The block options in feed do not work on ipad. You have to go to the community or user to perform the block.