Hey! In Mlem v1 there’s a setting for this at General > Confirm Image Uploads. We haven’t added this to the beta version yet but will be doing so.
Hi! I’m a developer for the Mlem iOS client. Join us on !mlemapp@lemmy.ml!
Hey! In Mlem v1 there’s a setting for this at General > Confirm Image Uploads. We haven’t added this to the beta version yet but will be doing so.
We’re glad you like it 😄
It should be back now on the weekly TestFlight :)
Yes, we’ll be adding it back in at some point 👍
I’m glad you like it :) Yes, we’re re-doing almost all of the code from scratch. It’s a lot of work but we’re getting there!
Eric’s posted the links :) Worth noting is that Mlem v2 doesn’t yet support mod/admin stuff, so if you use Mlem for administration duties you may want to consider waiting until the full release.
Sure, we’ll add an option for this in Mlem 2.0. We’re glad you’re enjoying Mlem 😄
I’m glad you’re enjoying Mlem :)
Hey! We haven’t implemented post searching yet, though we’ll be implementing it in the next version of Mlem (2.0).
To block an instance, you need to go to the instance page. You can do this by searching for the instance in the “Search” tab, or by tapping the (…)
button in the top-right of a community page or profile page and tapping the instance name. In the instance page, you can tap the (…)
button in the top-right and then choose “block” to block the instance.
To view blocked instances go to the Settings tab, then tap the button at the top of the page (your username), then tap “Blocklist”.
I should mention that I can’t get the new Testflight to work either. I use the old version, the Testflight for some reason is unavailable to me. Is it perhaps because I use an older model iPhone?
We closed the old TestFlight, as we don’t plan to release any major updates to Mlem v1 aside from critical bug fixes. The new TestFlight is for testing the upcoming Mlem v2, and requires iOS 17 or later. Mlem v1 supported iOS 16 and above. You can read more about our reasons for dropping iOS 16 support here.
Similarly, I sometimes don’t see comments, eg. a post might have 5 comments but I only see 3 or none.
Yeah, this happens because the Lemmy API only returns a limited number of comments initially for large comment threads. It’s the client’s responsibility to request more comments when needed. On the Lemmy website UI, you have to click a “Load (x) more comments” button, and it’ll load the rest. Mlem v1 (and presumably Voyager) haven’t implemented this yet. We’re planning to add it to Mlem v2.
We’re glad you like it 😄
Thanks for the report 👍 We’re tracking the issue here and will look into fixing it.
Thanks for the info. I’ll open an issue and try to reproduce it 👍
Version 2.0 isn’t out yet, but we’ve got beta versions available in the pinned post here. nocturne is correct - we don’t plan to release any more updates to the v1 version of the app unless Lemmy makes breaking changes to the API before v2 is ready.
I can’t reproduce this issue at the moment; it seems to be working fine for me on an iOS 18 iPad simulator. Which part of it doesn’t work - do the “Block Community” and “Block user” buttons not show up, or do they show up but not do anything when tapped? Thanks
Edit: it also seems to work correctly on iOS 17.5
Yeah, we’d love to have this but it’s unfortunately very difficult to implement so is unlikely to happen anytime soon. We’re tracking the issue here.
This is planned 👍 It may or may not be in 2.0; we’ll see.
I’m glad you’re looking forward to v2!
Voyager also seems to handle GIFs in comments better, is that something on the cards for Mlem?
It’s something we’d like to add at some point; we’re tracking the issue here. It may end up being in 2.0 or may not be.
Is there a plan to introduce swiping forward? I frequently accidentally swipe back to the community list and lose my place in the feed.
We’d love to have this feature but it is annoyingly very difficult to implement. The framework we’re using doesn’t natively support this, and neither does the framework that framework is built on. Apollo had this, but the code is of course closed-source so we can’t get any insight into how they did it. We’re tracking the issue here.
Are you using the beta or the App Store build?
Thanks for the info. That’s not the intended behavior; we’ll make sure it works properly in Mlem v2. Sorry about that!