One of the most useful features of Summit is the ability to filter the post feed so that only unread posts are shown. This feature was known as hide read.
Although hide read did it’s job, it was a confusing and sometimes annoying feature to use. It was halfway between an action and a toggle. When hide read is tapped, all read posts are hidden like which behaved like an action. However, when new posts are loaded, any read posts that are loaded will be omitted. This is where *hide read& acted like a toggle.
When a user refreshes the list (eg. pull to refresh), hide read disabled once again.
Long time Summit users might be used to how hide read works but it’s definitely not an intuitive feature.
This update adds a toggle next to hide read adding new behavior for hide read. If the toggle is turned on, unread posts will always be hidden when posts are loaded even if the user uses pull-to-refresh.
Then the hide read toggle is on, an indicator will be shown to let the user know that only read posts will be shown. The indicator can be tapped to turn off hide read.
This update also fixes several bugs and continues to improve upon the performance of the app.
Full changelog
- Add new FAB long press action to toggle hide read.
- Add a setting to finish the app when closed. This setting only has an effect on Android 12 and up. When this setting is enabled with Predicitive Back, the app will close on single back press and it will finish. Note that due to implementation conflicts with Precitive Back, the normal Predicitive Back animation will unfortunately not be played.
- Add setting to show navigation bar in post screen.
- Add new layout type: smart list. Smart list uses the list layout for non image posts and the large list layout for image posts. This mimics the default layout on Reddit.
- Change hide read to a combo button: a button on the left side that works like the old hide read effect and a switch on the right side.
- Change the behavior of double tap to close to use the system default closing mechanism. On Android 11 or below, this change will have no effect. On Android 12 or up, the app will be moved to the background when double back pressed. This makes the app back press behavior consistent with the system.
- Change the behavior of reselecting the home screen in the bottom navigation bar. Previously reselecting the home screen when the home screen was scrolled would reset the home screen. This meant certain state would be lost (eg. hide read state). After this change, reselecting the home screen will scroll the user back to the top of the screen.
- Change Hide duplicate posts as read to also mark the post at read on the server.
- Improve startup time of the app.
- Optimize how the app generates default avatars.
- Minor improvements to the create post screen.
- Greatly improve the performance of “emoji images”.
- Fix a bug where if you launch the app with no internet then the app will continue to show a no internet error even if internet is re-established later.
- Fix a bug when editing a comment where the old comment is shown instead of the new comment
- Fix a bug where the wrong image is shown in the post list.
- Fix a bug where the custom font is not applied to post titles if Prefer title text is on.
- Fix a bug where the custom font is not applied to community names/usernames.
- Fix a bug where the navigation rail would show when it shouldn’t
- Fix a few crashes that can occur in rare cases.
- Fix a bug on web settings screen where unsaved changes warning is shown even if changes are saved.
- Fix a bug when trying to sign in with a password longer than 60 characters on a Lemmy instance. Lemmy truncates all passwords to 60 characters. If you set a longer password, it doesn’t actually use your entire password, only the first 60 characters. To prevent confusion, the client will truncate the password it sends to the Lemmy server to 60 characters so that you can continue to sign in with passwords longer than 60 characters.
- Fix a crash when network is unstable.
Update
Found some bugs with the release. Fixing and releasing as v1.69.1.
- Fix a few crashes that can occur in rare cases.
- Improve startup time of the app.
Update 2
More bug fixes:
- Fix a bug that causes the wrong image to be shown for a post.
Update 3
More small changes incoming:
- Optimize how the app generates default avatars.
- Change the behavior of double tap to close to use the system default closing mechanism. On Android 11 or below, this change will have no effect. On Android 12 or up, the app will be moved to the background when double back pressed. This makes the app back press behavior consistent with the system.
- Add a setting to finish the app when closed. This setting only has an effect on Android 12 and up. When this setting is enabled with Predicitive Back, the app will close on single back press and it will finish. Note that due to implementation conflicts with Precitive Back, the normal Predicitive Back animation will unfortunately not be played.
- Fix a bug on web settings screen where unsaved changes warning is shown even if changes are saved.
- Fix a bug when trying to sign in with a password longer than 60 characters on a Lemmy instance. Lemmy truncates all passwords to 60 characters. If you set a longer password, it doesn’t actually use your entire password, only the first 60 characters. To prevent confusion, the client will truncate the password it sends to the Lemmy server to 60 characters so that you can continue to sign in with passwords longer than 60 characters.
- Minor improvements to the create post screen.
- Change the behavior of reselecting the home screen in the bottom navigation bar. Previously reselecting the home screen when the home screen was scrolled would reset the home screen. This meant certain state would be lost (eg. hide read state). After this change, reselecting the home screen will scroll the user back to the top of the screen.
- Change Hide duplicate posts as read to also mark the post at read on the server.
- Add setting to show navigation bar in post screen.
- Add new layout type: smart list. Smart list uses the list layout for non image posts and the large list layout for image posts. This mimics the default layout on Reddit.
Update 4
Doing a release as v1.69.3.
Update 5
Doing another release as v1.69.4.
- Greatly improve the performance of “emoji images”.
- Fix a crash when network is unstable.
Very nice, more features!
Question though, I seem to be having issues with the video player, 95% of them just show a black screen, even though the time is moving. Play pause etc works, but no image. Having searched here ane on github, I can’t seem to find any other mentions of this, am I missing something obvious?
Can you post an example to a video that refuses to play?
Sure, first one in the feed: https://sh.itjust.works/post/43865576
If I managed to link, that’s how it looks when “playing”.
Also, I should note that sound works, and if I enter the link proper the videos, sofar seem to work, it seems sofar to be just the preview, or what you’d call it, playing from the feed itself.
I can’t reproduce this one at all. If anyone has any additional information on how to reproduce this, please let me know.
Since you didn’t have any issues, and as mentioned I’ve yet to find any other mentions I started playing around with settings incase some unlucky combination were the culprit. After trying a bunch of different things, it worked when switching from compact to list feed mode. After that, it also kept on working after switching back to compact again.
Iöm fairly sure that was the only thing in that go, but it was after 20 or so minutes of fiddling around with it. For now it works so, that’s something.
Hmm that is so weird.
Sorry, seems I got over eager, the real fix was the fully dim read posts. When it’s enabled, the video is blacked out completely (dimming video issues?). Disabled it works fine.
Wow! Great work!
Could we have an option to make the “Hide Read” switch permanent, either globally in the settings or per community in the FAB? It now seems to reset after closing the app, not sure if this is intended or a bug?
Thanks for adding this feature and for all the great work you do!
This is the intended behavior. I’ll add something to the roadmap to force it to always be on.
Thanks! For contexts, this is one of the last features I’ve missed since moving from Sync. I often refresh my subscribed/all posts after reading for a while—still chasing that dopamine hit for new content—and end up with lots of read posts back in my feed if I forget to toggle the switch, which is still a lot better than constantly bashing the hide read earlier 🙂
Thanks
Eyy you worked out the wrong image issue. Thanks!
Lol. So my blind “fix random stuff” worked I guess haha.
Making a lot of progress, any chance you can add a preference to not double back to exit?
=)
If you are using a newer version of Android, Summit has a setting to use predictive back instead of double tap back to exit. In Summit, go to Settings > Misc > Use predictive back.
Which is cool, I’d still just like to exit.
If you enable this setting, the app should close on one back tap.
It doesn’t exit, it just moves to background.
I just tested Predictive back and I can confirm it does exit the app. I’m not sure what you mean by “It doesn’t exit, it just moves to background.”
If you hit the app icon again, it’s already running, just shows you where you were in the app just like moving it to the background (because this is what it does).
I want the double back to exit functionality to preferentially be single back to exit.
Not just moving the app to the background.
So it saves your state but it does exit the app. I verified this on my end. Double tap to exit should also be saving your state. The two should be using the same mechanism to exit.
I think that is system behavior. There isn’t any special code in Summit to move to the background on back press as far as I’m aware.
Just to make sure I understand, you want a feature where Summit kills itself when back is pressed? I think this is a completely different feature from the one you requested.
Double back does it, so this is a feature of the app.
