CreatureSurvive

joined 1 year ago
MODERATOR OF
[–] CreatureSurvive@lemmy.world 8 points 3 days ago (3 children)

My pleasure! I’m not exactly sure what is going on here, I submitted a new build to TestFlight 2 days ago, and it’s still waiting for review. I’ve always had really good luck with the review processes and it’s usually approved within an hour or so even with AppStore releases. I’m hoping it’ll be approved sometime today since the weekend is over.

I was really pushing to have the update ready before this happened, but I was not expecting such a long wait for review.

Anyway as others have pointed out, you can switch to the AppStore version without loosing any settings. Keep your eye out, I’ll be posting here when the new TestFlight version is live.

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

That is fair. There is a setting Settings > Appearance > Show Links In Comment which allows you to disable link previews in the comments section.

I do my best to fix issues as they are noticed, and I take all the feedback I can get. However, like you said, there is a much smaller following here than there is for apps like Voyager and Mlem, so I don’t get nearly as much feedback as I would like.

Being on an iPhone X makes sense. The iPhone X still had real force touch unlike all the newer phones which do not have pressure sensitive screens, and instead use a long-press for Haptic Touch. This should help in figuring out the issue you are having with links.

In Arctic tapping the active tab will scroll to the top, or act as a back gesture if you are already at the top. This was a feature that was requested early on from users coming over from Apollo, and missing that feature. I could definitely add an alternative option like this though.

[–] CreatureSurvive@lemmy.world 9 points 1 week ago (1 children)

It’s not abandoned. I had a very busy summer and did not have much time to work on it. I’m back at it now and I have a couple big updates coming over the next few weeks. Things should start picking up around here again. I plan to get back to weekly updates, I also have some time off from work next month so updates may be more frequent during that time.

[–] CreatureSurvive@lemmy.world 8 points 1 week ago (2 children)

Yes, I’m I’m working on finalizing some of the new features and bug fixes so I can push out the next release. If needed, I’ll disable some of the new features so I can push out a working build while I continue to work on them. Either way, I’ll have an update out before it expires.

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

Ahh, I see. Link previews can be disabled in settings. I added this before I had support for haptic tough on links. Also I enjoyed this feature from Apollo.

This is the first time I’ve heard about any issues with links. There is nothing special about the Haptic Touch for links, other than a custom background bubble. Are you jailbroken by chance? You’ve listed a few issues now that have never been reported before, and it makes me wonder if you perhaps have some conflicting tweaks that could be interfering. If not could you tell me your device and iOS version so I can try and figure out some of these issues.

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

Lemmy as well as most of the Fediverse uses the CommonMark Specification any markdown features I add will either be supported by CommonMark or by Lemmy. I do not want to create a a new specification, or use the Reddit specification unless it is adopted by Lemmy.

CommonMark does not support decimal numbers lists, so this is not an option as it would break list rendering on every other client. You have to remember that Lemmy is federated unlike Reddit. Users may be reading in a different app, on desktop, or even on a different platform like Mastodon. Changes like these need to be widely accepted and it would do more harm than good to implement breaking changes in Arctic that would not work correctly anywhere else.

Same goes for spoilers, and restricting italic markers. If these features do not meet the standard, then they will just cause harm.

As for in-line link previews. I’m not sure about this one. Most links are posted in context, like the middle of a sentence or paragraph. Putting previews in the middle like that would decrease readability. That’s partially why I treat them similar to footnotes and link them at the bottom of the context.

With that said I could add soupy for this, but it would be an optional feature that would be off by default.

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

There has been an open issue for this on the Lemmy-UI GitHub for 2 years now. They use the CommonMark specification in Lemmy and so do I for Arctic.

I do not want to try and strong arm the devs into adding a feature they may not want to add. Instead I may submit a pull request to Lemmy adding support for the inline spoiler tag. There does however seem to be some discrepancy about the format for the tag, since Markdown, nor html officially support inline spoilers.

