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-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.

  • Sjmarf@lemmy.ml
    link
    fedilink
    English
    arrow-up
    3
    ·
    2 months ago

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