CreatureSurvive

joined 1 year ago
MODERATOR OF
[–] CreatureSurvive@lemmy.world 2 points 2 weeks ago (1 children)

I like that idea more, I’ll definitely add support for this. Thanks for the idea!

[–] CreatureSurvive@lemmy.world 1 points 2 weeks ago (11 children)
  1. This is odd. I’ll have to look into this. Notifications have been working fine for the last year, but I received 2 reports about this issue this week. I’ll try and track this down tonight.
  2. I made some improvements to the bullet lists the other day, they will now have spacing between items in the list. For multiple paragraphs in list items, I’ll have to look into this, because you are right that they do not render correctly. All the text rendering in Arctic is completely custom, so it’s no surprise that missed some features. I will look into this though and try to find a solution.
  3. It seems that iOS changed some things with the image picker, and it’s no longer necessary to ask for photos access permission when selecting a photo. I’m going to look into this and see if I can’t simplify things for limited access. It’s definitely not ideal to have to select photos twice.
  4. As for displaying photos in-line, this is something that I’ve wanted to do for a while now, as currently any photos are just appended below the comment text. Like I said, the text rendering in Arctic is completely custom and this is a bit of a tricky task even though it may seem simple. For instance Apollo never managed to implement this either. IOS does support showing images in text views, though this would not work for gifs or videos due to limitations. I finally managed to get something working for this yesterday, and it’s now possible to display images or videos in-line. I do not have this fully implemented yet, as it does cause some text rendering issues that I’ll need to fix. I should definitely have this fully working here soon though. Also, with this new feature I should be able to improve support for spoilers and markdown tables using the same technique.
[–] CreatureSurvive@lemmy.world 1 points 2 weeks ago (3 children)

I can change it to to reddit instead of old.reddit it seems either way it links to the exact same page. I can see how that could be confusing to a novice user.

As for u/u_<user> in the link, I do filter those out so it will not show those in the results.

/c/ and /u/ were intentionally left unsupported due to this being a remnant prior to the new linking format of @<user>@<insatanc.xyz> and !<community>@<instance.xyz>. I can add support for these links though. I think for forward compatibility, I’ll have it automatically convert these links to the new format if one is typed.

[–] CreatureSurvive@lemmy.world 2 points 2 weeks ago (5 children)

I’ve finished up the reddit migrator for Arctic. This will behave exactly like the migrator in Voyager. Voyager did this vey well and I did not see much room for improvement. I made sure to give credit to Voyager for the feature idea.

I did experiment with loading reddit info to display in the feed such as subreddit icons, and subreddit descriptions and this worked, but it looks like reddit rate limits quite aggressively, so I could not include this in tool.

On a side not, these screenshots are from Arctic for MacOS which should be coming out next month if all goes well!

Arctic's Reddit Migrator

[–] CreatureSurvive@lemmy.world 1 points 2 weeks ago (13 children)
  1. This is a strange one, I have not received any reports of this behavior until now. I did restart the notification server today to see if that may resolve this issue, but I will be taking larger look into this during the week to see if I can’t find what might be causing this. In the meantime, could you try disabling and re-enabling the notifications in arctic to see if that resolves the issue?

  2. I will definitely add an option to cancel media uploads, this was a poor design choice on my part, I should have included a cancel feature from the start.

  3. You are absolutely right, this has to do with granting access to new images, I managed to resolve this for the next update. Limited access makes things a little more complicated than it should be. Now with limited access, Arctic will ask you to grant access to new photos before asking to choose new photos to upload. This can be configured in Arctics settings to ask about granting access before each upload, or only doing so once per app session.

[–] CreatureSurvive@lemmy.world 1 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

