Hmm, that’s a new one! Mlem’s audio is supposed to mix with other apps rather than stealing the audio session. Does this only happen with airplay, or do you also encounter it when using built-in or bluetooth audio output?

This looks like a sh.itjust.works issue—users are reporting the same behavior across multiple platforms.

Does this happen on all instances for you, or just sjw?

Not yet, but it will soon! We’re currently wrapping up our 2.2 build, which focuses on PieFed support. Once that releases we’re moving on to iOS26 support, which will include a design update to integrate Apple’s new design language.

Thanks for the bug report! We’re looking into it.

Thanks for the bug report! We’re looking into it.

Mlem is written in Swift using SwiftUI, which is not currently supported on Android. We’ve been keeping tabs on several promising projects to support cross-platform SwiftUI development, but none of them are mature enough yet for us to bring Mlem to Android.

Thanks for bringing that to our attention, we’ll look into cleaning that up

Not yet, but we’re planning to get that functionality in for the upcoming release. Currently the only way to get to a PieFed instance page is by navigating from the profile or community information of a PieFed entity.

Thanks! That does look like a server error—generally 504 is a gateway issue. I suggest bringing it up with your admins.

Could you provide us with the specific error message that occurs when this happens? You can view it by tapping the error popup or in the error log (Settings -> Advanced -> Developer -> Error Log).

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

Do you have compact comments enabled? The interaction bar is hidden in compact comments.

Thanks for the suggestion!

We try to only deprecate support once a version is basically unused—beehaw was the only major instance still on 0.18, so we maintained support until they recently upgraded. There are still a few personal instances running 0.18, but that’s an extremely small fraction of the user base.

We have an issue open to handle those cases—we’ll take your thoughts into account!

Thanks for the bug report! We’ll look into it

This happens when there isn’t enough room on the interaction bar—we have some common sense limits on how many items can be added to the bar to try to prevent this, but the emphasis on customization means that we can’t always account for every configuration and screen size. Handling this overflow elegantly is still an active topic in our design conversation.

Thank you!

@[email protected] deserves equal credit :)

I’ve created an issue to track this. I haven’t looked deeply into the technical feasibility–SwiftUI has some powerful tools for reversing layouts to accommodate languages that scan right-to-left, but I can’t promise this is a feature we can deliver without doing a bit more research.

We haven’t changed anything, but it’s possible your instance admins have made some configuration changes–there are some configuration settings that can mess with image proxying. The Voyager dev brought attention to this last week, plus put up a nice page about it–it’s possible that the sopuli admins fixed their config in response to that.

We’re also on the App Store, but every App Store release goes through TestFlight first.

This is correct. The GitHub releases feature doesn’t make a lot of sense for Mlem, since we primarily deliver through the App Store rather than via source downloads.