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-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
      link
      fedilink
      English
      arrow-up
      2
      ·
      2 days ago

      This is planned 👍 It may or may not be in 2.0; we’ll see.

  • darkfiremp3@beehaw.org
    link
    fedilink
    English
    arrow-up
    3
    ·
    14 days ago

    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.

    • EricOPM
      link
      fedilink
      English
      arrow-up
      4
      ·
      14 days ago

      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.

        • EricOPM
          link
          fedilink
          English
          arrow-up
          3
          ·
          13 days ago

          We don’t have a preference–we monitor both pretty actively so whatever is easiest.

  • nrab@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    3
    ·
    18 days ago

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

    • EricOPM
      link
      fedilink
      English
      arrow-up
      2
      ·
      18 days ago

      Hmm, that’s strange. Have you tried manually opting out of testing (“Stop Testing” in the TestFlight app) and clicking the link again?

  • TheRealCharlesEames@lemm.ee
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    18 days ago

    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.

    • Sjmarf
      link
      fedilink
      English
      arrow-up
      3
      ·
      16 days ago

      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 👍

    • nocturne@sopuli.xyz
      link
      fedilink
      English
      arrow-up
      2
      ·
      17 days ago

      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.

      • Sjmarf
        link
        fedilink
        English
        arrow-up
        3
        ·
        16 days ago

        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

  • slin@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    11 days ago

    This is so smooth, awesome.

    Will you bring back the “compact comments” setting in the future?

  • MsSprouts@vegantheoryclub.org
    link
    fedilink
    English
    arrow-up
    2
    ·
    12 days ago

    May I make a feature request for fediverse project developer flairs for those who are the officially behind Lemmy, Mastodon, Sublinks, Piefed.

    • Sjmarf
      link
      fedilink
      English
      arrow-up
      3
      ·
      11 days 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 :)

    • Sjmarf
      link
      fedilink
      English
      arrow-up
      2
      ·
      8 days ago

      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.

    • EricOPM
      link
      fedilink
      English
      arrow-up
      2
      ·
      10 days ago

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

  • nocturne@sopuli.xyz
    link
    fedilink
    English
    arrow-up
    1
    ·
    17 days ago

    The old bug of loud keyboard clicks is back. And now when I get a notification while Mlem is open my notifications are LOUD. I keep my ringer 2 up from off, but in Mlem (non-Mlem notifications coming in from any other app) are at about 2/3rd to 3/4th from max volume. But it appears if you turn the screen off and on again the loud keyboard clicks go away (still testing more).

    Random large blank spaces appear between posts when scrolling. It happens in subscribed and all. Sometimes scrolling past and back to it fixes it.

    Spoiler

    When editing a post, the text is all on a single line, it does not wrap at the screen edge.

    Spoiler

    Thank you for getting spoiler to work! And the markdown bar at the top of the keyboard is neat.

    While typing out this post the text window keeps going to the top. The cursor does not move, just the window itself.

    • Sjmarf
      link
      fedilink
      English
      arrow-up
      3
      ·
      16 days ago

      Thanks for the bug reports! We’ll look into it :)

      • nocturne@sopuli.xyz
        link
        fedilink
        English
        arrow-up
        2
        ·
        16 days ago

        Others I forgot:

        The new post button is greyed out and unusable (iPhone)

        Clicking on anything in the feed tray on iPad does nothing. I currently can only see all, saved, local, subscribed (from the menu at the top of the screen)

        The icon to open and close the feed tray on iPad is a very welcome addition. However in portrait it is covered by the feed and took me a while to realize I can swipe away.

        New comment numbers (the green +#) on posts is no longer appearing.

        • Sjmarf
          link
          fedilink
          English
          arrow-up
          2
          ·
          16 days ago

          Mlem 2.0 is missing a lot of features at the moment, which we’ll be re-adding before the final 2.0 release. You can find a full list in the “Roadmap” section on the 2.0 release post :)

          • nocturne@sopuli.xyz
            link
            fedilink
            English
            arrow-up
            1
            ·
            16 days ago

            I have read that list multiple times to ensure nothing I am reporting is on the list. If I reported something that was listed I do apologize for the double report.

  • egrets@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    7 days ago

    Very much looking forward to V2! I’ve had to switch to Voyager for working spoiler markdown – it’s also excellent, but I generally prefer Mlem.

    Cheeky questions while I’m here:

    1. Voyager also seems to handle GIFs in comments better, is that something on the cards for Mlem?
    2. Is there a plan to introduce swiping forward? I frequently accidentally swipe back to the community list and lose my place in the feed.
    • EricOPM
      link
      fedilink
      English
      arrow-up
      2
      ·
      7 days ago

      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.

    • Sjmarf
      link
      fedilink
      English
      arrow-up
      3
      ·
      edit-2
      7 days ago

      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.