Hi! I’m a developer for the Mlem iOS client. Join us on [email protected]!

  • 0 Posts
  • 45 Comments
Joined 11 months ago
cake
Cake day: October 5th, 2023

help-circle


  • Sjmarf@lemmy.mltoMlem for Lemmy@lemmy.mlQuestion on UI
    link
    fedilink
    English
    arrow-up
    7
    ·
    24 days ago

    There isn’t a way to do this at the moment. Apollo had this feature, and we’ve been keeping track of the idea here. Unfortunately, this is tricky to implement because of limitations imposed by Apple’s frameworks. It’s certainly possible, but would take some time to work out and isn’t on our immediate agenda.




  • We’re making several quality-of-life tweaks to the iPad layout in 2.0! So far, we’ve made the image viewer full-screen and updated the sidebar to look a bit more modern. Here’s a sneak peek:

    There’s also a setting for a more compact sidebar layout, if you prefer that:

    (This is all WIP, it might change. Ignore the lack of All/Local/Subscribed buttons, those will be back in before the first TestFlight).

    We’re also adding a setting that displays posts in a grid with two or more columns, which will make the posts look less wide in this format.

    Longer-term we’re considering some ways that we can improve the iPad layout as a whole - such as having a three-column layout - but there’s some navigation problems to work out and we can’t promise that anything like that will be in 2.0.






  • Sjmarf@lemmy.mltoMlem for Lemmy@lemmy.mlComment chains not appearing.
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    2 months ago

    Yep, this is a known issue. When a comment chain gets too long, Lemmy doesn’t send all of the comments in the initial API response. When this happens, the web UI displays a “show n more replies” button that can be tapped to load the remaining comments:

    We just haven’t got around to adding this button to Mlem yet, but it’s something we will certainly look into in future. We’re tracking the issue here.

    Sorry I didn’t see your comment until now; your post didn’t federate to lemmy.ml properly for some reason so I only just saw it whilst using my alt account.




  • Sjmarf@lemmy.mltoMlem for Lemmy@lemmy.mlIssue with login in Mlem
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    3 months ago

    Hey there! We’re sorry this isn’t working for you. Just to be clear, you should be typing “lemm.ee” in the “Instance” field and “chimera” in the “username” field.

    If that doesn’t work, there’s unfortunately something wrong with our login system. I’m currently unable to find the root cause - I’ve tried creating an account on lemm.ee, and am able to login without any problems. I’ve created an issue on our GitHub repository here and will let you know if we make any progress.


  • Sjmarf@lemmy.mltoMlem for Lemmy@lemmy.ml"Hot" Filter Bad?
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    3 months ago

    Hey there! Mlem doesn’t control the way that posts are sorted when using the “Hot” sort mode - that’s something that Lemmy does. The mechanism of the “Hot” sorting algorithm is described in detail here.

    You may prefer to use one of the “Top of…” sort modes instead, if you’d like to see more popular posts. In Mlem, you can change the default sort mode under Settings -> Sorting -> Posts.


  • Sjmarf@lemmy.mltoMlem for Lemmy@lemmy.mlHomescreen widgets?
    link
    fedilink
    English
    arrow-up
    6
    ·
    4 months ago

    Adding widgets is something we’re interested in; we’re keeping track of the feature here. Right now, it’s not high on our priority list as it doesn’t directly impact the core functionality of the app. Therefore, it’s unlikely to happen in the next few updates, though we do plan to explore it in future.




  • We’re aware of a bug in which Mlem sometimes crashes when moving into the background on iPad when “Lock with Face ID” is on. Do you have that setting enabled? We’ve looked into that issue and now know why it happens, but it’s unfortunately rather tricky to fix with our current architecture. In the next major update we’re rewriting a large part of our codebase, which should allow us to fix this.