Thread caching

Forgive me if this has already been answered but I couldn't find it with the forum search.

When you open a thread in the forum that has any decent length, you only get the first few posts actually pulled in to your browser, if you want the rest you need to scroll. Even then, a search from the browser fails to find the text as it seems to unload from the browser.

If you open the link I provided and search from your browser for "wireguard" you will find the first 11 mentions in the opening post. When in fact it mentioned in 15 different posts.

I'm not advocating for a particular position on this, yet.
Is there a way to stop this caching behaviour, either from the users end or from the forum administrator end?

I went to that thread, put "wireguard" in the search box, and got 15 hits directly, using Brave.

Perhaps try a different browser?

Which search, the forum's search or your browsers one?

The forum search will find 15 posts with the word 'wireguard' in them.
A browser search I would expect to find more than that as several posts will have 'wireguard' in there multiple times.

Forum. Browser search is pretty much unusable on a tablet where the keyboard is not there most of the time.

Yes, it sucks because Discourse implements "infinite scrolling" and only renders a few posts at a time, removing the rest from the browser's DOM when they get out of view. You'll have to use the search function of the forum, which is much worse than the "Find on page" feature of the web browsers.

This will not change unless MikroTik changes the forum software. We've tried to tell them about that many time in this huge thread Migration process from our old phpBB instance to Discourse is now done - Site Feedback - MikroTik community forum. But they still proceeded with the migration.

Thanks for the explanation. I learnt a bit. What an infuriating "feature".

What was "wrong" with phpBB? OK, I got used to new forum, at least a bit now, but tbo, all it did to me, it looks more chaotic.

This explains why Ctrl+F does not work reliably here.