Mlem 1.2 is ready for testing!

Major Features

  • Profile editor: you can now change your display name, biography, avatar and banner image, and matrix ID in Settings -> Account
  • Easy-tap links: links detected in posts and comments now get a nice big tappable button at the bottom of the post. You can copy and share these links via long-press on the link button.
  • Tab bar navigation: tapping the currently selected tab while at the top of the feed will navigate back. Reselecting the search tab from the top of the feed will focus the search bar.
  • Upgraded post composer: we’ve made the post composer prettier, added the ability to upload images from files and clipboard, and now shows the account you’re posting from. It also now displays a warning if your post runs afoul of your instance’s slur filter.
  • Instance page: you can now view detailed instance information, accessible from a community or profile via the ellipsis menu in the navigation bar
  • Saved content feed: saved content is now listed as a feed, rather than a sub-view of profile.

Minor Features

  • Voting icons are now colorized in compact mode
  • “Report” and “Block” items in context menus are now colored red and ask for confirmation
  • Fixed some inconsistent wording and incorrect capitalization
  • Improved performance of markdown rendering
  • Redesigned the account switcher and tweaked the behavior of long press/swipe up: long press on profile now swaps accounts immediately if you have two accounts and opens the switcher if you have more, while swipe up always opens the switcher. Both of these gestures can be enabled and disabled in Settings -> Accounts -> Quick Switcher
  • Added an indicator to posts from subscribed communities in All and Local feeds
  • Added headers to feed pages
  • Redesigned app icon selector
  • Added more app icons
  • Added a new comments indicator to posts you’ve already viewed
  • Added the option to open links in the system browser, rather than in-app
  • Added support for image links and shields.io badges
  • Added options for how your accounts are sorted in the account view and quick switcher
  • Tidied the settings page
  • Added the option to disable tap-to-collapse on comments
  • Refined the swipe action activation angle, so it should be harder to accidentally trigger it while scrolling
  • Added the option to require biometric unlocking when opening the app
  • Added the option to automatically collapse child comments
  • Redesigned the profile page

Bug Fixes

  • Disabled swipe actions on items embedded within the post/comment composer
  • Fixed a bug where favoriting a community from the ellipsis menu would cause the subscription status to display incorrectly
  • Fixed a bug where adding an account while already logged in would fail on instances running 0.19
  • Fixed a bug where account details were not being loaded in the user view
  • Fixed “failed to determine site version” error
  • Saved content now loads dynamically on scroll, rather than all at once

Update 2023-02-05: RC 1 Changes

  • Fixed an issue where interacting with items in the saved feed would crash the app
  • Fixed blocking communities from posts not working
  • Fixed “Show n replies” tap hitbox
  • Fixed “No items” message appearing briefly in Saved feed before content loads
  • Bubble picker now scrolls to the selected item on tap if it is partially offscreen
  • Fixed /u/user@instance and /c/community@instance links not behaving properly
  • Added options to adjust the behavior of easy-tap links in Settings -> General
  • Fixed sidebar navigation not working properly on iPad
  • Fixed the Saved feed not properly refreshing
  • Fixed comments of depth 1 not collapsing properly with auto collapse enabled

Cheers,

The Mlem Group

