reply on: Searching on Stacker.news and ordering by "recent" - results are not in order \ stacker news ~meta

pull down to refresh

68 sats \ 4 replies \ @k00b 4 Aug \ on: Searching on Stacker.news and ordering by "recent" - results are not in order meta

It's a gaussian notion of recent - meaning it's biases toward more recent content but is not ordered strictly.

We did this because it's hard to maintain relevance and recency simultaneously. I'll create a github issue if we don't have one.

In the meantime clamping it by time, e.g. 1 week should help.

133 sats \ 2 replies \ @SimpleStacker 4 Aug

This issue has come up a number of times now and makes it clear that user expectations for recent is that it'll be a strict recency sort order.

I wonder if recent searches should be keyword only, sorting all keyword matches strictly by date.

I vaguely remember that being the case before, but there was some other bug that made it too restrict thus often returning null results.

0 sats \ 0 replies \ @0xbitcoiner 4 Aug

Yeah, I’d noticed this was happening before. I think your solution’s the best one. One rule in software is: don’t do stuff the user didn’t ask for.

0 sats \ 0 replies \ @k00b 4 Aug

Your memory matches mine. In cases where there are otherwise no results, people want recent to be less strict. When there are many results, people want recent to be strict.

100 sats \ 0 replies \ @final 5 Aug

I am for having that stricter search from the past. Makes searching a post about a certain thing on a common word harder for me. Also made me take extra steps when I need to do help/support replies about GrapheneOS as I didn't always see who was discussing at first.