Also I am aware of the superscript issue in ton the composer, I do plan on fixing this, but it is low priority at the moment.

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

I would love to do this, because you are right, the spoilers in Lemmy do not function the same as spoilers on any other platform. However I can’t add this as a feature since it would only be supported in Arctic and people browsing on desktop or any other client would not would not have support for this. So until Lemmy officially supports in-line spoilers like Reddit, we will have to make do with the current system.

It doesn’t make sense to allow composing posts or comments that could only be properly viewed in Arctic.

[–] 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

0
Arctic release notes (testflight.apple.com)
submitted 1 year ago* (last edited 1 year ago) by CreatureSurvive@lemmy.world to c/arctic@lemmy.world
 

I haven’t been posting here about Arctic updates, and I realize that is a little counter productive towards building an active community here. So I would like to change that and start posting about changes in each release, and about active development.

I have been trying to wrap up a release every couple of days, and keep them coming as frequently as I can manage. Each update I try and throw in a mix of bug fixes and new features or quality of life improvements. I believe at this point I have all the crashes fixed except one, which I’ve received a good number of crash reports about. The crash usually happens after refreshing the posts feed when letting the app sit in the background for a while. Unfortunately I’ve not been able to reproduce this crash which makes it difficult to resolve. However I do know where the issue originates, and I hope to have it resolved in the next update.

What’s next?

In the next update I’m planning a few new features. First and foremost, is private messages. Currently, you can view private messages with Arctic, but there is no way to reply or create messages. I’ve been putting it off because I don’t have a clear idea of how I’d like to design this. I’ve never been a fan of the Messages app-like design within an app like Arctic, so I’m thinking of implementing it more like a forum than a chat app. Im also planning to add in UI support for post and comment reporting, as this is a critical feature that should already be implemented if I’m being honest. I’ll hopefully have instance sidebars added in the next update as well.

Going forward

Within the next couple of releases I’d like to tackle some of the biggest issues within Arctic currently. First is state synchronization. Currently the app state is poorly managed: for instance you can open a post and vote or comment on it, and back-out to the feed and the UI will not depict the changes. This is rather cumbersome task as UIKit does not have proper binding like SwiftUI does. But I have a good idea of how I will manage this.

The second issue will be improvements to scrolling performance in posts feeds. This is also a tricky task as UIKit does not handle changes to cell height in tables very well. Currently, Arctic tries its best to prefetch images before they are displayed to prevent having to resize visible cells, but dependent on network conditions, this may not always happen in time and it can cause some jumpy scrolling. I may never completely negate this issue without the the lemmy API providing image dimension data in the responses. However, I have some options for improving this that I have yet to try.

Lastly, I’d like to address issues with links being un-tappable in some posts. This one is really annoying, and honestly I’m just going to throw out the current system and rewrite the system using official techniques.

Some more thoughts

Once stability and core features are a bit more polished, I’ll be focusing on design. Currently Arctic is quite static in design, but I’d like to offer a bit more user control over appearance. Things like app-wide color themes, comment color themes, customizable action/swipe menus, etc. while implementing all of this, the settings section will also get an overhaul and be a little more organized.

I’ll also be working on implementing mod/admin tools. This is likely going to take some time, as there is a lot to implement, and familiarize myself with. I’ll keep everyone up to date on my progress with this when the time comes. I may also seek out some mod/admin users to test these features in a private testing group to avoid issues


Anywho, I didn’t intend on this being such a blanketed post, so I will leave it at that. I’ve included change-logs below as I’m not sure if anyone reads release notes in TestFlight releases. I’ll be sure to make a new release post here every time I release an update going forward.

Thank you, to all of the users. You’ve all been great. Our numbers are still quite low at the moment, only 153 testers at the time of writing this. Hopefully I can bump those up with the coming releases.

