This update adds Lemmy v0.19 (the latest version of Lemmy) support to the app. It also adds a number of user settings. There were more settings planned for this release but with the announcement of v0.19, I decided it was safer to cut the release now and add support for v0.19 as the latest lemmy update breaks a lot of stuff with old clients.
Changelog
- Added toggle to enable/disable Firebase Crashlytics
- Fixed a crash when loading certain posts containing spoiler tags
- Added toggle to the video player to enable auto-looping
- Added a setting to auto-collapse comments based on upvote percentage. This is enabled by default at 30%. Comments with less than 10 votes are exempt. Eg. if a comment has 10 upvotes and 20 downvotes, this is a upvote rate of (10 / (10 + 20)) = 33% and thus would not be collapsed. If a comment has 10 upvotes and 40 downvotes, that is a rate of (10 / (10 + 40)) = 20% and thus would trigger the auto-hide threshold.
- Added a setting to enable/disable the browsing history. The default is on.
- Updated app to be compatible with Lemmy v0.19.
- (v0.19 only) Added new sort orders for posts: controversial, scaled.
- (v0.19 only) Added support for server-sided instance blocking.
Update
Update is submitted to the playstore. Will test and roll out in the next couple of hours if no bugs spotted.
Update 2
Fully rolled out.
Hmm I can’t actually reproduce this issue. I’ve tried two different devices just to be sure and I’ve also tested the latest version downloaded directly from the play store. Do you have an account signed in?
Also, when you say the settings revert back to “Default” does this happen to both post sort order and comments sort order?
I’ve just tried it again after clearing the cache within the app, and also from the app info, & now the comments sort maintains the sort option selected (New), & Post sort reverts to display Default within the settings, after selecting New. As my account setting sort default is New anyway, I’m guessing that could be the reason?..it is sorting as I’d expect… Sorry if I’ve sent you down a rabbit hole…😬
Np. I’m glad you were able to fix the problem. I’m making the code for that setting more resilient in the next update. It will probably reset your sort order back to default when the next update comes out however it should no longer revert back when you leave settings.
Thanks for looking into it 👍🏻
BTW, Really liking the multicommunities option, it’s really handy for grouping similar communities across different instances…