Mlem is a free and open source project. 100% of our funding, which pays for things like server time, comes from our generous donors; we do not, and will never, run ads or sell data. If you’d like to help support Mlem, you can donate here.

  • syd@lemy.lolEnglish
    12·
    10 months ago

    Hmmm, shouldn’t 3rd swipe to the right, collapse from top-level comment, instead of comment itself? Since we can already one tap to collapse comments.

    Anyways, really good update. There’s so much features I’ve needed. Thank you guys <3

    • Sjmarf@lemmy.mlEnglish
      8·
      10 months ago

      Thanks for the feedback!

      We are aware that swiping to collapse the top-level comment would be a useful feature and are tracking the issue here. The swipe action to collapse comments was added back in September, and isn’t a new feature in this release.

    • SideshowBoz@lemmy.worldEnglish
      6·
      10 months ago

      Good point 👀

      Really depends on how we want it to work, I always program in redundant interactions that perform the same task, since some people like to tap and others swipe

  • ainen@lemmy.mlEnglish
    9·
    10 months ago

    I’ve been looking forward to this update after seeing all the commits on GitHub. So far so good, the update feels and looks great!

  • kowcop@aussie.zoneEnglish
    7·
    10 months ago

    Thanks for the app, it is my first go… Is there any way to see a list of things that I have upvoted?

    • Eric@lemmy.mlOPMEnglish
      5·
      10 months ago

      Unfortunately the API doesn’t support that and it’s infeasible to do client-side, so not for now. They have an issue for it but it’s closed as not planned, though they’ll reopen it if anybody wants to work on it so hopefully we will be able to offer this feature in the future.

  • slin@feddit.deEnglish
    6·
    10 months ago

    Awesome update. The new comment highlighter is a cool feature, it would be useful if the new comments got highlighted when opening the post.

    Are there any plans to remember collapsed comments and keep them collapsed when visiting a post again?

    An optional setting to disable inline images in comments would be cool too, some images are really big and I get lost in the comment.

    • Eric@lemmy.mlOPMEnglish
      4·
      10 months ago

      Highlighting new comments is a good idea! I’ll have to take a look at what support there is API-side for it.

      We’d like to remember collapse state, though that one’s a little trickier technically–collapse state is client-side, so we have to do some caching tricks to make that work. We’re reworking our backend modeling for 1.3 to include, among other things, a caching system, so we’ll see if we can work that in.

      • Sjmarf@lemmy.mlEnglish
        5·
        10 months ago

        I looked into the possibility of highlighting new comments when I added the indicator, but unfortunately there isn’t a support for it API-side. So we’d have to do it locally.

      • slin@feddit.deEnglish
        3·
        9 months ago

        Thank you for your technical explanation. You all are doing amazing work.

  • nocturne@sopuli.xyzEnglish
    93·
    10 months ago

    Not really liking how large the new subscription/all/local bar is.

    I like how much higher it is on iPad.

    I realize there is more screen real estate on iPad, but the font is fairly large on iPhone compared to other elements.

    • Eric@lemmy.mlOPMEnglish
      11·
      10 months ago

      Unfortunately not–Mlem is written entirely in Swift and SwiftUI, which as of right now doesn’t work on Android.

    • syd@lemy.lolEnglish
      11·
      10 months ago

      Since they’re developing the app with latest iOS SDK, I don’t think it will ever come to Android.

  • Chef_Boyargee@lemmy.worldEnglish
    3·
    10 months ago

    When I unsave items (deselect the green flag) it doesn’t always remove those items from the view. Additionally, when I block some communities, the app still populates some posts from that community.

    Are my lists too big? Do I need to log out and log back in to refresh everything?

    • Eric@lemmy.mlOPMEnglish
      2·
      10 months ago

      Thanks for the bug reports! Looks like there’s an error in the refresh logic for save–posts should remain in the view when initially unsaved (to avoid losing them forever on accidental unsave), but should disappear when the view is refreshed (which does not appear to be happening).

      As far as community blocking goes, that’s mostly handled server-side–once you block a community, the app should filter posts from that community out of the currently displayed feed, and relies on the server-side block functionality to keep those posts from appearing in subsequent loads. We load in pages of ~50 posts, so if you block a community from, say, the profile page, it won’t update that over on the Feeds tab (yet, we’re looking at ways to implement that behavior but it’s fairly involved) and so you’ll still see those posts in the feed until the next load. In theory, simply refreshing the feed will clear them out because it’ll fetch the page fresh from the server.

    • Eric@lemmy.mlOPMEnglish
      9·
      10 months ago

      Hmm, that’s odd–App Store Connect reports 1.2 as live for all of our testing groups. It might just be a little slow to propagate the build out to all the servers.

  • DPearl42@sh.itjust.worksEnglish
    2·
    10 months ago

    When I click a link to a community ( for instance in the trending communities) it shows a loading message that then shows a couldn’t find object error. iPhone SE 2020 iOS 17.3

    • Sjmarf@lemmy.mlEnglish
      3·
      10 months ago

      Thanks for the report! I’ve fixed this, and it’ll be live on TestFlight in a few days 👍

  • dzaffaires@sh.itjust.worksEnglish
    2·
    10 months ago

    Question for MLEM users. I’ve seen comments where the message is or contains directly an embedded image. While replying with this app, I’ve tried pasting an app (on iOS), and can’t seem to find how to do this. Is this a feature that is currently supported?

    Thanks to the devs!

    • Sjmarf@lemmy.mlEnglish
      2·
      9 months ago

      This isn’t supported yet, unfortunately. We’re tracking the feature here, and will definitely be implementing it at some point in future.

      If you want to attach an image to a comment, you can use the ![](image url) markdown. If you haven’t got a URL for your image, you’d have to post the comment from your instance’s website (which allows image uploading).