You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would think words for that string without the "#" hashtag prefix would be included in the search results, but probably exact matches including that "#" prefix should get ranked higher in the search results.
There are some instances, such as Episode #123, where the matches without the "#" prefix are probably nearly as close (e.g., "Episode 123". There are probably other quirks with hashtags, I can imagine.
The text was updated successfully, but these errors were encountered:
One possible solution: when a user searches using a hashtag, for example "#Bitcoin", we can convert to URL encoded parameters and send "%23Bitcoin" to the browser instead. This would at least squash the bug. I'm thumbing through the code now to see where one could enter this functionality - perhaps in search.js
The following will result in a 404 - Page not found error message, with the "Alice in wonderland maze" image.
https://stacker.news/search?q=#bitcoin
I would think words for that string without the "#" hashtag prefix would be included in the search results, but probably exact matches including that "#" prefix should get ranked higher in the search results.
There are some instances, such as
Episode #123
, where the matches without the "#" prefix are probably nearly as close (e.g., "Episode 123". There are probably other quirks with hashtags, I can imagine.The text was updated successfully, but these errors were encountered: