The request for this post isn’t specific to a difference found in the TestFlight version, but rather an adjustment that I think may be useful.
Being an avid user of the block list system to keep my All feed manageable, I’m glad that the functionality is well integrated into Arctic. Although most users’ block lists are likely short enough to make a search bar for them unnecessary, lists beyond several hundred entries become more difficult to search. Although at present I accomplish this by going to my user settings page in Safari and using the keyword search tool, an in-app solution would be helpful.
As I sometimes want to review a community’s posts before deciding whether or not to remove it from my blocklist, the ability to tap on an entry (user or community) to view its page would also be helpful. The end user could then choose to disable the block from there via the existing UI should they wish to review the content of recent posts, before deciding whether or not to reinstate the block.
I pushed an update last night that adds support for searching block lists and browsing blocked content. For now I just allow opening the content in the browser, but as I roll out the new API integration I’ll add support for opening the content in-app. I also made a few other minor improvements such as icons for the blocked lists, and counts to show the total blocked for each category.
Great ideas! Searchable block lists should be very simple to add. Actually I thought I had already added support for this, but I was mistaken.
For viewing blocked content on the other hand, this will take a bit more work. Lemmy does not return any content for users or communities that are blocked, so I’ll need to add support for viewing them as a guest. I’ll have to look into this one, as currently Arctic is not setup for viewing individual pages as an unauthenticated user. In the meantime for a quick release I could allow opening the communities and profiles in the browser.
I’m in the process of rewriting Arctics API library for Lemmy v1.0 support. This is a major, ground up rewrite, and I’ll add more granular support for unauthenticated requests.
[edit] I could also temporarily disable the block while viewing the blocked content, and re-enable it when leaving. I can look into this as well.
