CreatureSurvive

Adding a second tap to conceal NSFW content would disrupt the tap to open functionality. I prefer the tap to open to be a universal gesture across all media, rather than having special behavior for NSFW content.

Instead, I’ve modified the NSFW blur view to collapse into a button upon pressing. This button can then be tapped to re-hide the content. In my opinion, this combination strikes the best balance. It enables re-hiding content while maintaining the consistent tap to open behavior throughout Arctic.

Thank you for the suggestion, I've noticed the need for adding support for re-hiding content, but I never took the time to implement this. I'll probably release an update tonight for this feature.

This is definitely something I can look into. I do something similar in comments threads, as the API will still return the contents of deleted and removed comments, so Arctic will check if it’s deleted, and prevent displaying the content.

I can do the same for profiles by either filtering out the entry entirely, or replacing its content with Deleted by user. For this, I will likely just add a toggle to the filtering menu in the profile tab. I don’t delete much content, so I had never really noticed this as an issue.

[email protected] has forward navigation just like Apollo. Arctic is inspired by Apollo, so it should feel just as familiar as Voyager, only it’s a native app. I don’t recall Alien Blue having forward navigation, but it’s been so long I guess that I have forgotten about it.

Good suggestion! I implemented support for saving configuration options this morning before work. Additionally, I added a setting to configure which options are saved. If you prefer not to save the color scheme’s, etc state, you can simply leave that option out. The only option that is not saved is the comment depth, as it varies. I might consider adding an option to use min or max depth, so you can show a full comment chain by default.

I’m looking into this right now. As far as I can tell so far, the issue is not directly related to the feed settings. It appears to be crashing due to strict memory constraints (30mb) for widgets.

When the feed is loading, all images are resized to the size required for the widget style. However, resizing an image increases memory usage during the process. This seems to be the cause of the crash.

I’ve done a bit of refactoring, images are now cached to disk rather than memory, and I’m working on a more efficient way to resize images. In the past, I used Lemmy’s pictrs API to resize the image before downloading, but the resulting images are very low quality, and grainy when resizing via api.

Thanks for letting me know, I have this fixed now. I’ll release an update addressing this later today.

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.