(iOS | Web | Unity3D) Developer

the more you get, the less you are.

  • 26 Posts
  • 92 Comments
Joined 1 year ago
cake
Cake day: June 14th, 2023

help-circle


  • Thank you! This is something I’d been holding out for a while now waiting to see if it’d be implemented in the Lemmy API. I finally decided to roll my own solution in the meantime.

    There are a couple of issues with sorting, for instance Scaled and New Comments sort modes are not accurate in multi-communities. This is due to limitations in the API where I don’t have access to the necessary information to accurately implement the sorting algorithms client side. However, the pages are still fetched from the API using the proper sort mode, so all the same posts will be present in the per-page feed, the sorting just won’t be quite as accurate.

    Other than that, I am not aware of any other issues. Though this is new and I only tested it for a few hours before releasing the update. I do think I will add an option to the editor so that multi-communities can be linked to accounts. This will allow setting multi-communities for a single, or multiple accounts. I may do the same for favorite communities as well.




  • I spent all day trying to reproduce this issue without any luck. However I was finally able to track down where the mismatched data is being applied, and prevent it from happening, I’ll need to do a little more digging to find the root issue and properly fix it.

    I might have time to finish this up tomorrow morning, if not I’ll definitely have a patch released sometime on Friday. Thank you for bringing this to my attention, it’s probably been hiding there in plain sight for a while now without being noticed.


  • This is actually an issue I was aware of. Unfortunately textview on iOS does not have any native support for tables like the MacOS counterpart does. For tables in Arctic, I rolled my own using tab breaks for the layout, and some custom drawing for the background. This solution does not allow word wrapping within columns in the table, nor does text alignment work correctly when using tabs.

    In the end, what I’ll end up doing for this, is embedding a custom view within the text view for rendering tables. This will come later as I plan to include this in a larger text rendering update that will allow for in-line media rendering, link previews and improved code and block quotes etc.

    This would be a relatively trivial task using SwiftUI, but in UIKit, it’s going to take me some time to develop a custom solution.


  • I started adding support for this yesterday, any time a post is opened, or when you interact with an open post (vote, save, comment, etc) it will update the post feed with that information. This has been a long standing issue I’ve intended on fixing for a while.

    As for the YouTube previews, I really need this marked as an experimental feature. It uses a third party library that utilizes undocumented decryption to attempt loading the video, it doesn’t work at any for age protected videos, and it seems to be really spotty as to when it will actually work. YouTube intentionally try’s to block these types of libraries. I’ll see if I can’t come up with an alternative for this.




  • This is a peculiar one that I have not seen before. Had you noticed this at all before the latest beta release? I cannot think of anything that changed in that build that would have affected this.

    I see some odd issues here where the post you clicked is showing mixed data. The post content and community name is that of the c/technology post, but then the community icon is for c/tenforward.

    I see the post was created by a mbin user, perhaps it is due to a federation issue, or maybe the mbin api has changed and I need to update support.

    Next time you encounter this, would you mind checking some of these details such a as post creator instance, post content all matches, etc.

    I’ll start looking into this, thank you for informing me!


  • I believe this is a side affect of the media loading optimization I had mentioned in one of your previous posts about background refresh. It could also be that the image failed to load during the first request, and succeeded the second time when opening the post. I’d assume if you scrolled that post off screen and scrolled back, it would show the image.

    I have a few ideas for how to fix this, as I have seen it happen a few times. I’m hesitant to add support for retrying network requests for loading media, as it can impact performance. I may try it out though and see how it holds up. If not, I think I’ll add a message to the image view explaining that the media failed to load, with a button to retry, or open in the browser.


  • Looking at this, it appears the comment you linked includes a community link, not a crosspost link. Tapping the link seems to open the the correct community to the post feed. I see the community looks quite new, perhaps you were the first one on your instance to interact with that community, which could mean there was just a delay in federating the rest of the posts in that community. Is it possible you opened that link expecting it to open a single crosspost, and instead it opened to a community with only one post showing, thus mistaking it for an open post the views are quite similar in appearance)?

    If not, I may need some clarification on this issue, perhaps I misunderstood.




  • Yeh, there is room for improvement with hiding bars, and navigation that I just haven’t figured out how I want to address yet.

    I did manage to fix hiding the status bar in the media viewer for non-notched devices. I tested on an SE (gen 3) and it seems to be working well. I originally had disabled hiding the status bar on non-notched devices due to an ugly transition when the status bar hides, but I managed to fix that yesterday.

    Thank you so much for all the feedback lately, it’s been a big help in finally going through and addressing some long standing bugs and annoyances!


  • I think I have this fixed now. The default sort order will be applied when you first open a feed, after that, any changes you make to the sort order will only affect the open feed. I also added a new setting to remember the sorting mode, so if you change the sorting mode while browsing, it will update the default setting.

    As for the issue of resetting to Hot sorting on relaunch. I believe I have this fixed as well. In the cases where this would happen, did you have your sort mode set to one of the Top sorting modes? If not, please let me know as I might have to look into it some more.


  • This is in the works, fully customizable theme support is being implemented that will allow customizing colors for virtually everything. The theme support will come with a couple of prebuilt themes, but will also allow creating your own that can be copied, edited, shared, and imported.

    I’ll be setting up a free service for this where users can publish their themes, browse community themes, and install community themes within Arctic’s settings.

    Regrettably I did not implement theming support earlier in the project, so there is still a lot to be done before this will be ready for testing.


  • This isn’t so much to do with sorting and inserting posts above the current position, the posts are already loaded and displayed in order. The issue is due to loading previews (links, videos, images, etc). If the preview is not loaded in time for the cell to render it when it’s first displayed, then the cell is updated to adjust for the preview content. Usually this is not an issue because this typically happens off screen, or below the scroll position so the scroll position won’t jump.

    This definitely oversimplifies the behavior, as there are a lot of performance tweaks that happen behind the scene to attempt a guarantee that the cell will be sized properly, even if the content is not fully loaded in time, etc.

    Anyway, occasionally the previews will not load in time to properly size the cell while it is below the focal point of the screen, and it causes the onscreen content to jump down. I’m still working on a proper fix for this, as it is, I already prevent resizing cells if it is not yet visible, or already scrolled off screen.

    I’ll see if I can’t come up with something to improve this soon.