This is something I’ve noticed, and it’s been a headache to debug. It never crashes while I am looking into the issue, and the a few days later I’ll get a crash.

I’ve managed to narrow down where the crash occurred, but have not been able to reproduce it well enough to test solutions. I’ll see about looking into this further for the next release. It’s been a little while now since I researched this.

I think I found the cause of this and patched it yesterday. I’ll do some more testing, and if all goes well, I’ll release an update tonight to resolve this.

I noticed that as well. Unfortunately the extension needs its current permissions to open the URL in Arctic. I could monitor the URL without code injection, but there is no way to open the url without code injection. I wish apple would allow showing native views or alerts without needing to inject code as that would be perfect for this situation.

There is not exactly a good place to add a description explaining the access permissions. If I add it in the extension popup, it would only show after allowing it to run. Alternatively, I can add a more detailed description in the settings page, but the user will have to manually go to the settings page to see the description. It would be nice if I could add info to the alert like with photos access, but that is not possible with extensions.

Alas, I’ll add some information about this somewhere.

Alright, I’ve made some progress and believe I’ve finally resolved the issue. It turned out that my previous approach to checking for movement using tap gestures was only detecting movement after the gesture had already been recognized. I’ve updated the code accordingly, and I’ve been spamming pan gestures for the past day without any issues. So far, I haven’t noticed a single instance of the controls showing up.

As an additional layer of security, I might consider disabling the gesture while the user is zoomed, unless the tap occurs within the image margins, where the pan gesture is already not recognized.

I definitely appreciate your concern. This warning does seem excessive, considering the extension’s limited functionality, which only allows opening URLs in Arctic. This is Apple being thorough and transparent about the capabilities of Safari extensions.

Safari extensions are written in JavaScript, which is injected into the webpage. Injecting code into a website theoretically enables the theft of information entered on that website.

Open In Arctic performs several tasks:

1. It monitors URL changes.
2. It checks if the URL matches a regular expression for a Lemmy post, comment, user, or community.
3. It verifies that the server responds to Lemmy API endpoints.
4. It opens the URL in Arctic or displays a banner on the webpage with an “Open” button.

Unfortunately, I cannot hard-code the sites on which the extension operates due to Lemmy’s defederated nature. Therefore, it is up to the user to restrict which pages the extension can access. Regrettably, this means that the warning will be displayed frequently unless the user allows the extension access to all sites.

As an alternative, you can disable the Safari extension and use the “Open In Arctic” action from the share menu. The Safari extension is solely for convenience.

Absolutely, I’ll see about adding this tomorrow. I’ve been putting off integrating the hide post functionality of Lemmy because viewing hidden posts is somewhat broken. However, they added the ability to show hidden posts in feeds in a recent update so that shouldn’t be an issue anymore.

My pleasure, thanks again for the suggestion!

I included a new swipe action to Collapse Thread in last nights update. This will collapse to the root comment on any nested comment, or behave as the standard collapse action on a root level comment.

No problem! The update is out now, please let me know if you still have any issues.

Sorry for the late response, I somehow overlooked your post. I’m really glad you’re enjoying Arctic though!

This idea is really cool! It’s a fresh take on hiding read posts. Instead, it’s like a ‘While you were away’ feed for communities. This should be possible, but I’ll need to think about how I’ll go about implementing it.

Thanks for the suggestion! I’ll give it a closer look on my next day off.

No problem, always a pleasure!

Alright, I managed to resolve this. Now small pans will not trigger the controls to appear. I should be releasing an update tonight that will include these fixes.

This looks fantastic! I’d love to include this as a default theme option when you complete the light mode variant. However, I’ll need to make a few UI updates to include credit.

I had an idea to add a section to the theme definition file that allows linking a Lemmy profile for credit and possibly a brief description.

I haven’t had the chance to build the theme browser for hosting user themes yet. I’m honestly not sure if there’s much demand for it.

That’s a fantastic idea! I hadn’t even considered that before. Adding it should be straightforward. I’ll include it in the next release, which I hope to roll out tonight. Thank you for the suggestion.

I just found out about this crash right after I submitted the last update to the AppStore. I’ve already fixed it in the TestFlight beta version. I’ll send an update to the AppStore tonight to fix it.

In the meantime, you can use the TestFlight version to fix the issue. Thanks for letting me know! I forgot to submit the fix to the AppStore.

This one is a bit tricky. I’ve noticed the small threshold when dragging where nothing happens, and it can be recognized as a tap. I’m not exactly sure what is causing the dead zone for panning. I have a feeling it is due to 2 gestures waiting to get directional info to decide which one to trigger.

I’ll do some more digging and see what I can come up with. Things get rather convoluted when layering multiple gestures together.

Well, one down at least.

I took another look at the video rotation this morning. I had made a last minute change before submitting the update yesterday that I thought was harmless, but turns out it broke the rotation fix. I reworked this a bit and it seems to be working fine now.

I completely overlooked saving the playback position while scrubbing if the video is paused. I’ll add this in the next release.

[edit] I added support for saving media resume positions while scrubbing. I’ll still need to do a bit more testing to make sure it is working correctly.

You were correct; it was disregarding the autoplay setting when dismissing the media viewer. I’ve incorporated all of your suggestions into version 0.4.3.2, which I just released a few minutes ago. I appreciate your feedback, and please let me know if there are any problems with the update.

moving them by a few pixels brings up the controls layer

I’d never noticed this before. I actually wrote a custom gesture recognizer to handle a similar issue where moving a few pixels while zoomed in would trigger the zoom out action. I should be able to swap the controls gesture out to fix this as well.

Videos when rotated often fail to scale properly to the new aspect

I admittedly have not tested media previews with device rotation. There are probably a few issues to address here. I’ll look into this.

playback controls visible, then another tap brings up the share / dismiss controls over the top, and then finally a third tap leaves just the video

This is simple enough, I’ll have the video controls follow the same setting for other buttons visibility so they stay synchronized.

Dismissing a video should probably pause playback

I believe this follows the setting for autoplay of videos. If autoplay is enabled, the video will resume in the feed when dismissing the media viewer, otherwise, it will just synchronize the playback position. I could be mistaken, I’ll have to take a look at it tomorrow.

That’s a good point, for now I just added a new setting in the appearance section for placing links above or below the post. I’ll keep working on the updated layout. I’m half tempted to make a customizable layout that you can drag and drop elements where you want them to appear, but that’ll have to be part of a larger update.