v0.1.8


  • Fixed videos failing to load in the media viewer if more than one video is in the list
  • Fixed crash when trying to share a video from the media viewer (for now, only the link will be shared. I will add an option to share the video file soon)
  • Fixed videos not posing when swiping to the next page in the media viewer
  • Fixed the search bar not always showing on the initial load of the Search tab
  • Fixed issue where some community icons would fail to load
  • Fixed issue where some animated images would not animate in the full post-view
  • Fixed issue where link previews would fail to display a default icon if a site favicon is not found
  • Fixed markdown not being applied when opening the post editor
  • Added loading indicator in the media viewer when loading videos
  • Added support for cross-posting (option is available in the action menus)
  • Added a community selector to the post composer, for changing what community you are posting to
  • Added support for scrolling to the top when pressing the posts tab while it's already active
  • Added option to open the post composer when long pressing the posts tab
  • Added reply context preview to the Reply Composer, for viewing the context in which you are replying to

v0.1.7 hotfix


  • Fixed crash when pressing the cancel button in the Search view
  • Fixed placeholder text not hiding in the post editor when editing an existing post

v0.1.6


  • Redesigned Post Editor UI
  • Fixed issue that could cause the login screen not to recognize when username/password was pasted
  • Fixed crash that could occur while trying to scroll the subscriptions view before it's loaded
  • Fixed issue causing some comments to be truncated (cut short)
  • Fixed layout issue causing odd behavior with the statusbar on non-notched devices
  • Fixed an issue that could cause some animated images in the post feed not to animate
  • Added a Upload History manager for deleting previous media uploads
  • Improved error messages to be more descriptive
  • UI now depicts when an upload is in progress
  • Media in comments can now be opened in the Meia Viewer
  • Index scroller in the Subscriptions view is now easier to grab
  • Increased tappable area for user/community labels in post-cells
  • Tapping the stats section of a post cell now opens the post
  • Improved success rate for losing YouTube videos
  • Improved image-loading behavior in the post feed
  • Hopefully, TOTP tokens will now be auto-filled when using a password manager to login

v0.1.5


  • Added compact post option (work in progress)
  • Added a network monitor that will show when no network connection is available
  • Added inbox paging, inboxes will now load more content when scrolling
  • Added placeholder icon for users avatars in search view
  • Updated Search and Profile styling to match that of the post feed (spacer between cells)
  • Improved performance when scrolling posts in search and profile views
  • UI now shows when you've reached the end of a feed, or the feed is empty when browsing posts

v0.1.4


  • Fixed account switcher positioning issue that occurred after switching accounts
  • Added Guest Mode to the account switcher

v0.1.3


  • Added option to disable video scrubbing gesture
  • Added upload history tracking to manage media uploads (No UI Yet)
  • Fixed a crash that could occur while parsing username links
  • Added image upload support to the markdown editor
  • Provided default icons for communities without an icon
  • Added BOT badge to post cells for showing bot accounts
  • Community cells in the search tab now show more statistics
  • Added option to override the interface style (light/dark)
  • Added some experimental swiftUI views
0
submitted 1 year ago* (last edited 1 year ago) by CreatureSurvive@lemmy.world to c/lemmyapps@lemmy.world
 

cross-posted from: https://lemmy.world/post/3634233

After a few delays, Arctic is has finally been submitted to TestFlight and got the green light. For those of you who don’t know what Arctic is, it’s a Lemmy client for iOS 15+ built in pure Swift.

Arctic began as just a little side project for me. As an avid Apollo user I was missing a feature rich and familiar client for IOS. So I started working on Arctic. My primary goal with the project has been creating a native UI appearance, and content presentation, focusing on putting the important content directly in the feed without feeling cluttered. I’m finally at a point where I feel Arctic is stable enough, and houses enough features to go forward with beta testing.

