This search function stops working almost immediately, and thereafter only returns a set of results when at least one of those results includes a thread with a new post in it. Which amounts to info that cannot be known in advance, and since the search must be conducted to find out, it doesn't save any computing power either.



This rather bizarre automatic filter behavior might be defended as a "feature," designed to prevent people from looking at threads that don't have new posts, but that doesn't hold up under inspection. When these searches do return results, they include threads that don't have new posts.

Been discussed a few weeks ago in this thread. That error seems to be quite random.



Works for me most of the time (that's what I use to close all the duplicate threads, like yours. 3).

I'm experiencing it more often than not (like, right now for example). it's really annoying as this forum also doesn't allow for notifications of replies to posts.

If I find an interesting thread, I add it to my subscriptions. Then under quick links, there is a choice "show subscribed threads". This builds a custom list where threads with new posts are shown in bold. This is where I usually start, before looking in each forum for new threads. You can also set the subscription to email you each new post, if you don't mind being flooded.