Welcome to the Mlem 2.0 Feedback Megathread! This is where we will be posting changelogs for the Weekly TestFlight (the Stable Pre-Release changelogs will get full posts), so check back here to see what’s new!
This is also the place to post feedback on the Weekly beta (or you can just open an issue on our GitHub if that’s your style).
Please be aware that this is an early beta build, may be missing features you consider essential. See the “Roadmap” section of our 2.0 release post for more details.
If you want to join our Weekly TestFlight group, you can do so here.
If you would rather join the Stable Pre-Release group, which receives curated, stable pre-release builds, you can do so here
2024-11-22
Features
- Added the ban action for moderators and admins
- Added the option to disable infinite loading (i.e., manually load each next page)
- Updated feed loading behavior. Loading performance should be improved when browsing with read posts hidden on feeds with many read posts, and some quirky behavior around refreshing and switching feeds should be resolved.
2024-11-15
Features
- Added the block list (Settings -> account)
- The post title and community is now displayed on comments in a user profile or in the inbox
2024-11-01
Features
- “Swipe anywhere to navigate” setting. Note that this cannot be active at the same time as swipe interactions.
- Compact posts now show saved status
2024-10-25
Features
- Moderated feed
- Fediseer integration (Trust & Safety tab in the instance view)
- Basic account settings
- Added code blocks to Markdown tools
- Added the option to confirm image uploads
Bug Fixes
- Fixed placeholders being shown in comment editor
- Fixed cache size readout not updating when cache is cleared
2024-10-18
Features
- Moderator action to remove content
- OLED theme
- Easy-tap links
- Autoplay animated media (iOS 18 only)
- Refined expanded post view
Bug Fixes
- Fixed not being able to import settings files not created by Mlem
2024-10-11
Features
- Search posts
- Updated search design
- Collapse post content
- Pin and lock
- Default Sidebar Visibility setting
2024-10-04
Features
- Added preliminary video support:
- .gif, .webp, .mp4, .m4v, and .mov media can now be played by tapping the play button; tapping elsewhere opens the media viewer.
- Currently the only controls are tap to play/stop.
- Planned features, roughly in order include:
- .gifv support
- Thumbnails for .mp4/.m4v/.mov/.gifv content
- Pausing
- Scrubbing
- Updated design to use rounded rectangles
- Added the ability to edit posts
- Added more Markdown buttons: inline link, code block, and user/community/instance links
- Added a new comments indicator
- Added instance uptime statistics
- Expanded post can now be refreshed
- Added sign up prompts for new users
- Expanded posts now show if they’ve been crossposted with links to the crossposts
- Added a page for rendering deeply nested comment threads. Navigating to a comment (e.g., from inbox) will open this page.
- Added the ability to create crossposts from the post share menu
Bug Fixes
- Fixed iPad confirmation dialog appearing in the wrong place
- Fixed iPad sidebar navigation
- Fixed Markdown blocks would sometimes being truncated
- Fixed mark read on scroll not respecting the setting
- Fixed an issue preventing swipe actions on the account list and subscription list views
- Fixed some crashes
2024-09-18
Features
- Improved mark-read-on-scroll behavior
- This feature is only available on devices running iOS 18. On iOS 17, the old behavior will be used.
- Added dark and tinted app icons for iOS 18
Bug Fixes
- Fixed an issue where swipe actions were interfering with scrolling on iOS 18
- Fixed an issue where image context menu actions would fail on certain instances using image proxies
2024-09-14
Features
- Added image uploads, both for image posts and inline in post/comment bodies
- Added compact comments
- Added sign up to onboarding flow
- Added a settings import/export system (Settings -> General -> Import/Export Settings)
- Added the ability to save the current settings state and restore to that snapshot
- Added the ability to export the current settings state as a JSON file
- Added the ability to import settings files
- Added settings migration from v1 (pending 1.3.5 release to App Store)
- Added image proxy failure handling. If your instance’s image proxy fails, you can now choose to manually bypass the proxy and load directly from the image host. This behavior is fully opt-in.
- Added sorting and filtering options to search
Bug Fixes
- Improved scroll-top-comment behavior
- Fixed an issue where the image viewer would open at extremely low resolution
- Fixed an issue where the comment editor sometimes wouldn’t submit the right text
2024-09-02
Features
- Added two new color themes: Solarized and Dracula
- Added the ability to include links and images in posts
- Significantly optimized image handling, resulting in a smoother feed (especially in the Tiled layout) and a more responsive image viewer
- Added a “new account” flair
Bug Fixes
- Fixed an issue where the image viewer would not work on instances using image proxying
- Fixed a compatibility issue with versions running Lemmy v0.18
2024-08-29
We got a ton of great feedback from our initial release, and have implemented a number of new features and bug fixes:
- Added mark read on scroll (Settings -> General)
- Added a default feed setting (Settings -> General)
- Added a setting to adjust haptic behavior (Settings -> General)
- Fixed the lock icon being the wrong color
We’ve got a lot more in the works, so if you commented yesterday with a bug or feature request that isn’t mentioned here, stay tuned! We expect to be releasing builds fairly rapidly over the next few days.
2024-08-28
This is the initial beta release. We’re still bringing 2.0 up to feature parity with 1.0–this build should have everything you need to browse and interact with Lemmy. Please note that post creation and moderation tools are not currently supported in the 2.0 build–post creation is in active development and moderator tools are a high-priority item, so if you want to join the beta but those are important to you, check back in a week or two!
We’ve also got some new features:
- Markdown support
- Tiled post layout
- Keep place on account switch (allows you to switch accounts without fully reloading the app)
- Guest accounts
- Color themes
Check out our 2.0 release post for more details on the new release.
I can’t seem to upvote or post? When I upvote I get the animation then it returns to the old number. Posts I just get Error.
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.
Thank you! Is GitHub issues or here a better place to report?
We don’t have a preference–we monitor both pretty actively so whatever is easiest.
Just installed and poked around a bit. So far so good! I like the new look and feel.
Search by post works great 🫡🫶💪
Now we just need search by comment. The only reason why I still have Voyager.
New comment counts are back! Thanks.
I also submitted a bug report on GitHub, Mlem is marking posts read on scroll even when that option is unchecked in settings.
As I am typing this it appears the unearthly loud sounds are fixed too. Again, thank you.I spoke too soon about the sound.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.
The sound issue has proven a lot harder to track down, but we’re working on it.
I wish I could help more. All I can do is help finding and reporting as best I can. It seems when you first open the app when it is fully closed the sound is normal, but when reopening it and it was running in the background the sound goes crazy.
Uploading a photo to any community fails with Error. Anyone getting this issue too?
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.
It was exactly it! Image too large, it says. Fingers crossed Mlem make this process easier in the 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?
Thanks. I tapped the error message and turned out it was image too large. So not a bug:D
Viewing cross posts is probably my favourite feature for 2.0 so far. It’s been a little over a week, and I can’t believe I used Lemmy without it!
We’re glad you like it 😄
It’s great to read up on more conversations!
Finally Mlem has link support!
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). 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.
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.
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.
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.
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.
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.
Sure 👍 Mlem v1 had this; we’ll be adding it back in
Loving the new look so far! One thing I immediately noticed though is while scrolling through my subscriptions via the letters on the right, the view starts breaking with a ton of random space.
Changing the sorting back and forth seems to fix the view, but rapidly scrolling back and forth will break it again.
Thanks for the bug report! We’ll look into it.
The latest beta update is great!
Will this version include support for Apple’s translation API? I’d love to be able to read some of the posts that aren’t in my language.
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.
I used to be a TestFlight tester but I got removed and all I can see now when clicking the join link is that I was removed from the program ):
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?
Can we get a back button on iPad? Also, 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. Thanks for all that you do for Lemmy.
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).
deleted by creator
May I make a feature request for fediverse project developer flairs for those who are the officially behind Lemmy, Mastodon, Sublinks, Piefed.
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 :)
Thank you for the perspective. That is a good point raised.
