Is there a way to skip to the bottom of my feed on the "all messages" tab? I only pop into Zulip once in a while, and there's always a ton of new messages. The only way to see the latest ones is to scroll to the bottom, which is very slow because you have to scroll through every message, and wait for each block of messages to load before you scroll through them.
yeah its a problem
its even worse on mobile devices. Its probably my biggest complaint with Zulip (and I'm a fan)
I figured out I can mark all messages as read, and then it reloads and does skip to the bottom
on desktop, the chevron by the "all messages" link on the left has a "mark all messages as read" button - i think that also forces you to the bottom?
lol you posted it as i was typing
Does that exist on mobile? The android app at least seems pretty limited. I couldn't even figure out how to open a new topic
If the feed on a topic is too long, I do get a faded bottom pointing arrow in the bottom right corner of the Android app. That scrolls all the way to the end of the feed.
I am also in zulip beta, not sure if that's the reason I get it ?
I get the arrow on iOS, but it only scrolls to the bottom of the messages that are currently loaded (I have to hit it many times to go through weeks of messages)
is any part of zulip opensource by any chance?
I am tempted to just make a different client that is actually usable
the data model is probably fine, it's the UI and UX that make it worse than many other things for me
so this is it? https://github.com/zulip/zulip-mobile
I wonder if these issues are caused by React Native or by the Zulip Mobile app code
So I had thought the
End key was supposed to do this, based on the Help message that comes up when I hit
but @eddyb has pointed out that in a search query with a large number of unread messages (or that have not been otherwise locally cached), the
End key seems to first:
1. take you to the end of whatever is currently cached, and then
2. load a few more messages (maybe a dozen? Not sure)
and so you have to hit
End repeatedly to actually get to the end (or manually scroll)
This seems like a bug to us. Is there any reason for this behavior? Perhaps the search is performed locally on the client, so its not feasible to jump to the true end since an arbitrary amount of content must be loaded first?
If you file a issue w/ Zulip, mention that it is from Rust, they have a label for tracking our requests.