sjmarf

joined 2 years ago
[–] sjmarf@lemmy.ml 2 points 3 months ago* (last edited 2 months ago) (5 children)

A post is marked as read when you open, upvote, downvote, save, or reply to it. If you enable "mark read on scroll" it'll mark posts as read when you scroll past them. Posts that are marked as read will have a slightly dimmer title text.

I would maybe want some indication that there are hidden posts available to unhide.

Yeah, this is something we'd like to do. "Hide read" has proven to be a very common cause of confusion; we need to make it more obvious somehow.

[–] sjmarf@lemmy.ml 6 points 3 months ago (7 children)

Might you have "hide read" turned on? You can turn if off by tapping on the (...) button in the top-right of a community, then tapping "show read".

[–] sjmarf@lemmy.ml 3 points 3 months ago* (last edited 3 months ago)

~~Do you know where you installed the app from? Or, if you can post a screenshot of the app I can find out which one it is.~~

Edit: Ah, I see you've figured it out. :)

[–] sjmarf@lemmy.ml 1 points 3 months ago* (last edited 3 months ago)

Thanks! I've created an issue on our GitHub repo to keep track of this.

[–] sjmarf@lemmy.ml 2 points 3 months ago (2 children)

I've not seen this error before. Some guesses at what might be causing this: Maybe your report reason is too long? Or maybe it contains special characters? You could try changing your report reason to rule those out. If it's caused by one of these, let me know and we'll add a better error message for that eventuality.

If changing the report reason doesn't fix the issue, it would be helpful if you could message me a link to the content you're trying to report, if you're comfortable doing so. No worries if not, though :)

[–] sjmarf@lemmy.ml 3 points 3 months ago* (last edited 3 months ago) (1 children)

Mlem dev here. Mlem shows this warning for instances that require registration applications to be approved first (which, these days, is all instances).

The aim here was to make it clear to users that they won't be able to use their account immediately after signing up - otherwise, users may be confused that they can't log in. I do agree that it's a little scary though... we'll think about some ways to tone it down. I'm open to suggestions for better wording.

I wasn't aware that lemmy.world automated their process. It's possible that we could provide a different UI for certain instances that use similar systems, but we'd have to hard-code each case which isn't ideal.

The ability to sign up in Mlem was only added a month ago - before that, we directed users to the web browser to sign up. Our current implementation leaves much to be desired, but is more user-friendly than requiring the user to visit a website. I'm planning to make some improvements to the system in future. I was reading this Lemmy post the other day, which I think has some good ideas.

Here's an overview of our current sign-up flow, fyi:

Click to expand

When the user first opens the app, there is no full-screen onboarding flow. They are not asked to choose an instance - instead, they are connected as a guest to lemmy.world. This avoids scaring the user away with the concept of "instances" before they have the chance to see any content. Here's the first thing the user sees:

If the user taps "sign up", they are shown a list of instances ranked by their score on lemmyverse.net. This is one of the areas that I think needs the most improvement - we don't currently tell the user what an instance actually is, and the way that instances are sorted means that most users probably choose Lemmy.world, which isn't ideal.

And finally when the user taps on an instance they get shown the page you've already seen a screenshot of:

[–] sjmarf@lemmy.ml 5 points 3 months ago

That's a good idea - we'll see if we can get this fixed for the next TestFlight version 👍

[–] sjmarf@lemmy.ml 1 points 3 months ago

The only other thing I could think of is going to the way back machine and getting one of the earlier apps like Mlem or Memmy

Unfortunately, this is unlikely to work because lemm.ee is using a much newer Lemmy version than such versions would be designed for. Newer Lemmy versions introduced breaking changes that caused many older clients to stop working.

Tthe oldest iOS version that the oldest version of Mlem supports is iOS 16, and for Memmy I seem to remember that it's iOS 13 (though I can't find a reference to that right now). So I don't think either would be viable for OP. Arctic currently supports iOS 15 and later; I'm not familiar with whether it supported older versions in the past.

[–] sjmarf@lemmy.ml 5 points 3 months ago (1 children)

The Lemmy developers are implementing support for this in Lemmy 1.0 - we'll update Mlem to support that feature when Lemmy 1.0 releases. And yes, you're welcome to submit feature requests here :)

[–] sjmarf@lemmy.ml 5 points 3 months ago

Thanks for the kind words! We're glad you're enjoying Mlem. Love from... also the UK :)

[–] sjmarf@lemmy.ml 4 points 3 months ago (1 children)

Yeah, this would be nice to have! It looks feasible from a technical perspective, though we can't make any promises about how soon this will be implemented. We've got an issue open for this feature on GitHub here if you want to keep track of any progress we make :)

view more: ‹ prev next ›