This is the first pre-release of Thunder for v0.2.1+11! (if all things go accordingly and I don’t mess up TestFlight builds again)

Just an update: I’ll have a bit less time this week to work on Thunder, so updates may take a bit longer than before.

Be fully prepared to know that these pre-release versions may contain major bugs which could cause Thunder to crash or behave unexpectedly.

Without further ado, these are the changes from last time (based off changelog):

Added

  • Added colour to username in comments to distinguish your own comments
  • Added option to allow text preview on text posts in normal view - contribution from @coslu
  • Added option to share media link or external URL links in the dialog popup on post long press
  • Added back featured post icon on posts within a community
  • Added ability to customize swipe gestures on comments and posts
  • Added ability to develop with hot reload using docker - contribution from @Fmstrat
  • Added initial implementation for font size scaling for titles and content - this is very very rough at the moment so feedback is appreciated

Changed

  • Adjusted visual feedback in comment swipe gestures
  • Added option in settings to enable/disable swipe on bottom navigation bar to open sidebar on feed page - contribution from @bactaholic
  • Added option in settings to enable/disable double-tap on bottom navigation bar to open sidebar on feed page (this is disabled temporarily) - contribution from @bactaholic
  • Decreased scroll distance needed in order to fetch more comments from a thread
  • Improved error messages when more comments fail to fetch within a post
  • Decreased number of comments to fetch at a time to improve loading performance
  • Posts now load first before comment threads to make viewing posts more responsive

Fixed

  • Potentially fixed issues with HTTPS certificate errors when running on Android using Adguard with HTTPS filtering enabled
  • Improved performance for comment threads with a lot of comments
  • Fixed issue where the last comment on a thread could potentially not show up
  • Fixed issue where markdown links were not respecting “open in external browser” option - contribution from @Fmstrat
  • Fixed issue with download media not working on Android for some users - contribution from @minicit
  • Fixed issue where media download button appearance in light mode - contribution from @coslu

For things to test out, I would suggest:

  • general testing of app overall, vote, reply, comment, share, etc.
  • testing of custom swipe actions
  • scrolling through long comment threads
  • changing all of the settings in the setting pages
  • @darklightxiOPM
    link
    41 year ago

    Just curious but are you on the lemmy.world instance? I know I’ve been having a lot of connection issues with lemmy.world which causes some things to happen

    • the account profile page doesn’t show your account (this is because it couldn’t fetch your account details properly)
    • The subscriptions in the sidebar doesn’t show up properly (this is also because it couldn’t fetch your account details)

    If you try out another instance with less connection issues, those symptoms seem to disappear completely

    • Monsieur Koala
      link
      2
      edit-2
      1 year ago

      I am, changed the instance to lemmy.world after the posting issue from lemmy.ml. Both of your points happened, but seems a bit too convenient as I tried to reload the app 3 times with no success but everything went well after the clean install (and everything was fine minutes before update as well). Not sure what’s happening but just want to warn testers in case it happens to them, didn’t intend to bother you (yet) with that one !

      • @darklightxiOPM
        link
        1
        edit-2
        1 year ago

        Yeah, I’ve noticed a bit of issues with both lemmy.world and lemmy.ml - both of them (but moreso lemmy.world) have been causing some issues because of connection reasons for me

    • @[email protected]
      link
      fedilink
      01 year ago

      I can confirm that this works. I haven’t encountered any connection issues after switching to another instance.