I released v0.4.2.6 two days ago that includes this feature. The community and user labels will now show the remote instance. The instance will not be shown if the user or community is on the same instance as your account.

I have not added support for showing this information in comments yet, but I’ll look into this for a future update.

I forgot to get back to you about this, but as of v0.4.2.4 I added options to disable haptic feedback for specific features such as errors.

I released v0.4.2.6 yesterday that addresses this issue. I believe this covers all cases where this issue may occur, but if you do encounter this again, please let me know.

I think the issue with previous post about this was not your explanation of the problem, but rather my availability. I was very busy around that time and a little burnt out. I believe that is around the time I took a little break from working on Arctic, and it looks like this issue just slipped between the cracks when I came back.

I have not had the time to fully implement this feature just yet, however I did release v0.4.2.6 yesterday. This update moves the [[NSFW]] tag to the top of posts, but only if the Show Community On Top setting is enabled. I am working on an update to the large post layout that will offer a better implementation of this his feature, but it is not ready quite yet.

I managed to resolve this, it was a silly mistake no one had noticed until now. I’ll roll out a hot-fix for this tomorrow.

Thanks for letting me know about this, it looks like it’s been an unnoticed issue for months now.

Open source is absolutely in the roadmap for Arctic.

Arctic is 100% free and always will be, there are no paid or premium features. In app purchases are solely for the purpose of supporting development, and ongoing server costs for push notifications.

Why is Arctic closed source? Well, Arctic started out as a small personal project for myself. I did not have any idea the project would grow so big. I did not choose the best architecture for the project (MVC) and over time its become a bit unruly. I do not want to open source the project in its current state. I’m working on migrating to MVVM which will vastly improve readability, and overall code quality.

I’ve also been working on modularizing a lot of the larger components of Arctic into packages in an effort to clean up the core project. The project is built using UIKit instead of SwiftUI, thus the custom UI components such as the Markdown rendering system are cumbersome and complicated. Moving components such as this out of the core project into manageable dependencies is a major step towards open sourcing. Of course, all these packages will be open sourced along the way.

In the end, what I may end up doing is similar to mlem. Starting the project fresh, open source from the start, and based on a more sustainable pattern. I’ve leaned a ton while working on Arctic, and I have a much more concise view of the end product I want to build now. I think this would actually be an easier feat than refactoring the entire project. All that has been stopping me from doing so, is it would force Arctic to take several steps backwards in order to move forward.

Anyway, yes I am working to open source Arctic, and I am very excited to do so. I’m still working out the details on how I want to achieve this step.

I’m not sure if this is an issue with Arctic or not. I’ve tested on instances running v0.19.7 (db0 current version) and it seems to load feeds just fine. I don’t think there were any changes in the jump from v0.19.5 to v0.19.6(7) that would affect loading feeds.

If it’s timeout errors, it’s likely to be a network issue, or server issue. I think I’ll increase the timeout threshold for the next update. Currently, I believe it is set to 10 seconds, under poor network conditions, or heavy server load, this may not be enough.

I’ll also setup an account on db0, and see if I can’t reproduce the issue.

Thanks for letting me know, I’ll get back to you when I’ve had the chance to look into this further.

Great to hear! Personally I prefer to keep the status bar visible, so I ended up adding this as an option, and updated the design to add a background for the status bar while scrolling, or hide it all together. This seems more in line with what you’d expect from other apps.

I forgot to get back to you about this. I was running behind on the last update, and did not have time to look into this before releasing. There was a rather critical bug in the last update that I did not want to hold off on patching any longer than I had already. I’ll get this fixed in the next release which will hopefully be out on Monday. Having the exact steps to reproduce will be very useful, so thank you for that.

This is my fault, I misunderstood what you were talking about. This is not currently a feature. I know most other clients offer this option. Originally I did not add this option because it caused layout issues with long instance names, however, I believe most of those have been fixed since then. I will look into adding this as an option in the next release. Sorry about the confusion.

Thank you, I’m glad you’re enjoying it so far!

This is actually a great point, I hadn’t really considered the placement of that tag. I’ll see about adding this in the next release. I have some work to do on the title labels anyway to match the markdown rendering used on Lemmy’s web client. Also, I might add an option to blur NSFW for unsubscribed feeds only.

I just released an update that addresses this, it was caused by a bug introduced in the previous release.

This was a bug in v0.4.2.4, I just released an update that addresses this and a few other issues caused by the same bug. You should be able to access all the community information, and actions from community feeds now.

I finally got around to this and added options to customize the subscription list a bit. You will be able to disable icons, a compact style with a single line. I’m going to add support for adding additional information such as subscriber count, post and comment count, etc, but I do not have that part ready yet. I’ll hopefully have this update out tomorrow.

I hadn’t noticed this one before. I almost always leave my sorting on scaled, so it’s likely I just overlooked this. I am planning an update for tomorrow, so I’ll look into this before the release to see if I can’t track down the issue. There is at least one scenario where the default sorting will be reset. If you have the default sort as Scaled, and you switch to an account on an instance running Lemmy v0.18.x it will change the sorting to Active, since Scaled was not available prior to Lemmy v0.19. However this does not should like that is the cause of your issue. I’ll see what I can find. Thanks for letting me know!

In what location are you looking for the instance? I know there was an issue where opening a post would not load the community information, preventing the action menus from showing any instance or community actions such as blocking. I do have this fixed internally now, and I should have an update out tomorrow. Is this what you were referring to, or is there another location that is not showing the instance information?

I believe this is fixed now. It was due to changing the listing type from subscribed to all, when viewing a community feed you are not subscribed to. The behavior is still the same, but it will only affect that one feed, and not change the global setting.

This is fixed now, it was actually caused by the same issue preventing community sidebars from loading correctly.

Alright, I have this fixed now. It was a simple mistake of trying to load the community information, before the community id was set.

Alright, I was able to reproduce this issue. It looks like it is working correctly if you open the sidebar from an open post, but not from the community feed. I’m wondering if this is the same issue that is causing the post composer not to detect the open community.

This should probably be a simple fix, I’ll look into it here in a little while when I get home.