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!

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

TL;DR: Mlem v1 is not fast; Mlem 2.0 (announcements coming soon!) will be.

We’re aware of a number of performance issues with the current codebase, which all together result in the app not behaving as responsively as we’d like. Unfortunately these are largely due to design choices made during the hectic sprint to App Store release last summer, and so are infeasible to fix without rewriting the app from the ground up—which is why that’s precisely what we’re doing. Our 2.0 build should be significantly faster; we’ll have some announcements about that in the near future.

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.

Thanks for the bug report, we’re looking into it!

This is not possible in the current version, but our 2.0 rewrite gives us the level of granular color control required to effectively implement such a feature, so we’ll be sure to include it when that ships.