Welcome to the last major release of the year. I will be taking a break from all software development until next year.

This release brings some more user requested features and general improvements to the app.

This was supposed to be the release that added local event tracking but I didn’t end up having enough time to finish it. So instead of holding up the release I am releasing with local event tracking turned off. There will be more information about this once local tracking is ready. tl;dr is a lot of user requested features require local event tracking.

Full changelog

  • Add new FAB quick action - refresh posts.
  • Add listing type search filters (eg. filter by local, moderator view, subscribed).
  • Add feature to scroll post feed with volume rocker. Can be enabled in settings (Post feed). Default off.
  • Add setting to turn off saving recent communities.
  • Switch to use a different default user agent so the Summit client doesn’t look like a bot. This should fix network issues. If you encounter any new network errors after the release, please ping me!
  • Improve performance of hide read by using API to hide some read posts.

Update

I made a mistake and didn’t switch to using the new user-agent everywhere. Will fix this in a patch release (v1.74.1).

  • Use the new user-agent everywhere.
  • rescue_toaster@lemmy.zip
    1·
    4 days ago

    I have user agent set to let the app decide.

    I installed bloorp a few days ago and started using it. I’m comparing it and summit. The 400 and 500 error images simply don’t show anything in bloorp, whereas summit shows the error, so yeah, not an app issue.

    However, there are several images that load in bloorp and not summit, which gives an unknown error, getPixels failed with error invalid input.

    There is also the feed ending and not showing additional posts in summit with the 400 bad request still while I can infinitely doomscroll in bloorp. Occasionally, though not often, clicking retry will load an additional page of results.

    Edit: I tested all the user agents and none fixed the issue.

    • idunnololz@lemmy.worldOPM
      3·
      4 days ago

      Looks like on lemmy.zip for some reason requesting anything above page 10 results in a “couldnt_get_posts” error however this doesn’t occur on any other instance I’ve tested. The reason why other apps and web isn’t affected is because they use cursor based pagination, instead of page index. The reason why Summit doesn’t do this is because some features are simply easier using an index and also because Lemmy is very inconsistent about pagination. Some things are parginated with page indexes only so page indexes is the common ground for all pagination. Since Summit uses the same code for all pagination, not just posts (eg. for saved posts, search results, etc) it was simply easier to write it once using page index and not have to write two versions.

      I can look into write a 2nd version that uses cursors in the new year as unfortunately it is a pretty big change and I should be taking a break at the moment.

    • idunnololz@lemmy.worldOPM
      1·
      4 days ago

      Interesting. I was able to reproduce this but only on your instance. I can take a look later today.