mirror of
https://github.com/MCV-Software/TWBlue.git
synced 2026-10-16 02:06:52 +02:00
Jesús Pavón AbiánandClaude Opus 5
0e5a75048a
Thread buffers rebuilt themselves from scratch on every refresh with no deduplication and no guard against overlapping runs, and the list control was mutated from the update timer's background thread. Threads opened from the same account also shared a single session.db entry, because the buffer name was derived from the author instead of the post. - Name conversation buffers after the post URI, and navigate to an already open thread instead of opening a second buffer for it. - Deduplicate thread items by URI, and refuse a refresh while one is in flight. - Move the clear-and-fill step onto the GUI thread via wx.CallAfter. - Stop start_buffers() from starting a buffer that create_buffer() already started, since needs_init was never cleared. The direct messages list never focused an item after being rebuilt, so its position was announced as "0 of 1", which cannot exist. The conversation list now focuses an item whenever it cannot restore the previous selection, and the buffer navigation announcements no longer report a position while nothing is focused. Verified against the live Bluesky API that app.bsky.feed.getPostThread itself returns no repeated posts, so the duplication was entirely on our side. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>