this post was submitted on 16 Apr 2024
1 points (66.7% liked)

Arctic

361 readers
2 users here now

Arctic is a Lemmy client for iOS built on pure Swift. It currently supports iOS 15+ and Lemmy v0.17+

Get the latest version on TestFlight, or check it out on the AppStore.

If you would like to support Arctic’s development, feel free to Buy Me A Coffee

founded 1 year ago
MODERATORS
 

Direct messages in the inbox tab always show as ‘unread’ and there doesn’t seem to be a way to clear that. They also don’t show the name of the other person you’re messaging (seems to show my id instead). It would also be great to link to their profile so you can find their posts / comments easily.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 points 7 months ago (1 children)

So this is where I was expecting to see the other person’s name. And I’ve read / tapped on all the messages in this tbh read, but you can see the notification badge is stuck at the bottom:

screenshot

And yes, when I open that thread I see my messages on the right in blue.

[–] CreatureSurvive 1 points 7 months ago (1 children)

Okay, the mark read issue I can reproduce, the message is properly marked as read, turns out the issue is really dumb. It seems that messages you send yourself are marked as unread by default. It looks like I will have to either filter out self messages when checking unread status, or automatically mark them as read when sending them.

I can only assume this is the default behavior because the API allows you to message yourself. Either way, I’ll fix this in the next update.

[–] [email protected] 2 points 7 months ago (1 children)

Thanks for the message changers. 2 final bits I think—the profile image in the conversation list is still mine rather than the other persons, and when you open the thread the title is my name not theirs. But the menu and mark read stuff is all good :).

[–] CreatureSurvive 2 points 7 months ago

Dang, I though I caught it all in last nights update. I just fixed those issues this morning, and I’ll include that in the next update (probably tomorrow).