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

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

help-circle

  • 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.mlHomescreen widgets?
    link
    fedilink
    English
    arrow-up
    0
    ·
    2 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.




  • Hey there! We’re aware that the comment-collapse animation is a little jarring; this is something we want to improve in future.

    You can simplify the animations used when switching pages and when opening the image viewer by going into System Settings -> Accessibility -> Per-App Settings (right at the bottom) and enabling “Reduce Motion” and “Prefer cross-fade transitions” for Mlem.

    Disabling the comment-collapsing animation isn’t yet possible. I’ve opened an issue for this on our GitHub, and will look into disabling it when “Reduce Motion” is enabled 👍


  • Yep, that’s another way it could be done. We’re hoping to add a text-selecting popup in the next major update, which will make this possible. However, it’s not quite as seamless as having a dedicated “Translate” button that replaces the post/comment content inline, which I’d prefer to use if implementing it proves to be feasible.





  • Mlem is an open-source project developed by unpaid volunteers. Anyone is welcome to start or stop contributing to Mlem at any time.

    The number of people in our development team is the number of people who are passionate enough about the project to spend their free time working on it. We don’t control that number, and we certainly can’t just “expand our dev team” like a company can by employing more developers.

    The “crunch” you refer to was during the large influx of users migrating from Reddit. During that time more people (including myself) became interested in the project, and naturally a subset of those people were interested in developing for it. The development team grew because of the increased interest towards the project, not just because we wanted to expand it.

    If someone wants to contribute a custom low-level markdown renderer to the project, they’re more than welcome to.


  • We have a very small developer team working in our free time, and none of us have any prior knowledge in the area of low-level markdown extensions. It’s very complex, and we’d probably never leave beta if making a perfect markdown renderer was on our requirement list, so we omitted it. It might be possible to work out given enough time, but that’s time that we chose to invest in other areas instead.

    If you know of any other non-web apps (iOS or Android) that are able to correctly render all of Lemmy’s markdown, let us know. We may be able to learn from/use their implementation, depending on the license it’s distributed under. I haven’t seen any Lemmy clients that can do this yet.


  • Spoilers, subscripts and superscripts don’t work, but everything else does.

    Markdown in general is unfortunately rather difficult to render. We use an open-source treesitter that parses GitHub-flavored markdown, which is similar to Lemmy’s markdown. Fully supporting the Lemmy markdown specification (spoilers, for example) would probably require us to instead use a custom implementation built directly ontop of cmark.


  • Sjmarf@lemmy.mltoMlem for Lemmy@lemmy.mliPad bugs in mlem ver. 0.1.2
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    5 months ago

    Both saved posts and saved comments are mixed in together in the “Saved” feed. This is how it worked previously when the “Saved” feed was in the profile, too. If this isn’t working properly and you don’t see your saved comments in the “Saved” feed, let us know.

    In future, we’d obviously like to add more granularity here, such as being able to filter the saved feed by just posts or comments, or sorting the saved feed.




  • This isn’t supported by Lemmy yet. It would be relatively easy to let our users follow other users on the client-side, and show your followed users on the subscriptions page. However, as this isn’t supported by Lemmy, your followed users unfortunately wouldn’t sync with the web app or other clients.

    It would get a little more tricky to show notifications when a user posts, or create a “followed” feed that only shows posts from users you follow. To do either of these, we’d have to make a separate API request for each user that you follow. If you follow a large number of users, this could be problematic.

    One potential way to mitigate this would be to have a separate “send notifications” option for followed users, and we’d only allow you to enable this setting for ~5 users.

    I think this is a cool idea. Following users isn’t on our immediate roadmap, but it’s something we could look into in future.