Eh, I don’t think it’s that surprising. Getting a list of comments on a post vs getting them from a search term are very similar operations, so it doesn’t make too much sense for these to have different queries in the backend
Sure, but one would have thought that the ordering in a search is fundamentally different from the ordering in other places. Because you want something that contains the words you've searched for near each other to appear ahead of a post that has those words scattered at random because it's a 500 word essay. You want exact word matches prioritised ahead of entirely unrelated words that include the same characters. Like "enum" should turn up your comment, but rank a comment that contains the text "renumbers" much more lowly. A particularly smart search page might keep "enumerate" high while rejecting "renumbers", though.
Of course, it's true that at least in the current latest release, Lemmy fails at all of this. I hope 1.0 is at least fixing some of it?
