Sjmarf

Nope; we haven’t got one yet. We hope to add one sometime in the future though.

That’s what I use in mlem.

Mlem dev here - we added a button for this to both the post editor and comment editor in our 1.3 update.

Post	Comment

Octopus-Accelerated Machine Learning

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.

Yep! We fixed this in a TestFlight patch on Monday. GitHub

Yep, this isn’t possible right now. We’re tracking the issue here, and I’ll try to get it working in the next major update 👍

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.

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

We’re focusing on building the best Lemmy client possible right now, and aren’t considering branching out to cover multiple platforms. If we do ever consider that, it’ll be in the far future once the client is properly polished. Lemmy themselves are discussing potential video support - if that’s implemented into Lemmy, we would of course try to support it.

Yep, this is planned!

Thank you for making Lemmy ❤️

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.

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

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.

I’ll look into the possibility of implementing this 👍

We have an update scheduled soon™️, and we’re bug-fixing that release at the moment. This is unlikely to be in that release, unfortunately.

I operate my own local instance that I use for testing, so we won’t need a test instance. Thanks for offering though :)

Yep, we don’t have this functionality just yet.

To clarify - you’d have to upload the image to your instance in the browser, not within Mlem’s post creator. Mlem doesn’t provide a way of copying the URL of an image you attach to a post. And if you never post the image you attached, Mlem will request that your instance deletes the image.

Not currently, no. We’re aware of this feature and are tracking it here.

Sure, I’ll add this 👍

We hope to have a new TestFlight release out in the next few weeks or so.

Update: This is in today’s TestFlight release, and will be in the App Store build in a week or so. You can find the option under Settings -> General.

deleted by creator

Hey there! We’re aware of this issue. This is related to a system that we implemented hastily to get 0.19.0 support working; we’re working on a more robust solution for the next update. If you see this error, going back to the communities list and re-entering the feed should fix the issue.