Sjmarf

This would be possible to implement for PieFed, but not for Lemmy. It will become possible in Lemmy 1.0, though. Thanks for the suggestion - I’ve opened an issue on our GitHub to track this :)

Nice, I’m glad you sorted it :)

Thanks for the bug report. It looks like your username or password might be incorrect?

Mlem currently displays “something went wrong” when you get the password wrong for a PieFed instance. This is a bug - for a Lemmy instance, it shows “password is incorrect”. I’ve opened an issue to track this bug: https://github.com/mlemgroup/mlem/issues/2599

Thank you for the feedback, this is really helpful. I’ve created issues to track these feature requests and will let you know if we make any progress.

• https://github.com/mlemgroup/mlem/issues/2573
• https://github.com/mlemgroup/mlem/issues/1718
• https://github.com/mlemgroup/mlem/issues/2574
• https://github.com/mlemgroup/mlem/issues/2575
• https://github.com/mlemgroup/mlem/issues/2576

Unfortunately, there isn’t :( Lemmy is returning an error message back to us, so we can’t look any deeper without having access to the server logs. Usually a 400 status indicates that we’re sending the request wrong.

Having an exact post/comment and report reason that this error occurs with would be helpful, though I understand you might not want to share that information.

Thanks. Is your report reason quite long? There’s a maximum limit of 200 characters, it seems. If that’s not it, I’ve got no idea what’s causing this :(

Thank you, we’ll look into this. Are you on the TestFlight or the App Store version?

Hi, thanks for letting us know. Unfortunately I can’t reproduce this issue at the moment; reporting works for me :(

Next time you see this issue, could you please tap on the error popup and copy-paste the error message here? You can also go to Settings -> Developer -> Error Log to see all errors since the app was opened.

If there was a readAt date for the post, we’d be able to highlight comments created since that date. I don’t think tracking a readAt date is much less private than tracking a read boolean, which you’re already doing. It could always be made opt-out, if people are concerned about it. Having the date that someone read a post isn’t as exploitable as the link click tracking you mention, I don’t think.

Thanks for the info :) Lemmy 1.0 tracks a readAt timestamp; maybe it’s worth looking at how they’re doing it.

Currently, we are missing API support for this. Lemmy 1.0 (the upcoming version of Lemmy) includes this feature, so we’ll add support for it when Lemmy 1.0 is released :)

We could do, but ideally it would be implemented on the backend - some people use PieFed on both mobile and desktop, and storing the last read count locally wouldn’t carry over properly between clients. Lemmy 1.0 has backend support for this feature.

We accept bug reports and feature requests both here and on GitHub :)

If you already have a GitHub account, creating issues there is easier for us, but it really doesn’t matter too much. We also have a Matrix chat.

This looks like a backend issue again - the sh.itjust.works website is failing to load past the first page, too.

You can block instances within Mlem from the menu in the top-right of the instance page.

We require searching by comment to support listing_type=Local in order to support instance filtering (this PieFed issue). I see you’ve just added support for that, so we’ll re-enable the feature for the upcoming PieFed version release. Thanks :)

Mlem implements filtering by instance by sending a request with listing_type=Local to whichever instance you filter by. This shows comments made in communities on that instance. The Lemmy API does not have a way to filter by a specific non-local instance.

This is a feature in Lemmy 1.0 (the upcoming version of Lemmy). I’m not aware of any apps that implement it as a client-side-only feature.

There is no button for this, and unfortunately this would be tricky to implement. If you want to only see posts made recently, you could consider sorting by “top”.

At the moment this is technically infeasible, and this is unlikely to change anytime soon. If it becomes possible in the future, we will consider it.

On Mlem, long-press on a post then tap “Share…” -> “Crosspost”