Thanks for the bug report! We’ve already merged the mark read on scroll fix. The sound issue has proven a lot harder to track down, but we’re working on it.
Dev lead for Mlem, the iOS Lemmy client.
Thanks for the bug report! We’ve already merged the mark read on scroll fix. The sound issue has proven a lot harder to track down, but we’re working on it.
1.3.6 has just released to the App Store–it should resolve this issue.
Thanks for the feedback! We’ve received a couple requests for an oled/“blackout” theme–we’ll have one out soon.
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.
Thanks for the bug report! We’ll look into it.
Thanks for the bug report! Are you on Mlem 1.3 or the 2.0 beta?
To add a little more insight on the gifs side: video handling is the next major item I’m working on. In theory, the media framework we use should make gifs free once video handling is working, so hopefully they’ll be coming soon.
Thanks for the feature request! I’ve opened an issue to track it.
We don’t have a preference–we monitor both pretty actively so whatever is easiest.
Thanks for the bug report! It looks like this is due to the antique backend Beehaw is still running–we’ll have a compatibility patch out soon.
Thanks for the bug report! We’re working on it.
deleted by creator
deleted by creator
Thank you!
Haptic feedback settings aren’t in the current build, but we’ll have them in the next! That build should ship tomorrow.
Is there a way to preserve settings from the old version to the new?
Not right now. We’ve rewritten and reorganized the entire infrastructure that handles settings and configuration, and the new and old schemas are more or less alien. We’ve got an issue open to build a settings import/export tool which will allow things like easily migrating settings across platforms that should also make this possible.
Hmm, that’s strange. Have you tried manually opting out of testing (“Stop Testing” in the TestFlight app) and clicking the link again?
It’s looking like we’ll have the public 2.0 TestFlight launched within the next couple of weeks, though the error bars on that timeline are pretty wide because development speed is dependent on our free time. You can also check our roadmap post for a feature-by-feature list of what’s left; we’re expecting to merge a couple of the outstanding items in the next few days.
It looks like the biggest domain count driver by far is image fetching for link posts, since rendering a website preview involves fetching both the preview image from the linked website and the favicon from Google (favicons account for all those t1.gstatic
calls). Disabling website previews and the associated image fetching code cut the domain list down to just Lemmy instances. Mastodon appears to proxy image requests through the instance, which prevents that high domain count. Lemmy has recently added that feature, but right now only instances running the very latest Lemmy code perform image proxying.
We’re looking into adding enhanced privacy features to 2.0; we’ll include one to disable fetching favicons and image thumbnails, since favicons especially are a known tracking/fingerprinting vector.
Hmm, that’s interesting. I’m looking into it!
This issue should be fixed in the new 1.3.7 release.