I’m currently testing out Reimplementing the UI in SwiftUI as it allows for quicker iteration, and less boilerplate code. Though I’m not sure about performance yet. SwiftUI seems to be lacking in certain areas such as prefetching APIs for heavy feeds etc. you can find an experimental post feed in settings that uses SwiftUI.

As of right now, I have not set up an issue tracker for Arctic. The reason for this is that I don’t know for sure if I will be Open Sourcing the project yet. I’d like to keep the issues/project in the same repository, and I’m unable to have a private repo with public issues. I’ll be deciding what route I would like to take over the next week or so.

While on the subject of open source, I’d like to mention that Arctic does not collect any information from users devices. The only user specific information that is stored is the Lemmy account JWT Auth token for communication with the Lemmy api. Absolutely no personal information is collected, or leaves your device. Currently I have no plans to implement any analytics in Arctic, and if I ever do, it will be on an opt-in basis, and be completely anonymous only tracking information relevant to Arctic support.


Development

I feel the need to point out that I work a full time job, and am often busy outside of working. With that said Arctic development may be a bit slow compared to some of the other projects out there. I do however plan to release at leas one update every week for now. I will try to push out more frequently as my time permits, even if that means smaller hot-fix type releases. I do plan to support Arctic long term, as I’m already quite invested in the project and have really enjoyed working on it.

Anyways, please don’t hesitate to reach out and ask questions, or offer feedback/suggestions . I’m quite busy most days, but I will do my best to respond as soon as possible.

Almost forgot the most important part, here is the link to Arctic TestFlight


Current Features

  • Submitting / Editing Posts
  • Submitting / Editing Comments
  • Voting on Posts / Comments
  • Blocking Communities / Users / Instances
  • Subscribing to Communities
  • Search (URLs, communities, comments, posts, users)
  • Rich link previews
  • Uploading images
  • Rich Markdown Editor
  • Community browser
  • Basic guest (anonymous) mode
  • Multiple accounts, and quick switcher
  • Integrated Media Viewer
  • Upload manager manage previous media uploads)
  • In-line YouTube videos (experimental, this seems to have broken with recent changes to the YouTube api)

Known Issues:

  • Some in-line links do not recognize taps, I’m looking into overhauling the Markdown rendering and may be switching to swift UI for this, as it is better suited for that task instead of UIKit
  • State Sync, The UI does not update in all cases to reflect changes such as voting on a post, and then viewing it in the post feed
  • Some media fails to load and is unhandled by the UI
  • Scrolling performance needs improvement
  • Long usernames/community names can overlap action buttons
  • Fast scrolling can result in user/community icons showing in the wrong cell
  • Videos do not display in image gallery previews
  • YouTube videos fail to load at times
  • No spoiler support at the moment
  • No in-line images Yet
  • Private Messages are not currently supported, they will be coming soon

Previews

Preview 1

Preview 2

Preview 3

0
submitted 1 year ago* (last edited 1 year ago) by CreatureSurvive@lemmy.world to c/arctic@lemmy.world
 

After a few delays, Arctic is has finally been submitted to TestFlight and got the green light. For those of you who don’t know what Arctic is, it’s a Lemmy client for iOS 15+ built in pure Swift.

Arctic began as just a little side project for me. As an avid Apollo user I was missing a feature rich and familiar client for IOS. So I started working on Arctic. My primary goal with the project has been creating a native UI appearance, and content presentation, focusing on putting the important content directly in the feed without feeling cluttered. I’m finally at a point where I feel Arctic is stable enough, and houses enough features to go forward with beta testing.

I’m currently testing out Reimplementing the UI in SwiftUI as it allows for quicker iteration, and less boilerplate code. Though I’m not sure about performance yet. SwiftUI seems to be lacking in certain areas such as prefetching APIs for heavy feeds etc. you can find an experimental post feed in settings that uses SwiftUI.

