If you want to keep using Mlem while the TestFlight is down, you can just download it from the App Store--the current release build is identical to the TestFlight, and should keep all your preferences.
Should be pretty straightforward, we'll look into it for 2.0
Sure! One of the big things we’re reworking for 2.0 is how we handle accounts, which includes changing the format of how we persist account information. The compatibility changes in this build add extra decoding logic to the account persistence system so that both v1 and v2 can load a saved account regardless of which version saved it.
Hmm, that's odd--App Store Connect reports 1.2 as live for all of our testing groups. It might just be a little slow to propagate the build out to all the servers.
We've been working on it. A simple tap to jump to the top is pretty easy--things get tricky when you start adding complications like "jump back into the feed" or "navigate up a level," which require a more sophisticated architecture from the ground up. It is in active development, though, so we hope to have a prototype out soon enough.
Thank you! It means a ton to us.
Posts are marked as read when you interact with them (vote/save/reply/etc) or tap them to view the comments.
We have an issue open for marking read on scroll. The trouble with that feature is that the API only supports marking a single post as read at a time, so we either have to fake it locally or spam the API. The former is problematic because it either introduces what amounts to a memory leak as we track every read post or results in posts being displayed as read and then popping back up when the cache evicts that info. The latter is obviously unacceptable and constitutes extremely poor API citizenship.
We're currently working with the Lemmy devs to get a batch mark read endpoint, which will let us implement this feature without either of those problems.
The App Store requirements are extremely clear that if you have an option to create an account in-app, you need to also offer the option to delete it. According to our app reviewer (and, I reluctantly admit, the text of the requirements), even just linking to a sign-up site like join-lemmy is sufficient to require in-app deletion.
Gone but not forgotten! I can read all the deleted posts with my Mod Powers, and I've made sure to go through and catalog all the feature requests. IIRC yours was customizing swipe actions--we've got that scheduled for 1.2, though it's too far out to give a precise timeline.
The app was originally created as a solo project. When Lemmy suddenly took off, the founder started looking for devs to help out, and several of us showed up; for personal reasons, the founder chose to back out shortly thereafter. The dev team has remained largely consistent since then, though we've gained a couple new contributors.
Are you on iOS 18? There is a known issue where swipe gestures and scroll gestures conflict on iOS 18, which causes the behavior you describe. We have a fix currently in app review that should be live shortly.