This is definitely a caching issue. That menu is updated only as needed, but does not check for external changes. I’m going to update that so it is not cached and rechecks its state when opened.

I’m able to reproduce the issue with this video. I’ll look into it. It seems to only affect HLS streams with variable resolution. So it is likely not updating the zoom properly since the aspect ratio doesn’t change, but the size does.

Whoops, that’s not supposed to happen. It’s a super simple fix, I’ll have this patched really quick.

Sorry I’ve been absent the last week, I’ve been busy and haven’t had much time to work on Arctic. I appreciate all the feedback and reports!

A toggle would not be necessary for this one, I was planning to just add an action the the long press action menu on PeerTube links. By default, tapping the link would open it in the browser.

Eventually I’d like to support PeerTube link embedding in comments as well, but I’ve got a few things that are more pressing at the moment.

I’m not sure of any current means of federating PeerTube videos. However I can look into adding an action for PeerTube links to open them in the in app media viewer. Either way I should be able to patch this with any live video link and a few quick tests.

I’m not sure I’ve seen anyone that uses Lemmy Explorer as intensively as you do, so all your feedback has been great. I can definitely add a sort by date feature, as I believe that is included in the API. I’ll skim through the api and see if there are any other filters I can include in addition to this while I’m at it.

The last update reorganized the Lemmy Explorer swipe actions a bit, but I will look into making them customizable. There are several areas I need to add support for customizable swipe actions, so this will probably be bundled with an update addressing all of those views.

This is patched internally, I’ll have the fix out in the next update. I’m honestly not sure why this crash popped up out of nowhere, but nonetheless it was a simple fix.

I have this one patched internally, and I’ll include the fix in the next update. This was not specific to Lemmy Explorer, but rather all community block actions. Thank you for pointing this out!

This is mostly out of my control. The NSFW filter is not exactly as it seems. Any community or instance that allows NSFW posts is considered a NSFW subject by Lemmy Explorer. This means that even a casual community could be marked NSFW if it allows mature content of any kind. It would be nice if there was some more refined way of filtering this, but as it stands, there is not any API that detects NSFW by content rather than setting.

Sorry for the late response, it has been a tiring week for me.

I have not found an actively live stream to test this on just yet, but I’m sure that I can find some information on this subject. I’ll look into patching this crash in the next update.

This is one that I tried my best to find a good balance for. Lemmy doesn’t support marking a post as a text, media, link post. So, if a posts primary url is not a media link, the media will not be displayed in the feed. However, if the primary url is a media link, and the post body contains media URLs, then it will be displayed as a gallery.

Arctic used to render all posts with media as the primary URL, or media URLs in the post body as media posts, however there were a lot of instances where this was undesirable, so I changed it. I’m hoping in the future, Lemmy will support tagging image groups as gallery’s, and post types, eg: text, image, link, etc. in the mean time Arctic just tries to make a best guess. That said, I am going to look into rendering posts such as the one you linked as image posts, in the case that the entire body of the post is a media URL.

I hope that clarifies this instance, but I’m definitely open to feedback on this behavior.

Good to know, I see exactly what is causing this issue. I’ll have this patched in the next update. Thanks for letting me know!

This is something I haven’t seen before. I’m curious if this may have been an issue with the API considering your account was so new.

In case this is not an issue with the api, would you mind opening the profile tab, and then going to Settings -> About -> Arctic Logs. There should be an entry that shows the raw api request including the username sent with the request. It’s possible that the username is malformed in some way which would cause this issue.

The log entry I am looking for should look something like this:

[2025-03-02 01:13:49 +0000] [info] [lemmy] [performRequestWithCheckedResponse(_:)] LemmyAPI request: https://lemmy.world/api/v3/user?auth=_private_&limit=20&page=1&saved_only=false&sort=New&username=CreatureSurvive%40lemmy.world

I’m in the process of rewriting the notification server for Arctic. I added backend support for muting replies yesterday, I still have some work to do before it’s ready to use, but it should hopefully be within the next week.

The server rewrite will allow muting posts, or individual comment threads.

I was a day late, but this is fixed now. There is still an issue when changing the font size where it may not fully apply throughout the app until it is relaunched. I’m looking into this, and I’ll probably have it fixed in the next release.

Good catch, I hadn’t noticed this one yet. This should be a super simple fix, I’ll probably have a hotfix out for this tonight. Thanks for letting me know!

I just released an update to address this issue, thanks for letting me know about this!

I’m able to reproduce this on my end as well. I’ll see if I can’t release a hotfix for this tonight when I get home. Thanks for letting me know about this.

v0.4.5.10 had a lot of major changes behind the scenes, and a few issues slipped through that I didn’t catch in my tests.

The badge is usually cached, but since it’s updated frequently, it is not written to the on disk cache except when Arctic is closed. The badge is supposed to update automatically when launching Arctic, or changing accounts. However it looks like at some point I removed the initial update on launch. So the badge still updates, but not for about 30 seconds after opening the app, or like you noticed when opening the inbox tab.

I’ll fix this in today’s update to add the initial update back in so it will fetch the unread count immediately.