Welcome to the v1.57.0 release. This release is focused on addressing the rest of the user requests.
There’s a lot in this release so read through the changelog to see everything that has been added. Some highlights include adding auto-loading posts when “swipe between posts” is enabled, a new setting that allows you to change the app locale from within the app on any version of Android and some changes to make it easier to identify if an user is new to Lemmy.
This release also marks the start of some major changes to the app that I’ve been considering almost a full year ago.
One of Summit’s strength is the insane number of customizations available to a user. However this also poses a downside as new users may not want to spend hours checking and tweaking every setting. While Summit tries to make sure the default settings are pretty good, it’s obvious that the out-of-the-box settings are not for everyone.
The ideal middle ground is to offer a list of sane defaults, not just one. That way new users can setup the app to their liking while taking only seconds. This is what the next big feature will be aiming to solve.
I’ll provide more details regarding what these specific changes are over the next few releases. As always if you have any questions or suggestions please let me know in the comments.
Full changelog
- Add a setting to choose the direction of swipe gestures. By default this is left-to-right.
- Add a setting to change the default volume of the inline video player
- Add an option to share a community/instance in the community/instance screen.
- Add a setting to choose default app to open URLs with. By default Summit will open URLs within the app however setting a default browser will override this behavior.
- Add a setting to change the locale of the app.
- Add a setting to control whether community suggestions are shown in the community selector bottom sheet.
- Add a setting to enable/disable full bleed images in the full post view.
- Add an option to the “Take screenshot” screen to share the screenshot instead of saving it.
- Change the formatter for post titles. If a post’s title starts with the character ‘#’, it will be escaped. This fixes some edge cases where a post starts with a “hashtag”. Eg. “#summitforlemmy is an ok app for lemmy”.
- Fix a bug on the create post screen. If the webpage (based on the URL field) of a post does not have a valid title, the title will not be suggested.
- Update the design of the user info screen.
- Fix a bug where the settings page will not respect the app language if one is selected.
- Change the app behavior when handling posts with invalid thumnails. In rare cases the thumnail url and the url of the post are the same but the thumbnail url does not link to an image. Previously this would cause the app to not show the image or the link. This release changes the behavior so that the link will be shown in this case.
- Automatically load more posts when the end of the post feed is reached when “swipe between posts” is enabled.
- Change the default of the setting “Show new user tag” to true. New users (accounts that are less than 30 days of age) will display a yellow tag next to their account name.
- Fix a bug where sharing an image would not show a preview of the image being shared.
Update
Noticed some bugs in the app. One major bug is the inability to change the app base theme. Will push a fix out as v1.57.1.
- Fix a bug where the base theme setting is ignored.
- Fix a bug where some shadows are being clipped.
- Adjust default screenshot width from 500 -> 360 since 500 seemed too wide which produced smaller text when fit on screen.
Update 2
Found a crash so will update the release and release as v1.57.2.
- Fix a crash in rare cases when viewing the default apps settings screen.
Update 3
Rollout complete.
Can we also have the ability to turn off swipe gestures?
There is a setting to do this in Settings > Gestures. Let me know if it’s missing something.
I meant the one that closes a post
Oh I see. Just to make sure im addressing the underlying problem and not the “symptoms” what is purpose of this gesture? Eg. You can easily just not use the gesture instead of disabling it. Is there some negative of having it be enabled?
No big deal, it’s just sometimes it works, sometimes it doesn’t (I mean in some places of the app) and I’m using gesture navigation anyway so I find it kind of unnecessary. If it’s a hassle, there is no need to bother with it, it’s not an issue by any means
Hey, I was wondering if the ui elements for videos could be automatically hidden when the play button is pressed?
Also, not as important, click anywhere on player video to play/pause is another idea.
Thanks for the awesome work you are doing, summit is the best!
deleted by creator
Would it be possible to add a save button toggle on the post appearance? Something like this, where I’ve illustrated my amazing art skills to show where the save button can go?
Added to the roadmap.
I’m the annoying guy that asked about the share screenshot function (thank you by the way!) is it possible to add a toggle to the 3 dot menu as well so you don’t need to click on the post first?
It should already be there.
It’s there when I go into the actual post, but not from the main feed
Ah I see. I’ll add a roadmap item. To clarify you want to be able to take a screenshot from the post feed screen and share/save it right?
Just wanted to say I love this app. Your effort for the countless wishes and configurability is amazing!
Hi, I am getting some issues with the version 1.57.2
It seems like the client is struggling to hide read posts and showing up comments in the posts (it prompts me with a retry button that does nothing).
I tried to force close the app and clean up the cache without any luck.
I am unfortunately unable to reproduce any of the issues described. Could you please DM me an export of your settings? Can you also explain what “struggling to hide read posts” means? Is the app lagging or is it something else?
Sure, I’ll DM them!
What I meant with hiding the read posts is that it seems to only hide them once, or just in my 1st opening, if I refresh the app and try to hide them again with the float button (custom action set to hide read posts) will just show a loading ring quickly but do nothing.
About the comment section, I just get this error.
At first I thought it was an instance issue, but it seems that everything is working normally in other clients 🤔
I figured out the issue. There’s actually 2 issues combining together most likely.
The way “mark as read on scroll” currently works is it makes 1 api call everytime you scroll past a post. If you scroll a lot or very fast it will cause a rate limit error. This is probably why hide read seems to work so flakely for you.
The second issue is that the client does handle rate limit errors originally however it seems that somewhere in the past 2 years the way these errors present themselves has changed. This is why you see unknown error instead of a clearer error message.
Unfortunately there doesnt appear to be a great way to do mark on read on scroll at the moment. It looks like the dev of Lemmy has added an aggregate endpoint for mark as read however its planned to release as part of v1.0.0 which js not out yet.
As a temporary workaround you can disable mark as read on scroll while I look for other solutions.
Thank you for your research!
Why this started in the latest version though?
I have been using Summit exclusively for my mobile Lemmy browsing for months now and haven’t found any issues (despite the numerous updates and fixes that you have deployed) until this very version.
That is odd. I can look into if there is something that is causing the client to make more API requests than usual.
Hello, I have the same problem using lemm.ee instance. Seems they had downtime and it might have something to do with bot checks? I cannot seem to connect to my instance using your app and even using the different front ends for the web page.
Post here - https://lemm.ee/post/58524674
I’ve been trying to reproduce this issue on my lemm.ee test account but I haven’t had any luck so far. Can you clarify if nothing loads at all or if you just need to retry a lot?
Thank you I’d really appreciate, likewise, if you need more info I am here.
I didn’t find any other issues.
In my test you had to scroll really fast to hit the API limit. When you experience these issues are you scrolling pretty fast or do you get them even when you are going down the list slowly?
