Next channel is slow and shows nothing: one press should show the first text

littlefox commented

2026-10-18 09:57:05 +00:00

Owner

User, testing on Android against kom.lysator.liu.se: "When first logging in the app says something along the lines of 'To start reading, press the button below (or press space)' but doing that nothing happens. The button is called 'Go to next conference' and is terribly slow, making the user think nothing is happening."

Cause: entering a conference recounts its unread texts from scratch twice, once in Kom::enter_conf (self-heal) and once in the UI (unread_count), paging local-to-global 100 texts per call, before anything changes on screen. After all that, only a status line changes; a second press is needed to see a text. The button gives no sign that it's working.

Fix: use the cached count and recount in the background; show the first unread text on the same press; show that the button is busy.

User, testing on Android against kom.lysator.liu.se: "When first logging in the app says something along the lines of 'To start reading, press the button below (or press space)' but doing that nothing happens. The button is called 'Go to next conference' and is terribly slow, making the user think nothing is happening." Cause: entering a conference recounts its unread texts from scratch twice, once in Kom::enter_conf (self-heal) and once in the UI (unread_count), paging local-to-global 100 texts per call, before anything changes on screen. After all that, only a status line changes; a second press is needed to see a text. The button gives no sign that it's working. Fix: use the cached count and recount in the background; show the first unread text on the same press; show that the button is busy.

littlefox added the

area/ui

area/reading

kind/bug

labels

2026-10-18 09:57:05 +00:00

littlefox referenced this issue

2026-10-18 10:09:25 +00:00

Confusing app settings #97

littlefox referenced this issue

2026-10-18 10:11:30 +00:00

HTTPS mode for the Docker image (installable app on the home network) #98

littlefox referenced this issue

2026-10-18 10:17:51 +00:00

Thread view: a whole conversation at once #99

littlefox referenced this issue from a pull request that will close it,

2026-10-18 11:17:58 +00:00

One press shows a post: entering a channel reads its first one #108

littlefox referenced this issue from a commit

2026-10-18 11:18:00 +00:00

One press shows a post: entering a channel reads its first one

littlefox referenced this issue

2026-10-18 11:41:59 +00:00

Soak: a reconnect once stalled over 30 s at 'Återansluter…' #109

littlefox closed this issue

2026-10-18 11:42:01 +00:00

littlefox commented

2026-10-18 11:42:02 +00:00

Author

Owner

Merged in #108. Verified: tools/e2e.sh 169/169 (desktop, Android, iPhone); CI run #176 green; clippy native+wasm clean; devserver tests pass. Entering a channel now shows its first post on the same press, uses the cached count (recount runs in the background afterwards), and the button gets a spinner after 300 ms.

littlefox referenced this issue from a commit

2026-10-18 17:38:14 +00:00

Thread view: read a post in its whole conversation

Rows
Columns

Next channel is slow and shows nothing: one press should show the first text #96