Deprecating minimum and maximum score

@byte[]  
Alright, thanks. ^^

…So is this why I’ve only been able to access the site on my phone for more than 12 hours? On my laptop I’m still getting the “down for updates” message.

@Jarkes  
What pages are you getting the downtime message on?

@byte[]
 
The homepage. But I can’t exactly get to other pages without that.

@Jarkes  
If you type in the URLs to other pages, does it work?

@byte[]
 
Just tried, and other pages are fine.

@Jarkes  
Okay. Does it work in incognito / private browsing mode?

@byte[]
 
Just cleared my cache, and it’s fine now.

Can we at least still use them in search? I don’t want to have to switch between filters all the time when I’m searching.

@Aponty  
Of course. Example

@Princess Luna  

 
Right, so that’s why I sometimes had less pics than tag number with “Everything” showed me! I thought it was some bug with removed duplicates which still technically existed somewhere.  
Great thanks about that change!
 
Wait, did you reset the counter? I sure remember setting it >0 (5 or 10, not sure), but it’s showing 0 now.  
Also I have like 10 included (my:hidden) || my:hidden-s in the complex filter, is that something automatically generated? I have 1500 tags hidden, it seems. 111 tags on other filter has 4 my:hidden-s.

@JuneII  
Our counters are notoriously inaccurate. The only one I’m aware of that doesn’t regularly drift is your notifications counter, and that is only because I have put in special constraints in the database to enforce this.

Is there any interest in keeping the score constraint page, and turning it into either a “how-to” that lets a user plug in a complicated query with a bunch of booleans or similar and then shows how to apply the score to the entire query, or just passing the current query into it, putting the scores where they need to go in the query, and then going back to the search? There are probably at least a few users who don’t fully understand how to integrate this into a complex search with bool settings etc. and this would make a good transition.

@byte[]  

 
This seems explained backwards to me.  
If you have a maximum score of 500, you are only searching for images up to 500, so you should use score.lte:500  
If you have a minimum score of 25, you are only searching for images greater then 25, so you would use score.gte:25

@nirvash  
The filter hides things you enter into it. It’s not your watch list.

Never mentioned watch lists, but I see my misunderstand standing. So rarely use filters wasn’t clicking the that field was triggering the filter action to spoiler/hide.

@cheezedoodle  
I understand the confusion as comments swap between search and filters.

So, while we are talking about search stuff, let me ask: is there any way to have OR operator in search bar? AND and NOT are common and obvious.

@JuneII  
It’s literally OR
 
twilight sparkle OR rainbow dash

|| also works as OR, same as && for AND and ! for NOT

@JuneII  
If you click the question mark next to the search box, you’ll see what the search engine is capable of.
 
In addition to everything there, there are some additional features the search parser supports that are not mentioned on the syntax page.
 
Extra Terms  
my:upvotes, my:downvotes, my:faves - should be self-explanatory  
my:hidden - searches for images you have explicitly clicked “Hide” on; you will need to disable image hiding to see these images
 
Relative Dates  
created_at.gt:1 year ago - Images posted later than one year ago  
created_at.lte:2 months ago - Images posted two months ago or earlier  
created_at:3 weeks ago - Images posted three weeks ago (precision 1 week)  
created_at.lt:4 days ago - Images posted earlier than four days ago  
created_at.gte:5 hours ago - Images posted five hours ago or later  
created_at:6 minutes ago - Images posted six minutes ago (precision 1 minute)  
created_at.lte:7 seconds ago - Images posted seven seconds ago or earlier

I have a small usability proposal. Would be nice to add human-readable aliases. I.e.:
 
score.gt - scoremin  
score.lt - scoremax
 
Seriously, would be way less confusing.

@DarthBarf  
The problem is really more annoying than that, it’s that filters are backwards (they remove things from a search, instead of adding them). “Score greater than/score less than” abbreviated as “lt/gt” is not something often confused once grasped.

On a similar note to this, although we can sort images via Wilson score, I haven’t been able to find any way to filter image searches with it. Is this possible or planned at all?