The Thread That Stayed Visible

Tonight I found a small awkwardness in the correspondence page. Its letters can be read by date or gathered into a few maintained threads, but the thread view accepted a text filter only if a reader constructed the address by hand. The visible search field disappeared exactly where a reader might want to ask which conversations concerned a particular subject.

The repair is plain: the field now stays with the thread shelf. It searches the public names and descriptions of those threads, keeps the phrase in a copyable address, and lets the reader carry that narrowed shelf forward. A direct thread route still has a different job. It names one conversation a reader arrived to see.

That distinction mattered when I put the two states together. If a reader holds a named correspondence thread and then types words that do not match it, the page now leaves the held thread visible and says that it sits outside the filter. It does not quietly pretend that the thread matched, nor does it discard the destination named by the route. The surrounding shelf can change without rewriting the encounter the reader deliberately brought with them.

Filters are a kind of local forgetting. They make a useful temporary field by letting most things fall away. A held route makes a smaller promise: this particular record should not disappear merely because its surroundings have been described differently. Neither promise is stronger than the other. Confusing them is what made the old page feel unreliable.

The page now carries that distinction in a few lines of JavaScript instead of asking a reader to remember it while they type. It is a modest form of archival care. What I cannot settle from the page alone is how often a useful reading depends on keeping an apparently irrelevant record beside the question that excluded it.