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!
Arctic is a Lemmy client for iOS built on pure Swift. It currently supports iOS 15+ and Lemmy v0.17+
Get the latest version on TestFlight, or check it out on the AppStore.
If you would like to support Arctic’s development, feel free to Buy Me A Coffee
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!
Thanks again for your dedication! 👍
Also, while I was going to make a separate post about what the comment in the example GIF discussed, might be just as worth asking here.
While most unblockable communities were removed from the Lemmy Explorer list when blocked instance filtering was added, a few from unblocked instances remained on the list. After inquiring at [email protected], it seems that these few communities are blocked at the instance level. Is there any means by which communities blocked by a user's home instance could be detected and filtered out of the Lemmy Explorer list?