Might switch away from #pachliapp, it's got some weird quirks with the feed and I can't seem to see my notification count
Discussion
Loading...
@Inkstainthebat What sort of quirks?
@pachli Wow, thank you for responding!
The main thing that's been happening is that when re-entering the app I end up in an earlier part of the feed, which *then* updates and clunkily scrolls up a seemingly random amount. But about the notification thing that also seems to be an issue Tusky has...
Either way I'd be glad to check out the app again so I can report something more in-depth somewhere better ^w^
@Inkstainthebat When it's scrolling as you describe, is it scrolling to where you'd previously left off, or does it seem to go somewhere random?
Can you reliably reproduce this problem?
@pachli
Most often it's where I left off, although sometimes it seems to scroll to somewhere above or below it.
Either way I found another similar problem that I can reliably reproduce and describe in detail: during a tag search after getting beyond a certain point (the first time the feed had to load more results) every time I left out of a thread it resets all the way back to that point. I only found this after the first response
@Inkstainthebat The first behaviour is just how things work at the moment I'm afraid. The Mastodon + Google APIs don't let Pachli say "Give me the posts the user was last looking at", Pachli has to load around where you were, then go hunting in the list to restore your reading position. Normally this is very quick, but slower devices/servers can give the UX you see.
The search problem is a Pachli bug. That whole part of the code needs rewriting.
@pachli good to know the 2nd (more significant bug) is on the Todo list. About the first problem, I'd be fine to just have the timeline start at the latest posts up top instead of automatically where I last left off