Arctic v0.2.8 released on TestFlight yesterday. The biggest change in this version is updated support for Lemmy v0.19. I noticed d that several lemmy instances have already updated to v0.19 RC, so I wanted to get this release out as soon as possible.
I also finally added support for overriding the default system font size, and an option to open links in the default browser, or in reader mode.
I finally tracked down a long standing bug that would cause crashes for many users when exiting a post view, or shortly after doing so.
Coming up next in v0.2.9
In the next release I’ve added an all new Mod Zone for quick access to all your mod/admin tools. You can view all your reports, or mod-logs per community. I also added Admin support for managing new user applications.
You can now access your moderated communities in a new section on the subscriptions view, and you can also swipe to unsubscribe from communities.
I’m working on a few more QoL updates before rolling out the next release
v0.2.8 change-log
- Updated support for Lemmy v0.19 - Note: Not all of the new features are supported yet, though all of Arctic’s current features should be supported
- Added support for customizing the font size in Arctic
- Added the instance Lemmy version to the sidebar
- Added link options: - Open in default browser - Open in reader mode
- Added support for editing Community Watchers
- Added a new App Icon
- Fixed issue where the community selector search did not respect the sorting mode
- Fixed Lemmy Explorer failing to load communities
- Fixed issue where the application badge would not update immediately after changing notification settings
- Fixed an issue with image loading that could cause a crash when exiting a post view
- Updated post composer to pre-select the open community when using the long-press gesture
- Updated in-app Safari to use Arctic’s tint color
- Updated Arctic’s theme support
Arctic Push Notifications
- Added support for updating community notification
- Added support for notification sounds
- Added support for running on a local machine for debugging
- Added support for sending local-urls in notifications
- Added collapse identifiers to notifications, in the off chance a duplicate notification is sent, it will be collapsed with the previous one
- Fixed incorrect parsing of dates in community notifications
- Fixed an issue that would cause registration application notifications to send repeatedly until they were all approved
- Updated badge notifications to update less frequently, and improve reliability
- Updated support for Lemmy v0.19
- Updated the format of sent notifications to improve client-side parsing support
Links
- Website: getarctic.app
- TestFlight: testflight.apple.com
Awesome, thanks for adding reader mode and font size setting!
Notifications work well, but I noticed that tapping on arctic notifications opens the post in the in-app-browser inside arctic.
My pleasure!
This is more of a core issue in Arctic at the moment. When handling a lemmy url that is not on the same instance as the current account, it will be redirected to the browser. When opening a notification, Arctic should automatically switch to the account that the notification was sent to, but there is no guarantee that the link will be local to that instance. I had tested out using Lemmy’s search api to federate the content and retrieve the local URL, but it seems unreliable. I’m looking into how to better handle the issue, but honestly it has not been a high priority yet, and I haven’t spent much time on it. I’ll see if I can revisit this issue for the upcoming release.
This is definitely something that Biggs me as well, especially when I’m just browsing and I tap a link that opens the browser.
Thanks for the feedback, I’ll see if I can figure something out this evening.
[edit] I believe I found a solution to this, it won’t be 100% reliable in cases where the target instance is blocked by your instance. In those cases it will fallback to opening in the browser. Additionally, you may not be able to see the all comments when opening a comment or post link due to how federation works.
I’ll work on adding a view as guest, where you can view content on its home instance and federate the content you interact with. This will take some time to implement as it is somewhat of a major change.
I managed to get this working finally. Arctic now resolves post and comment URLs on the active instance. So far, this seems reliable in my testing. There are instances of dead links, and blocked instances where resolving fails, and it will take some time to add support for viewing as guest on the home instance. For now those cases fallback to opening in the browser.
Sounds awesome!