Done.

Now when you tap the search tab while it’s already active, firstly it will scroll to the top of the results if it’s not already there, otherwise it will activate the search bar. If it is scrolled down, you can double tap to scroll to the top and activate the search bar. And just like before you can long press the search tab while it’s not selected and it will open the search view and activate the search bar.

I’ve found myself accidentally doing this and it not working, but I never got around to adding this feature until now.

I should hopefully have an update out soon, I have a lot of other fixes and some new features just about ready for a release.

This is a good idea, I’ll look into adding this. Unfortunately this is not supported by the API, but it should be simple enough to maintain a list of blocked posts in Arctic.

[edit] I see this is actually a native feature on Lemmy v0.19.4. I’ll add support for this in the next release. I just integrated this feature in Swimmy, (Arctic’s Lemmy API wrapper), I just need to update the UI to support this.

It’s definitely a useful feature. I’m still hoping that this is eventually added to Lemmy natively, as it would be more efficient, and accessible for more users. It makes for a good alternative to following topics such as on mastodon.

It sounds like I should probably find a way to make this feature more apparent though. As it is right now, the UI doesn’t really express that this feature is available unless you’ve already created a community group.

No problem! I had hoped to have API support updated before Lemmy 0.19.4 started deploying, but I missed the mark. I’ll push another update soon with support for the rest of the additions in 0.19.4, this seems to have been the only breaking change in this release.

This should be resolved now, I just updated to v0.4.1.11 on TestFlight, and submitted a new release to the AppStore review as well.

Please let me know if you are still having issues after updating, or if you encounter any other API issues with the latest Lemmy release.

Thanks for the heads up, this is due to API changes in Lemmy v0.19.4. I just fixed this and I’ll be rolling out an update today.

Thanks for letting me now about this! I fixed the issue today, and I’ll be releasing an update either tonight or tomorrow.

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.

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!

No problem, it shouldn’t have been dependent on the post style to begin with. I just wanted to confirm I had found the cause of the issue and was not overlooking something.