this post was submitted on 17 Nov 2025
77 points (100.0% liked)
Voyager
7523 readers
23 users here now
The official lemmy community for Voyager, an open source, mobile-first client for lemmy.
Rules
- Be nice.
- lemmy.world instance policy
Sponsor development! 👇
💙
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I’ve heard of the double back bug (from a post it goes back to the communities list in one swipe) but I’ve never been able replicate it myself.
It anyone has good replication steps please lmk!
If the community side bar could be opened and closed without it refreshing the feed (overlaid instead of a screen change), then the bug would be less of an issue because the impact would be greatly reduced.
If the app thinks the app button is being pressed twice, then the app would just close instead of going to the communities list, so that wouldn't solve the problem. I need to get the the root of the problem with a reproduction in order to fix it.
Maybe, but I think many people would like the ability to do this regardless of the bug 😅.
Me too. I’ve personally never faced the bug you’ve mentioned myself but I do sometimes accidentally end up opening the communities sidebar and end up losing my place in the feed because I can’t just dismiss the sidebar. I have to select something and that will end up refreshing my feed. If we could just have a close button on the sidebar that would help immensely.
What if there was a setting that would make a toast message come up “swipe again to close feed”?
It would only activate/apply if the thing to swipe to is the communities list.
I’d have to do some testing but that wouldn’t be that hard to implement.
Not sure I fully understand. Did you mean swipe again to close feed or sidebar ? Just to be clear, what I’m looking for is a way to NOT close/refresh feed but to just dismiss the sidebar.
I also didn’t fully understand the proposed solution. Are you saying that there already exists a way to do it now and all that is required is to show a toast to educate users on how to do it ? If so, I’d be happy to try that solution and see if works and if it does, showing a toast would certainly help. Or are you saying the default behaviour needs to be changed and the toast is just a bonus to let users know about the change ?
I have that happen sometimes when I hit the back button whilst looking at a picture fullscreen.
other times just randomly..
any way to add an option to save your reading place in the feed by default and just a pull down to refresh?
really sucks sometimes when you're a few ~~hrs~~ mins scrolling deep only to have it start from the top.
It definitely happens random or after a certain amount of time. Are there any logs produced that could help identifying the probkem?
No logs for something like this.