Skip to main content

Weird search behavior

Bug Reports

I’m confused as to how search works. When I type rdr, I expect both rdr and rdr2 to be returned. So it seems to search for whole words, rather than fuzzy search.

Same deal here. But then when I start removing letters it does keep showing the partial search result.

But then below it does seem to be doing a fuzzy search… but also it searches for independent words it seems, rather than the full query.

It would be nice if rdr returns both rdr and rdr2 and power surge returns power surge and power surges, but not power(s) or surge(s) independently.

Also when typing something that doesn’t return any results, I kind of expect it to show some sort of a not found state. Hope this helps thank you so much!

4 comments

This request was merged into another request

Comments4

  • Magenta Andromeda

    I am going to add to this comment rather than post something new, but I came to understand some of the odd behaviour i was noticing while using the search feature that hopefully can be resolved.
    My current understanding of how text input is handled for search is as follows.

    (numbering indicates the number of characters entered into the search field)

    1. do nothing, display the entire list of chats chronologically

    2. same as 0.

    3. same as 0.

    4. all chats removed from list unless an exact 3 letter word is matched

    5. begin matching against partial strings as well as whole words

    6. (and onward) same as 4.

    Caveat: The above holds EXCEPT for when a whole word can be matched against the entered text. This will match to words like ‘we’ or individual characters like ‘a’ (or ‘c’ when asking about programming). Additionally, the search presumably treats punctuation as a word boundary in all cases, so searching for a single character ‘s’ will return results that are matching to the ‘s’ of a word (noun) written in possessive case (ie. Theo’s)

  • Blush Cascade

    I understand that the search functionality is crucial, and while I don't use it frequently, my experience has consistently been inconsistent and unintuitive.

    As other users have already pointed out, I believe that adding feedback messages would be extremely valuable. Phrases like 'No results found' or 'Searching threads...' would prevent the uncertainty and frustration of not knowing whether the search is failing or just taking time.

    Today, when attempting to use the search, I noticed that it initially appeared completely inoperable, returning no results for any query, even for my recent or pinned chats:

    Curiously, just as I was about to document the failure with more captures, the functionality suddenly began to work. This intermittent behavior reinforces the need for clear visual feedback on the search status.

    The Cmd+K shortcut seems to exhibit the same problem. Initially, it showed no results and took a while to sync. Even after the sidebar search started working again, the Cmd+K search remained unresponsive for a while before suddenly beginning to work.

    In summary, the introduction of status indicators (such as 'Loading threads' or 'No threads found') would resolve the current ambiguity and significantly improve the usability and perceived stability of the search functionality.

  • Crimson Watermelon

    Echoing this. For all the shit that some T3 managers love giving other chat apps for their ux, I’m surprised this one is still in the app.

    I needed to look up an old thread involving renewing a certificate for my job. So I went to search “cert”

    Couldn’t find anything, started losing my mind.

    Turns out I needed to search “certificate”????

    • Crimson Watermelon

      Was this issue fixed in one day?? Holy shit.

      To everyone at T3, I owe you an apology. I wasn’t really familiar with your game.