NodeBB search not finding content

[grahamperrin]

grahamperrin said:

… searching within a page (Control-F) is very weird, I can not yet understand what's going on.

Part of the disorientation is when content can not be found.

For example, the third paragraph of https://billboard.bsd.cafe/post/https%3A%2F%2Finfosec.exchange%2Fusers%2Ftinker%2Fstatuses%2F116340133804624101 (Mastodon original: https://infosec.exchange/@tinker/116340133804624101) begins with the word:

Nextcloud

BSD Cafe Billboard can not find the word:

@stefano does something in or around NodeBB needs a nudge? Or is this, maybe, a limitation of NodeBB?

Thanks

Cc @ciotbsd @tinker@infosec.exchange

[stefano]

I'm not sure about it. I'll check. Thank you for pointing it out!

[grahamperrin]

Thanks.

I began understanding a little of the complexities.

In response to Control-F:

When I first saw that, I assumed that it was debris from a previous search. On closer inspection, the string is:

in:topic-a503d113-b4b7-4765-8862-15b9912e51d7

– with a space at the tail.

So, I can type Nextcloud then key Enter, the resulting page is https://billboard.bsd.cafe/search?term=in%3Atopic-a503d113-b4b7-4765-8862-15b9912e51d7 Nextcloud&in=titles with the word not found.

If I change the search context from In titles (the default) to In posts, then search results comprise this post alone.

I guess, remote content is not indexed.

Also, for NLI (not logged in) users, the word is not found at the Mastodon instance:

https://infosec.exchange/search?q=Nextcloud&type=statuses

[grahamperrin]

Not a showstopper, as far as I can tell.

If I use the File menu of Firefox to Find in Page… Ctrl+F – without using the keyboard shortcut – then a match is found but may be invisible, and Control-G advances to the next match.

In the screenshot below, the matched word is not either of the pink highlights. The match should be visible with a green highlight.

It's weird, but usable.