Yes I am the developer of Arctic, thank you for taking the time to write out your thoughts. I’ll do my best to respond to all your feedback here.

  1. Swipe Gesture: when I mentioned a new feature to disable swipe gestures I was only referring to swipe actions on cells, eg. (upvote, downvote, reply, share, etc) swipe navigation is still enabled when disabling swipe actions. However with swipe actions enabled, you can still use swipe gestures to navigate the app, you just have to start your swipe at the edge of the screen just like navigation in the Mail app for instance. With that said, based on this feedback I added a new setting to enable full-screen navigation gestures, with this you can swipe left or right to go forward or back from anywhere on the screen. This is not a default iOS navigation gesture which is why I did not opt to include this from the start.
  2. Tap Gestures: This one I am unsure about, double tap to upvote makes sense, however Long Press, and Haptic Touch are the same thing on most devices now that Force Touch was removed from new devices, and there would be no good way to handle both on the same view. I’m not sure I understand what you mean by triggering something random every time? Do you mean swipe gestures are random?
  3. Post Footers: currently the information on the bottom left of the posts is just statistics label, its meant as an overview of the post contents, not as an interactive element, that is why the label is small, since interaction is not intended. As for the vote buttons to the right, I could definitely make the configurable like the swipe actions so you could configure their actions. I’d prefer not to use the left information label as buttons, but I can look into adding more customization to this footer view as a whole.
  4. The ••• menu: This is something I may be able to improve. I’ve opted to show repeated options like voting so the menu is consistent throughout the app. Users can change the swipe actions, and disable vote buttons, etc. so this menu may be the only place with those options left available, and I wanted that to be consistent in post feeds, open posts, comments, etc.
  5. Comment Threads: This is something that definitely has room for improvement. I am working on adding profile pictures which should help improve following conversations. I do not want to differentiate between comments, replies, subreplies, etc. These are all just comments whether it is a reply to the post or a parent comment. I do plan to add support for continuous lines to the left to make it easier to follow comment depth, However the current layout is basically the standard as far as comment feeds are handled in most other apps I’ve used with comment chains.
  6. Comment Profile Pictures: I mentioned this above, but this is something I am working on adding, I’ll hopefully have this included in the next update.
  7. Creating and Managing Communities: This is a feature already, Though I may need to improve its visibility. For editing a community you moderate, you can open the ••• menu at the top of the screen when viewing a community feed and select Edit Community. Here you can edit the community metadata and settings. For managing user reports, you can open the same menu and open the Mod Zone (only available if you moderate at least one community) which is available in the profile tab, or the subscriptions list view. For creating communities, currently this is only available in the profile tab under the ••• menu, but I will also be adding this to the subscriptions feed for better visibility.
  8. Default Tint Color: This one is something that won’t be changing. Arctic is modeled to behave and appear like a system app on iOS, most system apps use a default tint color of blue. Additionally, Arctic’s logo is primarily blue and this fits with Arctic’s branding. Blue is also a calming color with great contrast and legibility with both light and dark backgrounds. In designing Arctic, my primary influences were Apollo, and the system Mail app, both of which use the default system blue for the tint color. However, if you do not care for the default tint, you can always change it in Arctic’s Appearance settings. I am also in the process of adding full theming support for Arctic so you can customize the color scheme of basically every element in the app, and save multiple themes.

All of this is open to discussion, I’m always happy to add new features and improve Arctic. On that note, I did finish up the Reddit Migrator yesterday. The new migrator works almost exactly the same as the migrator in Voyager, It was done very well there and I did not see much room for improvement.

Thank you for all the feedback, it is always welcome!

[edit] I just finished number 6, comments will now display user avatar pictures. Users can enable or disable this feature in settings

[–] CreatureSurvive@lemmy.world 3 points 3 weeks ago (1 children)

No problem, please let me know if you are still experiencing this issue after the reboot.

[–] CreatureSurvive@lemmy.world 3 points 3 weeks ago* (last edited 3 weeks ago) (3 children)

I haven’t experienced this myself, but my notifications are handled on a separate notification server for testing, so it may be something that only affected the production server. I just restarted both servers because they have been running for nearly a year now without a reboot.

I should have some time this week to look into this further and see if I can’t find what may have been causing this.

Additionally, Arctic does not clear notifications when they are marked as read in the app. I just fixed this yesterday, so the next release will properly clear iOS notifications when they are read in the app.

[–] CreatureSurvive@lemmy.world 1 points 3 weeks ago (15 children)

I keep forgetting to enable clearing notifications when reading them in app. I added this feature, but had it disabled for testing. Thank you for reminding me.

As for real-time notification, this is just not possible yet due to API limitations. If they add support for web hooks in the future, then I will add real-time notifications. But currently the only way to get notifications is to request them from the instance. Im already fetching notifications once a minute for each account with notifications enabled. This translates to a lot of network traffic for instances, and I do not want to increase that beyond what it is currently.

[–] CreatureSurvive@lemmy.world 1 points 3 weeks ago (3 children)

Great feedback. I’ve already implemented a way to disable swipe gestures which will be included in the next release. This is something I added the other day to improve the navigation on MacOS, but I’ll also include it in the iOS builds.

The double tap/long press for voting is a good idea, I’ll look into adding this as an option to the gesture settings.

Adding a subreddit migrator should be very easy to implement. I’ve already implemented the Lemmy Explorer api, which should streamline the migrator. I could probably come up with a working migrator tomorrow morning.

[–] CreatureSurvive@lemmy.world 7 points 3 weeks ago

It’s not dead. I’ve been very busy and have not had the time to work on it recently. I’ve started working on the next update, and I nearly have it ready for the next TestFlight release. I have a dozen or so bugs patched and a few new features done. I’m also hoping to finish up theming support before the next release.

Next month I should have the time to finish up, and release the MacOS build I’ve been working on, along with improved iPad support.

Things should start moving here again. I’m hoping to get back to weekly updates here soon.

[–] CreatureSurvive@lemmy.world 3 points 3 weeks ago* (last edited 3 weeks ago) (1 children)

Done.

Now when you tap the search tab while it’s already active, firstly it will scroll to the top of the results if it’s not already there, otherwise it will activate the search bar. If it is scrolled down, you can double tap to scroll to the top and activate the search bar. And just like before you can long press the search tab while it’s not selected and it will open the search view and activate the search bar.

I’ve found myself accidentally doing this and it not working, but I never got around to adding this feature until now.

I should hopefully have an update out soon, I have a lot of other fixes and some new features just about ready for a release.

view more: ‹ prev next ›