sjmarf

Uploading images in comments will be in the next update, along with a fix for the inbox count bug! We're also working on a Mark Read on Scroll option, a Modlog page and support for moderator actions (which have all been highly requested features).

Unfortunately, full markdown support is rather tricky to do. We've done some deeper research into how we might implement this since the last time it was suggested; it's a large undertaking that would require some significant time input, but it should be possible. It's not something we're scoping for the upcoming update, but it's something we hope to dedicate time to further down the line.

Mlem dev here! We're still working on it - a PR is merged every couple of days on our GitHub. It's true that development isn't as active as it used to be in the height of the Reddit migration, which unfortunately leads to new features being announced less frequently, but that's to be expected. We're working towards another release sometime in the coming weeks.

If you noticed any bugs with Mlem and you'd like to report them, you can do so here and we'll look into it 👍

Side note: We don't currently have any plans to drop Lemmy 0.18 support. Supporting 0.18 isn't a major technical challenge for us at the moment, so we don't really have a reason to drop support for it.

Does this happen on every comment you post, or just some? I’m not able to reproduce this either yet, unfortunately.

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.

This would certainly be a useful feature. Unfortunately, Apple does not make their translation API available for us to use, so we'd have to use someone else's API instead. I haven't looked too deeply into potential options just yet, but have created an issue here to keep track of the suggestion 👍

The Saved feed has moved to the Feeds list, just below “All”, “Local” and “Subscribed”.

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 out of cmark.

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.