As of right now, I have not set up an issue tracker for Arctic. The reason for this is that I don’t know for sure if I will be Open Sourcing the project yet. I’d like to keep the issues/project in the same repository, and I’m unable to have a private repo with public issues. I’ll be deciding what route I would like to take over the next week or so.

While on the subject of open source, I’d like to mention that Arctic does not collect any information from users devices. The only user specific information that is stored is the Lemmy account JWT Auth token for communication with the Lemmy api. Absolutely no personal information is collected, or leaves your device. Currently I have no plans to implement any analytics in Arctic, and if I ever do, it will be on an opt-in basis, and be completely anonymous only tracking information relevant to Arctic support.


Development

I feel the need to point out that I work a full time job, and am often busy outside of working. With that said Arctic development may be a bit slow compared to some of the other projects out there. I do however plan to release at leas one update every week for now. I will try to push out more frequently as my time permits, even if that means smaller hot-fix type releases. I do plan to support Arctic long term, as I’m already quite invested in the project and have really enjoyed working on it.

Anyways, please don’t hesitate to reach out and ask questions, or offer feedback/suggestions . I’m quite busy most days, but I will do my best to respond as soon as possible.

Almost forgot the most important part, here is the link to Arctic TestFlight


Current Features

  • Submitting / Editing Posts
  • Submitting / Editing Comments
  • Voting on Posts / Comments
  • Blocking Communities / Users / Instances
  • Subscribing to Communities
  • Search (URLs, communities, comments, posts, users)
  • Rich link previews
  • Uploading images
  • Rich Markdown Editor
  • Community browser
  • Basic guest (anonymous) mode
  • Multiple accounts, and quick switcher
  • Integrated Media Viewer
  • Upload manager manage previous media uploads)
  • In-line YouTube videos (experimental, this seems to have broken with recent changes to the YouTube api)

Known Issues:

  • Some in-line links do not recognize taps, I’m looking into overhauling the Markdown rendering and may be switching to swift UI for this, as it is better suited for that task instead of UIKit
  • State Sync, The UI does not update in all cases to reflect changes such as voting on a post, and then viewing it in the post feed
  • Some media fails to load and is unhandled by the UI
  • Scrolling performance needs improvement
  • Long usernames/community names can overlap action buttons
  • Fast scrolling can result in user/community icons showing in the wrong cell
  • Videos do not display in image gallery previews
  • YouTube videos fail to load at times
  • No spoiler support at the moment
  • No in-line images Yet
  • Private Messages are not currently supported, they will be coming soon

Previews

Preview 1

Preview 2

Preview 3

 

I’m in the process of submitting my Lemmy client (Arctic) to TestFlight, and I had some concerns about NSFW options in my app.

As per section 1.2 User-Generated Content it states that NSFW content needs to be disabled by default, and can only be enabled through the website.

Apps with user-generated content or services that end up being used primarily for pornographic content, Chatroulette-style experiences, objectification of real people (e.g. “hot-or-not” voting), making physical threats, or bullying do not belong on the App Store and may be removed without notice. If your app includes user-generated content from a web-based service, it may display incidental mature “NSFW” content, provided that the content is hidden by default and only displayed when the user turns it on via your website.

Does this mean that I am not aloud to include any options in my apps interface regarding NSFW content, eg: Blur / Hide NSFW Content, Even if the content is hidden by default?

Any pointers here would be useful. I do see that other Lemmy clients are including options within apps and have not had any issues so far, but the policy seems to indicate this is not allowed.

1
submitted 1 year ago* (last edited 1 year ago) by CreatureSurvive@lemmy.world to c/foo_test@lemmy.ca
 

Lorem ipsum dolor sit er elit lamet, consectetaur cillium adipisicing pecu, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. Nam liber te conscient to factor tum poen legum odioque civiuda.

 

Lorem ipsum dolor sit er elit lamet, consectetaur cillium adipisicing pecu, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. Nam liber te conscient to factor tum poen legum odioque civiuda.

view more: ‹ prev next ›