It’s intentional to not mark as read when tapping an unread comment. I often don’t have the time t9 respond right away and prefer to keep them unread until I do respond. I could definitely add a setting to enable this behavior though. As for the mark all issue. I’ll have to look into this, I believe I am not using the mark all Lemmy api for this and rather marking individual posts. I do this to allow more granular control over what is marked as read. I wanted to be able to only mark mentions as read if viewing the mentions section, etc. the mark all button in the root of the inbox tab would mark everything as read though.

Either way, it sounds like it is not working correctly, so I will look into this in the next update.

Thank you so much! I have definitely put a lot of work into Arctic in the last few months, I’m glad it shows and you’re enjoying it!

sepia colour scheme (like pale yellow for background and dark brown text and antique white text boxes; it’s much easier on the eye balls)

For this I am planning to add full theming support. Themes like Sepia, Dracula, Mint, Lemmy-UI etc I am planning to have presets for, but I’m also planning to add a theme editor so users can design and share their own themes. I unfortunately did not implement support for this earlier, so it will take some time to add full theme support as I now have hundreds of views to update.

favoriting of communities

I added support for favoriting communities in yesterdays update. If you have any feedback about the implementation, please let me know!

color options for upvote/downvote

This will be added in with the theming options

color options for comment cascades

There are settings to select different comment themes in Appearance Settings, but I’ll also be adding settings to add custom comment themes.

option to toggle between “hold jump button for previous comment” and “hold jump button to return to top”

I actually played with a similar feature yesterday where a double tap would jump to the top, but it added a delay to the single tap jump and made it feel laggy. I may take this suggestion and add a setting to toggle the behavior.

default Home/Instance/All option

There is actually a setting for this, however it behaves as Remember last selection I’ll add a setting to toggle between remember last, and always use default.

on feed, three button menu, “Hide Read Posts / Unhide Read Posts”

I’m planning to add this in, however it’s going to take a bit more work than one may think. Arctic does some aggressive caching for rendering feeds in order to improve performance. I need to update the caching system to support hiding content without corrupting the cache, otherwise the feed would need to be reloaded every time the toggle is switched.

Once again, thank you! I really appreciate the detailed feedback and I’m very glad you’re enjoying Arctic. I apologize for the late response, I’ve been very busy the last few weeks.

I did just notice that watcher notifications do not update the tab when launching the app from a notification. So if you are in the inbox section for example, and then open a notification, it will load the post in the posts tab, but not switch to that tab. Is this the issue you are having, or is it not loading the post at all?

As for showing watchers in the inbox tab, this is something I would like to do. Currently I do not keep any logs for watchers on the notification server, so it’s not something that could be queried from the server. Currently the only logging I do for watchers is tracking the total number of hits a watcher finds. I would prefer not to store more information than necessary. However I may be able to do this next n the users device when a notification in received by logging the post id.

I did attempt doing this by using the device Notification Center, but it’s a little counter intuitive since the notification is cleared as soon as the user taps it.

I will look into it and see what I can come up with. If nothing else, I could always log the post id on my server so that you can load the full history of a watcher in-app. The only real downside with any of these approaches is that Lemmy does not currently support queries for multiple posts, so I order to show a list of hits, it could mean hundreds of api calls which I’d prefer to avoid.

I have a back-log for some of your suggestions such as a favorite communities, so I may not get to this right away.

Anyways, congrats on the new AppStore milestone release!

Thanks! I haven’t had the chance to write a post about this yet. Hopefully later today!

It’s my pleasure, I’m glad you’re enjoying enjoying it!

Favorite communities: Will there be a possibility to have a list of your favorite communities before the list of all subscribed communities starts?

Yes, this was finally added in yesterday’s update. If you have any feedback about the implementation, please let me know.

Theme implementation / individualisation: are you planning to let the user choose between more Color schemes or even to individualise them completely? Some grey texts are hard to read while in light mode.

This is something that I have been planning to add for a while now. I’ve unfortunately been far too busy working on other features to start working on this yet. I do intend on adding support for themes instead of just tint color options. I’m also planning to add a theme editor, so users can create and share their own themes. This is going to take some time though. I didn’t plan for this early enough, and so I’ll have hundreds of views to update with support for these features.

I have a couple of high priority features/fixes that I need to address first, but I should be able to start on this soon.

This is not a bug. In Lemmy, crossposts are determined by the post URL. Any post using the same URL will be considered a crosspost. I’m not sure how, or if this is handled for text based posts. Personally I think these should be called ”related posts” and actual crossposts should be explicitly set as such.

I think it’s a Lemmy issue as opposed to an Arctic issue. The Thunder App shows the same thing for this post.