2.0 Beta Megathread

Now we just need search by comment. The only reason why I still have Voyager.

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.

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.

We're glad you like it 😄

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 👍

I agree about the padding between posts, and if the diving line could be enlarged (or the size set by the user) that would help too.

Also if more room could be added after the bottom response in a thread. Currently the up/down vote and reply buttons are so close to the nav bar at the bottom I click the nav bar by mistake sometimes.

Thanks for the bug report! We'll look into it.

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.

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?

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.

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?

Thanks for the feedback! We've received a couple requests for an oled/"blackout" theme--we'll have one out soon.

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 :)

Yep, it'll be back :)

Thanks for the feature request! I've opened an issue to track it.

We shut down the old TestFlight for Mlem v1, which you can read about here. You can find links to join the new TestFlight in this post.

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

Can we get a back button on iPad?

I'm not sure what you mean by this. Could you elaborate please? There is a back button at the top of the screen here:

I tried to get used to the glow around sections in the OLED theme, but it’s just distracting and frankly ugly. I’m requesting an improvement here as well.

Yeah, we aren't happy with it either. Unfortunately adding a border to those elements isn't simple to do - Apple really doesn't want us changing the appearance of forms. We'll try to come up with a better solution before 2.0 release (no promises though).

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.

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 bug reports! We'll look into it :)