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.

all 20 comments

sorted by: hot top controversial new old

[–] kamenlady@lemmy.world 2 points 4 days ago (1 children)

I'm new to summit and it's great! This version fixed all the 401 responses i sometimes had when trying to open pictures.

[–] idunnololz@lemmy.world 2 points 4 days ago

Nice. Good to hear!

[–] Aielman15@lemmy.world 2 points 4 days ago (1 children)

Happy holidays 'lolz! Thank you for your wonderful app :)

[–] idunnololz@lemmy.world 2 points 4 days ago

Thanky you! Happy holidays to you as well!

[–] gila@lemmy.world 6 points 5 days ago (1 children)

Getting missing images on a lot of posts, which show up fine on my normal instance in a browser (posting on an alt because I normally block lemmy.world)

getPixels failed with error invalid input

App otherwise still working great! Enjoy your break

[–] idunnololz@lemmy.world 2 points 5 days ago (1 children)

Can you check Settings > Misc > Client user-agent and make sure " Let the app decide" is selected? If that is selected and you are still getting errors can you try playing around with that setting? If you find a certain setting works please let me know which one so I can figure out a better user agent to use. Thank you.

[–] gila@lemmy.world 1 points 3 days ago

I tried all the different user-agents, but unfortunately none worked. FWIW, although all images load on my browser on my main instance (lemmy.zip), and many fail in the app, switching to this lemmy.world account caused the image from the same post to load in the app without issue (using the flutter user-agent)

[–] Coelacanth@feddit.nu 25 points 1 week ago

Love the app, thank you for the continued development and being so in touch with the community ♥️

[–] Blaze@piefed.zip 19 points 1 week ago (1 children)

Thank you for your work, enjoy the holidays!

[–] idunnololz@lemmy.world 14 points 1 week ago (2 children)

Thank you! You too!

[–] rescue_toaster@lemmy.zip 4 points 6 days ago (1 children)

I'm still getting some missing images, the 500 error I think?, and eventually the 400 bad request error after scrolling way down my feed.

[–] idunnololz@lemmy.world 3 points 5 days ago (1 children)

500 errors are typically not caused by the client but instead indicate a server issue. Also, the new update only changes the default user agent. If you have changed the user agent manually via Misc > User agent in settings then this update will not change anything. You can try out changing the user agent yourself to a different one to see if it fixes the issue.

[–] rescue_toaster@lemmy.zip 1 points 5 days ago* (last edited 5 days ago) (2 children)

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.world 3 points 4 days ago* (last edited 4 days ago) (1 children)

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.

[–] Demigodrick@lemmy.zip 1 points 4 days ago (1 children)

Just FYI the 10 page limit is an issue with lemmy 0.19.4.

https://github.com/LemmyNet/lemmy/pull/6252

Some instances will have deployed their own fixes but most instances on this version will have this big/change

[–] idunnololz@lemmy.world 1 points 4 days ago (1 children)

Huh. I must have gotten lucky when I checked since all of the instances I tried didnt have an issue. I tried lemmy.ml, lemmy.world and lemmy.ca.

[–] Demigodrick@lemmy.zip 1 points 4 days ago

.ml is on .15 beta, .ca is on .13 still, and .world have a custom patch in place ☺️

Does look like you'll have to update the method based on the comments on github though (not that I understand it all that well)

[–] idunnololz@lemmy.world 1 points 5 days ago

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

[–] Blaze@piefed.zip 8 points 1 week ago

Thanks!