Keyboard accessibility is second to Weechat. Weechat responds instantly to all keypresses and never leaves janky UI on the screen. When reading Zulip threads I

Keyboard accessibility is second to Weechat. Weechat responds instantly to all keypresses and never leaves janky UI on the screen. When reading Zulip threads I frequently mute those I'm not interested in. To do so, you have to hit 'i' to open a menu, then 'M' (there is no shortcut on 'm'), then a popup message slowly animates in saying the thread is muted. If you hit 'n' to go to the next thread, the popup message doesn't clear, so it's covering the top message of the new thread, and the popup menu is still open covering the top 1-3 messages, still listing the last thread's title. So leaving a single thread I know I'm emphatically not interested in takes five seconds. There's a nasty positive feedback loop: catching up on threads is slow and frustrating, so I leave it longer, so there's more threads that take even more time and frustration, repeat. I reported this buggy workflow ~2 years ago and it's why I've repeatedly given up on a very interesting community's Zulip chat. There's plenty more flaky stuff, like switching messages with j/k sometimes not scrolling the screen, or long messages where you have to take your hand off the home row to scroll up and down because if you hit space the floating nav covers lines you haven't seen, long messages being "closed" so you have to navigate to each individually to read, no keys are customizable, death by a thousand cuts. I have my fingers crossed for a bitlbee integration.